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
| ||
|
Date: Wed, 5 Dec 2007 18:39:27 +1100 From: Herbert Xu <herbert@...dor.apana.org.au> To: David Miller <davem@...emloft.net> Cc: simon@...e.lp0.eu, linux-kernel@...r.kernel.org, netdev@...r.kernel.org Subject: Re: sockets affected by IPsec always block (2.6.23) On Tue, Dec 04, 2007 at 11:34:32PM -0800, David Miller wrote: > > TCP has some built-in assumptions about characteristics of > interent links and what constitutes a timeout which is "too long" > and should thus result in a full connection failure. > > IPSEC changes this because of IPSEC route resolution via > ISAKMP. > > With this in mind I can definitely see people preferring > the "block until IPSEC resolves" behavior, especially for > something like, say, periodic remote backups and stuff like > that where you really want the thing to just sit and wait > for the connect() to succeed instead of failing. Hmm, but connect(2) should succeed in that case thanks to the blackhole route, no? The subsequent SYNs will then be dropped until the IPsec SAs are in place. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists