Xref: utzoo sci.crypt:2769 comp.unix.xenix:10534 comp.sources.wanted:10918
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!lll-winken!elroy.jpl.nasa.gov!ames!uhccux!munnari.oz.au!cluster!jaa
From: jaa@cs.su.oz (James Ashton)
Newsgroups: aus.wanted,aus.sources,sci.crypt,comp.unix.xenix,comp.sources.wanted
Subject: Re: Sources for compatable crypt for XENIX
Keywords: crypt, XENIX
Message-ID: <758@cluster.cs.su.oz>
Date: 12 Mar 90 06:22:36 GMT
References: <26323@qfagus.OZ>
Sender: news@cluster.cs.su.oz
Reply-To: jaa@cluster.cs.su.oz (James Ashton)
Organization: Basser Dept of Computer Science, University of Sydney, Australia
Lines: 20

In article <26323@qfagus.OZ> arthur@qfagus.OZ (Arthur Raiskio) writes:
>I am after  a crypt function that produces an encryption code that is compatable
>with the encryptions produced by the standard XENIX facilities such as passwd
>and used by programs such as su and login. I an not trying to hack the crypt
>process I am just trying to write a front end processor and it would be nice if
>I could get away with using just 1 password file (/etc/passwd) as it would 
>make life just so much easier. I do not understand why the crypt facility was
>not included as a library function in XENIX. With thanks in advance for any
>possible assistance.

At the bottom of the SysV manual entry for crypt it says:

	This program is not available on software shipped outside
	the U.S.

This is because of government stupidity in the states - either it's illegal
or too bureaucratically nightmarish to export this stuff - technology
transfer & etc.  That's just the way it is.  I think this means you loose.

						James Ashton.