TCP vulnerability

Mailman List Mirror (Read Only)
1

In message <1386.64.235.224.55.1082482608.squirrel@mail.mzima.net>you write:

Since no one's mentioned it yet, apparently there was a change in plans.
It was just released a day early.

This is because of the story at http://www.washingtonpost.com/, in the
Technology section.

Thanks,
..Aviva

2

I suggest an extensive late-night BOF in San Francisco in the bar to discuss the mechanics of adding MD5 keys to all your sessions in 48 hours. Evidence of RSI and eyesight failure will be mandatory, along with battle stories about rt2 mail-loops and rancid-scraping awk scripts gone mad.

Joe

3

I suggest an extensive late-night BOF in San Francisco in the bar to
discuss the mechanics of adding MD5 keys to all your sessions in 48
hours. Evidence of RSI and eyesight failure will be mandatory

for those who prefer to be keyboard monkeys all their lives instead
of building tools to configure and manage networks

randy

4

I considered that, but I figured it would take longer to make a tool which could deal with the ten thousand ways that people want to coordinate this change (*and* speak to them over the phone) than it would to just get on and do it.

The passwords were generated, the databases were populated and the rt2 tickets were opened using a magnificent lump of awk though, if I do say so myself.

Joe

5

Zeitgeist at 7pm or the Toronado at 9pm?