From: Bart Trojanowski <bart@jukie.net>
To: Tamas Nagy <nagytam@rerecognition.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Idea: Encryption plugin architecture for file-systems
Date: Sat, 21 Apr 2001 15:13:43 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0104211509310.31611-100000@localhost> (raw)
In-Reply-To: <NFBBIDPOFIIFCBDDFGLEGEMICCAA.nagytam@rerecognition.com>
On Sat, 21 Apr 2001, Tamas Nagy wrote:
> extend the current file-system with an optional plug-in system, which allows
> for file-system level encryption instead of file-level. This could be used
> transparently for applications or even for file-system drivers. This
> doesn't mean an encrypted file-system, but a transparent encryption of a
> media instead.
Tamas,
you may want to read this:
http://encryptionhowto.sourceforge.net/Encryption-HOWTO-4.html
the international kernel patch (www.kerneli.org) has had this
implemented for some time. There is lot more info on crypto in Linux at:
http://encryptionhowto.sourceforge.net/
> Advantages:
> #1: optional security level for every data, without user interaction.
> #2: if this idea is used e.g. for portable media (like cdrom), your backup
> could be in safe also.
> #3: (almost;)) everybody could create own security plugin for their data,
> and not have to trust on the designers of a secure file systems.
I don't think it's that involved but you can certainly apply a cipher to a
mounted partition.
> So, what do you think about this? Is Linux kernel enough flexible to do
> this? What changes are necessary to do such a thing? Is there any other way,
> to have own security for file-systems or portable medias? Is this
> implementation could be used in the US?
You can use it in the states but you cannot develop for it within the
states - well, the regulations changes but I am not sure if the kerneli
guys will trust that... that's a totally different debate in itself.
Bart.
--
WebSig: http://www.jukie.net/~bart/sig/
next prev parent reply other threads:[~2001-04-21 19:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-21 18:52 Tamas Nagy
2001-04-21 19:10 ` Ian Stirling
2001-04-21 19:11 ` Alistair Riddell
2001-04-21 19:13 ` Bart Trojanowski [this message]
2001-04-21 19:21 ` Peter Makholm
2001-04-21 19:37 ` Andi Kleen
2001-04-21 20:26 ` Herbert Valerio Riedel
2001-04-21 22:50 ` Dan Hollis
2001-04-21 22:49 ` Dan Hollis
2001-04-22 9:42 ` Olaf Titz
2001-04-21 19:40 ` Stefan Jaschke
2001-04-23 20:12 ` Dale Amon
2001-04-24 2:54 ` David L. Nicol
2001-04-24 16:08 ` Dale Amon
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=Pine.LNX.4.33.0104211509310.31611-100000@localhost \
--to=bart@jukie.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nagytam@rerecognition.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
all inboxes | Powered by JetHome®