On Thu, 21 Oct 1999, Brian Lavender wrote:
> As I understand, Debian slink comes with MD5 crypt because of export
> restrictions.
To respond to this part of the message, MD5 os way more secure than DES.
It looks like a lot of systems are moving to MD5. Heck, cisco has been
using it for years. I would reccomend using it instead of DES. I have a
crypt library that will detect if the pass was crypted using MD5 or DES
and authenticate someone based on that if you want it. I also modified
the MD5 perl module to be able to generate MD5 shadow entries which is
useful for password changeing programs in perl.
I want to have a real crypt so I went to a german ftp
> server, found glibc 2.0.7 source and I downloaded it. Of course the real
> crypt is in a separate tar file. I downloaded that too and unpacked it
> in the glibc source tree I read the faq as far as compiling glibc and
> it said to do a configure like
>
> ./configure --enable-add-ons=crypt,linuxthreads
>
> What I am wondering is, is glibc on slink compiled in with linux threads? It
> seems as if there are issues either way and that I probably ought to
> go with it if it was compiled in originally.
>
> I am supposing that I can do the above configure and the following steps, and I should have glibc with crypt
>
> make
> su
> make install
>
> Here is the ftp site where I got crypt for glibc.
>
> ftp://ftp.gwdg.de/pub/linux/glibc/2.0.7pre6
>
> brian
> --
> Brian Lavender
> http://www.brie.com/brian/
>
Mike Machado
mike@innercite.com
InnerCite
Network Specialist
This archive was generated by hypermail 2b29 : Fri Feb 11 2000 - 16:20:20 PST