[112] in The Cryptographic File System users list
process accounting: stored cleartext
daemon@ATHENA.MIT.EDU (ldurham)
Thu Dec 10 08:30:20 1998
From owner-cfs-users@research.att.com Thu Dec 10 13:30:19 1998
Return-Path: <owner-cfs-users@research.att.com>
Delivered-To: cfs-mtg@bloom-picayune.mit.edu
Received: (qmail 21256 invoked from network); 10 Dec 1998 13:30:14 -0000
Received: from unknown (HELO rumor.research.att.com) (192.20.225.9)
by bloom-picayune.mit.edu with SMTP; 10 Dec 1998 13:30:14 -0000
Received: from research.att.com ([135.207.30.100]) by rumor; Thu Dec 10 08:23:15 EST 1998
Received: from amontillado.research.att.com ([135.207.24.32]) by research; Thu Dec 10 08:29:00 EST 1998
Received: from nsa.research.att.com (majordomo@nsa.research.att.com [135.207.24.155])
by amontillado.research.att.com (8.8.7/8.8.7) with ESMTP id IAA16897;
Thu, 10 Dec 1998 08:28:57 -0500 (EST)
Received: (from majordomo@localhost) by nsa.research.att.com (8.7.3/8.7.3) id IAA26700 for cfs-users-list; Thu, 10 Dec 1998 08:27:08 -0500 (EST)
X-Authentication-Warning: nsa.research.att.com: majordomo set sender to owner-cfs-users@nsa.research.att.com using -f
Received: from research.att.com (research.research.att.com [135.207.30.100]) by nsa.research.att.com (8.7.3/8.7.3) with SMTP id IAA26696 for <cfs-users@nsa.research.att.com>; Thu, 10 Dec 1998 08:27:06 -0500 (EST)
Received: from st6000.sct.edu ([168.28.176.249]) by research; Thu Dec 10 08:27:02 EST 1998
Received: by st6000.sct.edu (AIX 4.1/UCB 5.64/4.03)
id AA11784; Thu, 10 Dec 1998 08:18:00 -0500
From: ldurham@st6000.sct.edu (ldurham)
Message-Id: <9812101318.AA11784@st6000.sct.edu>
Subject: process accounting: stored cleartext
To: cfs-users@research.att.com
Date: Thu, 10 Dec 1998 08:18:00 -0500 (EST)
X-Mailer: ELM [version 2.4 PL25]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Sender: owner-cfs-users@research.att.com
Precedence: bulk
Just a heads-up in case you might have done what I did,
I had some binaries that I was running from the encrypted filesystem.
Also, I was running some process accounting software that recorded
these binaries' names as cleartext names on a non-encrypted filesystem.
I had to wipe the log files and disable the process accounting to
prevent future problems. Then, I realized that my shell was also
recording the cleartext names of the binaries as well as the names of
the encrypted files that I was using in my non-encrypted history file.
So now I use an encrypted history file.
Hopefully, this will help some other users. Any other tips on safely
using cfs for us novices are appreciated.
Later,
Ligon Durham
ldurham@spsu.edu
