netdev - Re: when having to acquire an SA, ipsec drops the packet

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]

Message-Id: <1173201286.3085.80.camel@faith.austin.ibm.com>
Date:	Tue, 06 Mar 2007 11:14:46 -0600
From:	Joy Latten <latten@...tin.ibm.com>
To:	James Morris <jmorris@...ei.org>
Cc:	davem@...emloft.net, herbert@...dor.apana.org.au,
	netdev@...r.kernel.org, paul.moore@...com, vyekkirala@...stedCS.com
Subject: Re: when having to acquire an SA, ipsec drops the packet

On Mon, 2007-03-05 at 22:21 -0500, James Morris wrote:
> On Mon, 5 Mar 2007, Joy Latten wrote:
> 
> > 5. Around the time the set of SAs for OUT direction are to be
> >    inserted into SAD, I see another ACQUIRE happening.
> >    
> >    I have not yet figured out where this second ACQUIRE comes from
> >    and why it happens. As long as the minimal SA or set of valid outgoing
> >    SAs exist in SAD, an ACQUIRE should not happen.
> 
> I saw something similar to this some time ago when testing various 
> failure modes, and discused it with Herbert.
> 
> IIRC, there's a larval SA which is not torn down properly by Racoon once 
> the full SA is established, and the larval SA keeps resending until it 
> times out.
> 
Ok, good to know. 
I thought a bit more about this last night but am not
sure best way to fix it. Perhaps a way to keep larval
SA around until all SAs resulting from xfrm_vec[xfrm_nr]
are established... oh well, just thinking out loud... :-) 


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