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

Message-ID: <1924840002.20050331215233@Sniff-em.com>
Date: Thu Mar 31 20:52:44 2005
From: Thierry at sniff-em.com (Thierry Zoller)
Subject: Reverse engineering the Windows TCP stack

Dear Pretty,

<Afaik>
That key does indeed control the number of times windows retries to
connect, *but* its not supposed to take that number into account
after it recieved an RST packet, it's supposed to act that way
when no answer is received at all.
</Afaik>

pv> TcpMaxConnectRetransmissions
pv> Key: Tcpip\Parameters
pv> Value Type: REG_DWORD - Number
pv> Valid Range: 0 - 0xFFFFFFFF
pv> Default: 5
pv> Description: This parameter determines the number of times that TCP
pv> retransmits a connect request (SYN) before aborting the attempt. The
pv> retransmission timeout is doubled with each successive retransmission in a
pv> particular connect attempt. The initial timeout value is three seconds.

-- 
Thierry Zoller