Displaying 3 results from an estimated 3 matches for "remote_users_shel".
Did you mean:
remote_users_shell
2023 May 29
1
command [argument ...] in ssh(1): a footgun
...itself.
The footgun is unrelated to shells.
The SSH_MSG_CHANNEL_REQUEST protocol message for "exec" (RFC 4254)
channels which are used to run a single remote command contains
exactly one string for the command.
sshd (see bottom of do_child() in session.c) runs that command string as:
remote_users_shell -c command
//Peter
2023 May 29
1
command [argument ...] in ssh(1): a footgun
...ells.
>
> The SSH_MSG_CHANNEL_REQUEST protocol message for "exec" (RFC 4254)
> channels which are used to run a single remote command contains
> exactly one string for the command.
>
> sshd (see bottom of do_child() in session.c) runs that command string as:
>
> remote_users_shell -c command
I'm aware of that. That's why I said what I said.
Sorry, but I don't understand what point you are making.
> //Peter
2023 May 27
2
command [argument ...] in ssh(1): a footgun
On Sat, May 27, 2023 at 12:08:43AM +0200, Thorsten Glaser <t.glaser at tarent.de> wrote:
> On Fri, 26 May 2023, Mingye Wang (Artoria2e5) wrote:
>
> > ssh(1) currently affords an argument-passing functionality, but as the manpage
> > states, all arguments are simply concatenated by space.
>
> How else would it do that? The arguments are processed by the
> shell