Date: Sun, 4 Jun 1995 10:33:43 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: asami@CS.Berkeley.EDU (Satoshi Asami) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-ports@FreeBSD.org Subject: Re: elm and descrypt (Re: UNIX crypt() source - the problem solved (fwd)) Message-ID: <199506040833.KAA26975@uriah.heep.sax.de> In-Reply-To: <199506040826.BAA02028@silvia.HIP.Berkeley.EDU> from "Satoshi Asami" at Jun 4, 95 01:26:28 am
next in thread | previous in thread | raw e-mail | index | archive | help
As Satoshi Asami wrote:
>
> According to Joerg:
>
> * 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.)
>
> Something like this?
>
> post-configure:
> if ! ldconfig | grep -q descrypt; then
> echo "Seems like you don't have the DES crypt library (libdescrypt)."
> echo "The internal message {en,de}cryption may be incorrect."
> fi
Seems to look okay. I'm not sure if elm forcibly uses DES encryption,
it should (even in the case where the default -lcrypt points to the
MD5 one). Its usage of crypt() is not related to actual password
encryption, but only to the message {en,de}cryption.
--
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?199506040833.KAA26975>