<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Lock down /var/spool/sockets/pwgr? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/lock-down-var-spool-sockets-pwgr/m-p/2807014#M83289</link>
    <description>This topic came up recently. see-&lt;BR /&gt;&lt;A href="http://search.hp.com/redirect.html?url=http%3A//forums.itrc.hp.com/cm/QuestionAnswer/1,,0xcc11543254bfd611abdb0090277a778c,00.html&amp;amp;qt=pwgr&amp;amp;hit=1" target="_blank"&gt;http://search.hp.com/redirect.html?url=http%3A//forums.itrc.hp.com/cm/QuestionAnswer/1,,0xcc11543254bfd611abdb0090277a778c,00.html&amp;amp;qt=pwgr&amp;amp;hit=1&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Generally it has to do with the password/group cache.&lt;BR /&gt;&lt;BR /&gt;-- Rod Hills</description>
    <pubDate>Mon, 16 Sep 2002 15:34:31 GMT</pubDate>
    <dc:creator>Rodney Hills</dc:creator>
    <dc:date>2002-09-16T15:34:31Z</dc:date>
    <item>
      <title>Lock down /var/spool/sockets/pwgr?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lock-down-var-spool-sockets-pwgr/m-p/2807013#M83288</link>
      <description>Under HPUX 11.11 (and probably others), we have a directory, /var/spool/sockets/pwgr, which seems to hold only socket files.&lt;BR /&gt;&lt;BR /&gt;All of these sockets are created world-writable.  More importantly, the directory itself is world-writable, without having the sticky bit set.&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;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.</description>
      <pubDate>Mon, 16 Sep 2002 15:30:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lock-down-var-spool-sockets-pwgr/m-p/2807013#M83288</guid>
      <dc:creator>Trever Furnish</dc:creator>
      <dc:date>2002-09-16T15:30:50Z</dc:date>
    </item>
    <item>
      <title>Re: Lock down /var/spool/sockets/pwgr?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lock-down-var-spool-sockets-pwgr/m-p/2807014#M83289</link>
      <description>This topic came up recently. see-&lt;BR /&gt;&lt;A href="http://search.hp.com/redirect.html?url=http%3A//forums.itrc.hp.com/cm/QuestionAnswer/1,,0xcc11543254bfd611abdb0090277a778c,00.html&amp;amp;qt=pwgr&amp;amp;hit=1" target="_blank"&gt;http://search.hp.com/redirect.html?url=http%3A//forums.itrc.hp.com/cm/QuestionAnswer/1,,0xcc11543254bfd611abdb0090277a778c,00.html&amp;amp;qt=pwgr&amp;amp;hit=1&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Generally it has to do with the password/group cache.&lt;BR /&gt;&lt;BR /&gt;-- Rod Hills</description>
      <pubDate>Mon, 16 Sep 2002 15:34:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lock-down-var-spool-sockets-pwgr/m-p/2807014#M83289</guid>
      <dc:creator>Rodney Hills</dc:creator>
      <dc:date>2002-09-16T15:34:31Z</dc:date>
    </item>
    <item>
      <title>Re: Lock down /var/spool/sockets/pwgr?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lock-down-var-spool-sockets-pwgr/m-p/2807015#M83290</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I believe you should leave the permissions 777 only right now, and change the ownership to root:root.&lt;BR /&gt;&lt;BR /&gt;This will resolve all your issues. Also, the applications should set a sticky bit against their own id's under this directory.&lt;BR /&gt;&lt;BR /&gt;That's what i have on all of my systems.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Anil</description>
      <pubDate>Mon, 16 Sep 2002 15:35:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lock-down-var-spool-sockets-pwgr/m-p/2807015#M83290</guid>
      <dc:creator>Anil C. Sedha</dc:creator>
      <dc:date>2002-09-16T15:35:44Z</dc:date>
    </item>
    <item>
      <title>Re: Lock down /var/spool/sockets/pwgr?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lock-down-var-spool-sockets-pwgr/m-p/2807016#M83291</link>
      <description>Anil,&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;On the other hand, I haven't yet read the link listed above - perhaps that will shed more light on it.&lt;BR /&gt;</description>
      <pubDate>Mon, 16 Sep 2002 15:40:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lock-down-var-spool-sockets-pwgr/m-p/2807016#M83291</guid>
      <dc:creator>Trever Furnish</dc:creator>
      <dc:date>2002-09-16T15:40:43Z</dc:date>
    </item>
    <item>
      <title>Re: Lock down /var/spool/sockets/pwgr?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lock-down-var-spool-sockets-pwgr/m-p/2807017#M83292</link>
      <description>The linked discussion is enough of an answer, although I'll say in passing that I think it's irresponsible of HP to ship the OS in this state in the first place.  Thanks for the info, guys - I'll disable it.</description>
      <pubDate>Mon, 16 Sep 2002 15:44:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lock-down-var-spool-sockets-pwgr/m-p/2807017#M83292</guid>
      <dc:creator>Trever Furnish</dc:creator>
      <dc:date>2002-09-16T15:44:46Z</dc:date>
    </item>
  </channel>
</rss>

