From: Steffen Klassert <steffen.klassert@secunet.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [PATCH 01/16] crypto: authenc - Don't multiply priorities
Date: Mon, 15 Aug 2011 10:02:57 +0200 [thread overview]
Message-ID: <20110815080257.GU16877@secunet.com> (raw)
In-Reply-To: <20110815071928.GA29761@gondor.apana.org.au>
On Mon, Aug 15, 2011 at 03:19:29PM +0800, Herbert Xu wrote:
>
> Actually the reason it places a bigger weight on the cipher's
> priority is because typically ciphers are slower than hashes.
> So this is expressing the fact that we'd rather use a faster
> cipher with a slower hash than the other way around.
I thought the underlying ciphers and hashes choose their
priority based on the algorithms speed. So I thought it would
be ok to just add their priorities in the authenc algorithms.
Do you think we shoud keep the weight on the cipher's priority?
>
> Do you have a particular scenario in mind where this is broken?
>
I don't think it is broken. It's just easier to handle if an underlying
algorithm changes it's priority. If the user changes the priority of a
certain algorithm, I take the difference of the old and new priority
value and add this to all subsequent algorithms. So this can not take the
weight into account without some 'per algorithm' priority update functions.
next prev parent reply other threads:[~2011-08-15 8:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 11:26 [PATCH 00/16] crypto user configuration api Steffen Klassert
2011-08-11 11:26 ` [PATCH 01/16] crypto: authenc - Don't multiply priorities Steffen Klassert
2011-08-15 7:19 ` Herbert Xu
2011-08-15 8:02 ` Steffen Klassert [this message]
2011-08-15 8:55 ` Herbert Xu
2011-08-15 10:08 ` Steffen Klassert
2011-08-16 12:30 ` Herbert Xu
2011-08-16 12:37 ` Steffen Klassert
2011-09-21 8:32 ` Steffen Klassert
2011-09-21 11:19 ` Herbert Xu
2011-08-11 11:27 ` [PATCH 02/16] crypto: Add a flag to identify crypto instances Steffen Klassert
2011-08-11 11:27 ` [PATCH 03/16] crypto: Add userspace configuration API Steffen Klassert
2011-08-11 11:28 ` [PATCH 04/16] crypto: Add a report function pointer to crypto_type Steffen Klassert
2011-08-11 11:29 ` [PATCH 05/16] crypto: Add userspace report for larval type algorithms Steffen Klassert
2011-08-11 11:29 ` [PATCH 06/16] crypto: Add userspace report for shash " Steffen Klassert
2011-08-11 11:30 ` [PATCH 07/16] crypto: Add userspace report for ahash " Steffen Klassert
2011-08-11 11:31 ` [PATCH 08/16] crypto: Add userspace report for blkcipher " Steffen Klassert
2011-08-11 11:31 ` [PATCH 09/16] crypto: Add userspace report for ablkcipher " Steffen Klassert
2011-08-11 11:32 ` [PATCH 10/16] crypto: Add userspace report for givcipher " Steffen Klassert
2011-08-11 11:32 ` [PATCH 11/16] crypto: Add userspace report for aead " Steffen Klassert
2011-08-11 11:33 ` [PATCH 12/16] crypto: Add userspace report for nivaead " Steffen Klassert
2011-08-11 11:34 ` [PATCH 13/16] crypto: Add userspace report for pcompress " Steffen Klassert
2011-08-11 11:34 ` [PATCH 14/16] crypto: Add userspace report for rng " Steffen Klassert
2011-08-11 11:35 ` [PATCH 15/16] crypto: Add userspace report for cipher " Steffen Klassert
2011-08-11 11:35 ` [PATCH 16/16] crypto: Add userspace report for compress " Steffen Klassert
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=20110815080257.GU16877@secunet.com \
--to=steffen.klassert@secunet.com \
--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;
as well as URLs for NNTP newsgroup(s).