<?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 executable stack in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/executable-stack/m-p/3370174#M747124</link>
    <description>Does having executable stack disabled afford any protection against the various "buffer overflow" alerts that regularly come out of CERT? For example, the latest alert for CDE, HPSBUX0311-297 - SSRT3657 rev.3 CDE libDtHelp &lt;BR /&gt;.&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;&lt;BR /&gt;Greg</description>
    <pubDate>Wed, 01 Sep 2004 12:01:12 GMT</pubDate>
    <dc:creator>Greg Wooden</dc:creator>
    <dc:date>2004-09-01T12:01:12Z</dc:date>
    <item>
      <title>executable stack</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/executable-stack/m-p/3370174#M747124</link>
      <description>Does having executable stack disabled afford any protection against the various "buffer overflow" alerts that regularly come out of CERT? For example, the latest alert for CDE, HPSBUX0311-297 - SSRT3657 rev.3 CDE libDtHelp &lt;BR /&gt;.&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;&lt;BR /&gt;Greg</description>
      <pubDate>Wed, 01 Sep 2004 12:01:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/executable-stack/m-p/3370174#M747124</guid>
      <dc:creator>Greg Wooden</dc:creator>
      <dc:date>2004-09-01T12:01:12Z</dc:date>
    </item>
    <item>
      <title>Re: executable stack</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/executable-stack/m-p/3370175#M747125</link>
      <description>Yes I believe so.&lt;BR /&gt;&lt;BR /&gt;But it is available only in 11i v 1 and above.&lt;BR /&gt;&lt;BR /&gt;Completely disabling it may render some of the applications unusable that require stack to be executable.&lt;BR /&gt;&lt;BR /&gt;You can use +es option with chatr to selectively enable the stack execution capablity.</description>
      <pubDate>Wed, 01 Sep 2004 12:14:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/executable-stack/m-p/3370175#M747125</guid>
      <dc:creator>Sundar_7</dc:creator>
      <dc:date>2004-09-01T12:14:43Z</dc:date>
    </item>
    <item>
      <title>Re: executable stack</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/executable-stack/m-p/3370176#M747126</link>
      <description>I've had executable_stack set to zero for some time with no ill effects. Do a Google search on "stack smashing" to see why this is a good thing to set.&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Sep 2004 12:40:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/executable-stack/m-p/3370176#M747126</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2004-09-01T12:40:12Z</dc:date>
    </item>
  </channel>
</rss>

