VT100 Terminal Emulator is one of the most popular terminal emulators available on the internet today. You can find this software anywhere online and they usually offer a free download. But how do you really use this software? What’s the big deal with this thing? Let’s take a look at what it can do for us.
The most common feature that you will see with a VT100 terminal emulator is the SecureCRT feature. This is an emulation of the classic IBM Model M keyboard. That’s right, the same model that was used by desktop computers back in the days. You can also find some other types of emulators for the IBM Model M as well. With this software, you have the ability to use the computer’s classic function keys and even the arrow keys.
So if you’re using Linux, does this mean that you can’t run a virtual terminal? Of course not. It’s important to realize that there are different operating systems out there and not all of them support interactive virtual terminals. Some only allow for graphical output through the console, which is kind of like a mini graphical user interface. If your system supports SecureCRT, then you can basically use it as a command-line virtual terminal.
Another feature that you may want to take a look at is the Secure Socket Layer (SSL) support. This is pretty self explanatory. Basically, when you are connecting to the internet you are connecting to a secure socket layer so that data can be encrypted and sent over the internet without being sniffed or tracked. For example, you would use this type of technology to connect to the internet in order to make secure payments online. Many of the retail websites do this with their shopping carts and when you make a purchase with the credit card you are actually making an offline payment to the website.
Using a Putty file as an intermediary for these types of transactions works well in most situations but if you need the ability to change the password you will have to either configure your SecureCRT settings or learn how to get around the chown command on your Linux system. Chown is one of the more complicated commands to learn which is why most people do not use it. What happens when you try to execute this command is that your privileges for the file changes and instead of the file actually belonging to you the file belongs to the new owner.
As you can see, although there are ways to change these permissions it is difficult to do it without knowing how to modify the permissions yourself. If you are working on a server that is not shared hosting you won’t have access to the chown command or to any of the other possible commands that are available. Unless you are the server owner you are stuck with the defaults and the fact that the file belongs to the new owner and that means that you will have to assign full control to them before being able to do anything to it.
There are two other options that you have to be able to change ownership of the VTS 100 terminal emulator but neither one is particularly recommended. One option is to change the ownership of the file directly using the command line “chown -R” but this command has never been tested on linux and probably won’t work at all. The second option is to change the user ownership of the file by using the “control group” command in effect which basically tells the computer to assume the user ownership of the file. Although this sounds like a legitimate method it has also been known to cause problems and even often give error messages on some occasions.
Since most people aren’t going to know how to do either of these methods it really boils down to either using the VPS (virtual private servers) that Linx offers or not. The good news though, is that if you do decide to switch from your normal windows based hosting to the Linx you will gain access to the VPS as root instead of the usual user that just happens to be a computer that has a windows based operating system. This means that you can then log into your VPS as root and actually be able to do whatever you want to your VPS as root. Just make sure to remember that the next time you try to login you will need to use the command-line chown command-line as explained in the last post in this series of Linux VPShooting Tips.