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:	Tue, 7 Jan 2014 15:59:56 +0800
From:	Fan Du <fan.du@...driver.com>
To:	Steffen Klassert <steffen.klassert@...unet.com>
CC:	<davem@...emloft.net>, <stephen@...workplumber.org>,
	<dev@...ts.strongswan.org>, <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next 0/2] Pack struct xfrm_usersa_info and struct
 xfrm_userpolicy_info



On 2014年01月07日 15:47, Steffen Klassert wrote:
> On Tue, Jan 07, 2014 at 02:48:57PM +0800, Fan Du wrote:
>> When trying to setup IPsec configuration on a 64bits host with
>> iproute2(32bits compiled), the intened xfrm policy and sa is
>> either deficit or wrong when kernel trying to parse user land
>> information.
>>
>> Further investigatino shows that:
>> L: kernel
>> R: iproute2
>>
>>            sizeof       userpolicy      usersa
>> 64bits(unpacked)        168/168        224/224
>> 32bits(unpacked)        164/164        220/220
>>                           ^   ^
>>                           L   R
>>
>> To keep kernel and user land see a consistent structure, after
>> add packing attribute, now it looks like this:
>>
>> 64bits(  packed)        164/164        217/217
>> 32bits(  packed)        164/164        217/217
>>                           ^   ^
>>                           L   R
>>
>
> We don't change userspace exported structures. This breaks
> existing userspace tools.
>

Then user with 32bits iproute2 or StrongSwan has to rebuild as 64bits?

-- 
浮沉随浪只记今朝笑

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ