From: Sridhar Samudrala <sri@us.ibm.com>
To: Matthias Andree <matthias.andree@gmx.de>
Cc: lksctp-developers@lists.sourceforge.net,
Linux-Kernel mailing list <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com.br>
Subject: Re: [PATCH] net/sctp/Config.in make oldconfig compatibility (bash)
Date: Tue, 17 Feb 2004 10:48:55 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0402171035440.32361@localhost.localdomain> (raw)
In-Reply-To: <20040217122347.GA15213@merlin.emma.line.org>
On Tue, 17 Feb 2004, Matthias Andree wrote:
> Hello,
>
> I've needed the patch enclosed below the signature to remove some "make
> oldconfig" complaints in the current Linux-2.4 BK version.
>
> Please Cc: feedback to my sender address unless you are including
> linux-kernel; I'm not subscribed to lksctp-developers.
>
I thought SCTP changes were backed out just because of these 'make oldconfig'
errors from the 2.4 tree.
Anyway, i have submitted the attached patch that should fix this to davem.
'make oldconfig' and 'make menuconfig' worked fine after applying this patch.
However i am having problem with 'make xconfig'. When CONFIG_SCTP_HMAC_MD5
or CONFIG_SCTP_HMAC_SHA1 is enabled, everything under Crptographic options
is greyed out.
I would appreciate if some config expert can take a look at this and figure
out what is happening.
Thanks
Sridhar
-------------------------------------------------------------------------------
diff -Nru a/crypto/Config.in b/crypto/Config.in
--- a/crypto/Config.in Mon Feb 16 15:39:29 2004
+++ b/crypto/Config.in Mon Feb 16 15:39:29 2004
@@ -11,7 +11,9 @@
"$CONFIG_INET6_AH" = "y" -o \
"$CONFIG_INET6_AH" = "m" -o \
"$CONFIG_INET6_ESP" = "y" -o \
- "$CONFIG_INET6_ESP" = "m" ]; then
+ "$CONFIG_INET6_ESP" = "m" -o \
+ "$CONFIG_SCTP_HMAC_MD5" = "y" -o \
+ "$CONFIG_SCTP_HMAC_SHA1" = "y" ]; then
define_bool CONFIG_CRYPTO y
else
bool 'Cryptographic API' CONFIG_CRYPTO
@@ -25,7 +27,9 @@
"$CONFIG_INET6_AH" = "y" -o \
"$CONFIG_INET6_AH" = "m" -o \
"$CONFIG_INET6_ESP" = "y" -o \
- "$CONFIG_INET6_ESP" = "m" ]; then
+ "$CONFIG_INET6_ESP" = "m" -o \
+ "$CONFIG_SCTP_HMAC_MD5" = "y" -o \
+ "$CONFIG_SCTP_HMAC_SHA1" = "y" ]; then
define_bool CONFIG_CRYPTO_HMAC y
else
bool ' HMAC support' CONFIG_CRYPTO_HMAC
@@ -39,7 +43,8 @@
"$CONFIG_INET6_AH" = "y" -o \
"$CONFIG_INET6_AH" = "m" -o \
"$CONFIG_INET6_ESP" = "y" -o \
- "$CONFIG_INET6_ESP" = "m" ]; then
+ "$CONFIG_INET6_ESP" = "m" -o \
+ "$CONFIG_SCTP_HMAC_MD5" = "y" ]; then
define_bool CONFIG_CRYPTO_MD5 y
else
tristate ' MD5 digest algorithm' CONFIG_CRYPTO_MD5
@@ -51,7 +56,8 @@
"$CONFIG_INET6_AH" = "y" -o \
"$CONFIG_INET6_AH" = "m" -o \
"$CONFIG_INET6_ESP" = "y" -o \
- "$CONFIG_INET6_ESP" = "m" ]; then
+ "$CONFIG_INET6_ESP" = "m" -o \
+ "$CONFIG_SCTP_HMAC_SHA1" = "y" ]; then
define_bool CONFIG_CRYPTO_SHA1 y
else
tristate ' SHA1 digest algorithm' CONFIG_CRYPTO_SHA1
diff -Nru a/net/sctp/Config.in b/net/sctp/Config.in
--- a/net/sctp/Config.in Mon Feb 16 15:39:29 2004
+++ b/net/sctp/Config.in Mon Feb 16 15:39:29 2004
@@ -14,31 +14,9 @@
if [ "$CONFIG_IP_SCTP" != "n" ]; then
bool ' SCTP: Debug messages' CONFIG_SCTP_DBG_MSG
bool ' SCTP: Debug object counts' CONFIG_SCTP_DBG_OBJCNT
-fi
-if [ "$CONFIG_CRYPTO_HMAC" = "n"]; then
- choice 'SCTP: Cookie HMAC Algorithm' \
- "HMAC-NONE CONFIG_SCTP_HMAC_NONE" HMAC-NONE
-else
- if [ "$CONFIG_CRYPTO_MD5" = "n" -a "$CONFIG_CRYPTO_SHA1" = "n"]; then
- choice 'SCTP: Cookie HMAC Algorithm' \
- "HMAC-NONE CONFIG_SCTP_HMAC_NONE" HMAC-NONE
- else
- if [ "$CONFIG_CRYPTO_MD5" != "n" -a "$CONFIG_CRYPTO_SHA1" != "n"]; then
- choice 'SCTP: Cookie HMAC Algorithm' \
- "HMAC-NONE CONFIG_SCTP_HMAC_NONE \
- HMAC-SHA1 CONFIG_SCTP_HMAC_SHA1 \
- HMAC-MD5 CONFIG_SCTP_HMAC_MD5" HMAC-SHA1
- else
- if [ "$CONFIG_CRYPTO_MD5" != "n" ]; then
- choice 'SCTP: Cookie HMAC Algorithm' \
- "HMAC-NONE CONFIG_SCTP_HMAC_NONE \
- HMAC-MD5 CONFIG_SCTP_HMAC_MD5" HMAC-MD5
- else
- choice 'SCTP: Cookie HMAC Algorithm' \
- "HMAC-NONE CONFIG_SCTP_HMAC_NONE \
- HMAC-SHA1 CONFIG_SCTP_HMAC_SHA1" HMAC-SHA1
- fi
- fi
- fi
+choice 'SCTP: Cookie HMAC Algorithm' \
+ "HMAC-NONE CONFIG_SCTP_HMAC_NONE \
+ HMAC-SHA1 CONFIG_SCTP_HMAC_SHA1 \
+ HMAC-MD5 CONFIG_SCTP_HMAC_MD5" HMAC-SHA1
fi
endmenu
next prev parent reply other threads:[~2004-02-17 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 12:23 Matthias Andree
2004-02-17 18:48 ` Sridhar Samudrala [this message]
2004-02-17 19:05 ` David S. Miller
2004-02-17 19:31 ` [Lksctp-developers] " Sridhar Samudrala
2004-02-17 21:06 ` Matthias Andree
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=Pine.LNX.4.58.0402171035440.32361@localhost.localdomain \
--to=sri@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=marcelo.tosatti@cyclades.com.br \
--cc=matthias.andree@gmx.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
all inboxes | Powered by JetHome®