On Fri, 18 Feb 2022 22:46:09 +0000 =?UTF-8?Q?Cormac_MacGiolla=C3=89ain?=
<[email protected]> wrote:
Hi Hillmar
I tested it on two different systems, with new Proftpd installations, i.e.
no existing proftpd.conf to overwrite.
I noticed it in the version in the stable release, then purged it,
installed the version in testing, same issue; purged that, installed the
version in unstable and it also appears there.
Regards
Cormac
Just tested it with proftpd v1.3.8+dfsg-2 and the bug is still there.
On a fresh docker image of Debian bookworm-slim I installed proftpd.
A grep shows a good uncommented Umask statement and a bad commented
Umask. As far as I understand this bug report, the commented Umask is
that Cormac is talking about.
root@51b918657f51:/# grep -i umask /etc/proftpd/proftpd.conf
# Umask 022 is a good standard umask to prevent new files and dirs
Umask 022 022
# # # Umask 022 is a good standard umask to prevent new files and dirs
# # Umask022 022
