mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Morris <jmorris@intercode.com.au>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: davem@redhat.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Added missing dependencies on CRYPTO_HMAC
Date: Sun, 18 May 2003 13:40:28 +1000 (EST)	[thread overview]
Message-ID: <Mutt.LNX.4.44.0305181334280.21675-100000@excalibur.intercode.com.au> (raw)
In-Reply-To: <20030518031546.GA4943@gondor.apana.org.au>

On Sun, 18 May 2003, Herbert Xu wrote:

> On Sun, May 18, 2003 at 12:19:09PM +1000, James Morris wrote:
> > 
> > See crypto/Kconfig, CRYPTO_HMAC is being defaulted to Y if these protocols 
> > are selected.
> 
> Yes, but the user can then set them to no.  This does happen as the
> Crypto menu is listed after Networking so someone going through it
> in that order can select INET_AH and then go on to disable Crypto.

Yes, we allow users to override the defaults if they wish, at their own 
peril.

> Dependencies are there to prevent these things from happening.

Using dependencies would mean that the ipsec protocols would not appear in 
the networking menu until after selecting the correct algorthims in the 
crypto menu.

How would users know what the minimally required set of algorithms are?  
Would they then know to go _back_ to the networking menu to enable the
protocols?


- James
-- 
James Morris
<jmorris@intercode.com.au>


  reply	other threads:[~2003-05-18  3:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-18  2:10 Herbert Xu
2003-05-18  2:19 ` James Morris
2003-05-18  3:15   ` Herbert Xu
2003-05-18  3:40     ` James Morris [this message]
2003-05-18  4:04       ` Herbert Xu
2003-05-18  5:17         ` David S. Miller
2003-05-18 12:46       ` Adrian Bunk
2003-05-18 15:03         ` James Morris
2003-05-18 15:14       ` Adrian Bunk

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=Mutt.LNX.4.44.0305181334280.21675-100000@excalibur.intercode.com.au \
    --to=jmorris@intercode.com.au \
    --cc=davem@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --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

all inboxes | Powered by JetHome®