Path: utzoo!attcan!uunet!olivea!samsung!cs.utexas.edu!execu!sequoia!rpp386!jfh
From: jfh@rpp386.cactus.org (John F Haugh II)
Newsgroups: comp.unix.sysv386
Subject: Re: crypt in European SCO Unix
Message-ID: <18820@rpp386.cactus.org>
Date: 14 Dec 90 13:33:26 GMT
References: <8493@star.cs.vu.nl> <18817@rpp386.cactus.org> <1990Dec14.025613.21542@robobar.co.uk>
Reply-To: jfh@rpp386.cactus.org (John F Haugh II)
Organization: Lone Star Cafe and BBS Service
Lines: 21
X-Clever-Slogan: Recycle or Die.

In article <1990Dec14.025613.21542@robobar.co.uk> ronald@robobar.co.uk (Ronald S H Khoo) writes:
>Yeah, John's right, get the comp.sources.unix stuff for encryption,
>but get lng225b from SCO if you need crypt(3) to compile John's shadow
>password stuff with :-)

Oh, and speaking of shadow password stuff, time for a shameless plug.

The version which I just posted to alt.sources is the old level of
code.  If you've been hearing about new stuff for the last few months,
it is still in the pipeline.  The most exciting parts are libraries
which allow you to access the security information (passwd, group,
shadow, gshadow) in a database-like fashion with a get/put/commit-like
interface and a complete DBM interface for all of those files.

I will take bug reports for that code level, but expect many of them
to have been replaced with new bugs. ;-)

Also, if someone would freight me a SCO UNIX box, I will try to port
the code there and get rid of that stupid SecureWare pseudo-security
code.  If you need a security bond, escrow account or bank references,
I am sure we can work that part out.