Date: Sun, 4 Jun 1995 08:22:09 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: freebsd-hackers@freebsd.org (FreeBSD hackers) Subject: Re: UNIX crypt() source - the problem solved (fwd) Message-ID: <199506040622.IAA25865@uriah.heep.sax.de> In-Reply-To: <Pine.BSI.3.91.950604104555.14315B-100000@leo> from "Brian Tao" at Jun 4, 95 10:48:30 am
next in thread | previous in thread | raw e-mail | index | archive | help
As Brian Tao wrote:
>
> I don't think the Pine client itself requires that crypt() use DES
> (pretty sure imapd doesn't either, but I haven't looked). My
> /usr/lib/libcrypt* is symlinked to /usr/lib/libscrypt*. Pine 3.91
> builds and runs just fine on my FreeBSD machines at IBMS (we use it to
> connect to gate's IMAP server).
Hmm, this reminds me of another pitfall. I don't know about Pine/
IMAPD, but Elm requires to be linked against -ldescrypt, in order to
get its internal message {en,de}cryption correct.
Satoshi, the configure script in our port should be aware of this, and
it might warn the user about the disfunctional encryption if there's
no such thing like -ldescrypt available. (I don't know who's the
maintainer of the elm port.)
--
cheers, J"org
joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506040622.IAA25865>