[169] in The Cryptographic File System users list
Re: cfs and list status
daemon@ATHENA.MIT.EDU (Holger Benl)
Tue Mar 14 09:31:33 2000
From owner-cfs-users@nsa.research.att.com Tue Mar 14 14:31:32 2000
Return-Path: <owner-cfs-users@nsa.research.att.com>
Delivered-To: cfs-mtg@CHARON2.mit.edu
Received: (qmail 11066 invoked from network); 14 Mar 2000 14:31:32 -0000
Received: from mail-blue.research.att.com (135.207.30.102)
by charon2.mit.edu with SMTP; 14 Mar 2000 14:31:32 -0000
Received: from amontillado.research.att.com (amontillado.research.att.com [135.207.24.32])
by mail-blue.research.att.com (Postfix) with ESMTP
id 929524CE02; Tue, 14 Mar 2000 09:31:31 -0500 (EST)
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 JAA26374;
Tue, 14 Mar 2000 09:32:17 -0500 (EST)
Received: (from majordomo@localhost) by nsa.research.att.com (8.7.3/8.7.3) id JAA01445 for cfs-users-list; Tue, 14 Mar 2000 09:25:51 -0500 (EST)
X-Authentication-Warning: nsa.research.att.com: majordomo set sender to owner-cfs-users@nsa.research.att.com using -f
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 JAA01441 for <cfs-users@nsa.research.att.com>; Tue, 14 Mar 2000 09:25:49 -0500 (EST)
Received: by mail-blue.research.att.com (Postfix)
id 115544CE17; Tue, 14 Mar 2000 09:26:31 -0500 (EST)
Delivered-To: cfs-users@research.att.com
Received: from smtp.myokay.net (db.myokay.net [195.211.211.74])
by mail-blue.research.att.com (Postfix) with SMTP id C99D14CE14
for <cfs-users@research.att.com>; Tue, 14 Mar 2000 09:26:29 -0500 (EST)
Received: (qmail 14504 invoked for bounce); 14 Mar 2000 14:26:24 -0000
Received: from unknown (HELO stud.uni-muenchen.de) (194.29.37.130)
by smtp.myokay.net with SMTP; 14 Mar 2000 14:26:24 -0000
Message-ID: <38CE59BC.54731A26@stud.uni-muenchen.de>
Date: Tue, 14 Mar 2000 15:24:45 +0000
From: Holger Benl <holger.benl@stud.uni-muenchen.de>
X-Mailer: Mozilla 4.61C-CCK-MCD Caldera Systems OpenLinux [en] (X11; I; Linux 2.2.10 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: cfs-users@research.att.com
Subject: Re: cfs and list status
References: <200003122141.QAA28388@pebble> <20000313034022.F1631@wyvern.ptw.com> <03a801bf8cc5$eacad2f0$8000000a@Matador> <20000313112156.A9731@argo.cit.nih.gov>
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 7bit
Sender: owner-cfs-users@research.att.com
Precedence: bulk
Anthony R Iano-Fletcher wrote:
>
> Hi
>
> Bill Dorsey wrote:
> > Check out tcfs (Transparent Cryptographic File System) at
> > http://tcfs.dia.unisa.it .....
> > If you are running some
> > other flavor of Unix, you'll have to stick with CFS for now.
>
> This is a strength of CFS over TCFS. I can run it on Solaris, SGIs
> and Linux and have everything work together.
Furthermore, TCFS is available for Linux 2.0.x kernels only.
There are other alternatives as well... for example, you can encrypt
loopback devices with the international linux kernel patch available
at www.kerneli.org (I haven't tried it, though, since I'm perfectly
happy with CFS).
More information on alternatives for Linux users can be found at
http://drt.ailis.de/crypto/linux-disk.html
IIRC, none of them could replace CFS for non-Linux users, though.
> Glenn Holmer wrote:
> > I am still using CFS. Isn't it linked against an older libc?
> > Should I be worried that it will eventually become unusable?
>
> you can always try to recompile it from scratch.
I've compiled mine recently (on Slackware 7.0), it's linked against
libc6 and works without any problems.
Holger.
