[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#571613: marked as done (openssh: tty allocation is not properly documented)



Your message dated Sat, 22 Aug 2015 10:33:52 +0100
with message-id <20150822093352.GV2382@riva.ucam.org>
and subject line Re: Bug#571613: openssh: tty allocation is not properly documented
has caused the Debian Bug report #571613,
regarding openssh: tty allocation is not properly documented
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
571613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571613
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: openssh
Version: 1:5.3p1-2
Severity: minor

It seems that by default (i.e. without -t or -T ssh option), tty
allocation is done only when one doesn't provide a command. If
the user provides a command, no tty allocation occurs by default:

ypig:~> ssh localhost echo \$TERM

ypig:~> ssh -t localhost echo \$TERM
xterm-debian
Connection to localhost closed.

This behavior is not documented in the ssh/sshd man pages.

In the ssh man page, I can only see:

  If a pseudo-terminal has been allocated (normal login session), the
  user may use the escape characters noted below.

but this is very ambiguous (what is a "normal login session"?).
Also, I wonder whether there's a difference between "pseudo-tty"
and "pseudo-terminal"; the man page should be consistent.

The sshd man page has:

  command="command"
    Specifies that the command is executed whenever this key is used
    for authentication.  The command supplied by the user (if any) is
    ignored.  The command is run on a pty if the client requests a
    pty; otherwise it is run without a tty. [...]

but this is just documentation about command="...".

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash



--- End Message ---
--- Begin Message ---
Source: openssh
Source-Version: 1:6.9p1-1

This was fixed upstream in OpenSSH 6.9.

-- 
Colin Watson                                       [cjwatson@debian.org]

--- End Message ---

Reply to: