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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID:  <m3hcc7ufgn.fsf@ursa.amorsen.dk>
Date:	Fri, 06 Jun 2008 10:37:12 +0200
From:	Benny Amorsen <benny+usenet@...rsen.dk>
To:	netdev@...r.kernel.org
Subject:  Re: How I can reset TCP sockets after long suspend/resume cyscle

Maxim Levitsky <maximlevitsky@...il.com> writes:

> This seems the right solution,
> if this is possible, why not to check for stuck TCP connections
> on resume?

Imagine a laptop on wireless going into suspend for a few minutes,
then getting woken up. If you're lucky today, the TCP connections
survive.

If you check for stuck TCP connections right after resume, you could
have problems because the wireless hasn't negotiated encryption keys
at that point. Isn't that a concern?

/Benny

--
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