<?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: SSH Experts in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-experts/m-p/4981130#M419879</link>
    <description>ok, I figured this out.  The commercial ssh and openssh generate the public key in different formats.  To change formats, run ssh-keygen -i -f &amp;gt;&amp;gt; authorized_keys.  Normally, you would just cat pubkey &amp;gt;&amp;gt;authorized_keys.&lt;BR /&gt;&lt;BR /&gt;chris</description>
    <pubDate>Fri, 26 May 2006 15:34:30 GMT</pubDate>
    <dc:creator>Chrisl_2</dc:creator>
    <dc:date>2006-05-26T15:34:30Z</dc:date>
    <item>
      <title>SSH Experts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-experts/m-p/4981126#M419875</link>
      <description>Hi all.  On my hp systems, I have created passwordless ssh logins thru the following simple procedure.&lt;BR /&gt;1. have the remote user generate keys:&lt;BR /&gt;ssh-keygen -t rsa&lt;BR /&gt;this creates id_rsa and id_rsa.pub files&lt;BR /&gt;2. copy id_rsa.pub to my box&lt;BR /&gt;3. add id_rsa.pub to my authorized_keys file&lt;BR /&gt;done - works great&lt;BR /&gt;Problem - on a remote SUN I have the user run &lt;BR /&gt;ssh-keygen -t rsa.  It creates id_rsa_2048_a and id_rsa_2048_a.pub. I copy the pub key over to my box and add it to authorized_keys.  I can't connect.  The format of the public key is different in that is actually looks like it is contained  in an email.  Should I edit the key in authorized_keys to make it look format wise like the HP generated keys?&lt;BR /&gt;&lt;BR /&gt;TIA</description>
      <pubDate>Fri, 26 May 2006 11:56:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-experts/m-p/4981126#M419875</guid>
      <dc:creator>Chrisl_2</dc:creator>
      <dc:date>2006-05-26T11:56:10Z</dc:date>
    </item>
    <item>
      <title>Re: SSH Experts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-experts/m-p/4981127#M419876</link>
      <description>No,&lt;BR /&gt;&lt;BR /&gt;first of all check both SSH keys are version2 ssh keys - then and only then they should look the same and be compatible.&lt;BR /&gt;&lt;BR /&gt;I had the very same issue on my Tru64 box which still used SSHv1 - I wouldn't even have noticed without the issues. :)</description>
      <pubDate>Fri, 26 May 2006 11:58:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-experts/m-p/4981127#M419876</guid>
      <dc:creator>Florian Heigl (new acc)</dc:creator>
      <dc:date>2006-05-26T11:58:48Z</dc:date>
    </item>
    <item>
      <title>Re: SSH Experts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-experts/m-p/4981128#M419877</link>
      <description>according to man ssh-keygen the -t rsa generates a version 2 protocol.</description>
      <pubDate>Fri, 26 May 2006 12:04:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-experts/m-p/4981128#M419877</guid>
      <dc:creator>Chrisl_2</dc:creator>
      <dc:date>2006-05-26T12:04:05Z</dc:date>
    </item>
    <item>
      <title>Re: SSH Experts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-experts/m-p/4981129#M419878</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;generally it would help if you tell the OS-versions of HPs and SUNs.&lt;BR /&gt;&lt;BR /&gt;You can get more and more verbose output when doing&lt;BR /&gt;ssh -v host&lt;BR /&gt;ssh -vv host&lt;BR /&gt;ssh -vvv host&lt;BR /&gt;&lt;BR /&gt;This should give sufficent output to analyze the problem.&lt;BR /&gt;&lt;BR /&gt;mfG Peter</description>
      <pubDate>Fri, 26 May 2006 12:09:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-experts/m-p/4981129#M419878</guid>
      <dc:creator>Peter Nikitka</dc:creator>
      <dc:date>2006-05-26T12:09:17Z</dc:date>
    </item>
    <item>
      <title>Re: SSH Experts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-experts/m-p/4981130#M419879</link>
      <description>ok, I figured this out.  The commercial ssh and openssh generate the public key in different formats.  To change formats, run ssh-keygen -i -f &amp;gt;&amp;gt; authorized_keys.  Normally, you would just cat pubkey &amp;gt;&amp;gt;authorized_keys.&lt;BR /&gt;&lt;BR /&gt;chris</description>
      <pubDate>Fri, 26 May 2006 15:34:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-experts/m-p/4981130#M419879</guid>
      <dc:creator>Chrisl_2</dc:creator>
      <dc:date>2006-05-26T15:34:30Z</dc:date>
    </item>
    <item>
      <title>Re: SSH Experts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-experts/m-p/4981131#M419880</link>
      <description>see thread&lt;BR /&gt;</description>
      <pubDate>Fri, 26 May 2006 15:35:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-experts/m-p/4981131#M419880</guid>
      <dc:creator>Chrisl_2</dc:creator>
      <dc:date>2006-05-26T15:35:32Z</dc:date>
    </item>
  </channel>
</rss>

