we actually should open the log file in the chroot, the bug is in
the code.
This commit is contained in:
Omar Polo 2024-03-03 15:42:06 +00:00
parent 9f1cce3d0e
commit 0ed763b03d
1 changed files with 6 additions and 7 deletions

View File

@ -11,7 +11,7 @@
.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
.Dd March 3, 2024
.Dd January 11, 2024
.Dt GMID.CONF 5
.Os
.Sh NAME
@ -121,13 +121,12 @@ the process to the given
The daemon has to be run with root privileges and thus the option
.Ic user
needs to be provided too, so privileges can be dropped afterwards.
If enabled all the paths in the configuration file are relative to the
chroot directory, except for the
All the paths in the configuration file are relative to the chroot
directory, except for the
.Ic cert ,
.Ic key ,
.Ic ocsp
.Ic key
and
.Ic log access
.Ic ocsp
paths.
Defaults to the
.Ic user
@ -140,7 +139,7 @@ The available options are as follows:
.It Ic access Ar file
Log the requests to
.Ar file .
The path is not relative to the
The path is relative to the
.Ic chroot .
.It Ic style Ar style
Set the logging style, defaults to