netdev - Re: [PATCH net-next] tcp: avoid tcp loop connection on lo device

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: <20120925.130436.2297001740930119160.davem@davemloft.net>
Date:	Tue, 25 Sep 2012 13:04:36 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	shanwei88@...il.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH net-next] tcp: avoid tcp loop connection on lo device

From: Shan Wei <shanwei88@...il.com>
Date: Tue, 25 Sep 2012 16:12:34 +0800

> Tcp supports simultaneous Connection, but we meat odd phenomenon
> that tcp client can receive what send by itself. tcp client and tcp
> server communicate through loop device. tcp server selects port
> 40000 to listen which is in local port range. But after tcp server
> program is killed, tcp client still can connect successfully.

This is expected behavior and we're not special casing this after
it being this way for 20+ years.
--
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