On Thu, Oct 21, 1999 at 03:13:22PM -0700, Brian Lavender wrote:
> As I understand, Debian slink comes with MD5 crypt because of export
> restrictions. 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
I figured out that the above just drops everything in /usr/local/
so that's not quite what I was looking for. I discovered that
$ ./configure --enable-add-ons=crypt,linuxthreads --prefix=/usr
would cause it to replace my original glibc. I am still wondering
about the linuxthreads, so if anyone has comments about that, I am
certainly interested.
I compiled it on a test machine, which worked, so now I am wondering
how do I verify that crypt uses the real crypt and not the MD5 crypt?
brian
>
> 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/
-- Brian Lavender http://www.brie.com/brian/
This archive was generated by hypermail 2b29 : Fri Feb 11 2000 - 16:20:20 PST