2 ms·
At a previous job, I had a Sys Admin who once wrote a guy up because he used telnet instead of SSH to connect to a client's server. All I could think while read
by AdmiralAsshat 11y ago
At a previous job, I had a Sys Admin who once wrote a guy up because he used telnet instead of SSH to connect to a client's server. All I could think while reading the article was, "He must've used telnet..."
- empressplay 11y agoshoulda fired whoever left telnet running on the client's server first?
- AdmiralAsshat 11y agoThe client themselves would often leave the telnet service running because their employees would use it to connect to the server internally. Our clients were not the most tech-savy individuals, either, so if it was an issue where we needed to fix something and they hadn't bothered to turn the SSH service on, we could either call them and bounce around personnel until we found someone with root access whom we could convince to turn on the SSH daemon...or we could use telnet. This, to my mind, mirrors the "jaywalking" metaphor. It was bad practice, but it was either "Fight the client and force them to improve their own security so that we can safely assist them," or, "Do something we know is unsafe in order to get the job done quickly so that the client will stop bitching at us while paradoxically making it more difficult for us to help them."