- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Lock down /var/spool/sockets/pwgr?
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
Discussions
Discussions
Discussions
Forums
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
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
тАО09-16-2002 08:30 AM
тАО09-16-2002 08:30 AM
All of these sockets are created world-writable. More importantly, the directory itself is world-writable, without having the sticky bit set.
I've cleaned up everything else already, removing the o+w bit from most files and directories that had it, setting the rest to sticky - but I'm not sure of the effect on this particular directory.
Can anyone provide info on that directory and how restrictive the permissions can be or how lax they have to be? I'd really prefer not to leave any world-writable directories or normal files without the sticky bit set.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-16-2002 08:34 AM
тАО09-16-2002 08:34 AM
Solutionhttp://search.hp.com/redirect.html?url=http%3A//forums.itrc.hp.com/cm/QuestionAnswer/1,,0xcc11543254bfd611abdb0090277a778c,00.html&qt=pwgr&hit=1
Generally it has to do with the password/group cache.
-- Rod Hills
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-16-2002 08:35 AM
тАО09-16-2002 08:35 AM
Re: Lock down /var/spool/sockets/pwgr?
I believe you should leave the permissions 777 only right now, and change the ownership to root:root.
This will resolve all your issues. Also, the applications should set a sticky bit against their own id's under this directory.
That's what i have on all of my systems.
Regards,
Anil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-16-2002 08:40 AM
тАО09-16-2002 08:40 AM
Re: Lock down /var/spool/sockets/pwgr?
Setting stuff 777 is exactly what I DON'T want to do - if you have a file mode 777 it doesn't matter who owns it, anyone can write to it. That means any app that can write to /var at all can fill it completely by writing to that directory. It also means that any app can delete the files in the directory, presumably causing negative effects on whatever is using them.
On the other hand, I haven't yet read the link listed above - perhaps that will shed more light on it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-16-2002 08:44 AM
тАО09-16-2002 08:44 AM