Timeline for Adding a user who can only execute scripts remotely
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 27, 2024 at 15:43 | comment | added | glades | I like this, but is there a way to pass arguments as well? | |
| Mar 19, 2012 at 10:07 | comment | added | Coren | @HandyGandy This is the most simple part. I have added 2 ways of doing it, but I think there's more | |
| Mar 19, 2012 at 10:05 | history | edited | Coren | CC BY-SA 3.0 |
added 291 characters in body
|
| Mar 19, 2012 at 9:19 | comment | added | HandyGandy | Ok. I woke up in the middle of the night and decided to check answers. Since I'm drowsy I will not assimilate the entire answer but ask something which leaves me confused. How does this prevent hg_quest from logging in from a tty? | |
| Mar 19, 2012 at 8:30 | history | edited | Coren | CC BY-SA 3.0 |
added 109 characters in body
|
| Mar 19, 2012 at 8:20 | comment | added | jofel |
Beside command=, the options no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty are needed to really restrict the account.
|
|
| Mar 19, 2012 at 8:14 | comment | added | jirib | I don't think you need to specify that command in ssh on client side, it is 'forced' command so it would be always executed ;) The user on remote site still needs valid shell defined in /etc/passwd. | |
| Mar 19, 2012 at 8:09 | history | answered | Coren | CC BY-SA 3.0 |