From owner-freebsd-stable Wed Mar 8 23:20:44 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail4.uunet.ca (mail4.uunet.ca [209.167.141.34]) by hub.freebsd.org (Postfix) with ESMTP id CFBE537B759 for ; Wed, 8 Mar 2000 23:20:40 -0800 (PST) (envelope-from matt@ARPA.MAIL.NET) Received: from epsilon.lucida.qc.ca ([216.95.146.6]) by mail4.uunet.ca with ESMTP id <211113-9871>; Thu, 9 Mar 2000 02:20:33 -0500 Date: Thu, 9 Mar 2000 02:20:33 -0500 From: Matt Heckaman X-Sender: matt@epsilon.lucida.qc.ca To: Nino Dehne Cc: FreeBSD-STABLE Subject: Re: ssh1 + openssh 1.2.2 + tcsh 6.09.00 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 9 Mar 2000, Nino Dehne wrote: [...] : i've discovered the same problem here, every command directly executed : with ssh 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 /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