| 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: <20091020221354.5a714323.billfink@mindspring.com> Date: Tue, 20 Oct 2009 22:13:54 -0400 From: Bill Fink <billfink@...dspring.com> To: Gilad Ben-Yossef <gilad@...efidence.com> Cc: netdev@...r.kernel.org, ori@...sleep.com Subject: Re: [PATCH RFC] Per route TCP options On Tue, 20 Oct 2009, Gilad Ben-Yossef wrote: > Turn the global sysctls allowing disabling of TCP SACK, DSCAK, > time stamp and window scale into per route entry feature options, > laying the ground to future removal of the relevant global sysctls. > > You really only want to disable SACK, DSACK, time stamp or window > scale if you've got a piece of broken networking equipment somewhere > as a stop gap until you can bring a big enough hammer to deal with > the broken network equipment. It doesn't make sense to "punish" the > entire connections going through the machine to destinations not > related to the broken equipment. For certain test situations, it is sometimes desirable to globally disable TCP timestamps. Although I have not personally wanted to globally disable the other mentioned features, I can imagine test scenarios where it could be useful. Admittedly it could also be accomplished with per route features, just not as conveniently, especially if there are a large number of interfaces and/or routes. -Bill -- 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