Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!ssbell!dsndata!wayne From: wayne@dsndata.uucp (Wayne Schlitt) Newsgroups: comp.sys.hp Subject: Re: crypt BS? Message-ID: Date: 31 Jul 90 16:17:52 GMT References: Sender: wayne@dsndata.UUCP Distribution: comp Organization: Design Data Lines: 36 In-reply-to: steve@apollo.cfht.hawaii.edu's message of 31 Jul 90 01:34:05 GMT In article steve@apollo.cfht.hawaii.edu (Steven Smith) writes: > > > So why does running the crypt command produce the following message: > "This command is not available."? > its to remind you not to use the crypt command because you can break the encryption fairly easily by using the crypt-breakers-workbench. (available at any source archive near you... 1/2 :-) > > Just how am I supposed to keep my prying sysadm from reading all my files? > (nevermind that he is me). to keep prying sysadmins from reading your files, use one of the good des encryption programs available at a source archive near you. > [ ... ] Or decrypt all those things I crypted > with an earlier version of the OS? umm... you can either restore the crypt command from a backup, get someone else with the crypt command to decript it for you, or get the crypt-breakers-workbench... > > Is this only happening to me because I work at Canada-France-Hawaii Telescope > Corp (a non-profit US company, with a foreign sounding name)? > no, we dont have it either.... -wayne