From owner-freebsd-hackers@FreeBSD.ORG  Mon Jul 22 07:28:06 2013
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id CA3B09B0
 for <freebsd-hackers@freebsd.org>; Mon, 22 Jul 2013 07:28:06 +0000 (UTC)
 (envelope-from adrian.chadd@gmail.com)
Received: from mail-we0-x230.google.com (mail-we0-x230.google.com
 [IPv6:2a00:1450:400c:c03::230])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 654C92659
 for <freebsd-hackers@freebsd.org>; Mon, 22 Jul 2013 07:28:06 +0000 (UTC)
Received: by mail-we0-f176.google.com with SMTP id q57so2209498wes.21
 for <freebsd-hackers@freebsd.org>; Mon, 22 Jul 2013 00:28:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date
 :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
 bh=ihbIJFIMquOk5/ILHRRwZ8jyjmuU5dQN4pUY9+B4F3M=;
 b=Fedae18RLXIic96bDTppduCYXUhr/RT47cV2Varu7OE7+g36aMGaYhPWS2kA5oFQnl
 xIo44sf8Rf1/Zk5vFxRWy0902/A5o75fN5k2+M+Oh8AcOcHz4lNYgbpRFP1JmwVDdHbc
 MPFAdjWpXK/hvxQmN8m2S8vDCIYX4KRvGL6L+zWHHLdTp80kVF+JV0WxcsRnLoMAL4te
 vVMKKowdqlFYH12VToeTdD4DzIl9j0pffrBry8jUhQGMD7WsseFTjFkEkslMlUG7pSFb
 zpOVnNq6HFhjO2YBYsJVXBvW6nBDpHWxFsfb66jn8sPbR3DIBwdhIBwtxWRkdIVm6uds
 uWmQ==
MIME-Version: 1.0
X-Received: by 10.194.63.229 with SMTP id j5mr18146115wjs.79.1374478084717;
 Mon, 22 Jul 2013 00:28:04 -0700 (PDT)
Sender: adrian.chadd@gmail.com
Received: by 10.217.94.132 with HTTP; Mon, 22 Jul 2013 00:28:04 -0700 (PDT)
In-Reply-To: <94798.1374462380@server1.tristatelogic.com>
References: <CAJ-VmonDfzG7H1pPOxt+PTpdigrzuGe8di8zhoUsLGi3cGZAXA@mail.gmail.com>
 <94798.1374462380@server1.tristatelogic.com>
Date: Mon, 22 Jul 2013 00:28:04 -0700
X-Google-Sender-Auth: NspVAktLy2RD8njSduNhI2F-11k
Message-ID: <CAJ-VmokAhE+uy4-3QAW6mK__sgw+L2_Y6M29O_+X+Ak5hoaW6Q@mail.gmail.com>
Subject: Re: bin/176713: [patch] nc(1) closes network socket too soon
From: Adrian Chadd <adrian@freebsd.org>
To: "Ronald F. Guilmette" <rfg@tristatelogic.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: freebsd-hackers@freebsd.org
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jul 2013 07:28:06 -0000

Right. Yes, I had a typo. I meant that it shouldn't die on seeing a
read EOF after closing the write side of the socket.

So, what you're saying is:

* nc sees EOF on stdin
* nc decides to abort before seeing the rest of the data come in from
the remote socket (and then trying to write it, and aborting if it
sees EOF on stdin _and_ EOF/error on writing to stdout)

Right?


-adrian