4 ms·
A story about telnet escape... Back in the early 90s the local university used to have a free dial-up that you'd connect to via modem and then could telnet any
by cmrdporcupine 7y ago
A story about telnet escape...
Back in the early 90s the local university used to have a free dial-up that you'd connect to via modem and then could telnet anywhere. You didn't need to be a student or anything. As a teenager I used this to connect to various shell accounts I had around, and to various MUDs. (This was in the pre-ISP days -- there was nobody in my area offering dial-up Internet at all.)
At some point they pulled this and made it for students only. But they had a dial-up gopher service for campus information and library access that was actually a telnet session to a gopher client on a SunOS machine somewhere.
But they didn't disable the telnet escape character.
So for a few months back then the way I got Internet access was to dial into the gopher client, hit ^], close the session to the gopher client, and open to anywhere else I chose. Eventually they closed this hole, too, but it was glorious for a while.
- tobinfricke 7y agoSame here. University of California, Irvine dialup in my case.
- mds 7y agoOh man, I have the same memory. Back in ‘92 or ‘93, in addition to the “^]” telnet trick, our local dial up gopher could launch vi sessions for sending emails which they hadn’t thought to lock down to prevent it from executing “sh”. Poking around in those university systems was my first exposure to Unix and I’d say pretty directly influenced my career path. So, thanks telnet!
- hinkley 7y agoMy roommate volunteered as the webmaster for a non-profit, and they had a little tool that gave him vi access but no shell access. Apache won't serve certain files unless the permissions are just so, and he could not get them to fix them or give him a shell to do it himself. So he couldn't do his job. I ended up telling him about the shell escape trick.
- ardenpm 7y agoAh, reminds me of using Slirp back on those dialup links to get a proper SLIP/PPP connection and TCP/IP over my regular shell account. Of course that hole to was closed eventually also. Though their first attempt at it was just blacklisting the executable by name which was quickly worked around but they wised up after that.
- hinkley 7y agoWe had to ban the IP block for an entire university due to troublemakers, but the problem is that one of our regulars was from the same U. One of us happened to know about such a forwarding service, so we gave him the address after a strict warning and promise that he'd behave himself. He was having a rough time, and nobody wanted to be the one to tell him he was going to be kicked by association, so it was lucky we had a workaround.
- Jamwinner 7y agoBanning an ip block is always a bonehead move. Its trivial for an attacker to change ips, fix the root problem.
- hinkley 7y ago“The early 90’s” is coming up on 30 years ago. Do you even remember 30 years ago? The sort of people who could do that back then generally had much better things to do with their time. And resources. When you’re dealing with idiots who only have access to dialup or their university computer lab, it doesn’t take much to stop them. It was just a bunch of 20 year olds trying to have fun. Not defense networks.
- rsync 7y ago"At some point they pulled this and made it for students only. But they had a dial-up gopher service for campus information and library access that was actually a telnet session to a gopher client on a SunOS machine somewhere." Was this, by chance, a .umn.edu dialup ? Just curious ...
- cmrdporcupine 7y agoNope, ualberta