linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@mandrakesoft.com>
To: Erik Mouw <J.A.K.Mouw@its.tudelft.nl>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Rajaram Suresh Gaunker <rajarams1@rediffmail.com>,
	linux-fsdevel@vger.kernel.org, kernelnewbies@nl.linux.org
Subject: Re: Hi
Date: Wed, 19 Feb 2003 17:09:38 +0100	[thread overview]
Message-ID: <86lm0ctfp9.fsf@trasno.mitica> (raw)
In-Reply-To: <20030219154020.GC2516@arthur.ubicom.tudelft.nl> (Erik Mouw's message of "Wed, 19 Feb 2003 16:40:20 +0100")

>>>>> "erik" == Erik Mouw <J.A.K.Mouw@its.tudelft.nl> writes:

erik> On Wed, Feb 19, 2003 at 04:37:13PM +0100, Juan Quintela wrote:
>> I think that the only reason why encryption at the filesystem level
>> makes sense is when you want to only encrypt _some_ files, but at that
>> point, you can also encrypt by hand them with some script/similar :(

erik> Or do something like libz: on the fly or even transparent
erik> encryption/decryption of files.

I meaned basically to do it out of kernel land, that solution also
works for me :)

Later, Juan.

-- 
In theory, practice and theory are the same, but in practice they 
are different -- Larry McVoy

  reply	other threads:[~2003-02-19 16:09 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-18 15:04 Hi Rajaram Suresh Gaunker
2003-02-18 16:34 ` Hi Erik Mouw
2003-02-18 23:07   ` Hi David Woodhouse
2003-02-19 14:54     ` Hi Juan Quintela
2003-02-19 15:22       ` Hi David Woodhouse
2003-02-19 15:37         ` Hi Juan Quintela
2003-02-19 15:40           ` Hi Erik Mouw
2003-02-19 16:09             ` Juan Quintela [this message]
2003-02-19 15:35     ` Hi Erik Mouw
2003-02-19 15:44       ` Hi David Woodhouse
2003-02-19 16:49         ` Hi Erik Mouw
2003-02-19 17:00       ` Hi Jan Harkes
2003-02-18 18:55 ` Hi Bryan Henderson
  -- strict thread matches above, loose matches on Subject: below --
2022-06-15 21:59 Hi Emerald Johansson
2018-12-19 20:08 HI Mrs Suzara Maling Wan
2015-10-20  1:45 Hi Judith Guest
2015-06-14  2:09 Hi Patricia Horoho
2013-12-21  8:18 Hi 906sl5glxg
2013-07-12  8:21 hi voady4cool
2013-01-03 17:04 hi keketa vieira
2011-10-28 11:10 Hi lisa hedstrand
2011-09-23 13:16 hi Mrs. Xue Chong
2010-11-06  8:24 hi Gabriel kante
2010-06-14 20:34 HI Dora Saki
2006-02-23 15:26 hi Edmund P. Hilton, V
2006-02-18  4:57 hi Bobbie M. Hancock
2002-09-15 23:57 hi Bety Lora
2002-09-08  5:10 hi Matthew Stapleton
2002-09-08 11:39 ` hi Matti Aarnio
2002-09-07 20:30 hi Angel GrefurT

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86lm0ctfp9.fsf@trasno.mitica \
    --to=quintela@mandrakesoft.com \
    --cc=J.A.K.Mouw@its.tudelft.nl \
    --cc=dwmw2@infradead.org \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=rajarams1@rediffmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).