From owner-freebsd-bugs@freebsd.org  Tue Dec  8 18:13:50 2015
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id DA7A09D3C08
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Tue,  8 Dec 2015 18:13:50 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id B157F193A
 for <freebsd-bugs@FreeBSD.org>; Tue,  8 Dec 2015 18:13:50 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tB8IDoE2054366
 for <freebsd-bugs@FreeBSD.org>; Tue, 8 Dec 2015 18:13:50 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 205144] [patch] make rsh(1) compatible with recent Cisco IOS
 versions
Date: Tue, 08 Dec 2015 18:13:50 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 10.2-STABLE
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: eugen@grosbein.net
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status keywords bug_severity priority component assigned_to
 reporter attachments.created
Message-ID: <bug-205144-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Dec 2015 18:13:50 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205144

            Bug ID: 205144
           Summary: [patch] make rsh(1) compatible with recent Cisco IOS
                    versions
           Product: Base System
           Version: 10.2-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Keywords: patch
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: eugen@grosbein.net
          Keywords: patch

Created attachment 163996
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=163996&action=edit
rsh.diff

It's not uncommon to run periodic jobs that use rsh(1) to connect to Cisco IOS
devices (routers, switches) to manage them or collect some information not
available via SNMP using "show ..." commands.

Our rsh(1) implementation does "shutdown(rem, SHUT_WR)" when it detects
"end-of-file" condition for standard input stream to inform remote host of EOF.
Jobs created with cron(8) have standard input redirected from /dev/null and
rsh(1) calls mentioned shutdown() just after connection is created.

Recent Cisco IOS versions (e.g. 15.x) close remote shell session immediately on
receiving such end-of-stream indication that results in empty output of "show
..." commands.

Attached patch introduces new "rsh -N" option that acts like opposite to 
"rsh -n" mode preventing shutdown of socket sending path. This prevents of
premature disconnect of rsh session by remote host.

-- 
You are receiving this mail because:
You are the assignee for the bug.