| 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: Fri, 27 Mar 2009 15:46:28 -0700 (PDT) From: David Miller <davem@...emloft.net> To: ram.vepa@...erion.com Cc: netdev@...r.kernel.org Subject: Re: [net-2.6 PATCH 1/9] Neterion: Driver help file From: Ramkrishna Vepa <ram.vepa@...erion.com> Date: 27 Mar 2009 14:54:08 -0800 I'm not apply any of this patch set. > +4) Performance Suggestions: > +--------------------------- > + > +- Set MTU to maximum - 9000 for switch setup, 9600 for back-to-back. > +For MTU 1500: > +------------- > +### IPV4 specific settings > +# turns TCP timestamp support off, default 1, reduces CPU use > +$sysctl -w net.ipv4.tcp_timestamps = "0" You have got to be kidding me. I see this garbage in the "tuning suggestions" sections of various manuals of proprietary products for Linux. But there is no way I'm letting this junk slip into Linux proper too. All of these suggestions are ill founded, have side effects that are not even passively mentioned in these "suggestions", and are even dangerous. Do you even know the security implications of turning off TCP timestamps? Do you know or even feel the need to mention the performance implications over long haul networks of turning timestamps off? If the default sysctl parameters are not correct, let's fix them instead of telling every user how to break their system with "tweaks". -- 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