Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Stephan Mueller <smueller@chronox.de>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] crypto: prevent helper ciphers from being allocated by users
Date: Tue, 17 Mar 2015 22:45:52 +1100	[thread overview]
Message-ID: <20150317114552.GA12326@gondor.apana.org.au> (raw)
In-Reply-To: <1442292.caf3IdtESe@tauon>

On Tue, Mar 17, 2015 at 12:40:12PM +0100, Stephan Mueller wrote:
>
> >How about adding a flag to all these internal algorithms and then
> >change crypto_alg_mod_lookup to disable that flag by default?
> 
> The issue with flags is the following: first we have to think about 
> whether we want a black list or white list approach. Your suggestion 
> implies a black list. Black lists for ensuring security is not good IMHO 
> as it has a tendency to miss cases. This especially applies to this area 
> where we have already an indicator for internal ciphers: the prio is so 
> low that it will never ever be selected based on the name. Now, adding a 
> flag means that we mark such an internal cipher twice.

Huh? Using prio is already a black list.

In any case abusing the priority field like this is not acceptable,
especially when the priority can be set from user-space.

Cheers,
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

  reply	other threads:[~2015-03-17 11:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 21:09 [RFC PATCH] crypto: prevent helper ciphers from being allocated by users Stephan Mueller
2015-03-15 11:49 ` Stephan Mueller
2015-03-17 11:23 ` Herbert Xu
2015-03-17 11:40   ` Stephan Mueller
2015-03-17 11:45     ` Herbert Xu [this message]
2015-03-17 14:59       ` Stephan Mueller

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=20150317114552.GA12326@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smueller@chronox.de \
    /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