full-disclosure - Reverse engineering the Windows TCP stack

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1ca1c14105032521066831b1b0@mail.gmail.com>
Date: Sat Mar 26 05:06:26 2005
From: synfinatic at gmail.com (ADT)
Subject: Reverse engineering the Windows TCP stack

Ok, so how does it behave inconsistently?  Can you give any examples
that we might be able to replicate?

-ADT

On Fri, 25 Mar 2005 21:28:45 -0500, Vladamir
<wireless.insecurity@...il.com> wrote:
> I never said it incorrectly behaved, I said it inconsistently behaves.
> 
> Thierry Zoller wrote:
> > Dear Vladamir,
> >
> > V> So if it's BSD's work, and BSD behaves "correctly", why can't Windows?
> > You still failed to give us any info on how Windows behaves
> > incorrectly. I may have msised it though