Re: Provide a way to source shell-specific startup files for noninteractive commands

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

 



On 22.05.2022 2:00, Thorsten Glaser wrote:
On Sun, 22 May 2022, Ivan Pozdeev wrote:

2) In addition to `~/.ssh/rc`, source `~/.ssh/<shell>rc`, and do that in the
As shell maintainer, I’d be very cross if this happened.

The shell manpages clearly document in which circumstances
their various startup files are sourced. If you need to
have them sourced, fulfill the respective requirements;
usually, this means use the ssh(1) -t option.

From what I can see, there's no way to pass options to the shell that would run the command.
As per https://github.com/openssh/openssh-portable/blob/bedb93415b60db3dfd704a3d525e82adb14a2481/session.c#L1709-L1713 ,
it's always run as `<shell> -c <command>` which makes it non-login and non-interactive regardless of whether a terminal is allocated.

bye,
//mirabilos

--
Regards,
Ivan

_______________________________________________
openssh-unix-dev mailing list
openssh-unix-dev@xxxxxxxxxxx
https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev




[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux