miniroon

commit 70fc3ed776441da3b905f91d1aea7479f3e7953b
parent 4cfdbae176d84e4243c77b463dd14f69f567edb0
Author: Jan Pobrislo <ccx@te2000.cz>
Date:   Sat, 15 Feb 2025 23:15:28 +0000

Provide verify file example

Diffstat:
M
README
 | 
5
+++++

1 file changed, 5 insertions(+), 0 deletions(-)
diff --git a/README b/README
@@ -61,6 +61,11 @@ The `verify` file is supposed to set up environment variables that may be change
 execute `miniroon-verify` with the same arguments it got.
 Similarly to `s6-sudod` only the environment variables which are present but empty can
 be changed by the provided miniroon.
+Commonly the verify file would look something like:
+
+    #!/bin/sh
+    exec env var1= var2= var3= miniroon-verify "$@"
+
 The `miniroon-verify` program then does the actual verification of full miniroon
 including the provided signature verifying each part of miniroon starting with the
 content of the `secret` file in the rundir.