wsinpvb@eutrc3.urc.tue.nl (p.v.bemmelen) (08/17/89)
I am writing a program on a UNIX system that uses the crypt() function. Now I want to port this program to MS-DOS, but the problem is that I don't have a crypt() function, (source or object code). Who can help me obtain a crypt() function ?? One that runs faster than the standard unix one would also be welcome to speed up the UNIX version as well. Greetings, wsinpvb@eutrc3.UUCP wsinpvb@eutrc3.urc.tue.nl
hinton@netcom.UUCP (Greg Hinton) (08/18/89)
In article <855@eutrc3.urc.tue.nl> wsinpvb@eutrc3.urc.tue.nl (p.v.bemmelen) writes: >Who can help me obtain a crypt() function ?? One that runs faster than the >standard unix one would also be welcome to speed up the UNIX version as well. I believe Robert T. Morris has just what you're looking for! :-) -- Greg Hinton INET: hinton@netcom.uucp UUCP: ...!uunet!apple!netcom!hinton
nghiem@walt.cc.utexas.edu (Alex Nghiem) (08/20/89)
[request for crypt function] Didn't I read somewhere that Unix encryption was restricted to U.S.A. and not for export? What happens if the function gets in the "wrong" hands through the network? nghiem@walt.cc.utexas.edu !cs.utexas.edu!ut-emx!walt!nghiem
roy@phri.UUCP (Roy Smith) (08/20/89)
In <17369@ut-emx.UUCP> nghiem@walt.cc.utexas.edu (Alex Nghiem) writes: > What happens if [crypt()] gets in the "wrong" hands through the network? The ruskies will then be able to decode all of our secret military transmissions, bringing about the fall of democracy as we know it today and subjecting the entire planet to the dominance of the evil empire. -- Roy Smith, Public Health Research Institute 455 First Avenue, New York, NY 10016 {att,philabs,cmcl2,rutgers,hombre}!phri!roy -or- roy@alanine.phri.nyu.edu "The connector is the network"
dts@quad.uucp (David T. Sandberg) (08/21/89)
In article <3947@phri.UUCP> roy@phri.UUCP (Roy Smith) writes: :In <17369@ut-emx.UUCP> nghiem@walt.cc.utexas.edu (Alex Nghiem) writes: :> What happens if [crypt()] gets in the "wrong" hands through the network? : : The ruskies will then be able to decode all of our secret military :transmissions, bringing about the fall of democracy as we know it today and :subjecting the entire planet to the dominance of the evil empire. Not to mention that the Colonel's secret fried chicken recipe would be placed in grave danger! -- David Sandberg - Quadric Systems "Strike Hard, Strike Sure" PSEUDO: dts@quad.uucp Bomber Command, R.A.F. ACTUAL: ..uunet!rosevax!sialis!quad!dts
amb@cs.columbia.edu (Andrew Boardman) (08/22/89)
In article <17369@ut-emx.UUCP> nghiem@walt.cc.utexas.edu (Alex Nghiem) writes: >Didn't I read somewhere that Unix encryption was restricted to >U.S.A. and not for export? What happens if the function gets >in the "wrong" hands through the network? Not a lot. Picture this: person who is in another country with his machine on the Internet ftp's the appropriate crypt binary (or source if he has it) via one of his accounts in the US. It's quite probably happened quite a few times; it's not a high-security item. It's just Officially Frowned Upon for some terribly good reason which escapes me at the moment. (This last bit was explained to me by an ex-NSA friend who's now at DEC of all places.) Andrew Boardman amb@cs.columbia.edu (for those that must, ab4@cunixc on bitnet)
gwyn@smoke.BRL.MIL (Doug Gwyn) (08/22/89)
In article <17369@ut-emx.UUCP> nghiem@walt.cc.utexas.edu (Alex Nghiem) writes: >Didn't I read somewhere that Unix encryption was restricted to >U.S.A. and not for export? What happens if the function gets >in the "wrong" hands through the network? Nothing happens. The UNIX crypt routines (all of them) have long been in the "wrong hands". The export restriction applies to software vendors, primarily because they haven't been able to obtain blanket export licenses from the Commerce Dept. and the cost of doing them one at a time is prohibitive.
wvenable@spam.ua.oz (Bill Venables) (08/23/89)
In article <10793@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn) writes: > In article <17369@ut-emx.UUCP> nghiem@walt.cc.utexas.edu (Alex Nghiem) writes: >>Didn't I read somewhere that Unix encryption was restricted to >>U.S.A. and not for export? What happens if the function gets >>in the "wrong" hands through the network? > > Nothing happens. The UNIX crypt routines (all of them) have long been > in the "wrong hands". [...] Let me confirm (although noone seems to doubt it) that the crypt() facility is not available on UNIX machines in Australia, and I must say I find this circumstance, although petty, a rather gratuitous insult from Uncle Sam. wnv. -- Dr. W. N. Venables, Dept. Statistics, | ACSnet: wvenable@spam.ua.oz.au Univ. of Adelaide, South Australia. |