|
|
Sponsored Content
Operating Systems
AIX
Users kicked out after changing their password in an ssh session
Post 302451223 by johnf on Monday 6th of September 2010 05:52:49 AM
09-06-2010
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello
Can user change his date ( date -u ) and not being as root?
i need it for testing. (1 Reply)
Discussion started by: umen
1 Replies
2. AIX
:confused:We've had close to 100 calls about users logging into our AIX server. The users open up about 3 to 5 sessions in the server. After 2hrs of idle time, users are frozen or stuck in the IBM UniVerse Application. We (system administrators) have been blaming the application (which we'll take... (2 Replies)
Discussion started by: Sarccastik Dude
2 Replies
3. UNIX for Advanced & Expert Users
host1 & host2 : Solaris 10 - SPARC server
From host1 able to ssh to host2 as same user with out password prompt. But, when ssh to different user in
host2, it prompts for password
DETAILS
=======
In host1:
1) logged as root
2) ssh-keygen -t dsa -b 1024 (no pass phrase)
3)... (5 Replies)
Discussion started by: vjkatsun
5 Replies
4. Shell Programming and Scripting
Hi
Can anyone help me in automate a ssh session with password using shell script (7 Replies)
Discussion started by: raghav288
7 Replies
5. Solaris
The Sun Solaris x86 system seemed to accept my username and password when I do SSH, but then the login prompt went away or hang. What happened? (8 Replies)
Discussion started by: conandor
8 Replies
6. Shell Programming and Scripting
I am using Net::SSH::Expect to connect to the device(iLO) with SSH. After the $ssh->login() I'm able to view the prompt, but not able to send any coommands.
With the putty I can connect to the device and execute the commands without any issues.
Here is the sample script
my $ssh =... (0 Replies)
Discussion started by: hansini
0 Replies
7. HP-UX
Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also? (1 Reply)
Discussion started by: yoda9691
1 Replies
8. AIX
Hi,
I search the way to limit, for a group on a AIX 5.3, one telnet session by user (Simultaneous).
I search a lot in /etc/security but the only way found is with the pam authentication that i not use.
No solution found also in smit menu...
Thanks for your help. (2 Replies)
Discussion started by: feilong
2 Replies
9. AIX
hi guys need some help. when ever i'm login ssh to aix server session always closed.
when trying t0 type wrong password the session still continues, but we tried the correct password it automatically ends.
what could be the problem to this
please see .profile details
... (6 Replies)
Discussion started by: bocha
6 Replies
10. HP-UX
We have an old (11.11) HP-UX system. A couple of months ago, our customers started having problems with their logins.
After sitting idle for roughly an hour, their screens would lock up and they would be kicked out of the system. This happens if they are in the application or on the command... (2 Replies)
Discussion started by: slkdnichols
2 Replies
LEARN ABOUT OSX
pwconv
pwconv(1M) System Administration Commands pwconv(1M) NAME
pwconv - installs and updates /etc/shadow with information from /etc/passwd SYNOPSIS
pwconv DESCRIPTION
The pwconv command creates and updates /etc/shadow with information from /etc/passwd. pwconv relies on a special value of 'x' in the password field of /etc/passwd. This value of 'x' indicates that the password for the user is already in /etc/shadow and should not be modified. If the /etc/shadow file does not exist, this command will create /etc/shadow with information from /etc/passwd. The command populates /etc/shadow with the user's login name, password, and password aging information. If password aging information does not exist in /etc/passwd for a given user, none will be added to /etc/shadow. However, the last changed information will always be updated. If the /etc/shadow file does exist, the following tasks will be performed: Entries that are in the /etc/passwd file and not in the /etc/shadow file will be added to the /etc/shadow file. Entries that are in the /etc/shadow file and not in the /etc/passwd file will be removed from /etc/shadow. Password attributes (for example, password and aging information) that exist in an /etc/passwd entry will be moved to the corre- sponding entry in /etc/shadow. The pwconv command can only be used by the super-user. FILES
/etc/opasswd /etc/oshadow /etc/passwd /etc/shadow ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
passwd(1), passmgmt(1M), usermod(1M), passwd(4), attributes(5) DIAGNOSTICS
pwconv exits with one of the following values: 0 SUCCESS. 1 Permission denied. 2 Invalid command syntax. 3 Unexpected failure. Conversion not done. 4 Unexpected failure. Password file(s) missing. 5 Password file(s) busy. Try again later. 6 Bad entry in /etc/shadow file. SunOS 5.10 9 Mar 1993 pwconv(1M)