<?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 crossing uid in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-crossing-uid/m-p/5062876#M738129</link>
    <description>&lt;!--!*#--&gt;... and for the actual connection, there are two ways to do it:&lt;BR /&gt;  ssh -l uid2 system2&lt;BR /&gt;or&lt;BR /&gt;  ssh uid2@system2&lt;BR /&gt;&lt;BR /&gt;MK</description>
    <pubDate>Mon, 13 Aug 2007 14:43:02 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2007-08-13T14:43:02Z</dc:date>
    <item>
      <title>ssh crossing uid</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-crossing-uid/m-p/5062874#M738127</link>
      <description>I have a system1 with uid1 &amp;amp; would like to authenticate using publickey to system2 using uid2.&lt;BR /&gt;&lt;BR /&gt;Is this possible allowed using ssh?&lt;BR /&gt;&lt;BR /&gt;Thx&lt;BR /&gt;Paresh</description>
      <pubDate>Mon, 13 Aug 2007 14:33:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-crossing-uid/m-p/5062874#M738127</guid>
      <dc:creator>Paresh</dc:creator>
      <dc:date>2007-08-13T14:33:05Z</dc:date>
    </item>
    <item>
      <title>Re: ssh crossing uid</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-crossing-uid/m-p/5062875#M738128</link>
      <description>Of course. Generate the key for uid1 on system1 using ssh-keygen. Put the public key in ~uid2/.ssh/authorized_keys on system2. That's all there is to it.</description>
      <pubDate>Mon, 13 Aug 2007 14:35:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-crossing-uid/m-p/5062875#M738128</guid>
      <dc:creator>Jeff_Traigle</dc:creator>
      <dc:date>2007-08-13T14:35:22Z</dc:date>
    </item>
    <item>
      <title>Re: ssh crossing uid</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-crossing-uid/m-p/5062876#M738129</link>
      <description>&lt;!--!*#--&gt;... and for the actual connection, there are two ways to do it:&lt;BR /&gt;  ssh -l uid2 system2&lt;BR /&gt;or&lt;BR /&gt;  ssh uid2@system2&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Mon, 13 Aug 2007 14:43:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-crossing-uid/m-p/5062876#M738129</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2007-08-13T14:43:02Z</dc:date>
    </item>
    <item>
      <title>Re: ssh crossing uid</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-crossing-uid/m-p/5062877#M738130</link>
      <description>Tried it, does not work, whileas it works for the same id.&lt;BR /&gt;&lt;BR /&gt;lnaunx24.prd&amp;gt;/home/cyborg/.ssh:ssh  -v hrdload@lnaunx25.prd.na.lafarge.com&lt;BR /&gt;OpenSSH_4.2p1-hpn, OpenSSL 0.9.7i 14 Oct 2005&lt;BR /&gt;HP-UX Secure Shell-A.04.20.004, HP-UX Secure Shell version&lt;BR /&gt;debug1: Reading configuration data /opt/ssh/etc/ssh_config&lt;BR /&gt;debug1: Connecting to lnaunx25.prd.na.lafarge.com [10.178.13.108] port 22.&lt;BR /&gt;debug1: Connection established.&lt;BR /&gt;debug1: identity file /home/cyborg/.ssh/id_rsa type 1&lt;BR /&gt;debug1: identity file /home/cyborg/.ssh/id_dsa type -1&lt;BR /&gt;debug1: Remote protocol version 2.0, remote software version OpenSSH_4.2p1-hpn&lt;BR /&gt;debug1: match: OpenSSH_4.2p1-hpn pat OpenSSH*&lt;BR /&gt;debug1: Enabling compatibility mode for protocol 2.0&lt;BR /&gt;debug1: Local version string SSH-2.0-OpenSSH_4.2p1-hpn&lt;BR /&gt;debug1: SSH2_MSG_KEXINIT sent&lt;BR /&gt;debug1: SSH2_MSG_KEXINIT received&lt;BR /&gt;debug1: kex: server-&amp;gt;client aes128-cbc hmac-md5 none&lt;BR /&gt;debug1: kex: client-&amp;gt;server aes128-cbc hmac-md5 none&lt;BR /&gt;debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024&amp;lt;1024&amp;lt;8192) sent&lt;BR /&gt;debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP&lt;BR /&gt;debug1: SSH2_MSG_KEX_DH_GEX_INIT sent&lt;BR /&gt;debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY&lt;BR /&gt;debug1: Host 'lnaunx25.prd.na.lafarge.com' is known and matches the RSA host key.&lt;BR /&gt;debug1: Found key in /home/cyborg/.ssh/known_hosts:1&lt;BR /&gt;debug1: ssh_rsa_verify: signature correct&lt;BR /&gt;debug1: SSH2_MSG_NEWKEYS sent&lt;BR /&gt;debug1: expecting SSH2_MSG_NEWKEYS&lt;BR /&gt;debug1: SSH2_MSG_NEWKEYS received&lt;BR /&gt;debug1: SSH2_MSG_SERVICE_REQUEST sent&lt;BR /&gt;debug1: SSH2_MSG_SERVICE_ACCEPT received&lt;BR /&gt;debug1: Authentications that can continue: publickey,password,keyboard-interactive&lt;BR /&gt;debug1: Next authentication method: publickey&lt;BR /&gt;debug1: Offering public key: /home/cyborg/.ssh/id_rsa&lt;BR /&gt;debug1: Authentications that can continue: publickey,password,keyboard-interactive&lt;BR /&gt;debug1: Trying private key: /home/cyborg/.ssh/id_dsa&lt;BR /&gt;debug1: Next authentication method: keyboard-interactive&lt;BR /&gt;Password: &lt;BR /&gt;lnaunx24.prd&amp;gt;/home/cyborg/.ssh:</description>
      <pubDate>Mon, 13 Aug 2007 15:01:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-crossing-uid/m-p/5062877#M738130</guid>
      <dc:creator>Paresh</dc:creator>
      <dc:date>2007-08-13T15:01:51Z</dc:date>
    </item>
    <item>
      <title>Re: ssh crossing uid</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-crossing-uid/m-p/5062878#M738131</link>
      <description>When you created the RSA key for this connection did you simply confirm the default suggestion of ~/.ssh/id_rsa,&lt;BR /&gt;or did you specify a different file name?&lt;BR /&gt;If so then you also need to refer to this when you start the connection, using the -i option.&lt;BR /&gt;&lt;BR /&gt;e.g.&lt;BR /&gt;&lt;BR /&gt;$ ssh -i ~/.ssh/some_other_keyfile_name -l remote_user remote_host remote_command&lt;BR /&gt;&lt;BR /&gt;Note that you only name the file name of the private key (without the suffix .pub).&lt;BR /&gt;&lt;BR /&gt;Also, check on remote host in remote user's $HOME/.ssh/authorized_keys if the public key from key issuer really is contained.&lt;BR /&gt;(compare fingerprints issued by ssh-keygen command)&lt;BR /&gt;Check the owner ship and perms of $HOME/.ssh and $HOME/.ssh/authorized_keys on remote host.&lt;BR /&gt;Look into remote syslog.log for sshd messages.</description>
      <pubDate>Tue, 14 Aug 2007 09:04:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-crossing-uid/m-p/5062878#M738131</guid>
      <dc:creator>Ralph Grothe</dc:creator>
      <dc:date>2007-08-14T09:04:09Z</dc:date>
    </item>
    <item>
      <title>Re: ssh crossing uid</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-crossing-uid/m-p/5062879#M738132</link>
      <description>It might also be a good idea to check out that you're using compatible ssh versions on the machines...</description>
      <pubDate>Wed, 15 Aug 2007 11:17:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-crossing-uid/m-p/5062879#M738132</guid>
      <dc:creator>Tor-Arne Nostdal</dc:creator>
      <dc:date>2007-08-15T11:17:44Z</dc:date>
    </item>
    <item>
      <title>Re: ssh crossing uid</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-crossing-uid/m-p/5062880#M738133</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Here is how I did it.&lt;BR /&gt;&lt;BR /&gt;ssh-keygen -t dsa &lt;BR /&gt;&lt;BR /&gt;&lt;ENTER through="" all="" the="" questions=""&gt;&lt;BR /&gt;&lt;BR /&gt;I take id_dsa.pub to the secon server, different user (used sftp)&lt;BR /&gt;&lt;BR /&gt;cat id_dsa.pub &amp;gt;&amp;gt; authorized_keys&lt;BR /&gt;&lt;BR /&gt;In the .ssh directory.&lt;BR /&gt;&lt;BR /&gt;This appended the entry and immediately let usera on the orignal host log into the user account of userb on the target server without a password.&lt;BR /&gt;&lt;BR /&gt;SEP&lt;/ENTER&gt;</description>
      <pubDate>Wed, 15 Aug 2007 11:31:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-crossing-uid/m-p/5062880#M738133</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2007-08-15T11:31:33Z</dc:date>
    </item>
    <item>
      <title>Re: ssh crossing uid</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-crossing-uid/m-p/5062881#M738134</link>
      <description>It's working now.&lt;BR /&gt;&lt;BR /&gt;Not sure what I did wrong earlier.&lt;BR /&gt;&lt;BR /&gt;Anyways thanks to all for getting back.&lt;BR /&gt;&lt;BR /&gt;This forum support is really cool&lt;BR /&gt;&lt;BR /&gt;Thx&lt;BR /&gt;Paresh.</description>
      <pubDate>Thu, 16 Aug 2007 13:45:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-crossing-uid/m-p/5062881#M738134</guid>
      <dc:creator>Paresh</dc:creator>
      <dc:date>2007-08-16T13:45:36Z</dc:date>
    </item>
    <item>
      <title>Re: ssh crossing uid</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-crossing-uid/m-p/5062882#M738135</link>
      <description>all is good.</description>
      <pubDate>Thu, 16 Aug 2007 13:47:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-crossing-uid/m-p/5062882#M738135</guid>
      <dc:creator>Paresh</dc:creator>
      <dc:date>2007-08-16T13:47:39Z</dc:date>
    </item>
  </channel>
</rss>

