security/fortify
2
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 37 Wiki Activity
fortify/internal
History
Ophestra 3ae2ab652e
All checks were successful
Test / Create distribution (push) Successful in 24s
Details
Test / Run NixOS test (push) Successful in 3m14s
Details
system/wayland: sync file at caller specified address 
Storing this in sys is incredibly ugly: sys should be stateless and Ops must keep track of their state.

Signed-off-by: Ophestra <cat@gensokyo.uk>
2025-02-17 13:24:17 +09:00
..
app
system/wayland: sync file at caller specified address
2025-02-17 13:24:17 +09:00
fmsg
fmsg: implement suspend in writer
2025-02-16 18:51:53 +09:00
linux
internal: beforeExit before reachable fatal calls
2025-02-16 19:03:34 +09:00
state
fmsg: implement suspend in writer
2025-02-16 18:51:53 +09:00
system
system/wayland: sync file at caller specified address
2025-02-17 13:24:17 +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
proc: remove duplicate compile-time fortify reference
2025-01-18 11:59:33 +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