Re: openSSH and PATH

From: those who know me have no need of my name (not-a-real-address@usa.net)
Date: 01/29/02 

From: those who know me have no need of my name <not-a-real-address@usa.net>
Date: Tue, 29 Jan 2002 01:40:41 -0000

<Mnm58.3511$pb.983@nwrddc01.gnilink.net> divulged:
>"those who know me have no need of my name" <not-a-real-address@usa.net>
>wrote in message news:u5bg0orqcjru80@news.supernews.com...
>> <3c5586ac@news.uni-ulm.de> divulged:

>> >I have installed openSSH 3.0.2p1 successfully under DigitalUnix 4.0F.
>> >Now, when I logged in with ssh, my PATH is not correct! My homedirectory
>> >ist not in the searchpath and other paths are duplicated in the
>> >searchpath.
>>
>> those things are generally set by your system's login program. in
>> general ssh daemons do not invoke the system login program. you can
>> change that, in the sshd configuration.
>
>Umm. A lot of us prefer to use our .cshrc, .profile, or other shell
>configuration file, depending on your user's shell.

some people do replace their path, but most expect it to be initialized,
i.e., they use PATH=/new/path:$PATH. it's the difference in
initialization that can be important.

>There are some fairly
>strong historic reasons to avoid the use of /bin/login by SSH, mostly due to
>security issues between /bin/login on particular OS's and programs that are
>handing off login requests from a slightly different environment, namely
>that of sshd itself. Those are *hard* to control! Much better to avoid
>/bin/login and set it in the local shell profiles.

aye, sshd doesn't manage to hand off new connections to the system login
service properly in most revisions. this is a flaw in sshd. not one
that has stopped people from using it, mostly they just ignore the loss
of functionality in the hope that the gain in security is sufficient. 

-- 
okay, have a sig then

Relevant Pages

  • Re: openSSH and PATH
    ... >>ist not in the searchpath and other paths are duplicated in the ... > those things are generally set by your system's login program. ... > general ssh daemons do not invoke the system login program. ... A lot of us prefer to use our .cshrc, .profile, or other shell ...
    (comp.security.ssh)
  • Re: ftp access
    ... > On Tue, 27 Feb 2001, Brooks Davis wrote: ... Otherwise they can just use ssh to spawn a shell for themselves: ... via ssh unless you don't allow them to run ANYTHING via sshd. ...
    (FreeBSD-Security)
  • Re: The "USER" environment variable
    ... Alexander Skwar wrote: ... Which shell ... Logged in locally, via su, via ssh? ... sshd *does* set a USER environment variable, ...
    (comp.unix.solaris)
  • Re: Double /etc/issue
    ... BV> just fine from work to home, but when I do I get a double echo of ... It's probably being printed once by sshd, and once by your login program ... or shell. ...
    (comp.security.ssh)
  • Re: SFTP is not working
    ... When I try to use sftp or scp2, I get a message like this: ... sftp and scp2 both actually work by running ssh in a subprocess, ... The reason the shell startup files are relevant at all, ...
    (comp.security.ssh)