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 for Android: free password hash cracker in your pocket

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

Message-ID: <42440FDC.6000005@gmail.com>
Date: Fri Mar 25 13:20:04 2005
From: wireless.insecurity at gmail.com (Vladamir)
Subject: Reverse engineering the Windows TCP stack

So if it's BSD's work, and BSD behaves "correctly", why can't Windows?

James Longstreet wrote:
> On Thu, 24 Mar 2005, Tim wrote:
> 
> 
>>Last I read, the license requires credit be given where credit is due.
>>Maybe I missed it, but I haven't ever seen that credit be given in the
>>documentation shipped with Windoze.
> 
> 
> I don't know if it's credit per se, but I just ran strings on XP's
> finger.exe:
> 
> 
>><snip>
>>s_perror
>>MSWSOCK.dll
>>@(#) Copyright (c) 1980 The Regents of the University of California.
>> All rights reserved.
> 
> 
> I've done it with ftp.exe and a few others as well, I'd imagine most of
> those utilities were borrowed from BSD.
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
>