netdev - Re: [XFRM]: xfrm_user: fix selector family initialization

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 10 Apr 2008 02:55:46 +0200
From:	Patrick McHardy <kaber@...sh.net>
To:	Kazunori MIYAZAWA <kazunori@...azawa.org>
CC:	David Miller <davem@...emloft.net>, pupilla@...mail.com,
	netdev@...r.kernel.org
Subject: Re: [XFRM]: xfrm_user: fix selector family initialization

Kazunori MIYAZAWA wrote:
> Patrick McHardy wrote:
>> Kazunori MIYAZAWA wrote:
>>>
>>> Sorry, I missed the thread.
>>> I have no idea to solve the regression.
>>
>>
>> Wouldn't explicitly initializing the SA family for
>> inter-family tunnels work?
> 
> I guess it is same as the original Herbert's patch.
> It needs to explicitly initialize the family for inter-family tunnel.


Thanks for looking into this, I haven't seen Herbert's patch,
but I'd assume comparing the SA family to the policy family
would work for determining whether its an inter-family tunnel
in case the family in explicitly initialized. The only thing
that would need to be changed in the kernel is the check
in xfrm_init_state().


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