<?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: SSL in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ssl/m-p/3202667#M166958</link>
    <description>If you use named based virtual hosting its not possible to run ssl on the server.&lt;BR /&gt;&lt;BR /&gt;I think you can get away with it if you use ip based virtual hosting or dedicate an ip address to the ssl connection.&lt;BR /&gt;&lt;BR /&gt;I'm working on that and will report back.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Thu, 26 Feb 2004 01:15:00 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2004-02-26T01:15:00Z</dc:date>
    <item>
      <title>SSL</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssl/m-p/3202664#M166955</link>
      <description>Hi&lt;BR /&gt;     If we decided to take away ftp,rlogin,remsh,finger and try to work with SSH,SCP will the codes that were written with open socket function get affected , or I can just concentrate on finding out codes that are using remsh,rcp and ftp .&lt;BR /&gt;&lt;BR /&gt;Thanx</description>
      <pubDate>Thu, 26 Feb 2004 00:53:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssl/m-p/3202664#M166955</guid>
      <dc:creator>Sathish C</dc:creator>
      <dc:date>2004-02-26T00:53:03Z</dc:date>
    </item>
    <item>
      <title>Re: SSL</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssl/m-p/3202665#M166956</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Yes it will get affected, you have to look for code using remsh,rcp anf ftp</description>
      <pubDate>Thu, 26 Feb 2004 01:07:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssl/m-p/3202665#M166956</guid>
      <dc:creator>Ravi_8</dc:creator>
      <dc:date>2004-02-26T01:07:08Z</dc:date>
    </item>
    <item>
      <title>Re: SSL</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssl/m-p/3202666#M166957</link>
      <description>anything that uses remesh can be done with ssh&lt;BR /&gt;anything that can be done with rcp can be done with scp&lt;BR /&gt;anything you do with ftp can be done, even scripted with sftp.&lt;BR /&gt;&lt;BR /&gt;Good choice.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 26 Feb 2004 01:11:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssl/m-p/3202666#M166957</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2004-02-26T01:11:57Z</dc:date>
    </item>
    <item>
      <title>Re: SSL</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssl/m-p/3202667#M166958</link>
      <description>If you use named based virtual hosting its not possible to run ssl on the server.&lt;BR /&gt;&lt;BR /&gt;I think you can get away with it if you use ip based virtual hosting or dedicate an ip address to the ssl connection.&lt;BR /&gt;&lt;BR /&gt;I'm working on that and will report back.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 26 Feb 2004 01:15:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssl/m-p/3202667#M166958</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2004-02-26T01:15:00Z</dc:date>
    </item>
    <item>
      <title>Re: SSL</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssl/m-p/3202668#M166959</link>
      <description>How do we do about socket() functions that were written via c or c++ code ? What I mean is If search my Configuration Control System with codes that contains remsh,ftp,rcp this will not suffice this SSL implementation , Am I right ?</description>
      <pubDate>Thu, 26 Feb 2004 01:17:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssl/m-p/3202668#M166959</guid>
      <dc:creator>Sathish C</dc:creator>
      <dc:date>2004-02-26T01:17:36Z</dc:date>
    </item>
    <item>
      <title>Re: SSL</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssl/m-p/3202669#M166960</link>
      <description>You will need to change and recompile that code.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 26 Feb 2004 01:24:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssl/m-p/3202669#M166960</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2004-02-26T01:24:06Z</dc:date>
    </item>
    <item>
      <title>Re: SSL</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssl/m-p/3202670#M166961</link>
      <description>If you want all communications from your system encrypted, you might consider using IPSEC, which can be configured at the IP level and thus can cover everything at once.&lt;BR /&gt;&lt;BR /&gt;Note that this is _not_ the same as excrypting at the socket layer a la SSL.&lt;BR /&gt;&lt;BR /&gt;As pointed-out, if you also want arbitrary socket applications to use SSL you will need to take steps to compile them to use it.</description>
      <pubDate>Fri, 27 Feb 2004 14:01:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssl/m-p/3202670#M166961</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2004-02-27T14:01:03Z</dc:date>
    </item>
  </channel>
</rss>

