The functions are available, as an add-on (see ?addon). People in the US
may get it from the same place they got GNU libc from. People outside the
-US should get the code from ftp.funet.fi [128.214.248.6] in the directory
-pub/gnu/funet, or another archive site outside the USA. The README explains
+US should get the code from ftp.gwdg.de [134.76.11.100] in the directory
+pub/linux/glibc, or another archive site outside the USA. The README explains
how to install the sources.
If you already have the crypt code on your system the reason for the failure
unpack the crypt distribution along with the rest of the C library and
build; you can also build the library without getting crypt. Users
outside the USA can get the crypt distribution via anonymous FTP from
-ftp.funet.fi [128.214.248.6] in the directory pub/gnu/funet, or
+ftp.gwdg.de [134.76.11.100] in the directory pub/linux/glibc, or
another archive site outside the USA. Archive maintainers are
encouraged to copy this distribution to their archives outside the
-USA. Please get it from ftp.funet.fi; transferring this distribution
+USA. Please get it from ftp.gwdg.de; transferring this distribution
from ftp.gnu.org (or any other site in the USA) to a site outside the
USA is in violation of US export laws.
Support for the @code{crypt} function is distributed separately because
of United States export restrictions. If you are outside the US or
Canada, you must get @code{crypt} support from a site outside the US,
-such as @samp{ftp.ifi.uio.no}.
+such as @samp{ftp.gwdg.de}. @samp{ftp.gwdg.de} has the crypt
+distribution in @code{pub/linux/glibc}.
@c Check this please someone:
(Most non-US mirrors of @samp{ftp.gnu.org} will have it too.) The file
you need is @file{glibc-crypt-@var{VERSION}.tar.gz}.