- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Reject login pam module
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-14-2005 11:55 PM
02-14-2005 11:55 PM
Reject login pam module
we are running several HP machines (11.0 + 11i) which are configured as NIS clients.
Unfortunately the NIS-Servers are administred by other people. Using the logins command we have detected some additional root-users in NIS (various usernames with uid=0).
Now we are looking for a good method to prevent the login (via ssh, rlogin, telnet, su from another already logged in user) for uid = 0 and username != root.
One idea was to use PAM. I found the xadpam package, but it does not compile on HP.
Any suggestions are welcome
Hans-Dieter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2005 12:12 AM
02-15-2005 12:12 AM
Re: Reject login pam module
How about a combination of /etc/securetty + /etc/default/security
the /etc/securetty will prevent direct login to root
in the /etc/default/security you can add a SU_ROOT_GROUP=xxx
Check these links for more info.
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=784797
http://www4.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000076457542
Hope this helps,
Robert-Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2005 12:52 AM
02-15-2005 12:52 AM
Re: Reject login pam module
thank you for your immediate reply. I believe it works for direct root-logins.
But what if the NIS-Admin creates a clone of our locally defined su_root_group (same groupname, same gid) and assigns a NIS-user. I suspect this NIS-user will be allowed to su to one of the "roots".
Hans-Dieter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2005 02:55 AM
02-15-2005 02:55 AM
Re: Reject login pam module
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-15-2005 08:07 PM
02-15-2005 08:07 PM
Re: Reject login pam module
U=$(whoami)
if who | grep "^${U}" > /dev/null ;then
echo "user already logged in"
sleep 2
logout
fi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-17-2005 03:42 AM
02-17-2005 03:42 AM
Re: Reject login pam module
perhaps I should explain in more detail where the problem arises from: the admin of the NIS server is able to define a root alias and gain control over the NIS clients. Usually this may not be a problem when the NIS server admin and NIS client admin is the same person. In our case these are different people working for different companies.
Meanwhile we have defined all the root-aliases as local users in /etc/passwd so they cannot login. That works fine for the known users. But the NIS server admin is able to define another uid-0-user at any time.
I think what really would be helpful is a method to deny a users login on a combined username and uid basis (if uid = 0 and username != root then deny login).
Sorry for insisting ...
Hans-Dieter