Johnathan Corgan 682d7be69a Write the Windows service log to a rolling file ...

A process started by the service control manager has no standard
handles, and writes to its absent stdout report success, so everything
the daemon logged in service mode was lost. So were config-load
failures, the service's own error report and panic messages, which all
went to stderr.

In service mode the daemon now logs to C:\ProgramData\fips\fips.log.
The file is rolled at 10 MiB with four old files kept, so it takes at
most about 50 MiB. A roll that fails, for example because another
process holds the file, keeps writing to the current file and is not
retried until another 10 MiB have been written. Config-load failures,
the service error and panic messages go to the same file. A foreground
run still logs to the console, and --install-service names the log
file.

The writer is built in rather than taken from a crate, so it is tested
on every platform and adds no dependency.

The Windows ZIP's README and the fips reference now say where the
service log goes, and install-service.ps1 prints the log path.

2026-09-24 23:12:45 +00:00

..

index.rs

Update dependencies: rand 0.10, rtnetlink 0.20, tun 0.8, and others

2026-02-24 18:02:06 +00:00

logfile.rs

Write the Windows service log to a rolling file

2026-09-24 23:12:45 +00:00

mod.rs

Write the Windows service log to a rolling file

2026-09-24 23:12:45 +00:00

sockbind.rs

Merge maint into master, carrying the twenty-one security fixes

2026-08-23 15:49:39 +01:00

sockperm.rs

Create the control socket and its directory with a restrictive mode

2026-08-23 11:45:30 +01:00