- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Trusted system misbehavior?
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2006 07:24 AM
02-07-2006 07:24 AM
modprdef umaxlntr=999
Nevertheless, users are getting locked out for trying too many times with the wrong password. The customer, as a result, is very frustrated; they have scripts with passwords hardcoded into them (that date from the 15th century BC, and they simply refuse to change things) that can't access the system when the accounts lock.
I realize that the security implications of all this are abominable, but I need to figure out how to definitively turn off "locking the account after so many bad logins." Is there a way to do this? Have I just screwed it up?
Thanks!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2006 07:32 AM
02-07-2006 07:32 AM
SolutionJeff Traigle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2006 07:41 AM
02-07-2006 07:41 AM
Re: Trusted system misbehavior?
Sorry to say but how can the give the wrong password if it's hardcoded in the scripts.
If it's going wrong they are to blame.
Also make sure the are responsible if there is a security issue. Now you are hold responsible for the security but the want no security. If you are going through with this you must do /usr/lbin/modprpw -m umaxlntr=0 userid. Also make sure the password never expires.
But still this is not recommanded you are creating a security issue.
grtz. Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2006 07:43 AM
02-07-2006 07:43 AM
Re: Trusted system misbehavior?
Check with sam the default user properties.
lastb
This command will let you know if there really have been bad logins.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2006 08:21 AM
02-07-2006 08:21 AM
Re: Trusted system misbehavior?
I doubt the problem is with the number if incorect logins. What is the password aging policy for the users ? - If the user didnt change the password before the "lifetime" , the account will get locked out.
Again, I agree with the above post , how can they feed the wrong password if it is hardcoded.
Post the output of /usr/lbin/getprdef -p
Sundar.