Date: Thu, 9 Mar 2000 02:20:33 -0500 From: Matt Heckaman <matt@ARPA.MAIL.NET> To: Nino Dehne <dehne@c-nit.de> Cc: FreeBSD-STABLE <stable@freebsd.org> Subject: Re: ssh1 + openssh 1.2.2 + tcsh 6.09.00 Message-ID: <Pine.BSF.4.21.0003090216590.1508-100000@epsilon.lucida.qc.ca> In-Reply-To: <Pine.BSF.4.21.0003090802290.6577-100000@gateway.tcm.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 9 Mar 2000, Nino Dehne wrote: [...] : i've discovered the same problem here, every command directly executed : with ssh <host> <command> makes the login shell die, no matter which one : it is. on both sides ssh version is: I did not try that, as that's a feature I very rarely use. If I didn't have a large assignment do, I'd go try that right now - but I'll get back to you on it.. [...] : one small "solution" i've found to work is to set "UseLogin" to "no" in : the sshd_config. I did not try that, as I feel it's unacceptable to run ssh without the UseLogin option in my situation, I have my reasons for that. It is a valid feature, it should work, yes? [...] : btw, can it be considered a security risk if users are able to execute a : shell with ssh <host> /bin/sh directly? i'm asking because this way no : utmp entry is generated and the user is invisible in w/who/etc. outputs.. As far as I know, there are reasons for this - I feel that relying solely on something like utmp/w/who/etc is at best unreliable. There are numerous other ways to produce this same result. -Matt : regards, : : nino : : -- : there are 3 kinds of people: those who can count & those who can't [...] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0003090216590.1508-100000>