Warning: If you're ever gonna use telnet for accessing something like a server. Then don't use telnet for it, because telnet is a very insecure remote access protocol. Because all your data going between you and the remote client are unencrypted. Even your username and password are unencrypted, so don't ever use telnet for stuff like that. Because then you're most likely to have your server hacked.
@@Santerim SSH particularly SSH version 2. Because SSH version 1 is not secure either. As SSH encrypts all of your data, that being the commands you type, your username, password, and all other important data. Plus with SSH you can set up what's called public key authentication. When enabled, you copy your ssh identify (or public key) onto the remote client. Then you reload the service, and every time you log into the server it would authenticate users with public key authentication only. That is if you disable password authentication. So if a hacker tries to hack into your server. Then they can't log in, because the server authenticates users only with their public keys instead of passwords. Edit: From testing this with SSH, I can't connect to the server without telnet. So if you're going to try this. Do this with either a virtual machine, an old computer you won't mind getting it compromised, or use a vpn. But I think it's better to do it on an old device that you won't mind it getting potentially hacked. I also tested this on an old Linux laptop (that was a windows laptop), and it also works on that.
@@alexanonymous4429 well pretty much from what I can tell, he didn't log into a server. It seemed like a web request that downloads those files onto your command line. So if you think it's safe to do it, then go ahead. Just maybe see if your antivirus sees it as potential malware. But I think those files aren't meant to be harmful.
@@alexanonymous4429 Ok so after trying this on my computer. You would be connected to a server without being promoted for a username or password. But I start capturing all the packets that are going from my computer to the server. Which is of course unencrypted, so if you are to do this. Then maybe do this on an old computer or a virtual machine. Or use a VPN, or something that would keep you safe from being potentially hacked. I also tested this on a Linux system, and it also works on there. So I would say maybe do this at your own risk.
this the exact thing I hate about this guy, he explains everything with like extremely simple surface level one click explanations and he misses more things than he actually says because he doesn't expect anyone to do it, he just does it for the views
Yeah Telnet is something that I would rarely use. I wouldn't use it for some secret server, I would just use it for experimenting. Like if I want to capture telnet packets, when I connect to my old Linux laptop with telnet. I would set up a temporary dummy user account on Linux, and make it not have strong user privileges and make it have a weak password (And maybe connect an ethernet cable between my 2 computers). So that later I can easily delete the dummy account, and I wouldn't have to worry about getting hacked.
Good to know others are aware about the security of application protocols, I wish it were widely known as it would be easier to prevent malware and other cyber threats.
Not only Telnet is old, but it's also insecure. Because all of your user data is unencrypted (input, output, username, password, etc.), when I tested this for myself in a Linux computer. I did packet capturing, the packets showed exactly what I was typing in and its output.
@@pyp2205 Telnet is insecure, but using a client does not leave you machine vulnerable like many people seem to be confused about. A few points, everything you do on Telehack is visible by other users, this is part of the game. You can also connect to Telehack via SSH or HTTPS if you so desire. Telehack is MUCH more than just starwars. From the Manual: Telehack is a simulation of a stylized arpanet/usenet, circa 1985-1990. It is a full multi-user simulation, including 26,600+ simulated hosts from the early net, thousands of files from the era, a collection of adventure and IF games, a working BASIC interpreter with a library of programs to run, simulated historical users, and more.
@@4everblacknite I have tried connecting to telehack with ssh. But it says that the connection was refused. Might be that it doesn't have ssh set up or I have to use a different port number other than ssh's default port (Default SSH Port 22, Default Telnet Port 23). I noticed when I was capturing telnet packets, that when I loaded 2048 on telehack. It did show some data when it was opened, but after that it didn't show any more telnet data. I saw encrypted TCP packets. But of course it's best to not use telnet especially if you're going to remotely access a remote server. Because we all know that telnet doesn't encrypt data (username, password, commands, etc.).
They say the same thing about you using buggy ass OpenGL to play games at half framerate --- but only after spending three weeks hacking around in text files with bullshit editors like vi just to get the mouse orientation correct.
@@smarterthanyou9090who hurt you? but for real, gaming on linux is really not that bad now, most games run the same as on windows in my experience. Also you don't need to use vi or vim or emacs or anything, just use nano or a gui text editor...
Not necessarily true, as this is a client. You aren’t spawning any kind of access by having a client available. It does however provide another vector for maintaining access if a malicious source has local access to a computer.
The danger of Telnet is not access vulnerabilities. It’s the fact that your traffic is unencrypted plain text, so any passwords or login credentials you use while interfacing with a switch, server, etc can be easily seen with a simple packet sniffer.
@@whitekr0w telnet is unsecure and all they need to know is your ip to get into your pc. this while not publicly accessable can easly be found out. while the stuff you are downloading may not be bad enabling telnet itself is full stop.
100%, the problem with these short creators is that they can quickly spread dangerous info that people fall for, earlier today someone was trying to convince their viewers to download videos containing Trojans.
This guy definitely has a discord full of 12yo girls and makes them fight for his attention Edit: if you're mad at my comment and want to retaliate, at least do better than just saying "actually no that's you". That's just lazy. At least make me laugh if you're gonna try and insult me.
Don't do this, please!! Telnet is not secure for one thing. In addition, you are running a script written by God only knows. While it is playing Star Wars in ASCII who knows what other mischief it is getting into.
Just get Putty. Telnet is from the BBS days yo. When us Gen Xrs grew up watching War Games :D. I worked on a Diku Mud in college that used Telnet. That was '91.
The reason why it was removed was because it was unsecure to use telnet. It doesn't add commands the telnet commands are just like those options you get to turn on an extra feature.
You're going to want to make certain that your firewall rules are set to deny incoming telnet connections - and that you really trust your firewall. Otherwise, you are inviting the world to your box
I’m sure your way will work, but it’s actually Windows+R to open Run window, then type ‘optionalfeatures’ to install and enable Windows’ optional features; like Telnet.
Tellnet that's crazy they still have to telnet built into windows computers When you use tell that it's for Connecting into someone else's computer so you're really disconnecting to a server when you do this Kind of like a prompt way of connecting to a website
or its more complex and some may think it is more difficult but you can also do a bit of a longer process open CMD and type telnet then enter then type o then enter the type
