Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi, everyone.
I have a task I need to enable root telnet on SLES 11.
I know about security hole, it is a must requirement accordingly to executing some scripts.
Telnet works for the other user , but not for root
SSH work properly.
Added pts/0 .. pts/24 to the /etc/securetty
Please, help me
Hi, everyone.
I have a task I need to enable root telnet on SLES 11.
I know about security hole, it is a must requirement accordingly to executing some scripts.
Telnet works for the other user , but not for root
SSH work properly.
Added pts/0 .. pts/24 to the /etc/securetty
Please, help me
Thank you
You need to restart the service for changes to take effect. And by what you've described, your situation makes no sense.
If you've GOT SSH working, you've got inbound terminal access, to run whatever scripts you want. If you're automating something, passwordless SSH is far easier than writing expect scripts for telnet, and no matter what....if you can log in as a 'regular' user, why can't you use SUDO or even "su", to avoid logging in as root???
TB0ne,
Thank you for the prompt answer
I restarted services maybe thousand time, either xinetd and network but doesn't work.
You are absolutely right regarding to possible changes, and I tried to describe options to the man , who write the script , but for him there is only solution - use remote telnet as a root.
So I need to find the way to enable root telnet
TB0ne,
Thank you for the prompt answer
I restarted services maybe thousand time, either xinetd and network but doesn't work.
You are absolutely right regarding to possible changes, and I tried to describe options to the man , who write the script , but for him there is only solution - use remote telnet as a root.
So I need to find the way to enable root telnet
If you're responsible for the system, then it's YOU who provides the solution, and it's YOU who's going to be held accountable if something bad happens.
If "the man who write the script" is that dumb, that they can't understand how bad this is from a security standpoint, let alone not understand the options, then they shouldn't be writing ANY code for ANY one.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
