netdev - Re: why would EPIPE cause socket port to change?

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: <20070123111858.GA29425@gondor.apana.org.au>
Date:	Tue, 23 Jan 2007 22:18:58 +1100
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	Michael Tokarev <mjt@....msk.ru>
Cc:	dean gaudet <dean@...tic.org>, netdev@...r.kernel.org
Subject: Re: why would EPIPE cause socket port to change?

On Tue, Jan 23, 2007 at 02:15:45PM +0300, Michael Tokarev wrote:
> 
> Still, after the connection has been closed, there's no chance to do
> anything with the filedescriptor but to close it as well, right?  Or
> can the fd be reused by making new connection with it, as if it were
> just returned from socket() call?

Yes you can connect out on it again if you're in TCP_CLOSE.  The fact
that the port number has changed implies that you've entered TCP_CLOSE.

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
-
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