Red Hat Bugzilla – Bug 209929
insecure password and config files permissions
Last modified: 2007-11-30 17:11:45 EST
Description of problem:
The ss5 password file (ss5.passwd) and the config file (ss5.conf) is installed
with mode 0644, e.g. readable by everyone.
The password file contains clear text passwords.
The config file can contain ldap passwords.
Version-Release number of selected component (if applicable):
Any version ever released for Fedora Extras.
Extract from the .spec file:
These files should be readable only by the ss5 daemon which runs under the root
account, e.g. they should be mode 0640 or more securely mode 0600.
Maybe the SELinux rules could enhance it even more.
I changed spec.file with 0640 mode and made a rebuild for Devel (FC-6).
Tell me if is ok and if I have to do it also for old dist (FC-4/5)
(In reply to comment #1)
Yes, it is definitely better.
I think that this change should be reflected in all builds. It enhances the
daemon files protection.
Maybe you could also check permissions in the application and log week permissions.
I am currently trying to make the selinux module for ss5. Tell me if you are
interrested. Use my address directly.
OK, I'm going to fix also FC4/5
About SELinux, it could be very interesting, even if ss5 should works also for
Solaris and FreeBSD.
(In reply to comment #4)
The SELinux does not mean changes to the application. It defines the rules,
limits and borders under which the application runs. (Ex.: it can read and write
to/from certain log file but it cannot read other files. You can imagine
something like chroot.)
The source and other ports will remain unchanged.
The SELinux module can be used by anyone trying to protect ss5 under SELinux. If
Solaris or FeeeBSD uses SELinux, it can use the module as well.
Look at pure_ftpd in Extras.
Close this bug, it is solved.
I hope that one and only response will suffice. :)