|
|
Sponsored Content
Top Forums
UNIX for Dummies Questions & Answers
Lockout Users
Post 20249 by Kelam_Magnus on Tuesday 23rd of April 2002 02:17:29 PM
04-23-2002
Probably the easiest one is to do a "/sbin/init.d/inetd stop" and then when you are done do a "/sbin/init.d/inetd start".
_______________________________________________
There are several ways to do this.
There is one caveat, "Don't log out yourself".
1) you can kill the inetd daemon. Can't login without a telnet session or FTP session. As above...
2) Move the password file. Can't login without a password.
3) Change permissions on the / directory to 700. This will disallow users from logging in as well. I did this once by accident. You can search for others who have done the same by accident!
4) Reboot into single user mode. Removes all network connectivity.
I am sure there are several other ways, but these are the most useful.
Of course you must either kick out the active users, or ask them to logout for maintenance. Try to be as nice as possible.
_______________________________________________
There are several ways to do this.
There is one caveat, "Don't log out yourself".
1) you can kill the inetd daemon. Can't login without a telnet session or FTP session. As above...
2) Move the password file. Can't login without a password.
3) Change permissions on the / directory to 700. This will disallow users from logging in as well. I did this once by accident. You can search for others who have done the same by accident!
4) Reboot into single user mode. Removes all network connectivity.
I am sure there are several other ways, but these are the most useful.
Of course you must either kick out the active users, or ask them to logout for maintenance. Try to be as nice as possible.
|
|
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi, I am extremely new to UNIX and was recently promoted to administer the system for a small company. Anyhow, the time came for passwords to change, and I made the huge mistake of entering in the command (as root)
passwd -l
After logging out (oblivious to what would happen next), the root... (4 Replies)
Discussion started by: newbieadmin
4 Replies
2. AIX
Hi,
We are using 4.3.3.0 and I would like to make a global change to the "number of failed logins before user account is locked"
Any ideas, other than using SMIT one user at a time.... ???
Thanks... Craig. (2 Replies)
Discussion started by: stumpy
2 Replies
3. AIX
I want to know if there is any easy way of stopping 1 user from using su? perferabily any su but I can make do with not allow him to su to root but allow other user to su to root. (3 Replies)
Discussion started by: daveisme
3 Replies
4. Red Hat
Hi all;
I m using Red Hat Enterprise Linux Server release 5.1 (Tikanga) and I'm trying to setup password lockout policy so that a user account locks out after 3 failed attempts.
Here are the entires of my /etc/pam.d/system-auth
#%PAM-1.0
# This file is auto-generated.
# User changes... (1 Reply)
Discussion started by: maverick_here
1 Replies
5. UNIX and Linux Applications
What is the best way to implement account lockout in openldap? I have an openldap server with Ubuntu desktop client connecting to it for authentication. I want he accounts to locked out after say 5 failed authentication attempts
I have enabled ppolicy layout in slapd.conf.
overlay ppolicy... (0 Replies)
Discussion started by: nitin09
0 Replies
6. Red Hat
On a redhat linux 4 server, how to find if there is an account lockout duration is set. Is it configured under pam or /etc/shadow? what entries I need to find out? Is it pam_time.so module?
I desperately need an answer because on one of the servers, no one was able to login through any account... (4 Replies)
Discussion started by: Tirmazi
4 Replies
7. Red Hat
having account lockout issues with an RHEL 5 server. My users are getting locked out for 10 minutes after one failed login attempt even though /etc/pam.d/sshd is configured for 5 failed attempts:
auth include system-auth
auth required pam_tally2.so deny=5 onerr=fail... (1 Reply)
Discussion started by: nerdalert
1 Replies
8. Solaris
Greetings,
I work with a Solaris Sun Server V240 system (GCCS) and have run into a problem where I can't seem to unlock my SECMAN account at the NON-GLOBAL level. I have access to all global accounts to include sysadmin and secman. I have access to the non-global sysadmin account and root... (4 Replies)
Discussion started by: TLAMGUY
4 Replies
9. Red Hat
Good day. I have setup hardening the password (test system so far) prior to doing any work on production. Here is what I have set.
Snippet from /etc/pam.d/system-auth
auth required /lib/security/$ISA/pam_env.so
auth required /lib/security/$ISA/pam_tally.so... (3 Replies)
Discussion started by: smurphy_it
3 Replies
LEARN ABOUT DEBIAN
roarmonhttp
roarmonhttp(1) System User's Manual: roarmonhttp roarmonhttp(1) NAME
roarmonhttp - CGI and inetd based streaming server emulation for RoarAudio SYNOPSIS
roarmonhttp [--inetd] DESCRIPTION
This program emulates a streaming server using RoarAudio. It can be run from via a webserver as CGI or via inetd in inetd mode. IN CGI mode it is limited to client (listener) HTTP connections. In inetd mode it can handle source clients and gopher, too. There is no need for a specal port for gopher. The protocol is detected per client at runtime. OPTIONS
--inetd Enables inetd mode. --server SERVER Set Server to connect to. This may be usfull in inetd mode. --rate, --bits, --channels, --codec Sets the default rate, bits, channels or codec. Those option taking a argument for the given option. Codec names may be used. --rel-id SID Set the stream ID for the stream this stream is relative to. --help Show a brief help. EXAMPLES
Here is an example of a roarmonhttp listening on port 8000 using inetd: 8000 stream tcp nowait roard /usr/bin/roarmonhttp roarmonhttp --inetd SEE ALSO
inetd(8), inetd.conf(5), roartips(7), libroar(7), RoarAudio(7). HISTORY
For history information see RoarAudio(7). RoarAudio January 2010 roarmonhttp(1)