<?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 Locking down hpasm under RHEL 6 in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/locking-down-hpasm-under-rhel-6/m-p/6881784#M54883</link>
    <description>&lt;P&gt;Trying to secure some RHEL 6 server and seeing hundreds of files under /var/spool/hpasm with the S_ISGID (2000) bit set.&amp;nbsp; Is there a valid reason for this?&amp;nbsp; If not, if I manually change all of the files, will hpasm just reset them?&lt;/P&gt;</description>
    <pubDate>Mon, 25 Jul 2016 16:38:25 GMT</pubDate>
    <dc:creator>BradV</dc:creator>
    <dc:date>2016-07-25T16:38:25Z</dc:date>
    <item>
      <title>Locking down hpasm under RHEL 6</title>
      <link>https://community.hpe.com/t5/operating-system-linux/locking-down-hpasm-under-rhel-6/m-p/6881784#M54883</link>
      <description>&lt;P&gt;Trying to secure some RHEL 6 server and seeing hundreds of files under /var/spool/hpasm with the S_ISGID (2000) bit set.&amp;nbsp; Is there a valid reason for this?&amp;nbsp; If not, if I manually change all of the files, will hpasm just reset them?&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jul 2016 16:38:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/locking-down-hpasm-under-rhel-6/m-p/6881784#M54883</guid>
      <dc:creator>BradV</dc:creator>
      <dc:date>2016-07-25T16:38:25Z</dc:date>
    </item>
  </channel>
</rss>

