Steve Langasek wrote:
Create text file logins.txt like
===cut===
username1
username2
password2
===cut===
then run
db3_load -T -t hash -f logins.txt /etc/vsftpd_login.db
User "username1" will have empty password.
I've done this, and I'm still unable to authenticate a user with an empty
password using pam_userdb 0.67-23.
Please try use exactly these options:
# cat /etc/pam.d/vsftpd
auth required /lib/security/pam_userdb.so db=/etc/vsftpd_login debug dump
account required /lib/security/pam_userdb.so db=/etc/vsftpd_login
Done, and I still get these results in /var/log/auth.log:
Oct 1 16:23:20 minbar pam_userdb[21111]: Verify user `vorlon' with password `'
Oct 1 16:23:20 minbar pam_userdb[21111]: Database dump:
Oct 1 16:23:20 minbar pam_userdb[21111]: key[len=6] = [EMAIL PROTECTED]',
data[len=0] = `(null)'
Oct 1 16:23:20 minbar pam_userdb[21111]: password in database is
[(nil)]`(null)', len is 0
Oct 1 16:23:20 minbar pam_userdb[21111]: error returned by dbm_fetch: No such
file or directory
Oct 1 16:23:20 minbar pam_userdb[21111]: user `vorlon' not found in the
database
Sorry, I just don't see how this ever worked with pam_userdb; if you had
this working before, I don't think it was pam_userdb 0.76-23 that was
authenticating these users. Both a look at the code, and my tests with
pam_userdb, support this conclusion.
Steve,
I've found that if user with empty password is *the only* user in
vsftpd_login.db then it is *not* authenticated by either version.
Please create at least two users (with logins.txt shown above): first with
empty password, second with non-empty password.
Then the first user will be well authenticated with libpam-modules 0.76-23 but
not with 0.79-*.
I believe that is some sort of bug in libpam-modules.
Thanks,
Max
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
