All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter_22@gmx.de
To: linux-crypto@nl.linux.org
Cc: clemens@endorphin.org, ml@bitfalle.org,
	linux-kernel@vger.kernel.org, linux-crypto@nl.linux.org
Subject: Re: Announce loop-AES-v3.0b file/swap crypto package
Date: Wed, 19 Jan 2005 00:30:58 +0100 (MET)	[thread overview]
Message-ID: <11521.1106091058@www31.gmx.net> (raw)
In-Reply-To: 1106006804.3336.37.camel@localhost

http://clemens.endorphin.org/LinuxHDEncSettings  
  
Did you ever take a look at that page?!  
I did. I´d say the best are the photos. The rest isn
´t much of a help. 
Ever since I grabbed me SuSE Linux 8.2 and managed to  
compile some standard kernel according to the 
loop-aes.readme it´s proven to the world: 
You do no longer need to study "Computer Science & 
Economics" to encrypt 200GB serial ata drives with 
128bit on AMD64 CPUs under linux. 
  
As there is no replacement for loop-aes to be found 
in the download section I´ll have to live with aes in 
its "weak" CBC implementation. 
Is there anyone out to think I´ll exchange 
AMD64-optimized, rock solid code & working software 
for dm-cryptoloop? 
 
In case there are more complaints concerning loop-aes 
everyone is free to launch either fixes or reveal 
urls with something better at hand. 
It should be: 
-easy to compile 
-rock solid in everyday usage 
-survive power losses & crashes (yes, I play UT2004 
from encrypted root + swap) 
-compatible with the future 
-third-party stand-alone software (not a kernel 
patch) 
-optimized for AMD64 CPU 
-well documented 
-bootable from removeable media 
(usb-hdd/SD-Cards/etc.) 
-able to move partition table from encrypted drive to 
removable medium 
 
I´m looking forward to read about your solutions! 

-- 
10 GB Mailbox, 100 FreeSMS http://www.gmx.net/de/go/topmail
+++ GMX - die erste Adresse für Mail, Message, More +++

  reply	other threads:[~2005-01-18 23:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-16 21:58 Announce loop-AES-v3.0b file/swap crypto package Jari Ruusu
2005-01-17  4:26 ` Bill Davidsen
2005-01-17  5:10   ` Willy Tarreau
2005-01-17 15:08   ` Jari Ruusu
2005-01-17 19:14     ` Fruhwirth Clemens
2005-01-17 19:29       ` Paul Walker
2005-01-17 21:04         ` Fruhwirth Clemens
2005-01-17 21:39           ` Paul Walker
2005-01-18 15:35           ` Jari Ruusu
2005-01-18 17:23             ` Andries Brouwer
2005-01-18 18:38               ` Venkat Manakkal
2005-01-19  0:18                 ` Dan Hollis
2005-01-19  0:46                   ` Kyle Moffett
2005-01-19 17:03                   ` Bill Davidsen
2005-01-19 17:57                     ` Fruhwirth Clemens
2005-01-19 21:24                       ` James Morris
2005-01-19 22:18                         ` Fruhwirth Clemens
2005-01-20 16:42                       ` Bill Davidsen
2005-01-17 21:26       ` markus reichelt
2005-01-17 23:11         ` Fruhwirth Clemens
2005-01-18  0:06           ` Daniel Harvey
2005-01-18 23:30             ` Peter_22 [this message]
2005-01-18  9:49           ` jerome etienne
2005-01-18 15:36             ` Jari Ruusu
2005-01-20 22:38           ` markus reichelt
2005-01-21 18:29       ` Sytse Wielinga
2005-01-17 20:28     ` Andreas Jellinghaus
2005-01-17 21:38     ` Paul Walker

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=11521.1106091058@www31.gmx.net \
    --to=peter_22@gmx.de \
    --cc=clemens@endorphin.org \
    --cc=linux-crypto@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ml@bitfalle.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.