netdev - Re: [PATCH] [IPV6 0/3] Deprecate IPv6 Routing Header Type 0.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20070618.153424.27464098.yoshfuji@linux-ipv6.org>
Date:	Mon, 18 Jun 2007 15:34:24 +0900 (JST)
From:	YOSHIFUJI Hideaki / 吉藤英明 
	<yoshfuji@...ux-ipv6.org>
To:	davem@...emloft.net
Cc:	pekkas@...core.fi, netdev@...r.kernel.org, yoshfuji@...ux-ipv6.org
Subject: Re: [PATCH] [IPV6 0/3] Deprecate IPv6 Routing Header Type 0.

In article <20070617.231749.18606024.davem@...emloft.net> (at Sun, 17 Jun 2007 23:17:49 -0700 (PDT)), David Miller <davem@...emloft.net> says:

> > [PATCH 1/3] [IPV6]: Restore semantics of Routing Header processing.
> > [PATCH 2/3] [IPV6]: Do not send RH0 anymore.
> > [PATCH 3/3] [IPV6]: Make IPV6_{RECV,2292}RTHDR boolean options.
> 
> I think it is sufficient to schedule this for 2.6.23 and not
> to rush it into 2.6.22
> 
> Do you agree?

I agree for 3/3 (and 2/3, maybe).

On the other hand, I would rather like to push 1/3 to 2.6.21-stable
and 2.6.22(-stable) to restore the basic semantics, if possible.
Or I need to put the patch(es) on-line for users.

--yoshfuji
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html