Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Michael Halcrow <mike@halcrow.us>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [CRYPTO] is it really optimized ?
Date: Sat, 14 Apr 2007 14:44:35 -0500	[thread overview]
Message-ID: <20070414194434.GA18988@halcrow.us> (raw)
In-Reply-To: <E1Hco0p-0007np-00@gondolin.me.apana.org.au>

On Sun, Apr 15, 2007 at 05:34:19AM +1000, Herbert Xu wrote:
> Francis Moreau <francis.moro@gmail.com> wrote:
> > 
> > hmm yes indeed it should do the job, but I don't see how you do that.
> > For example, let say I want to use "aes-foo" with eCryptfs. I can give
> > a higher priority to "aes-foo" than "aes" one. When eCryptfs asks for
> > a aes cipher it will pass "aes" name and since "aes-foo" has a higher
> > priority then the cypto core will return "aes-foo" cipher, right ? But
> > in this scheme, eCryptfs has not a higher priority than other kernel
> > users. How can I prevent others to use "aes-foo" ?
> 
> You would assign "aes-foo" a lower priority and then tell eCryptfs to
> use "aes-foo" instead of "aes".

Note that eCryptfs whitelists the cipher name (see
fs/ecryptfs/crypto.c::ecryptfs_cipher_code_str_map[] and associated
functions). This is because eCryptfs needs to pick a cipher code
(RFC2440-ish) to identify the cipher in the encrypted file
metadata. Shall I go ahead with a patch to add support for the '-'
qualifier?

Mike

  reply	other threads:[~2007-04-15  1:18 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <38b2ab8a0704130630v4c840bd1w19f2a239f86a93b@mail.gmail.com>
2007-04-14  4:30 ` [CRYPTO] is it really optimized ? Herbert Xu
2007-04-14 13:15   ` Francis Moreau
2007-04-14 19:34     ` Herbert Xu
2007-04-14 19:44       ` Michael Halcrow [this message]
2007-04-15 11:06         ` Satyam Sharma
2007-04-15 14:31           ` Satyam Sharma
2007-04-15 15:31             ` Michael Halcrow
2007-04-15 16:10               ` Satyam Sharma
2007-04-14 21:10       ` Francis Moreau
2007-04-15  7:52         ` Herbert Xu
2007-04-16  8:37           ` Francis Moreau
2007-04-17  0:41             ` Herbert Xu
2007-04-17 12:36               ` Francis Moreau
2007-04-17 13:04                 ` Evgeniy Polyakov
2007-04-17 13:42                   ` Herbert Xu
2007-04-17 14:01                     ` Francis Moreau
2007-04-17 15:08                       ` Evgeniy Polyakov
2007-04-17 15:34                         ` Francis Moreau
2007-04-17 15:57                           ` Evgeniy Polyakov
2007-04-17 16:18                             ` Francis Moreau
2007-04-17 17:07                               ` Evgeniy Polyakov
2007-04-17 13:57                   ` Francis Moreau
2007-04-17 13:40                 ` Herbert Xu
2007-04-17 13:59                   ` Francis Moreau
2007-04-17 14:02                     ` Herbert Xu
2007-04-17 14:41                       ` Francis Moreau
2007-04-17 15:40                         ` Roland Dreier
2007-04-17 16:14                           ` Francis Moreau
2007-04-17 16:33                             ` Roland Dreier
2007-04-17 17:24                               ` Francis Moreau
2007-04-17 17:34                                 ` Roland Dreier
2007-04-19  8:07                                   ` Francis Moreau
2007-04-23 13:56                                     ` Francis Moreau

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=20070414194434.GA18988@halcrow.us \
    --to=mike@halcrow.us \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@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