hi, there!
On Thu, 23 Nov 2000, Chris Knight wrote:
> > NODESCRYPTLINKS was always intended as a temporary workaround. The
> > solution is to use passwd_format=des in your default login class.
> >
> It's a solution for login. It's not a solution for any application that
> dynamically links to li
Kris Kennaway wrote:
>
> On Tue, Nov 21, 2000 at 03:32:49PM -0800, David O'Brien wrote:
> > On Tue, Nov 21, 2000 at 08:27:50AM -0800, Kris Kennaway wrote:
> > > No longer correct. You don't need to futz with libraries and symlinks
> > > any more,
> >
> > Shouldn't we remove "NODESCRYPTLINKS" from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 21 Nov 2000, Nevermind wrote:
...
: And if I wanna manage both -- DES & MD5? For example I have about 200
: users on one machine and I have no physical ability to make them
: change their passwords. It seems to me it worked fine somewhere
: be
Hello, Matt Heckaman!
On Tue, Nov 21, 2000 at 07:09:57AM -0500, you wrote:
> FreeBSD has actually defaulted to MD5 passwords for quite a long time to
> those of us not within the US. However, installing the US crypto has
> always forced the usage of DES passwords by default. In order to switch
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 21 Nov 2000, Nevermind wrote:
...
: The same thing...
: Mabe the point is in DES/md5 passwords?
FreeBSD has actually defaulted to MD5 passwords for quite a long time to
those of us not within the US. However, installing the US crypto has
alwa
Hello, Chris Byrnes!
On Mon, Nov 20, 2000 at 06:33:21PM -0600, you wrote:
> I recently went 4.1.1-stable to 4.2-release and now lots of
> passwords...don't work.
> Any ideas?
The same thing...
Mabe the point is in DES/md5 passwords?
--
Alexandr P. Kovalenko http://nevermind.kiev.ua/
NEVE-RIP