Xref: utzoo comp.org.eff.talk:1197 sci.crypt:4067
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!rex!uflorida!gatech!mcnc!uvaarpa!murdoch!newton.acc.Virginia.EDU!spm2d
From: spm2d@newton.acc.Virginia.EDU (Steven P. Miale)
Newsgroups: comp.org.eff.talk,sci.crypt
Subject: Re: Vendor's Responsibilities on seized equipments
Keywords: what to do, authorities, etc..
Message-ID: <1991Jan15.035239.11538@murdoch.acc.Virginia.EDU>
Date: 15 Jan 91 03:52:39 GMT
References: <13899@uudell.dell.com> <1991Jan10.041906.27901@ddsw1.MCS.COM>
Sender: news@murdoch.acc.Virginia.EDU
Organization: University of Virginia
Lines: 21
Ireallyam: spm2d

In article <1991Jan10.041906.27901@ddsw1.MCS.COM> karl@ddsw1.MCS.COM (Karl Denninger) writes:
>In article <13899@uudell.dell.com> sblair@upurbmw.dell.com (Steve Blair) writes:
>I'd chuckle, giggle and snicker - and then give them the source to the 
>program.  First and foremost, I doubt if even the best computer they have 
>right now would help, given that the user of the cryptosystem in question 
>used a reasonable key on the file(s) in question.

Actually, I have another method a bit similar to the one you used:

To each character in the file, a character from the password is added. Then,
the number of times the encryption program has gone through the password
is subtracted. Add to this the character number in the password, and
XOR it with the CRC of the password. Makes for lots of fun. I'm not
sure of the *actual* secureness of this algorithm, and I would be pleased
if some of the code experts out there would tell me if it is actually secure
or if it could be easily broken. My program accepts passwords of any
length, and most of mine are over 20 characters...

Steven Miale
spm2d@virginia.edu