<?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: Protocol for download file in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/protocol-for-download-file/m-p/2995564#M125306</link>
    <description>ftp</description>
    <pubDate>Thu, 12 Jun 2003 12:37:26 GMT</pubDate>
    <dc:creator>twang</dc:creator>
    <dc:date>2003-06-12T12:37:26Z</dc:date>
    <item>
      <title>Protocol for download file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/protocol-for-download-file/m-p/2995563#M125305</link>
      <description>We use UNIX as the database server , the users use emulation program ( Netterm / Reflection ) to telnet to access the database and download files , cos they support different protocol , we work fine to use sz for netterm and unixlink2 for reflection , could you suggest what protocol is the best for download files on diff. dmulation program ? thx.</description>
      <pubDate>Thu, 12 Jun 2003 09:02:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/protocol-for-download-file/m-p/2995563#M125305</guid>
      <dc:creator>juno2</dc:creator>
      <dc:date>2003-06-12T09:02:20Z</dc:date>
    </item>
    <item>
      <title>Re: Protocol for download file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/protocol-for-download-file/m-p/2995564#M125306</link>
      <description>ftp</description>
      <pubDate>Thu, 12 Jun 2003 12:37:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/protocol-for-download-file/m-p/2995564#M125306</guid>
      <dc:creator>twang</dc:creator>
      <dc:date>2003-06-12T12:37:26Z</dc:date>
    </item>
    <item>
      <title>Re: Protocol for download file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/protocol-for-download-file/m-p/2995565#M125307</link>
      <description>There are many levels of security needed.&lt;BR /&gt;&lt;BR /&gt;I would use ftp for all but the least secure type of downloads.  &lt;BR /&gt;&lt;BR /&gt;If security is an issue, then I'd go whole hog and use a double blind sockets with return connect and encryption keys in the OOB data.&lt;BR /&gt;&lt;BR /&gt;Tim Sanko</description>
      <pubDate>Thu, 12 Jun 2003 12:50:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/protocol-for-download-file/m-p/2995565#M125307</guid>
      <dc:creator>Tim Sanko</dc:creator>
      <dc:date>2003-06-12T12:50:30Z</dc:date>
    </item>
    <item>
      <title>Re: Protocol for download file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/protocol-for-download-file/m-p/2995566#M125308</link>
      <description>The answer really is that ftp with good password policies on the Unix servers will work for almost all of the non -critical security downloads.  &lt;BR /&gt;&lt;BR /&gt;For NSA-NASA-DOD the other custom type applications go so far beyond a Kerebros or other validation program it is unusual to see them because of the costs associated in making them work.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Tim</description>
      <pubDate>Thu, 12 Jun 2003 12:56:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/protocol-for-download-file/m-p/2995566#M125308</guid>
      <dc:creator>Tim Sanko</dc:creator>
      <dc:date>2003-06-12T12:56:35Z</dc:date>
    </item>
    <item>
      <title>Re: Protocol for download file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/protocol-for-download-file/m-p/2995567#M125309</link>
      <description>As long as moderate security is adequate then I would choose FTP; specifically using the Perl Net::FTP module. You can download and install one of the freely available Perl's for Windows (&lt;A href="http://www.activestate.com" target="_blank"&gt;www.activestate.com&lt;/A&gt; is one) and then script everything inclding the database access and the downloads. The same scripts would work on PC's and UNIX; you wouldn't even need a terminal emulator in the picture. I've posted several example so if you search for "FTP" and "Perl" you will get some ideas.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 12 Jun 2003 13:12:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/protocol-for-download-file/m-p/2995567#M125309</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2003-06-12T13:12:01Z</dc:date>
    </item>
    <item>
      <title>Re: Protocol for download file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/protocol-for-download-file/m-p/2995568#M125310</link>
      <description>Secure shell is prolly the best and most secure.  You can get WinSCP for the Windows side of the equation.  Its a little slow making the initial connection, but once that is made is just as fast as ftp or rcp. &lt;BR /&gt;&lt;BR /&gt;And instead of Reflection, consider Citrix Metaframe for Unix.  It is also secure because it is compressed and encrypted.  Its also A LOT more easy to maintain in the long run.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Chris</description>
      <pubDate>Thu, 12 Jun 2003 13:16:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/protocol-for-download-file/m-p/2995568#M125310</guid>
      <dc:creator>Chris Vail</dc:creator>
      <dc:date>2003-06-12T13:16:45Z</dc:date>
    </item>
  </channel>
</rss>

