| 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
| ||
|
Message-ID: <20111109032729.GA11312@gondor.apana.org.au> Date: Wed, 9 Nov 2011 11:27:30 +0800 From: Herbert Xu <herbert@...dor.apana.org.au> To: Daniil Stolnikov <danila.st@...l.ru> Cc: davem@...emloft.net, linux-kernel@...r.kernel.org, netdev@...r.kernel.org, linux-crypto@...r.kernel.org, linux-security-module@...r.kernel.org, adobriyan@...il.com, peter.p.waskiewicz.jr@...el.com Subject: Re: Add IPSec IP Range in Linux kernel Daniil Stolnikov <danila.st@...l.ru> wrote: >> Like I said, if you want address ranges, ask the userland IPSEC daemon >> authors to synthesize it. > > In this letter, the mailing list http://marc.info/?l=strongswan-users&m=130613736616488&w=4 strongswan-users say that their product has support for IP ranges, but the stack of Linux is based on network masks. So I do not understand how this would work without the support at the kernel level? How will coordination of policies? Simple, you break a range policy into parts that can be expressed as network/mask and install multiple policies. The actual policies in the kernel just has to have the same effect as the one you negotiated with the other side, it does not have to look the same. This is also why you can do the same thing with masks + netfilter. Cheers, -- Email: Herbert Xu <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 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