Tag Info

New answers tagged


First of all, chroot is not a security feature. Arguably, what you need to implement is a reproducible, auditable method of limiting the ability of the user to perform actions other than the strictly allowed. If you register your users in LDAP, surely you have already deployed the mechanisms to perform LDAP authentication on any machine connected to this ...


PAM is telling you that it is configured with "retry=3" and it will ignore any further auth requests from sshd within the same session. SSH however will continue trying until it exhausts MaxAuthTries setting (which defaults to 6). You should probably set both of these (SSH and PAM) to same value for maximum auth retries. Updated To change this behaviour: ...


It had something to do with this, but I don't understand why. service auth-worker { user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { mode = 0660 user = postfix } }


It would be very hard to use RADIUS without using PAM. PAM defines an API for accessing credentials providers (and other session related stuff) which can be the usual files, NIS, LDAP, RADIUS.... The bit you're talking about changing is the credentials provider. There are places that PAM can't go - and to handle these cases it might be worth looking at ...


I recently had an issue which was solved here: http://download.pureftpd.org/pure-ftpd/doc/FAQ Not enough questions link to the answers in the FAQ. To log in, the shell assigned to your users must be listed in the /etc/shells file


Ok so my suggestion is use pam-mysql which accepts these formats of password encription

Top 50 recent answers are included