Hi,
Thanks for using mini-httpd !
Indeed, not logging CGI has security implications, for sure. However,
the version of mini-httpd in buster/bullseye has a LOAD of other issues
as well (multihosting bugs, a buffer overflow I believe, no systemd
service, etc).
That version predates me as a maintainer of this package.
If I were to release a backport of mini-httpd to stable and/or
oldstable, I would have to port all new patches and retest, since it
would be of little help to create a whole release just for CGI logging. Sadly, I currently lack the manpower for this.
I have to ask, is there any reason at all for you to not just use the
current testing (12) release on stable/oldstable ? You would get lots
of other benefits in addition to fixing your CGI issue (systemd with hardening, better logging in general, etc) That's what I already do in production with my setup. As Salvo said, this is not RC for trixie as
these changes are already applied in time for the trixie freeze.
I'll close this in a few days if nothing happens
Have a good one,
Alexandru
Therefore, I recommend the source route and I'll give you all
instructions, works on a fresh stable VM. Hope this solves your issue
Lloyd :D (until perhaps you update to trixie when it comes out)
P.S: Please rush to change bug severity to normal
(Perhaps if you have a bit of time you can help me
confirm his problem too granted you're also on stable
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 483 |
Nodes: | 16 (2 / 14) |
Uptime: | 84:24:20 |
Calls: | 9,576 |
Calls today: | 7 |
Files: | 13,666 |
Messages: | 6,143,357 |
Posted today: | 2 |