netdev - Re: [PATCH] Have af-specific init_tempsel() initialize family field of temporary selector

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, 04 Nov 2008 12:46:44 +0100
From:	arno@...isbad.org (Arnaud Ebalard)
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	Andreas Steffen <andreas.steffen@...ongswan.org>,
	Martin Willi <martin@...ongswan.org>,
	Kazunori MIYAZAWA <kazunori@...azawa.org>
Subject: Re: [PATCH] Have af-specific init_tempsel() initialize family field of temporary selector

Hi,

Herbert Xu <herbert@...dor.apana.org.au> writes:

> On Tue, Nov 04, 2008 at 11:24:51AM +0100, Arnaud Ebalard wrote:
>> Hi,
>> 
>> While adding MIGRATE support to strongSwan, Andreas Steffen noticed that
>> the selectors provided in XFRM_MSG_ACQUIRE have their family field
>> uninitialized (those in MIGRATE do have their family set).
>> 
>> Looking at the code, this is because the af-specific init_tempsel()
>> (called via afinfo->init_tempsel() in xfrm_init_tempsel()) do not set
>> the value.
>> 
>> Even if current apps probably do not rely on it, is there any argument
>> for not doing it or is it just an omission?
>> 
>> The patch below is more for discussion than anything else.
>
> We should ask the MIP6 folks since this may affect them.

Sorry Herbert, my initial comment was misleading: the family is not set
in the selectors provided in the *XFRM_MSG_ACQUIRE*, which is not MIPv6 
related. I could check again, but I think the patch below will impact
all native key managers. Or did I miss something and there is a specific
reason why MIPv6 folks may be impacted?

>> Reported-by: Andreas Steffen <andreas.steffen@...ongswan.org>
>> Signed-off-by: Arnaud Ebalard <arno@...isbad.org>
>> ---
>>  net/ipv4/xfrm4_state.c |    1 +
>>  net/ipv6/xfrm6_state.c |    1 +
>>  2 files changed, 2 insertions(+), 0 deletions(-)
>> 
>> diff --git a/net/ipv4/xfrm4_state.c b/net/ipv4/xfrm4_state.c
>> index 07735ed..55dc6be 100644
>> --- a/net/ipv4/xfrm4_state.c
>> +++ b/net/ipv4/xfrm4_state.c
>> @@ -33,6 +33,7 @@ __xfrm4_init_tempsel(struct xfrm_state *x, struct flowi *fl,
>>  	x->sel.dport_mask = htons(0xffff);
>>  	x->sel.sport = xfrm_flowi_sport(fl);
>>  	x->sel.sport_mask = htons(0xffff);
>> +	x->sel.family = AF_INET;
>>  	x->sel.prefixlen_d = 32;
>>  	x->sel.prefixlen_s = 32;
>>  	x->sel.proto = fl->proto;
>> diff --git a/net/ipv6/xfrm6_state.c b/net/ipv6/xfrm6_state.c
>> index 89884a4..60c78cf 100644
>> --- a/net/ipv6/xfrm6_state.c
>> +++ b/net/ipv6/xfrm6_state.c
>> @@ -34,6 +34,7 @@ __xfrm6_init_tempsel(struct xfrm_state *x, struct flowi *fl,
>>  	x->sel.dport_mask = htons(0xffff);
>>  	x->sel.sport = xfrm_flowi_sport(fl);
>>  	x->sel.sport_mask = htons(0xffff);
>> +	x->sel.family = AF_INET6;
>>  	x->sel.prefixlen_d = 128;
>>  	x->sel.prefixlen_s = 128;
>>  	x->sel.proto = fl->proto;
>
> Cheers,

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