Hello Steve, Versions: pam: 0.72 pop3 server: spop3d So for usernames over 13 characters: spop against shadow passwords WORKS spop against shadow passwords (via PAM) DOES NOT WORK proftp against shadow WORKS proftp against shadow (via PAM) DOES NOT WORK I am pretty confident that PAM is the problem. Is there anyway to increase logging for PAM? When PAM fails it fails abruptly, saying connection closed, it doesn't return any helpful messages. It may be meer coincidence but 13 can also be a crypted string. I appreciate your help. Thanks Chris -----Original Message----- From: pam-list-admin@redhat.com [mailto:pam-list-admin@redhat.com]On Behalf Of Steve Langasek Sent: Sunday, 29 April 2001 10:11 AM To: pam-list@redhat.com Subject: Re: username above 13 characters not accepted Hi Chris, On Sat, 28 Apr 2001, Chris Siakos wrote: > Hello, > I am using pam_mysql to authenticate pop users against a mysql database. > All works well until I enter a username longer than 13 characters. I spoke > to the authors of pam_mysql and they are puzzled as the length of the > username is returned by pam itself and not the module. I also authenticated > against the system pass account via pam, and that also failed (for long > usernames). > Pointing to a pam problem rather than pam_mysql. > Any ideas will be greatly appreciated. I am using PAM on a Linux SuSE 7.0 > distribution. What version of PAM does SuSE include, and what POP server are you using? I've just tested with a 16-character username, and I'm afraid I'm not able to reproduce this problem on a RedHat 6.1 machine (pam 0.72) using pam_unix and the 'su' command. Steve Langasek postmodern programmer
