[200] in The Cryptographic File System users list
using cfs with /home
daemon@ATHENA.MIT.EDU (Ravikant K.Rao)
Mon Oct 16 09:28:23 2000
From owner-cfs-users@crypto.com Mon Oct 16 13:28:23 2000
Return-Path: <owner-cfs-users@crypto.com>
Delivered-To: cfs-mtg@CHARON.MIT.EDU
Received: (qmail 28365 invoked from network); 16 Oct 2000 13:28:23 -0000
Received: from mx.crypto.com (207.140.168.138)
by charon.mit.edu with SMTP; 16 Oct 2000 13:28:23 -0000
Received: (from majordomo@localhost)
by MultiHostMXServer (8.9.3/8.9.x4) id JAA16722
for cfs-users-list; Mon, 16 Oct 2000 09:19:10 -0400 (EDT)
X-Authentication-Warning: mx.crypto.com: majordomo set sender to owner-cfs-users@crypto.com using -f
Received: from nsa.research.att.com (H-135-207-24-155.research.att.com [135.207.24.155])
by MultiHostMXServer (8.9.3/8.9.x4) with ESMTP id JAA08179
for <cfs-users@crypto.com>; Mon, 16 Oct 2000 09:19:09 -0400 (EDT)
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by nsa.research.att.com (8.7.3/8.7.3) with ESMTP id JAA07191 for <cfs-users@nsa.research.att.com>; Mon, 16 Oct 2000 09:19:07 -0400 (EDT)
Received: by mail-blue.research.att.com (Postfix)
id BAA174CEA8; Mon, 16 Oct 2000 09:19:08 -0400 (EDT)
Delivered-To: cfs-users@research.att.com
Received: from symonds.net (adsl-63-194-20-32.dsl.lsan03.pacbell.net [63.194.20.32])
by mail-blue.research.att.com (Postfix) with ESMTP id 1E7344CE66
for <cfs-users@research.att.com>; Mon, 16 Oct 2000 09:19:08 -0400 (EDT)
Received: from ravi by symonds.net with local (Exim 3.12 #1 (Debian))
id 13lAAV-0006Dt-00; Mon, 16 Oct 2000 06:19:07 -0700
Date: Mon, 16 Oct 2000 06:19:07 -0700
From: "Ravikant K.Rao" <ravi@symonds.net>
To: cfs-users@research.att.com
Subject: using cfs with /home
Message-ID: <20001016061907.B23833@symonds.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0.1i
Sender: owner-cfs-users@crypto.com
Precedence: bulk
Hi all:
I was wondering if anyone had custom scripts built to work along
with CFS so that the /home directory is maintained encrypted and the
encryption/decryption process is done transparently so that normal users
logging into the machine do not really know that crypt is working in the
background, while system level security is maintained? I'd appreciate any
pointers/links/suggestions/comments on this idea.
Thanks
-ravi
