I had some problems with authenication on my computer after update (I
am running testing). Now authenication works fine, but cyrus
authenication doesn't work correctly.
If I am tring to test:
# testsaslauthd -u vadim -p xx
0: OK "Success."
but
# imtest -u vadim -w xx localhost
S: * OK kutsyy.c
coping these files from /var/backups to /etc/ fixed the problem.
Thanks,
PS: I still have no idea what happened, and somehow cyrus authenication
is brocken.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
comparing to backup, /etc/shadow change for a few users (I made the
change). /etc/passwd did chance, It is empty.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Tue, Dec 20, 2005 at 04:57:23PM -0800, Vadim wrote:
> I updated my box today morning (I am using testing), and I lost my
> authenications. Seems like PAm is not using shadow passwords. My
> common-password contains only one live (default):
>
> password requiredpam_unix.so nul
I updated my box today morning (I am using testing), and I lost myauthenications. Seems like PAm is not using shadow passwords. Mycommon-password contains only one live (default):passwordrequiredpam_unix.so nullok obscure min=4 max=8 md5
Are there any other parameters which co
I updated my box today morning (I am using testing), and I lost myauthenications. Seems like PAm is not using shadow passwords. Mycommon-password contains only one live (default):
password required pam_unix.so nullok obscure min=4 max=8 md5Are there any other parameters which could contribute to
6 matches
Mail list logo