Commits
- Commit:
67c49bc5c794c4375344ea010be608572d6f0070
- From:
- Omar Polo <op@omarpolo.com>
- Date:
mention landlock in the README
- Commit:
3499ce5a9ac180a805d8e507207accf8ea352f48
- From:
- Omar Polo <op@omarpolo.com>
- Date:
landlock the server process
Trying to implement some landlock policies (rules?) where possible.
The server process is, of course, the most dangerous process so start
with that.
The following should be equivalent to the unveil(2) call on OpenBSD:
allows only to read files and directories inside the vhost roots.
I'm assuming seccomp is enabled so I'm not trying to disallow actions
such as LANDLOCK_ACCESS_FS_EXECUTE or LANDLOCK_ACCESS_FS_REMOVE_FILE
which require syscalls that are already disallowed. I'm only trying
to limit the damage that the currently allowed system calls can do.
e.g. since write(2) is allowed, gmid could modify *any* file it has
access to; this is now forbidden by landlock.
There are still too many #ifdefs for my tastes, but it's still better
than the seccomp code.
- Commit:
d85aa60208bc38ff99fb170559188d5ec9545e04
- From:
- Omar Polo <op@omarpolo.com>
- Date:
define HAVE_LANDLOCK accordingly
- Commit:
4c31de2915cd2ef3e7d5463bde48cf9064c89d20
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add configure check and shim for landlock
First move towards landlock support (#3). The shim is needed until
libc provides the proper wrappers for the landlock APIs; I hope it
doesn't take too long, but landlock was merged back in May and are
still missing.
- Commit:
fba809b5c775fd4d3c28a012259ee3b1908d4e40
- From:
- Omar Polo <op@omarpolo.com>
- Date:
tag 1.7.3
bump version number
- Commit:
ca3d8bfde617a2be55fda5f25faf071f40325f6f
- From:
- Omar Polo <op@omarpolo.com>
- Date:
retroactively mention the fstat64 fix
- Commit:
39c5bfd64bb020a6e8a17c2a5e96efa02ba85fcc
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix changelog syntax
- Commit:
e30e5385f15dec8279c1ece2eb6cb6691b5d6d63
- From:
- Omar Polo <op@omarpolo.com>
- Date:
sort tests
- Commit:
b03b7d5baee99ec806081e6658db3edb7a9ed698
- From:
- Omar Polo <op@omarpolo.com>
- Date:
sync changelog
- Commit:
db623d7551caaed88664d4e7c379b231f89c6ca4
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix syslog logging on FreeBSD
Due to capsicum(4), opening the log on-demand via syslog(3) fails.
openlog(LOG_NDELAY) forces the log to be opened immediately, before we
enter capsicum.
This doesn't affect OpenBSD (where pledge(2) doesn't stop syslog) nor
linux (where the log process is not sandboxed.)
Reported by Karl Jeacle, thank you!
- Commit:
f2478b332f0f60a53113cdc6434f134c34a2155c
- From:
- Omar Polo <op@omarpolo.com>
- Date:
sync
- Commit:
2e319276065bb4564aaa5d4990e058c3d8a6e95f
- From:
- Omar Polo <op@omarpolo.com>
- Date:
don't crash if -n is given without -c
If -n is given without -c, config_path is still NULL and it would
crash due to a NULL deference.
- Commit:
83272dfee9eb5292ce21de55ebdbb3876a37fcb1
- From:
- Omar Polo <op@omarpolo.com>
- Date:
don't yyerror if we can't open the file
the global var file could still be NULL and yyerror would crash.
- Commit:
ef352ec3b87210945429d033625bbfb06de4d7c4
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix wrong arguments order for send_log
- Commit:
03747a6c5101855b4d9db42f27e696f26ba2484d
- From:
- Omar Polo <op@omarpolo.com>
- Date:
sync