fortify/internal
Ophestra 6d4ac3d9fd
All checks were successful
Test / Create distribution (push) Successful in 26s
Test / Fortify (push) Successful in 2m33s
Test / Data race detector (push) Successful in 3m20s
Test / Flake checks (push) Successful in 42s
internal: store fortify path in internal
This now makes more sense due to the changes in build system.

Signed-off-by: Ophestra <cat@gensokyo.uk>
2025-02-26 12:03:25 +09:00
..
app dbus: set process group id 2025-02-25 18:12:41 +09:00
fmsg fmsg: PrintBaseError skip empty message 2025-02-18 17:01:26 +09:00
state fmsg: implement suspend in writer 2025-02-16 18:51:53 +09:00
sys app: separate interface from implementation 2025-02-18 23:07:28 +09:00
comp.go cmd: shim and init into separate binaries 2024-11-02 03:13:57 +09:00
executable.go internal: beforeExit before reachable fatal calls 2025-02-16 19:03:34 +09:00
exit.go fmsg: implement suspend in writer 2025-02-16 18:51:53 +09:00
path.go internal: store fortify path in internal 2025-02-26 12:03:25 +09:00
prctl.go internal: do PR_SET_PDEATHSIG once 2025-01-17 23:08:46 +09:00
sysconf.go app: check username length against LOGIN_NAME_MAX 2025-02-14 12:44:55 +09:00