Bug 24968
| Summary: | sshd: connections using '-t' always run a shell, not what was specified. | ||
|---|---|---|---|
| Product: | Base System | Reporter: | kway <kway> |
| Component: | misc | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | 4.2-STABLE | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
kway
2001-02-09 16:30:01 UTC
On Fri, Feb 09, 2001 at 07:36:39AM -0800, kway@wgate.com wrote: > > >Number: 24968 > >Category: misc > >Synopsis: sshd: connections using '-t' always run a shell, not what was specified. > >Originator: Kevin Way > >Release: FreeBSD 4.2-STABLE : Fri Jan 12 > >Organization: > >Environment: > FreeBSD way.eng.tvol.net 4.2-STABLE FreeBSD 4.2-STABLE #0: Fri Jan 12 15:15:31 EST 2001 root@way.eng.tvol.net:/usr/obj/usr/src/sys/KEVIN i386 > >Description: > sshd fails to run the specified command if the client specifies the -t option. instead it ALWAYS runs an interactive shell. This behaviour differs from the previous version of OpenSSH. > >How-To-Repeat: > ssh machine uname -a, and you'll get results > ssh -t machine uname -a, and you'll get a login shell Hmm. Doesn't seem that way to me: [roam@ringworld:v2 ~]$ ssh -t localhost uname -a roam@localhost's password: FreeBSD ringworld.oblivion.bg 4.2-STABLE FreeBSD 4.2-STABLE #10: Fri Feb 9 12:08:48 EET 2001 root@ringworld.oblivion.bg:/usr/obj/usr/src/sys/RINGWORLD i386 Connection to localhost closed. [roam@ringworld:v2 ~]$ Hmm.. when did OpenSSH-2.3.0 hit -stable? This correct behavior with mine just might be because of something that is different in 2.3.0. G'luck, Peter -- What would this sentence be like if it weren't self-referential? > > >How-To-Repeat: > > ssh machine uname -a, and you'll get results > > ssh -t machine uname -a, and you'll get a login shell > > Hmm. > Doesn't seem that way to me: > > [snip successful use of ssh -t] > > Hmm.. when did OpenSSH-2.3.0 hit -stable? This correct behavior with mine > just might be because of something that is different in 2.3.0. This was a bug in OpenSSH 2.3.0 as a result of some FreeBSD modifications. It was fixed in -current on the 21st of January in src/crypto/openssh/session.c: ---------------------------- revision 1.13 date: 2001/01/21 05:45:27; author: green; state: Exp; lines: +2 -2 Actually propagate back to the rest of the application that a command was specified when using -t mode with the SSH client. Submitted by: Dima Dorfman <dima@unixfreak.org> ---------------------------- It was merged to RELENG_4 on the 4th (see rev. 1.4.2.7). Dima Dorfman dima@unixfreak.org State Changed From-To: open->feedback Can you try updating your -STABLE sources, and see if this works for you, as Dima Dorfman explained it should with sources after Feb 4th? State Changed From-To: feedback->closed Closed at originator's request. |
