Bug 1746 - unexpected warning for mux control commands when stdin is not connected to a tty
Summary: unexpected warning for mux control commands when stdin is not connected to a tty
Status: CLOSED FIXED
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: ssh (show other bugs)
Version: 5.4p1
Hardware: All OpenBSD
: P2 minor
Assignee: Assigned to nobody
URL:
Keywords:
Depends on:
Blocks: V_5_6
  Show dependency tree / graph
 
Reported: 2010-03-27 11:26 AEDT by Salvador Fandiño
Modified: 2011-01-24 12:33 AEDT (History)
1 user (show)

See Also:

Attachments
/tmp/hushmuxtty.diff (541 bytes, patch)
2010-03-27 13:06 AEDT, Damien Miller 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Salvador Fandiño 2010-03-27 11:26:04 AEDT 
Example:

$ ssh -O check -S /foo/bar -- host </dev/null
Pseudo-terminal will not be allocated because stdin is not a terminal.

Is there any reason to force tty allocation when a mux command is given?

As a workaround -T can be used:
$ ssh -T -O check -S /foo/bar -- host </dev/null
Comment 1 Damien Miller 2010-03-27 13:06:20 AEDT 
Created attachment 1825 [details]
/tmp/hushmuxtty.diff

hush TTY warning for -O
Comment 2 Damien Miller 2010-03-27 13:08:21 AEDT 
It was just a bogus warning, no TTY handling is performed when executing mux commands.
Comment 3 Damien Miller 2010-04-10 15:53:56 AEST 
patch applied - will be in OpenSSH 5.6p1.
Comment 4 Damien Miller 2011-01-24 12:33:59 AEDT 
Move resolved bugs to CLOSED after 5.7 release