<?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 over virtual IPs in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-over-virtual-ips/m-p/4498723#M364587</link>
    <description>I don't like the solution of having identical host keys for two servers, even if they're part of a cluster. What I do, which might be considered overkill, is run an SSH service on an alternate port, with a different sshd_config file, and it references its own host key which is linked to the virtual IP only. I go as far as putting the keyfile in a filesystem with is part of the package so it moves with the package from one node to another.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 17 Sep 2009 01:05:31 GMT</pubDate>
    <dc:creator>Olivier Masse</dc:creator>
    <dc:date>2009-09-17T01:05:31Z</dc:date>
    <item>
      <title>SSH over virtual IPs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-over-virtual-ips/m-p/4498721#M364585</link>
      <description>hi,&lt;BR /&gt;i am using SSH host-based password less authentication for cluster.&lt;BR /&gt;cluster node physical IP (ssh clients) cnB1 and cnB2 independently connect to a SSH server. I had to put physical IP/hostname of cluster nodes in server. authentication doesnot work, if i put package IP of the cluster in ssh_known_hosts in /etc/opt/ssh of the SSH server. its bit difficult to manage so many physical IP and keys. &lt;BR /&gt;how can i make authentication work over virtual IP of cluster.&lt;BR /&gt;thanks.</description>
      <pubDate>Wed, 16 Sep 2009 15:24:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-over-virtual-ips/m-p/4498721#M364585</guid>
      <dc:creator>Pradep</dc:creator>
      <dc:date>2009-09-16T15:24:34Z</dc:date>
    </item>
    <item>
      <title>Re: SSH over virtual IPs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-over-virtual-ips/m-p/4498722#M364586</link>
      <description>When the SSH client moves between cluster nodes:&lt;BR /&gt;&lt;BR /&gt;ssh -o BindAddress=IP.address.of.package &lt;OTHER parameters=""&gt;&lt;BR /&gt;&lt;BR /&gt;If the outgoing SSH connections are made by a particular user account and the home directory of that user is included on the package disk(s), put the BindAddress= option to the ~/.ssh/config file of that user.&lt;BR /&gt;&lt;BR /&gt;The same "-o BindAddress=1.2.3.4" option can be used with scp and sftp too.&lt;BR /&gt;&lt;BR /&gt;-----------&lt;BR /&gt;&lt;BR /&gt;When the SSH server moves between cluster nodes:&lt;BR /&gt;&lt;BR /&gt;The cluster nodes are supposed to generally look like multiple incarnations of the same host when viewed from the outside of the cluster, right? &lt;BR /&gt;&lt;BR /&gt;This is a situation where it might be useful to copy the SSH host keys (/opt/ssh/etc/ssh_host_*_key* on HP SSH, /etc/ssh/ssh_host_*_key*) from one node to all other nodes, so that each node of the cluster uses the same set of host keys.&lt;BR /&gt;&lt;BR /&gt;This makes the client receive the same SSH host key when contacting the packet IP address, no matter which node the package is running on.&lt;BR /&gt;&lt;BR /&gt;MK&lt;/OTHER&gt;</description>
      <pubDate>Wed, 16 Sep 2009 19:06:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-over-virtual-ips/m-p/4498722#M364586</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2009-09-16T19:06:40Z</dc:date>
    </item>
    <item>
      <title>Re: SSH over virtual IPs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-over-virtual-ips/m-p/4498723#M364587</link>
      <description>I don't like the solution of having identical host keys for two servers, even if they're part of a cluster. What I do, which might be considered overkill, is run an SSH service on an alternate port, with a different sshd_config file, and it references its own host key which is linked to the virtual IP only. I go as far as putting the keyfile in a filesystem with is part of the package so it moves with the package from one node to another.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Sep 2009 01:05:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-over-virtual-ips/m-p/4498723#M364587</guid>
      <dc:creator>Olivier Masse</dc:creator>
      <dc:date>2009-09-17T01:05:31Z</dc:date>
    </item>
    <item>
      <title>Re: SSH over virtual IPs</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-over-virtual-ips/m-p/4498724#M364588</link>
      <description>the scenario is pkg is not moved to another node. but still ssh dont authenticate if the enter the pkg IP in SSH server /etc/opt/ssh/ssh_known_hosts files&lt;BR /&gt;it only works if the enter physical client hostname in the server side file.&lt;BR /&gt;&lt;BR /&gt;actually my question was why SSH needs to work on physical client IP address entries in ssh_known_hosts file of the SSH server.&lt;BR /&gt;&lt;BR /&gt;eg:-&lt;BR /&gt;&lt;BR /&gt;this entry dont work&lt;BR /&gt;# cat ssh_known_hosts&lt;BR /&gt;phyClienthost.com ssh-dss AAAAB3NzaC....&lt;BR /&gt;&lt;BR /&gt;the SSH server dont authenticate when entry on SSH server side is&lt;BR /&gt;&lt;BR /&gt;# cat ssh_known_hosts&lt;BR /&gt;pkgClienthost.com ssh-dss AAAAB3NzaC....&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;similarly i have to put, this entry for host based authentication equivalency.&lt;BR /&gt;&lt;BR /&gt;# cat shosts.equiv&lt;BR /&gt;phyClienthost.com     root&lt;BR /&gt; and pkgClienthost.com  root dont work.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Sep 2009 01:38:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-over-virtual-ips/m-p/4498724#M364588</guid>
      <dc:creator>Pradep</dc:creator>
      <dc:date>2009-09-17T01:38:48Z</dc:date>
    </item>
  </channel>
</rss>

