10-15-2012
If you disable all logins, how do you plan on logging on to perform maintenance, such as patching?
If you want to disable remote access, just don't run telnet or sshd.
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
saslfinger
saslfinger(1) General Commands Manual saslfinger(1)
NAME
saslfinger - A utility to collect SMTP AUTH relevant configuration for Postfix
SYNOPSIS
saslfinger [-chs]
DESCRIPTION
saslfinger is a utility to collect SMTP AUTH relevant configuration for Postfix. Depending on how you run it, it will search for informa-
tion on server-side or client-side SMTP AUTH configuration settings in Postfix and Cyrus SASL.
OPTIONS
-c If you run saslfinger with the option -c it will collect data required for client-side SMTP AUTH. Client-side SMTP AUTH is when
Postfix smtp daemon uses SMTP AUTH to authenticate itself with a remote mail server that offers SMTP AUTH.
saslfinger will try to telnet to all hosts listed in smtp_sasl_password_maps, if it may read smtp_sasl_password_maps
The telnet test verifies your host is able to reach the remote servers and shows what AUTH mechanisms they offer - in some cases
this is required to debug client-side SMTP AUTH.
Important: By default smtp_sasl_password_maps must be read-only to root, since these maps contain the usernames and passwords to
authenticate. If you run saslfinger as root access will be no problem, but saslfinger will fail if you lack the permissions to
access smtp_sasl_password_maps.
If you want to run the telnet test, but don't want to run saslfinger as root change permissions of smtp_sasl_password_maps so that
the user running saslfinger may access smtp_sasl_password_maps while you debug.
*note: You don't need to worry about saslfinger doing anything with the username or password stored next to the remote hosts in your
smtp_sasl_password_maps; saslfinger completely ignores these informations!
-h If you run saslfinger with the option -h it will print a little help message that tells you about the options you can use.
-s If you run saslfinger with the option -s it will collect data required for server-side SMTP AUTH. Server-side SMTP AUTH is when
Postfix smtpd daemon offers SMTP AUTH to mail clients.
FILES
saslfinger - the script you need to run.
saslfinger.1 - the man page you are currently reading.
AUTHOR
Patrick Koetter, <patrick.koetter@state-of-mind.de>, http://www.state-of-mind.de
You will find the newest version of saslfinger at http://postfix.state-of-mind.de/patrick.koetter/saslfinger/.
BUGS
Please report bugs to <patrick.koetter@state-of-mind.de>
Manuals User saslfinger(1)