<?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: /etc/useracct/utmpd_read, why world writable? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-useracct-utmpd-read-why-world-writable/m-p/4247381#M677679</link>
    <description>Thank you everyone for your replies. TTr, thank you for pointing out that the file is a socket. I overlooked that fact. I will likely push for an exception for this file from the security violation.&lt;BR /&gt;</description>
    <pubDate>Thu, 07 Aug 2008 18:06:23 GMT</pubDate>
    <dc:creator>Carl Cloutier</dc:creator>
    <dc:date>2008-08-07T18:06:23Z</dc:date>
    <item>
      <title>/etc/useracct/utmpd_read, why world writable?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-useracct-utmpd-read-why-world-writable/m-p/4247377#M677675</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;I am getting a security audit violation for having world writable permissions on the  /etc/useracct/utmpd_read file. Does this file have to be world writable and if so why?&lt;BR /&gt;&lt;BR /&gt;Thank you,&lt;BR /&gt;Carl</description>
      <pubDate>Wed, 06 Aug 2008 15:48:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-useracct-utmpd-read-why-world-writable/m-p/4247377#M677675</guid>
      <dc:creator>Carl Cloutier</dc:creator>
      <dc:date>2008-08-06T15:48:08Z</dc:date>
    </item>
    <item>
      <title>Re: /etc/useracct/utmpd_read, why world writable?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-useracct-utmpd-read-why-world-writable/m-p/4247378#M677676</link>
      <description>Shalom Carl,&lt;BR /&gt;&lt;BR /&gt;Strange day for me. Lots of stuff I never saw before.&lt;BR /&gt;&lt;BR /&gt;I'm not familiar with this file. I'm not even sure its a part of HP-UX.&lt;BR /&gt;&lt;BR /&gt;Can you do a uname -a and let us know what version of the OS this is and what security enhancements you have installed?&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 06 Aug 2008 16:33:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-useracct-utmpd-read-why-world-writable/m-p/4247378#M677676</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2008-08-06T16:33:53Z</dc:date>
    </item>
    <item>
      <title>Re: /etc/useracct/utmpd_read, why world writable?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-useracct-utmpd-read-why-world-writable/m-p/4247379#M677677</link>
      <description>Hi Carl:&lt;BR /&gt;&lt;BR /&gt;Since this file and its companions are part of the accounting for currently logged-in users, I think that the audit isn't context-sensitive".  Stated differently, the audit may be overly paranoid.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/B3921-60631/utmpd.1M.html" target="_blank"&gt;http://docs.hp.com/en/B3921-60631/utmpd.1M.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I would suspect that the 'umask' setting at the time accounting is enabled may be too lax.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Wed, 06 Aug 2008 16:39:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-useracct-utmpd-read-why-world-writable/m-p/4247379#M677677</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2008-08-06T16:39:45Z</dc:date>
    </item>
    <item>
      <title>Re: /etc/useracct/utmpd_read, why world writable?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-useracct-utmpd-read-why-world-writable/m-p/4247380#M677678</link>
      <description>That file is not a regular file, it is a socket. Typically sockets are world writable and if you search in the system for more sockets (find / -type s -exec ll {} \;) you will find that most sockets are world writable. I can't tell what will happen if you change the permissions.&lt;BR /&gt;Every socket file is used by two or more processes. If these processes are owned by the socket owner/group they should be able to use the socket if you take away the world write access. &lt;BR /&gt;</description>
      <pubDate>Wed, 06 Aug 2008 16:56:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-useracct-utmpd-read-why-world-writable/m-p/4247380#M677678</guid>
      <dc:creator>TTr</dc:creator>
      <dc:date>2008-08-06T16:56:49Z</dc:date>
    </item>
    <item>
      <title>Re: /etc/useracct/utmpd_read, why world writable?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/etc-useracct-utmpd-read-why-world-writable/m-p/4247381#M677679</link>
      <description>Thank you everyone for your replies. TTr, thank you for pointing out that the file is a socket. I overlooked that fact. I will likely push for an exception for this file from the security violation.&lt;BR /&gt;</description>
      <pubDate>Thu, 07 Aug 2008 18:06:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/etc-useracct-utmpd-read-why-world-writable/m-p/4247381#M677679</guid>
      <dc:creator>Carl Cloutier</dc:creator>
      <dc:date>2008-08-07T18:06:23Z</dc:date>
    </item>
  </channel>
</rss>

