Yet another correction to the TCP exploit workaround (and now I know WHY!)

Painfully, the corrected workaround turns out to have another version of
the same problem in it. And now I know why -- an SMTP directive deep in
my mailing list configuration files turns out to incorrectly insert "/" in
a set of extremely rare circumstances that these messages today have
triggered. Since I didn't write the original configuration the actual
purpose for this is not clear -- and it does appear to be purposeful.
It's probably been in there from original configurations used well more
than 10 years ago and updated over time. This has now been removed.

So let's try this again. As Bullwinkle would say: "This time for sure!"

Here's a fragment from /etc/sysctl.conf on one of my machines, in this case
one to permit packet forwarding:

net.ipv4.ip_forward=1

This shows the standard format of the directives.

The workaround for the TCP exploit requires adding:

net.ipv4.tcp_challenge_ack_limit = 999999999

So in MY case we end up with:

net.ipv4.ip_forward=1
net.ipv4.tcp_challenge_ack_limit = 999999999

Write out the file, then use:

sysctl -p

(or presumably you could restart the "procps" service on various systems)

and you should be good to go for now.

I just love stealth bugs deep in mail systems. Yeah.

--Lauren--
Lauren Weinstein ([email protected]): https://www.vortex.com/lauren 
Lauren's Blog: https://lauren.vortex.com
Founder: Network Neutrality Squad: https://www.nnsquad.org 
         PRIVACY Forum: https://www.vortex.com/privacy-info
Co-Founder: People For Internet Responsibility: https://www.pfir.org/pfir-info
Member: ACM Committee on Computers and Public Policy
Google+: https://google.com/+LaurenWeinstein
Twitter: https://twitter.com/laurenweinstein
Tel: +1 (818) 225-2800
I have consulted to Google, but I am not currently 
doing so -- my opinions expressed here are mine alone.
 - - -
The correct term is "Internet" NOT "internet" -- please don't 
fall into the trap of using the latter. It's just plain wrong!
_______________________________________________
pfir mailing list
https://lists.pfir.org/mailman/listinfo/pfir

Reply via email to