From: "David S. Miller" <davem@redhat.com>
To: yoshfuji@linux-ipv6.org
Cc: kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com
Subject: Re: [RFC,PATCH] remove IPV6_AUTHHDR socket option / ancillary data
Date: Sun, 8 Feb 2004 12:58:18 -0800 [thread overview]
Message-ID: <20040208125818.02eba2f5.davem@redhat.com> (raw)
In-Reply-To: <20040208.141117.116936870.yoshfuji@linux-ipv6.org>
On Sun, 08 Feb 2004 14:11:17 +0900 (JST)
YOSHIFUJI Hideaki / ^[$B5HF#1QL@^[(B <yoshfuji@linux-ipv6.org> wrote:
> AH is now handled by the XFRM engine.
> IPV6_AUTHHDR socket option / ancillary data are deprecated.
>
> For sender side, it is very difficult (or even almost impossible) to
> create "correct" AH in userspace.
> For receiver side, none set opt->auth and user space application
> never get authentication data.
>
> IPV6_AUTHHDR is very Linux-specific and applications which use
> these feature are not portable at all.
I totally agree, I didn't even know this broken thing existed
to be honest.
Let's kill this now.
Patch applied, thanks Yoshfuji.
prev parent reply other threads:[~2004-02-08 20:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 5:11 [RFC,PATCH] remove IPV6_AUTHHDR socket option / ancillary data YOSHIFUJI Hideaki / 吉藤英明
2004-02-08 20:58 ` David S. Miller [this message]
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=20040208125818.02eba2f5.davem@redhat.com \
--to=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.com \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).