Skip to main content
25 events
when toggle format what by license comment
Apr 26, 2022 at 21:05 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Dec 24, 2021 at 17:03 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Aug 20, 2021 at 14:02 history bumped CommunityBot This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Jul 11, 2021 at 3:43 answer added Nassim Bentarka timeline score: 1
Apr 13, 2017 at 12:36 history edited CommunityBot
replaced http://unix.stackexchange.com/ with https://unix.stackexchange.com/
Feb 16, 2016 at 16:04 comment added Mark Plotnick Judging from that error message, you're probably running sudosh as your shell on the remotes. Talk to the admins there to expand the allowable set of commands.
Feb 16, 2016 at 16:01 comment added Adi maybe this is helping? This is how to restrict commands - you have something like this in config files? cmdln.org/2008/02/11/restricting-ssh-commands in authorized_keys you should have a line in your authorized keys like this no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty,command=”/home/backup_user/bin/authprogs”. especially command= part which is allowing what to be run.
Feb 16, 2016 at 15:43 history tweeted twitter.com/StackUnix/status/699620113197219842
Feb 16, 2016 at 13:58 history edited firtydank CC BY-SA 3.0
added 196 characters in body
Feb 16, 2016 at 13:54 comment added firtydank @EightBitTony - done, but I'm having this problem even when I execute the command from the jumpbox itself, so I doubt it has anything to do with the jumpbox config. I also now found a host where the remote command does work via the jumpbox, once again convincing me this is a setting on the remote host.
Feb 16, 2016 at 13:52 history edited firtydank CC BY-SA 3.0
added 196 characters in body
Feb 16, 2016 at 13:50 comment added EightBitTony Can you include your .ssh/config file in the question.
Feb 16, 2016 at 13:48 comment added firtydank @Jakuje - I connect via a ProxyCommand in my ssh/.config. Yes, when I log in with the shell everything works as expected.
Feb 16, 2016 at 13:48 comment added Rui F Ribeiro What kind of ssh daemon has that jumpfox? Dropbear does not execute ssh arguments...
Feb 16, 2016 at 13:47 comment added firtydank @EightBitTony - No, only authorized_keys2 and known_hosts. No sshrc file in /etc/ssh either.
Feb 16, 2016 at 13:40 comment added EightBitTony On remoteHost is there a /home/user/.ssh/rc file (or an /etc/ssh/sshrc file) and do they contain anything interesting?
Feb 16, 2016 at 13:39 comment added Jakuje how do you connect to the servers behind jumpbox? What is your configuration? Are you sure you are not running the command on jumpbox? Does it work directly if you execute the command from shell?
Feb 16, 2016 at 13:33 history edited firtydank CC BY-SA 3.0
added 209 characters in body
Feb 16, 2016 at 13:24 comment added EightBitTony On the remoteHost, can you show us the content of the /home/user/.ssh/authorized_keys file?
Feb 16, 2016 at 13:18 history edited firtydank CC BY-SA 3.0
edited body
S Feb 16, 2016 at 13:17 history suggested techraf CC BY-SA 3.0
improved formatting
Feb 16, 2016 at 13:16 review Suggested edits
S Feb 16, 2016 at 13:17
Feb 16, 2016 at 13:16 review First posts
Feb 16, 2016 at 13:20
Feb 16, 2016 at 13:16 comment added firtydank The hosts behind the jumpbox all run Red Hat, if that makes a difference.
Feb 16, 2016 at 13:13 history asked firtydank CC BY-SA 3.0