4 ms·
Why not just outright ban the use of normal SSH and enforce all legitimate SSH activity to go through a wrapper program that reports to a monitoring service? I
by rpgwaiter 3y ago
Why not just outright ban the use of normal SSH and enforce all legitimate SSH activity to go through a wrapper program that reports to a monitoring service?
It could be a 4-line bash alias, any SSH activity that doesn't go through your wrapper could be considered suspicious
- jasonm23 3y agoI think we should be installing subdermal surveillance implants in all tier 2 workers and lower. The plebs can't be trusted to respect our wealth and superiority. /s
- arantius 3y agoYou're aware that (Open)SSH can have its behavior, including port forwards, modified at runtime after launch? See e.g. https://linux.die.net/man/1/ssh https://linux.die.net/man/1/ssh section "Escape Characters" and "~C' Open command line. Currently this allows the addition of port forwardings ..."
- AtlasBarfed 3y agoThat's basically the end goal of most SSL and security enterprise product pushers: a crappier, less usable un-automatable replacement of SSH. (Example: teleport). Of course any concerns about the vulnerabilities in their closed source implementations are handwaved away.