<?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 Process vulnerability versus NESSUS in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/process-vulnerability-versus-nessus/m-p/4368803#M684431</link>
    <description>Hello,&lt;BR /&gt;&lt;BR /&gt;I have a process (written in C language) acting as a server, that listens on a socket for connections.&lt;BR /&gt;&lt;BR /&gt;My goal is to make it "secure" versus NESSUS attacks.&lt;BR /&gt;&lt;BR /&gt;I have improved the communication protocol by checking received messages and closing the socket if the message is not the expected one.&lt;BR /&gt;&lt;BR /&gt;My problem is that all socket connections coming from NESSUS process remain in CLOSE_WAIT status and the number of files open in charge of my process grows undefinitely.&lt;BR /&gt;(I close the socket by executing shutdown + close)&lt;BR /&gt;&lt;BR /&gt;How can I manage such a issue?&lt;BR /&gt;&lt;BR /&gt;Many thanks&lt;BR /&gt;&lt;BR /&gt;Giuseppe&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Sat, 28 Feb 2009 08:33:46 GMT</pubDate>
    <dc:creator>Fedele Giuseppe</dc:creator>
    <dc:date>2009-02-28T08:33:46Z</dc:date>
    <item>
      <title>Process vulnerability versus NESSUS</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/process-vulnerability-versus-nessus/m-p/4368803#M684431</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;I have a process (written in C language) acting as a server, that listens on a socket for connections.&lt;BR /&gt;&lt;BR /&gt;My goal is to make it "secure" versus NESSUS attacks.&lt;BR /&gt;&lt;BR /&gt;I have improved the communication protocol by checking received messages and closing the socket if the message is not the expected one.&lt;BR /&gt;&lt;BR /&gt;My problem is that all socket connections coming from NESSUS process remain in CLOSE_WAIT status and the number of files open in charge of my process grows undefinitely.&lt;BR /&gt;(I close the socket by executing shutdown + close)&lt;BR /&gt;&lt;BR /&gt;How can I manage such a issue?&lt;BR /&gt;&lt;BR /&gt;Many thanks&lt;BR /&gt;&lt;BR /&gt;Giuseppe&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 28 Feb 2009 08:33:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/process-vulnerability-versus-nessus/m-p/4368803#M684431</guid>
      <dc:creator>Fedele Giuseppe</dc:creator>
      <dc:date>2009-02-28T08:33:46Z</dc:date>
    </item>
  </channel>
</rss>

