AIX logon attempts


 
Thread Tools Search this Thread
Special Forums Cybersecurity AIX logon attempts
# 1  
Old 06-20-2003
Question AIX logon attempts

Is it true that within AIX, logon attempts with a blocked user
(password set to NP or *) are still logged in the syslog file, provided the shell of the user is /dev/null? And that if the user does not have a shell (or a shell set to /bin/false), any logon attempts with these blocked users will NOT be logged?

Thanks!
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Cybersecurity

Help troubleshooting RSA Key login attempts

I'm stumped on an issue I'm having with RSA key based SSH logons. I have 30 servers in a database cluster. They are all Red Hat Enterprise Linux Server release 6.4. I want to be able to run a command on all of them from any one of them using SSH. I generated private and public keys on... (1 Reply)
Discussion started by: derndingle
1 Replies

2. UNIX for Dummies Questions & Answers

Maximum unsuccessful attempts in unix

Hello everyone, Can anyone help me out where is the maximum unsuccessful login attempts stored in unix? How can we know how many unsuccessful login attempts an user has made? Where is the blocked users info maintained or how can we get whether the user is blocked? Thanks in advance. (3 Replies)
Discussion started by: anandrec
3 Replies

3. AIX

aix logon

how do I create a script to logon to db2inst1 with a password , then issue db2 command :( (5 Replies)
Discussion started by: trekme
5 Replies

4. AIX

Invalid login attempts

How can I see the number of invalid login attempts of a user? Thanks, (9 Replies)
Discussion started by: agasamapetilon
9 Replies

5. Solaris

Number of login attempts on solaris 10

Hi, I want to sent number of login attempts ,so that after that much attempts user account should be locked on solaris 10 (2 Replies)
Discussion started by: manoj.solaris
2 Replies

6. AIX

ftp check for failed attempts

Hi, I have created the below ftp script to put files over to our capacity server, the check at the end works if ftp fails to run however if the script cannot login or the transfer itself failed there is no warnings. Does anyone know the syntax to trap the erorr codes or to put a check within... (3 Replies)
Discussion started by: chlawren
3 Replies

7. AIX

AIX; Auto clearing of 'too many invalid login attempts by user'

Does anyone have a good script / cron job that handles this? I have looked in smit and see it is clearing this count with: chsec -f /etc/security/lastlog -a "unsuccessful_login_count=0" -s '{userid}' However when I looked around to find ways to automate this I have not found an easy... (0 Replies)
Discussion started by: Keith Johnson
0 Replies

8. Solaris

invalid login attempts...

I am wondering if solaris captures id's associated w/invalid login attempts? when I try to login as "test1" several (3-5) times, I do not find any userID info under "/var/adm" files: utmpx wtmpx messages lastlog Is there another location/log I should be checking? Is it necessary for... (6 Replies)
Discussion started by: mr_manny
6 Replies

9. UNIX for Advanced & Expert Users

Maximum 3 login attempts

Hi, I notice in my Sun Solaris 8 sparc workstation, if I failed my login in the 5th time, I will be closed the connection from the host. I want to make 3 times. That is, if user fails to login with 3 attempts, he will be closed the connection. How to do it? Of course I am the admin of the... (2 Replies)
Discussion started by: champion
2 Replies
Login or Register to Ask a Question
su(1)							      General Commands Manual							     su(1)

NAME
su - switch user SYNOPSIS
[username [arguments]] [username] DESCRIPTION
The (set user or superuser) command allows one user to become another user without logging out. username is the name of a user defined in the file (see passwd(4)). The default name is (that is, superuser). To use the appropriate password must be supplied unless the current user is superuser and is not using the option. If a valid password is entered, executes a new shell with the real and effective user ID, real and effective group ID, and group access list set to that of the specified user. The new shell is the one specified in the shell field of the new user's entry in the password file, The arguments are passed along to the new shell for execution, permitting the user to run shell procedures with the new user's privileges. When exiting from the new shell, the previous username and environment are restored. All attempts to become another user are logged in including failures. Successful attempts are flagged with failures, with They are also logged with (see syslog(3C)). Options recognizes the following options: If the option is specified, the new shell starts up as if the new user had initiated a new login session. If the option is omit- ted, the new shell starts as if a subshell was invoked. See more details below. If DCE (Distributed Computing Environment) is being used as the authentication mechanism, the option must be specified. With this option, even superuser will be prompted for the user's password. The reason for this is because DCE credentials for a user cannot be obtained without that user's pass- word. This option cannot be used with shell arguments. If the option is specified, the new shell starts up as if the new user had initiated a new login session. Exceptions are as follows: o The variable is reset to the new user's home directory. o If the new user name is the path and prompt variables are reset: For other user names: o The variable is retained. o The rest of the environment is deleted and reset to the login state. However, the login files are normally executed anyway, usually restoring the expected value of and other variables. If the option is omitted, the new shell starts as if a subshell was invoked. Exceptions are as follows: o If the new user name is the path and prompt variables are reset: o The previously defined and environment variables are removed. o The rest of the environment is retained. If the shell specified in is sets the value of parameter in the new shell (referenced as to If the option of the command is specified, sets parameter to If the shell specified in is not sets the value of parameter in the new shell to shellname. If the option of the command is specified, sets parameter to For example, if the Korn shell is invoked, the value of shellname will be either or By comparison, the command always sets parameter to HP-UX Smart Card Login If the user account is configured to use a Smart Card, the user password is stored in the card. This password has characteristics identi- cal to a normal password stored on the system. In order to using a Smart Card account, the Smart Card from the destination user account must be inserted into the Smart Card reader. The user is prompted for a PIN instead of a password during authentication. The password is retrieved automatically from the Smart Card when a valid PIN is entered. Therefore, it is not necessary to know the pass- word, only the PIN. The card is locked if an incorrect PIN is entered three consecutive times. It may be unlocked only by the card issuer. SECURITY FEATURES
Except for user users cannot use to change to an account that has been locked because of expired passwords or other access restrictions. Refer to the file in the security(4) manual page for detailed information on configurable parameters that affect the behavior of this com- mand. Currently, the supported parameters for the command are: EXTERNAL INFLUENCES
Environment Variables User's home directory The language in which messages are displayed. If is not specified or is null, it defaults to (see lang(5)). If any internationalization variable contains an invalid set- ting, all internationalization variables default to (see environ(5)). User's login name Command name search path Default prompt Name of the user's shell International Code Set Support Characters in the 7-bit US-ASCII code sets are supported in login names (see ascii(5)). EXAMPLES
Become user while retaining the previously exported environment: Become user but change the environment to what would be expected if had originally logged in: Execute the command, using the temporary environment and permissions of user In this example, user bin's shell is invoked with the argu- ments Become user in the DCE environment: WARNINGS
After a valid password is supplied, uses information from and to determine the user's group ID and group access list. If is linked to and group membership for the user trying to log in is managed by the Network Information Service (NIS), and no NIS server is able to respond, waits until a server does respond. DEPENDENCIES
Pluggable Authentication Modules (PAM) PAM is an Open Group standard for user authentication, password modification, and account validation. In particular, is invoked to perform all functions related to This includes password retrieval, account validation, and error message displays. FILES
User's profile System's default group access list file System's password file System's profile Log of all attempts Security defaults configuration file SEE ALSO
env(1), login(1), sh(1), initgroups(3C), syslog(3C), group(4), passwd(4), profile(4), security(4), environ(5). Pluggable Authentication Modules (PAM) pam_acct_mgmt(3), pam_authenticate(3). HP-UX Smart Card Login scpin(1). STANDARDS CONFORMANCE
su(1)