Commits
- Commit:
359c56ce35111808ad8ccb48c32ff2d4f5a30a3d
- From:
- Omar Polo <op@omarpolo.com>
- Date:
contrib/gmid.service: remove User and Group
May cause weird errors (status=216/GROUP) on some distros, and
running as root is already the default, so remove the two lines.
Reported by and debugged together with leandro del Flug, thanks!
- Commit:
c2dcb5fa6ea5ca08f1f40ddcb07211a11450d648
- From:
- Omar Polo <op@omarpolo.com>
- Date:
contrib/gmid.service: start as root by default
Various techniques used by gmid are effective only when the daemon
is started as root. Strongly suggest to do so by switching the
sample configuration. This way, provided that a local user is
created as well, the chroot configuration will work out-of-the-box
and the TLS certificates can be readable only by root.
- Commit:
5d12e6a1047b1ddafb01fd3014fbb6c97d06b0a4
- From:
- Omar Polo <op@omarpolo.com>
- Date:
improve the description for -f
- Commit:
0d8eb9b60cd4dcc17a6d9ba1c71092c52c2110e7
- From:
- Omar Polo <op@omarpolo.com>
- Date:
typo: semicolors -> semicolons
- Commit:
5864f3ce3cf1a25f652bf0194372d3fbd8098d9a
- From:
- Omar Polo <op@omarpolo.com>
- Date:
set next version
- Commit:
9536c8ca63fe03d66068c1b391c71dd8afc02044
- From:
- Omar Polo <op@omarpolo.com>
- Date:
prepare release 2.0.1
- Commit:
40b71b6861fc7ddbe8ee66a7a3c6b253912e0c5f
- From:
- Omar Polo <op@omarpolo.com>
- Date:
changelog for 2.0.2
- Commit:
42235e3fc2853ac5c1b0fa355c1dda45d558ee11
- From:
- Omar Polo <op@omarpolo.com>
- Date:
add a test for the config dumping
- Commit:
f53f5e5fe13af9ae5b55eda34635e61a5c11b538
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix config dumping (-nn) handling
with the privsep rework the config dumping was unadvertitely broken,
it prints the content of the key itself.
- Commit:
40ea7b163e15d70788aa7a8189f9000109a7b931
- From:
- Omar Polo <op@omarpolo.com>
- Date:
use -Werror=implicit-function-declaration for function detection
the previous -Werror triggers too easily: on NixOS for example the
FORTIFY_SOURCE #warning about a missing optimization level breaks all
the checks when using -O0 (which is the default for non-release builds).
- Commit:
be265175c65f1b5425e294b06874e87aa900bde1
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix landlock test
include stddef.h for size_t
- Commit:
8aba5d8b210a17b49cfc8f02b12fd7b62c228fb3
- From:
- Omar Polo <op@omarpolo.com>
- Date:
remove dead code
- Commit:
7c83689428d30bf646bea610ca4ee04aded74024
- From:
- Omar Polo <op@omarpolo.com>
- Date:
update mac CI target to sonoma
- Commit:
248fb833f9883b714c48cd3edac2b212cbcd565f
- From:
- Omar Polo <op@omarpolo.com>
- Date:
fix `log access path' with chroot
We should open the log file inside the chroot; missed in
4acf495f41d2c26136e99072293ca8b9bff91dc0.
See https://github.com/omar-polo/gmid/issues/24
- Commit:
0ed763b03d653afcd34eac9a0802303c21c4fd1d
- From:
- Omar Polo <op@omarpolo.com>
- Date:
revert 9f1cce3d0e53209180eabbcd48878c1e989101e7
we actually should open the log file in the chroot, the bug is in
the code.