netdev - Re: How I can reset TCP sockets after long suspend/resume cyscle

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: <484702EC.30209@hp.com>
Date:	Wed, 04 Jun 2008 14:02:36 -0700
From:	Rick Jones <rick.jones2@...com>
To:	Stephen Hemminger <shemminger@...tta.com>
CC:	Adam Langley <agl@...erialviolet.org>,
	Maxim Levitsky <maximlevitsky@...il.com>,
	netdev@...r.kernel.org
Subject: Re: How I can reset TCP sockets after long suspend/resume cyscle

While I know of at least one OS/stack which allows a root user to issue 
a command to abort a TCP connection, (and it may be two given their 
shared history) its use was always strongly discouraged.

> TCP should recover from this anyway. As soon as any activity happens
> on the connection the other end will respond with reset.  For an IMAP
> session doing the next get-mail should cause a connection reset.
> Now it is possible that mail client has other problems.

And one way for there to be activity would be for the application(s) in 
question to have an application-layer keepalive mechanism, or at the 
very least, set SO_KEEPALIVE on their connections.  And if they don't 
want to rely on the sysadmin to have set what they consider a 
"reasonable" value for when to start sending keepalive probes, a 
TCP_KEEPIDLE setsockopt() perhaps.

rick jones
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html