Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site dciem.UUCP Path: utzoo!dciem!reid From: reid@dciem.UUCP (Reid Ellis) Newsgroups: net.micro.mac Subject: Re: copy protection Message-ID: <1744@dciem.UUCP> Date: Sat, 7-Dec-85 19:32:42 EST Article-I.D.: dciem.1744 Posted: Sat Dec 7 19:32:42 1985 Date-Received: Sat, 7-Dec-85 22:10:27 EST Reply-To: reid@dciem.UUCP (Reid Ellis) Distribution: net Organization: D.C.I.E.M., Toronto, Canada Lines: 28 Keywords: Copy protection and lab use Summary: In article <1009@security.UUCP> jkm@security.UUCP (Jonathan K.Millen) writes: >the REALLY ideal scheme should identify the purchaser rather than the >machine. The software should freeze on the buyer's fingerprint, or >some other personal characteristic which (unlike a password) can't be >given away. I wish I could think of a way to do that. How about the way the person types? I believe that there is an area of identification in which the rhythm of the user typing in his password is as important as the password he types. Of course, the amount of code required to do this would probably be prohibitive, but this is an *ideal* solution after all.. Some thoughts on implementation: When run the first time, the program gives you a dialog box in which you type your password. If you botch the password (or actually plain text, listed in the dialog if you like) it clears and waits for another try. There is a standard "Cancel" button to return to the finder. The information is recorded in a file and if that file is found missing, the program returns to the finder. Thereafter, the user needs to type in a password or short phrase and there you go. A problem would be that typing the password would be tedious if done too often, if the program is used many times per day. As well, of course, you could copy the program first, and *then* run it, so maybe this isn't the *ideal* scheme after all. -- -- Reid Ellis "Roads? Where we're going, who needs _roads_?" {{allegra,decvax,duke,floyd,linus}!utzoo,{ihnp4,utzoo}!utcsri}!dciem!reid This message brought to you courtesy of the Poslfit Committee