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: Sun, 10 Jul 2016 00:19:32 +0200 From: Hannes Frederic Sowa <hannes@...essinduktion.org> To: Bjørn Mork <bjorn@...k.no>, netdev@...r.kernel.org Cc: Valdis Kletnieks <Valdis.Kletnieks@...edu>, Jonas Lippuner <jonas@...puner.ca>, 吉藤英明 <hideaki.yoshifuji@...aclelinux.com> Subject: Re: [PATCH net] ipv6: addrconf: fix Juniper SSL VPN client regression Hi Bjorn, On Sat, Jul 9, 2016, at 23:13, Bjørn Mork wrote: > The Juniper SSL VPN client use a "tun" interface and seems to > be picky about visible changes.to it. Commit cc9da6cc4f56 > ("ipv6: addrconf: use stable address generator for ARPHRD_NONE") > made such interfaces get an auto-generated IPv6 link local address > by default, similar to most other interface types. This made the > Juniper SSL VPN client fail for unknown reasons. > > Fixing this regression by effectively reverting the behaviour to > what we had before, while keeping the new "addrgenmode random" > feature. I wonder if we can simply add a flag, something like IFF_SUPPRESS_AUTO_IPV6_LL, to net_device->priv_flags and use that. So we can keep behavior for qmi, vxlan-gpe and gre. tun is the only device that is really user space facing, so maybe we just limit it to this? Thanks, Hannes
Powered by blists - more mailing lists