10-15-2012
Hi all,
thanks for your contribute.
Reading blogs, forum and techdoc came out that there's no way to deny a specific user (except root) to login directly with telnet.
I was able to make some tests in the lab and I think that the right solution is the one provided in my first post.
Moreover I'm going to discuss with colleagues to stop the telnet service so that we should solve the problem of direct access with specific user "X".
Thanks again.
Kind regards,
Evan
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
After Configuring a brand new netraT1, It appears, the only way you can log in as root is throught the Serial Port (console). I believe there is a file in /etc which can be edited to allow root to access login via other methods
eg: telnet, ssh, etc.
My Question:
Which file contains... (2 Replies)
Discussion started by: SmartJuniorUnix
2 Replies
2. AIX
If user login and don't do anything in 15 mins, the user is kicked off from the server. how to disable it? (5 Replies)
Discussion started by: rainbow_bean
5 Replies
3. Linux
Hi Guys....
I am a newbie to unix. I have a requirement. I have a server. I have to configure ssh to disable direct root login and then add a user with sudo access to this server.Then change the ssh port to 22315 and the server should permit the ssh only from my local machine ip.I also have to... (1 Reply)
Discussion started by: mahesh_raghu
1 Replies
4. Solaris
Is there a way to disable a certain local user from remote login, and only allow su to that user. :confused:
i know i can stop remote login for root user, i need it for other users.
Appreciate your help (4 Replies)
Discussion started by: mduweik
4 Replies
5. UNIX for Dummies Questions & Answers
I have already disabled root login over the ssh by modifying /etc/ssh/sshd_config.
But how would i disable root login on a server itself.
We have implemented LDAP in our environment and our security guide states that root login must be obtained by first logging into the host using his/her own... (2 Replies)
Discussion started by: pinga123
2 Replies
6. Solaris
Hi,
I am trying to setup direct login from server test1 (Solaris 10) to server test2 (Solaris 9) using id taops (ldap id).
Process Followed on Test 2.
created .rhosts file in home directory of user taops
geneted public key on test1 and appended to authorized keys on test2.
Now trying... (8 Replies)
Discussion started by: tuxian
8 Replies
7. AIX
I have disabled rlogin for root successfully , but after that i could not login to root from console and could not su to root from other users as it responded as expired account
I did not have any admin user but I have managed to recover the situation by accessing rootvg before mounting it, but... (5 Replies)
Discussion started by: majd_ece
5 Replies
8. Solaris
HI Gurus
can I temporary disable users to connect to Solaris, need help
Regards (3 Replies)
Discussion started by: smazshah
3 Replies
9. Shell Programming and Scripting
Hi guys,
been scratching round the forums and my mountain of resources.
Maybe I havn't read deep enough
My question is not how sed edits a stream and outputs it to a file, rather something like this below:
I have a .txt with some text in it :rolleyes:
abc:123:xyz
123:abc:987... (7 Replies)
Discussion started by: the0nion
7 Replies
10. Red Hat
All,
I need to disable "sudo -i" and "su - " for all servers in our environment, We want to make sure no one run commands or delete files across environment using switching to root account. can you guys please lets me know if this is achievable.
Thanks and Regards
shekar (2 Replies)
Discussion started by: shekar777
2 Replies
LEARN ABOUT DEBIAN
login.access
LOGIN.ACCESS(5) BSD File Formats Manual LOGIN.ACCESS(5)
NAME
login.access -- login access control table
DESCRIPTION
The login.access file specifies on which ttys or from which hosts certain users are allowed to login.
At login, the /etc/login.access file is checked for the first entry that matches a specific user/host or user/tty combination. That entry can
either allow or deny login access to that user.
Each entry have three fields separated by colon:
o The first field indicates the permission given if the entry matches. It can be either ``+'' (allow access) or ``-'' (deny access) .
o The second field is a comma separated list of users or groups for which the current entry applies. NIS netgroups can used (if configured)
if preceeded by @. The magic string ALL matches all users. A group will match if the user is a member of that group, or it is the user's
primary group.
o The third field is a list of ttys, or network names. A network name can be either a hostname, a domain (indicated by a starting period),
or a netgroup. As with the user list, ALL matches anything. LOCAL matches a string not containing a period.
If the string EXCEPT is found in either the user or from list, the rest of the list are exceptions to the list before EXCEPT.
BUGS
If there's a user and a group with the same name, there is no way to make the group match if the user also matches.
SEE ALSO
login(1)
AUTHORS
The login_access() function was written by Wietse Venema. This manual page was written for Heimdal.
HEIMDAL
March 21, 2003 HEIMDAL