On Fri, Feb 04, 2000 at 03:11:57PM +0200, Mark Murray wrote:
>
> You want to work on PAM's, go ahead!
I had time for this then, but not now. :-(
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> On Thu, Feb 03, 2000 at 10:09:22AM -0800, Kris Kennaway wrote:
> > a proper fix might be to add a login class which determines which of
> > MD5 and DES you should use for new passwords
>
> I believe PAM is the more "approved" way to implement this
> functionality. Before PAM it would be /etc/a
> > AFAIK this has always been the way it works: if you install libdescrypt,
> > the system makes the (mistaken) assumption you want DES passwords all the
> > time.
>
> This is true for the initial installation. However, `make world' used to
> respect the an existing symlink. src/secure/lib/lib
On Thu, Feb 03, 2000 at 10:09:22AM -0800, Kris Kennaway wrote:
> a proper fix might be to add a login class which determines which of
> MD5 and DES you should use for new passwords
I believe PAM is the more "approved" way to implement this
functionality. Before PAM it would be /etc/auth.conf.
I
On Thu, Feb 03, 2000 at 10:09:22AM -0800, Kris Kennaway wrote:
> AFAIK this has always been the way it works: if you install libdescrypt,
> the system makes the (mistaken) assumption you want DES passwords all the
> time.
This is true for the initial installation. However, `make world' used to
r
In article <[EMAIL PROTECTED]>,
Kris Kennaway <[EMAIL PROTECTED]> wrote:
> On Thu, 3 Feb 2000, Anders Andersson wrote:
>
> > I add a new user, and with 'vipw' I notices that this user now gets a
> > DES based passwd. (we only use MD5 passwords around). Then I looked in
> > /usr/lib and noticed t
On Thu, 3 Feb 2000, Anders Andersson wrote:
> I add a new user, and with 'vipw' I notices that this user now gets a
> DES based passwd. (we only use MD5 passwords around). Then I looked in
> /usr/lib and noticed that libcrypt now is symlinked to libdescrypt:
AFAIK this has always been the way it
Long time ago I used the crypto code on cvsup.internat.freebsd.org and
all was nice.
Now I need to use crypto from internat to be able to use OpenSSH. I have
to have openssl in my base system otherwise I cannot use the port.
So, on my -current box I cvsup both todays -current source and the
cryp
