[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(usagi-users 03675) Routing header reversal support is missing!
- To: usagi-users@xxxxxxxxxxxxxx
- Subject: (usagi-users 03675) Routing header reversal support is missing!
- From: "Sérgio Gomes" <sergiomdgomes@xxxxxxxxx>
- Date: Fri, 26 May 2006 15:23:15 +0000
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=p2BwInlIK76O1lM3b4mIvnOM4pYwSdsmToCriYj2tv6H4n2FUX+GeRdoN+3/Gt4EB9NmoiwoxBW+qJ02qW77mrOVQ34xqz43k+CU0NGGN6V/g5mBjY2Ttgmh8ctxOxURLVmDJ6YK8YVg7Vb05XYs2XuH90OscH1kVU6seqqZkuU=
- Reply-to: usagi-users@xxxxxxxxxxxxxx
Hello everyone!
As a followup to my previous post, and because I received no reply, I
began carefully analysing the IPv6 source code in the USAGI webcvs,
and I realized that the support for point 8.4 (Responding to Packets
Carrying Routing Headers) of the IPv6 RFC2460 is incorrect.
It states that it should be possible to reverse routing headers if
authentication (namely IPSec AH) is present in the connection.
However, the only thing related to routing header reversal is a
backdoor left for testing: ipv6_invert_rthdr in exthdrs.c.
is there any specific reason why the correct support isn't present?
Thanks,
Sérgio