full-disclosure - Re: Vulnerability in TCP

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <AANLkTimYAWAtj99GZPYWJpCfsLiHLGHHoZIKDyqfwtxn@mail.gmail.com>
Date: Sat, 26 Jun 2010 05:11:41 -0300
From: Fernando Gont <fernando.gont@...il.com>
To: Valdis.Kletnieks@...edu
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: Vulnerability in TCP

On Fri, Jun 25, 2010 at 10:14 PM, <Valdis.Kletnieks@...edu> wrote:

The problem was known for a long time before that:
> R.T. Morris, "A Weakness in the 4.2BSD UNIX TCP/IP Software",
> CSTR 117, 1985, AT&T Bell Laboratories, Murray Hill, NJ.
> http://pdos.csail.mit.edu/~rtm/papers/117-abstract.html<http://pdos.csail.mit.edu/%7Ertm/papers/117-abstract.html>
>
> Any vendor still botching it in 2010 deserves to be mocked mercilessly.
>

 FWIW, CPNI (http://www-cpni.gov.uk) published a very thorough technical
report on TCP security:
http://www.cpni.gov.uk/Docs/tn-03-09-security-assessment-TCP.pdf

An the IETF is currently workin on a RFC version of it:
http://tools.ietf.org/id/draft-ietf-tcpm-tcp-security-01.txt . This one is
the original IETF individual submission, which contains those sections that
have not yet been commited to the IETF-adopted one:
http://tools.ietf.org/id/draft-gont-tcp-security-00.txt

Thanks,
Fernando Gont

Content of type "text/html" skipped

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/