From: Valdis.Kletnieks@vt.edu
To: Andries.Brouwer@cwi.nl
Cc: ahu@ds9a.nl, linux-kernel@vger.kernel.org
Subject: Re: what is needed to test the in-kernel crypto loop?
Date: Tue, 15 Jul 2003 14:29:39 -0400 [thread overview]
Message-ID: <200307151829.h6FITd43003528@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 11 Jul 2003 15:46:55 +0200." <UTC200307111346.h6BDktG25627.aeb@smtp.cwi.nl>
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
On Fri, 11 Jul 2003 15:46:55 +0200, Andries.Brouwer@cwi.nl said:
> Try util-linux 2.12, available in 60 hours.
(using this version from ftp.kernel.org/pub/linux/utils/util-linux:
-rw-r--r-- 1 korg korg 1285674 Jul 13 22:09 util-linux-2.12pre.tar.bz2
Umm.. OK... I'll bite. How do I get 2.12pre to actually use cryptoloop?
losetup -e aes /dev/loop yadd yadda says 'Unknown encryption type aes',
mostly because of this code in lomount.c:
struct crypt_type_struct {
int id;
char *name;
} crypt_type_tbl[] = {
{ LO_CRYPT_NONE, "no" },
{ LO_CRYPT_NONE, "none" },
{ LO_CRYPT_XOR, "xor" },
{ LO_CRYPT_DES, "DES" },
{ -1, NULL }
};
static int
crypt_type (const char *name) {
int i;
if (name) {
for (i = 0; crypt_type_tbl[i].id != -1; i++)
if (!strcasecmp (name, crypt_type_tbl[i].name))
return crypt_type_tbl[i].id;
}
return -1;
}
none, xor, DES. Those are the choices - and yes, aes.o is built and in-kernel.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2003-07-15 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 13:46 what is needed to test the in-kernel crypto loop? Andries.Brouwer
2003-07-15 18:29 ` Valdis.Kletnieks [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-16 23:30 Andries.Brouwer
2003-07-11 13:08 bert hubert
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=200307151829.h6FITd43003528@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=Andries.Brouwer@cwi.nl \
--cc=ahu@ds9a.nl \
--cc=linux-kernel@vger.kernel.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 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).