netdev - Re: [PATCH RFC 1/2] ipv6: add the IPV6_FL_F_REPLY flag to IPV6_FL_A

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 12 Dec 2013 11:39:30 +0100
From:	Florent Fourcot <florent.fourcot@...t-bretagne.fr>
To:	netdev@...r.kernel.org
Subject: Re: [PATCH RFC 1/2] ipv6: add the IPV6_FL_F_REPLY flag to IPV6_FL_A_GET

There two patches extend the flow API. It adds three new actions with
IPV6_FLOWLABEL_MGR:

 * setsockopt with IPV6_FL_A_GET and IPV6_FL_F_REPLY set:
      enable the reply of flow label, packet are sent with the
      last low label read in packet sent by remote device
 * setsockopt with IPV6_FL_A_PUT and IPV6_FL_F_REPLY set:
      disable the flow label reply
 * getsockopt with IPV6_FL_A_GET and IPV6_FL_F_REPLY set:
      get the flow label send by the remote device

I'm not sure of the best way to do that. First, should we allocate a
real flow label in the global flow label? I don't think so, and it could
add hard issues with the system of permission/sharing.

Second, I was not sure of the best way for the coverage for all TCP states.

Regards,

Florent.
--
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