From: Alexey Dobriyan <adobriyan@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH] Fix ESP SA loading (by default)
Date: Sat, 1 Nov 2008 14:38:35 +0300 [thread overview]
Message-ID: <20081101113835.GA3127@x200.localdomain> (raw)
In-Reply-To: <20081101050458.GA17807@gondor.apana.org.au>
On Sat, Nov 01, 2008 at 01:04:58PM +0800, Herbert Xu wrote:
> On Sat, Nov 01, 2008 at 07:37:37AM +0300, Alexey Dobriyan wrote:
> > digest_null algorithm is now mandatory for ESP.
> >
> > Steps to reproduce:
> >
> > kernel with CONFIG_CRYPTO_NULL=n
> >
> > #!/usr/sbin/setkey -f
> > flush;
> > spdflush;
> > add 192.168.0.1 192.168.0.42 esp 15701 -E 3des-cbc "123456789012123456789012";
>
> You do realise that this is totally insecure against man-in-the-
> middle attacks, right?
It's a cut down example. This won't work either:
#!/usr/sbin/setkey -f
flush;
spdflush;
add 192.168.0.1 192.168.0.42 ah 15700 -A hmac-md5 "1234567890123456";
add 192.168.0.1 192.168.0.42 esp 15701 -E 3des-cbc "123456789012123456789012";
add 192.168.0.42 192.168.0.1 ah 24500 -A hmac-md5 "1234567890123456";
add 192.168.0.42 192.168.0.1 esp 24501 -E 3des-cbc "123456789012123456789012";
spdadd 192.168.0.42 192.168.0.1 any -P out ipsec
esp/transport//require
ah/transport//require;
spdadd 192.168.0.1 192.168.0.42 any -P in ipsec
esp/transport//require
ah/transport//require;
next prev parent reply other threads:[~2008-11-01 11:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 4:37 [PATCH] Fix ESP SA loading (by default) Alexey Dobriyan
2008-11-01 5:04 ` Herbert Xu
2008-11-01 11:38 ` Alexey Dobriyan [this message]
2008-11-01 11:50 ` Herbert Xu
2008-11-02 4:33 ` David Miller
2008-11-03 0:16 ` Alexey Dobriyan
2008-11-03 1:04 ` Herbert Xu
2008-11-05 9:31 ` David Miller
2008-11-05 9:38 ` Herbert Xu
2008-11-05 9:54 ` Alexey Dobriyan
2008-11-05 9:55 ` David Miller
2008-11-05 10:03 ` Patrick McHardy
2008-11-05 10:26 ` David Miller
2008-11-05 10:30 ` Patrick McHardy
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=20081101113835.GA3127@x200.localdomain \
--to=adobriyan@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@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