Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83 based; site hou2h.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxj!houxm!hou2h!jsw
From: jsw@hou2h.UUCP (J.SOLTES)
Newsgroups: net.crypt
Subject: Using crypt with ksh
Message-ID: <777@hou2h.UUCP>
Date: Thu, 17-Jan-85 15:30:42 EST
Article-I.D.: hou2h.777
Posted: Thu Jan 17 15:30:42 1985
Date-Received: Fri, 18-Jan-85 02:56:18 EST
Organization: AT&T Bell Labs, Holmdel NJ
Lines: 12

[.lunch]

  I just realized a problem with using crypt with ksh. Since ksh
maintains a .history file with previously executed commands in it,
the crypt command line (which includes the key) is added to .history!
Worse yet, .history is kept in your HOME directory, which is usually
the least protected! Is there a better way around this than editing
the lines out of .history?

				John Soltes - AT&T Consumer Products

Just because you're paranoid doesn't mean they're not out to get you.