summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/rangehttpserver
diff options
context:
space:
mode:
authorIndeedNotJames <git@indeednotjames.com>2023-03-01 23:44:21 +0100
committerIndeedNotJames <git@indeednotjames.com>2023-03-01 23:44:21 +0100
commit249f6c4c1df410ee339a8136416092fdcc0b16c2 (patch)
treead6dad28f94ba92ddc926ebdf644b30c8284add2 /pkgs/development/python-modules/rangehttpserver
parent29211dc4b4b67d30a18f2e3f315d5a8f18129e62 (diff)
nixos/tests/gitea: test gpg commit signing key
`/api/v1/signing-key.gpg` spawns a `gpg` process, which is great to test if `gpg` is available and can be invoked from in the unit. Which is somewhat relevant, since `gpg` was missing from the unit's `$PATH` until recently. And even after adding `gpg` to the unit's `$PATH`, configuring commit signing for a instance resulted in http/500s nonetheless. That's due to `@memlock` being present in `SystemCallFilter=~` and `gpg` trying to use `mlock` (probably to prevent secrets in the memory to swap), resulting in an immediate `SIGKILL` of any spawned `gpg` processes.
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions