Mailinglist Archive: opensuse-security (685 mails)

< Previous Next >
PAM-Entry for Yast2 (was long passwords)
  • From: Michael Zimmermann <zim@xxxxxxxx>
  • Date: Wed, 27 Feb 2002 08:45:30 +0100
  • Message-id: <20020227074551.48F19477F@xxxxxxxxxxxxx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

At Dienstag, 26. Februar 2002 22:15 michael stone wrote:
> I found the problem, I did not have a md5 password. I had
> changed my password with Yast2, but it does not store the password as md5.

Is there a way to tell Yast2 to generate md5-passwords?
After adding 'md5' to the password-entry in /etc/pam.d/password
I found that yast2 is generating md5-look-alike passwords,
but is using only a two-char seed as apposed to the usual 8-char
seed when using /usr/bin/passwd. So somehow yast2 might
be looking at /etc/pam.d/passwd, but is not implementing
the full PAM-md5 method to generate the passwords (i.e.
yast2 seems to use only the usual crypt-seed of 2 characters long).

Perhaps it might be an idea to have yast2 use full PAM support
with it's own PAM-parameter-file like /etc/pam.s/yast2 ?

Greetings
Michael
- --
Michael Zimmermann (Vegaa Internet Services)
<zim@xxxxxxxx> phone +49 89 6283 7632 hotline +49 163 823 1195
Key fingerprint = 1E47 7B99 A9D3 698D 7E35 9BB5 EF6B EEDB 696D 5811
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8fI6q72vu22ltWBERAqF3AJwPU9I46ScVQBBEiEZ8tmn8akh5kQCeIsUZ
Sv2ztAj1kUhbThkKfmIpcz0=
=G+88
-----END PGP SIGNATURE-----

< Previous Next >
Follow Ups
References