How can i make login as root in telnet service

LittleMaster · 08-02-2012, 09:14 AM

Hi
Whether there is any possibity to login root user using telnet.
Im looking for alternative for ssh login in case any ssh failure.i have to capture my remote server using telnet service .

acid_kewpie · 08-02-2012, 09:20 AM

Don't don't don't don't don't do this. never run telnet.

If you want to deliberately run an insecure network service that is widely discredited you can install the telnet-server package (or equivalent name) and edit the config file, which is probably /etc/xinetd.d/telnet to fine tune the settings.

You really should NEVER be able to log in remotely as root, even over SSH. Use a normal user account, and then elevate to root once logged in. Root over telnet would not be something a good sysadmin would ever willingly do.

TenTenths · 08-02-2012, 09:46 AM

If you really want to mitigate against SSH failure then invest in a remote management card for your server which will at least allow you "direct" console access in the event of a daemon failure or see if your hosting provider will provide some form of KVM over IP access.

273 · 08-02-2012, 10:55 AM

Added to the above abut not running telnet and not logging in as root directly I like the idea of moving SSH to a high port, if you're not already -- especially if you must log in as root for some reason.

anomie · 08-02-2012, 11:49 AM

Quote:

Originally Posted by TenTenths

If you really want to mitigate against SSH failure then invest in a remote management card for your server which will at least allow you "direct" console access in the event of a daemon failure or see if your hosting provider will provide some form of KVM over IP access.

Exactly.

Just as you don't remove one of your living room walls (in case your front-door lock stops working), you don't enable a clear-text protocol service (in case sshd stops working).

If you cannot install a remote management device, then work with your hosting provider for a plan to address this sort of scenario. It may involve a person physically logging into your server to assist you.

acid_kewpie · 08-03-2012, 01:40 AM

Quote:

Originally Posted by 273

Added to the above abut not running telnet and not logging in as root directly I like the idea of moving SSH to a high port, if you're not already -- especially if you must log in as root for some reason.

https://www.owasp.org/index.php/Avoi...y_by_obscurity

273 · 08-03-2012, 05:58 AM

Quote:

Originally Posted by acid_kewpie

https://www.owasp.org/index.php/Avoi...y_by_obscurity

It's not security through obscurity in that sense at all. Try going through an auth.log from an SSH server on port 22 looking for succesful brute force attacks compared to one on port 2022. It's pretty much certain your SSH server on the standard port will get hundreds of script kiddies "testing the door handle". Yes, of course, use fail2ban or others but moving the port saves a little time when going through logs and leaves you to concentrate on the more serious attempts.