Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

Re: ERRATA : interactive and login shells: bug or design decision ?

Subject: Re: ERRATA : interactive and login shells: bug or design decision ?
Date: Thu, 24 Mar 2005 12:16:23 -0500
On Thu, Mar 24, 2005 at 02:44:42PM +0100, Cristian Zoicas wrote:
When I execute: <ssh user@somesite.com>,  I get a login shell, but
when I execute: <ssh user@somesite.com command>, command does not run
      under a login shell.

Correct.

The question is the same: Is this behaviour a bug or a design decision ?

It's intentional.

If it is a design decision, then what are the reasons to have it like this.

Because login shells are only used when you log in.  Firing off a
background task should not welcome you to the system, show you the
messages of the day, inform you whether you have new mail, give you a
random fortune cookie, etc.  That sort of stuff should only be done when
you log in.

<Prev in Thread] Current Thread [Next in Thread>