Re:Shellfirm: Intercept risky patterns at the command line
by t-3 on Sunday July 31, 2022 @05:11AM
(#32294367)
The standard way is to set PS1 (the commandline prompt text) to indicate the environment. With escape codes, you can pretty trivially get some flashing red text telling you to be careful.
[ Parent
| on HN ]
Re:Shellfirm: Intercept risky patterns at the command line
by hobs on Sunday July 31, 2022 @07:55AM
(#32294947)
If used properly the -Confirm parameter in powershell can also have you change the impact level in your environment and ask for confirmation on things that in dev would not be cared about.
Also its underused but the just in time access stuff where you can grant users subsets of permissions (again, per environment) is also pretty impressive.
Re:Shellfirm: Intercept risky patterns at the command line
by formerly_proven on Sunday July 31, 2022 @05:45PM
(#32299162)
A not-so standard way is to output a banner via shrc (instead of putting it in the motd, which the ssh daemon will only output for interactive sessions) - which incidentally will also break pretty much all tools using SSH as a transport (scp, rsync, among others).