HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Nis+ in trusted system
Operating System - HP-UX
1833187
Members
3260
Online
110051
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
04-10-2002 11:58 PM
04-10-2002 11:58 PM
Nis+ in trusted system
We have two nodes with MC/Service Guard one of them is nis+ server and the other is a replica server, we have also another hp-ux this is nis+ client only. All of them are trusted.
We have implemented our security policies filling the tables passwd (shadow fields) and trusted in this way:
trusted.org_dir
XXXX:1:6:31536000:0:0:0:1:1:0:10:::1018356085::::
passwd.org_dir XXXX:criptedpass:12345:54321:you:/home/you:/usr/bin/ksh:11786:2:35:35:185:12146:0
All is working correctly except: if a user must be locked (i.e. it makes 3 fails while login), it is locked only in the local machine not in the nis+ domain.
said in other way the nis+ policies restrict the login attempts to 2 If user A fails 3 times in machine XX user A is only blocked in machine XX it can login in machine YY without problems.
with XX and YY any machine of the nis+ domain.
This is not correct for us because if the production packet goes to the other node the user prod can be blocked. Is there a way to change that?
Thx in advance
Regards
We have implemented our security policies filling the tables passwd (shadow fields) and trusted in this way:
trusted.org_dir
XXXX:1:6:31536000:0:0:0:1:1:0:10:::1018356085::::
passwd.org_dir XXXX:criptedpass:12345:54321:you:/home/you:/usr/bin/ksh:11786:2:35:35:185:12146:0
All is working correctly except: if a user must be locked (i.e. it makes 3 fails while login), it is locked only in the local machine not in the nis+ domain.
said in other way the nis+ policies restrict the login attempts to 2 If user A fails 3 times in machine XX user A is only blocked in machine XX it can login in machine YY without problems.
with XX and YY any machine of the nis+ domain.
This is not correct for us because if the production packet goes to the other node the user prod can be blocked. Is there a way to change that?
Thx in advance
Regards
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP