search for: remotecommand

https://bugzilla.mindrot.org/show_bug.cgi?id=1815 Summary: RemoteCommand and PseudoTTY config options Product: Portable OpenSSH Version: 5.1p1 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: ssh AssignedTo: unassigned-bugs at mindrot.org...

https://bugzilla.mindrot.org/show_bug.cgi?id=3209 Bug ID: 3209 Summary: Make overriding RemoteCommand on the cli easier Product: Portable OpenSSH Version: 8.3p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-bugs at mindrot.org Report...

...ter: daniel.black at ovee.com.au feature request for remote command to be allowed to be specified in the ssh_config. What I'd like this for is to set up entries like: host client-tx-web02-console user clientname hostname lish-dallas.linode.com RequestTTY force RemoteCommand tx-web02 This would be for Linode's lish console but other uses are convenient: ( https://blog.linode.com/2013/04/30/lish-ssh-gateway/ ) This perhaps would solve part the requirement in #1368 too. -- You are receiving this mail because: You are watching the assignee of the bug.

...anged: What |Removed |Added ---------------------------------------------------------------------------- CC| |gtisza at gmail.com --- Comment #5 from Tisza Gerg? <gtisza at gmail.com> --- One possible use case for RemoteCommand would be to set different prompts on certain machines (e.g. if we SSH to the production server, change the prompt to red). This could be done via sshrc, but that might be inconvenient or controversial if the remote account is used by many different people. -- You are receiving this mail because:...

https://bugzilla.mindrot.org/show_bug.cgi?id=2558 Bug ID: 2558 Summary: Add RemoteCommand option to ssh client Product: Portable OpenSSH Version: 7.2p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: ssh Assignee: unassigned-bugs at mindrot.org Rep...

...5714 that this isn't a unique wish, and existing solutions are kind of baroque. Typical reasons to do this are to immediately go into a screen or tmux session; for myself, I often want to relaunch bash as "bash -lo vi" on boxes where I don't have bashrc control. Basically, we want RemoteCommand to be turned on for interactive sessions, but ignore it when we've already specified a command as part of the client invocation. I wondered if there would be support for, or interest in, adding a new condition called "interactive" (or similar) to the Match keyword? Although my use ca...

...39;t a unique > wish, and existing solutions are kind of baroque. Typical reasons to do > this are to immediately go into a screen or tmux session; for myself, I > often want to relaunch bash as "bash -lo vi" on boxes where I don't have > bashrc control. Basically, we want RemoteCommand to be turned on for > interactive sessions, but ignore it when we've already specified a command > as part of the client invocation. > > I wondered if there would be support for, or interest in, adding a new > condition called "interactive" (or similar) to the Match key...

...nd they will immediately be dropped back into their old session with all the context like they left it. Right now, I have two different approaches to this, both of which have some problems. The first thing I tried is setting up some config on the local machine in `~/.ssh/config` to make use of the RemoteCommand and LocalCommand options. I basically want to do the equivalent of sshing in and immediately running `tmux attach-session -t tty-1` (though for my tool the attach command obviously looks a bit different). The tricky bit is that I can't write down the name of the local tty in my RemoteCommand be...

...a > unique wish, and existing solutions are kind of baroque. Typical > reasons to do this are to immediately go into a screen or tmux > session; for myself, I often want to relaunch bash as "bash -lo > vi" on boxes where I don't have bashrc control. Basically, we want > RemoteCommand to be turned on for interactive sessions, but ignore > it when we've already specified a command as part of the client > invocation. > > I wondered if there would be support for, or interest in, adding a > new condition called "interactive" (or similar) to the Match key...

Hey Damien, > Would something like this help? > > Match sessiontype shell > User foo > Match remotecommand "none" > User foo2 > Match sessiontype exec remotecommand "/rsync" > User bar > Match sessiontype subsystem remotecommand "sftp" > User baz > > > diff --git a/readconf.c b/readconf.c > <snip> Thanks for looking into it, much apprecia...

https://bugzilla.mindrot.org/show_bug.cgi?id=1815 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #9 from Damien Miller <djm at mindrot.org> --- Close all resolved bugs after 7.3p1 release

On Mon, 6 May 2024, openssh at tr.id.au wrote: > Hey Damien, > > > Would something like this help? > > > > Match sessiontype shell > > User foo > > Match remotecommand "none" > > User foo2 > > Match sessiontype exec remotecommand "/rsync" > > User bar > > Match sessiontype subsystem remotecommand "sftp" > > User baz > > > > > > diff --git a/readconf.c b/readconf.c > > <snip&g...

Dear OpenSSH developers, I hope you don't mind that I resubmit my patch for OpenSSH. This patch adds a new ssh_config option "ExecRemoteCommand", which is the missing equivalent to the "-N" command line option. For implementation notes, please have a look at the top of the patch. Regards, Volker -- Volker Diels-Grabsch ----<<<((()))>>>---- -------------- next part -------------- A non-text attachment w...

...and != NULL && sshbuf_len(rcommand) > 0) + criteria = xstrdup("exec"); + else + criteria = xstrdup("shell"); + r = match_pattern_list(criteria, arg, 0) == 1; + if (r == (negate ? 1 : 0)) + this_result = result = 0; + } else if (strcasecmp(attrib, "remotecommand") == 0) { + if (rcommand != NULL && sshbuf_len(rcommand) > 0) { + if ((criteria = + sshbuf_dup_string(rcommand)) == NULL) + fatal_f("dup command failed"); + } else if (options->remote_command != NULL) + criteria = xstrdup(options->remote_command)...

... and I guess your next question will be about compilation environment, so: ``` $ gcc --version gcc (Gentoo 13.2.1_p20240210 p14) 13.2.1 20240210 Copyright (C) 2023 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ``` I'm running on gentoo. I tested that the

https://bugzilla.mindrot.org/show_bug.cgi?id=3456 Bug ID: 3456 Summary: provide a way to have forwardings killed, when the remote command/shell finishes Product: Portable OpenSSH Version: v9.0p1 Hardware: Other OS: All Status: NEW Severity: enhancement Priority: P5

Hi, I'm working on a program (for Linux) that uses OpenSSH with multiplexing and X11 forwarding. The first call to ssh has arguments -MNfX, so the connection is only established. Later, remote commands using X are called with "ssh -S path -fX remoteCommand". For some obscure reason, this does not work from my program, which is also responsible for starting the X server and setting the authorizations. I have tried everything I could think of, without success. It seems that the problem come from the first call to ssh. There must be something my pr...

...s at underscores, rather than whitespace. Let's summarize the general situation, though: -- We cannot reduce the local shell's influence re: quoting to zero as that's what the (interactive) user uses to input the (remote) command in the first place. (Ignoring the possibility of RemoteCommand in a (pseudo?) config file for the moment.) -- We cannot reduce the remote shell's influence to zero as long as sshd(8) uses that to execute the command. -- If we avoid that and execv() the command directly, we make the UI disparate from what the user experiences with an interactive...

...inting of results directly in SSHFP format. bz#2821 * regress tests: fix PuTTY interop test broken in last release's SSHv1 removal. bz#2823 * ssh(1): Compatibility fix for some servers that erroneously drop the connection when the IUTF8 (RFC8160) option is sent. * scp(1): Disable RemoteCommand and RequestTTY in the ssh session started by scp (sftp was already doing this.) * ssh-keygen(1): Refuse to create a certificate with an unusable number of principals. * ssh-keygen(1): Fatally exit if ssh-keygen is unable to write all the public key during key generation. Previously it...

...===== This is primarily a bugfix release. It also contains substantial internal refactoring. Security -------- * sftp-server(8): in read-only mode, sftp-server was incorrectly permitting creation of zero-length files. Reported by Michal Zalewski. New Features ------------ * ssh(1): add RemoteCommand option to specify a command in the ssh config file instead of giving it on the client's command line. This allows the configuration file to specify the command that will be executed on the remote host. * sshd(8): add ExposeAuthInfo option that enables writing details of the authen...