<?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: fsecure &amp;amp; openssh key conversion in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/fsecure-amp-openssh-key-conversion/m-p/3356402#M746906</link>
    <description>OpenSSH's "ssh-keygen" command has options to convert keys from commercial to openssh format and vice versa.&lt;BR /&gt;&lt;BR /&gt;Last time I looked, the commercial SSH could only convert from openssh to commercial format.&lt;BR /&gt;&lt;BR /&gt;If you have the commercial format key as "commercial.pub", you would convert it with OpenSSH ssh-keygen like this:&lt;BR /&gt;&lt;BR /&gt;  ssh-keygen -i -f commercial.pub &amp;gt; openssh.pub&lt;BR /&gt;&lt;BR /&gt;The conversion from OpenSSH to commercial format would be:&lt;BR /&gt;&lt;BR /&gt;  ssh-keygen -e -f openssh.pub &amp;gt; commercial.pub&lt;BR /&gt;&lt;BR /&gt;Private keys can also be converted with these commands, but usually you don't need to do that unless you're replacing one kind of SSH software package with the other kind.&lt;BR /&gt;&lt;BR /&gt;If your OpenSSH ssh-keygen does not have these conversion options, your OpenSSH distribution is very old and very probably has known weaknesses. Upgrade.</description>
    <pubDate>Fri, 13 Aug 2004 07:40:45 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2004-08-13T07:40:45Z</dc:date>
    <item>
      <title>fsecure &amp; openssh key conversion</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fsecure-amp-openssh-key-conversion/m-p/3356401#M746905</link>
      <description>Hi,&lt;BR /&gt;Anyone can share with me how to convert fsecure keys to openssh? I need to rsh to openssh machine without having to key-in my password. &lt;BR /&gt;Being a newbie in ssh, I'd appreciate if anyone can provide a step-by-step guide to do this. Thanks.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 13 Aug 2004 03:25:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fsecure-amp-openssh-key-conversion/m-p/3356401#M746905</guid>
      <dc:creator>Rosli Ahmad</dc:creator>
      <dc:date>2004-08-13T03:25:46Z</dc:date>
    </item>
    <item>
      <title>Re: fsecure &amp; openssh key conversion</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fsecure-amp-openssh-key-conversion/m-p/3356402#M746906</link>
      <description>OpenSSH's "ssh-keygen" command has options to convert keys from commercial to openssh format and vice versa.&lt;BR /&gt;&lt;BR /&gt;Last time I looked, the commercial SSH could only convert from openssh to commercial format.&lt;BR /&gt;&lt;BR /&gt;If you have the commercial format key as "commercial.pub", you would convert it with OpenSSH ssh-keygen like this:&lt;BR /&gt;&lt;BR /&gt;  ssh-keygen -i -f commercial.pub &amp;gt; openssh.pub&lt;BR /&gt;&lt;BR /&gt;The conversion from OpenSSH to commercial format would be:&lt;BR /&gt;&lt;BR /&gt;  ssh-keygen -e -f openssh.pub &amp;gt; commercial.pub&lt;BR /&gt;&lt;BR /&gt;Private keys can also be converted with these commands, but usually you don't need to do that unless you're replacing one kind of SSH software package with the other kind.&lt;BR /&gt;&lt;BR /&gt;If your OpenSSH ssh-keygen does not have these conversion options, your OpenSSH distribution is very old and very probably has known weaknesses. Upgrade.</description>
      <pubDate>Fri, 13 Aug 2004 07:40:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fsecure-amp-openssh-key-conversion/m-p/3356402#M746906</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2004-08-13T07:40:45Z</dc:date>
    </item>
  </channel>
</rss>

