From: "David S. Miller" <davem@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: kazunori@miyazawa.org, netdev@oss.sgi.com
Subject: Re: [AH6] Disallow mutable bits after AH header
Date: Fri, 23 Jul 2004 13:37:37 -0700 [thread overview]
Message-ID: <20040723133737.447a9598.davem@redhat.com> (raw)
In-Reply-To: <20040723135320.GA26000@gondor.apana.org.au>
On Fri, 23 Jul 2004 23:53:21 +1000
Herbert Xu <herbert@gondor.apana.org.au> wrote:
> As we discussed before, mutable headers should not be allowed after
> the AH header. In fact, this appears to be the intention of RFC 2402.
> It is further clarified in section 3.1.1 of
>
> http://www.ietf.org/internet-drafts/draft-ietf-ipsec-rfc2402bis-07.txt
>
> This allows us to simplify the code in ah6.c. As a result, this also
> fixes the following issues:
>
> * Dependence on skb->h in ah6_output().
> * Bogus clearing of auth_data of 2nd AH header in ipv6_clear_mutable_options().
Applied, thanks Herbert.
next prev parent reply other threads:[~2004-07-23 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 13:53 [AH6] Disallow mutable bits after AH header Herbert Xu
2004-07-23 20:37 ` David S. Miller [this message]
2004-07-28 11:46 ` Herbert Xu
2004-07-28 16:11 ` David S. Miller
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=20040723133737.447a9598.davem@redhat.com \
--to=davem@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=kazunori@miyazawa.org \
--cc=netdev@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.