>>>>> Evan Leibovitch writes:
Evan> On 22 Aug 1999, Andreas Jaeger wrote:
>> For Linux you should differentiate on the used C library. RedHat 4.2
>> for example uses libc5. With glibc 2 [1] you have to include
>> <crypt.h> and add -lcrypt. glibc 2.x.y is used in AFAIK all current
>> Linux distributions (Suse 6.0 and newer, RedHat 5.0 and newer, Debian
>> 2.0,...).
Evan> Caldera 2.2, which otherwise uses glibc2.1, doesn't include libcrypt by
Evan> default. Caldera's legal advice indicates that libcrypt cannot be legally
Evan> exported from the US.
It's a long time ago that I've compiled glibc without the crypt
add-on. But looking at the code again, even without the crypt add-on,
you get a libcrypt and a crypt call - it just uses a different
algorithm (see md5-crypt/* and sysdeps/generic/crypt* in the glibc
2.1.x sources) that doesn't have US export control problems. If
Caldera comes without any libcrypt, they've broken glibc support[1].
Evan> Apparently the other distributions are just hoping that nobody will
Evan> notice.
:-)
Evan> Caldera's support website indicates where to get libcrypt from outside the
Evan> US, but it's not shipped on the CD by default.
If you're running Caldera without this libcrypt, please check what
they're doing.
Andreas
Footnotes:
[1] I do think we generate always a libcrypt but would have to double
check it.
--
Andreas Jaeger aj@??? jaeger@???
for pgp-key finger ajaeger@???
