<?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 host based auth. quesion in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/ssh-host-based-auth-quesion/m-p/3742866#M51721</link>
    <description>Thomas,&lt;BR /&gt;&lt;BR /&gt;an initial test on OpenVMS Alpha V8.2 and TCPIP V5.5 seems to support your impression.&lt;BR /&gt;&lt;BR /&gt;Once I add 'client.node.domain user' to SYS$SYSDEVICE:[TCPIP$SSH.SSH2]SHOSTS.EQUIV on the server (after copying all required host key files), this user can login to all accounts on the host (using $ SSH -l username host) from the SSH client.&lt;BR /&gt;&lt;BR /&gt;There may be SSH options, which would prevent this, but I'm not yet familiar enough with all this stuff. The best docu I've found so far, does not seem to talk about this in enough detail:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/openvms/products/ssh/ssh.pdf" target="_blank"&gt;http://h71000.www7.hp.com/openvms/products/ssh/ssh.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
    <pubDate>Thu, 02 Mar 2006 13:05:41 GMT</pubDate>
    <dc:creator>Volker Halle</dc:creator>
    <dc:date>2006-03-02T13:05:41Z</dc:date>
    <item>
      <title>SSH host based auth. quesion</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ssh-host-based-auth-quesion/m-p/3742865#M51720</link>
      <description>Question:&lt;BR /&gt;&lt;BR /&gt;Using host based authentication,  is it possible to restrict to a single user on a remote (client) node to only have access to a single account on the local (server) node?&lt;BR /&gt;&lt;BR /&gt;I'm under the impression that if you specify a trusted host and user in the shosts.equiv file, that gives that user access to _ALL_ accounts on the local (i.e. server) node.  Am I correct?</description>
      <pubDate>Thu, 02 Mar 2006 12:00:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ssh-host-based-auth-quesion/m-p/3742865#M51720</guid>
      <dc:creator>Thomas A. Williams</dc:creator>
      <dc:date>2006-03-02T12:00:56Z</dc:date>
    </item>
    <item>
      <title>Re: SSH host based auth. quesion</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ssh-host-based-auth-quesion/m-p/3742866#M51721</link>
      <description>Thomas,&lt;BR /&gt;&lt;BR /&gt;an initial test on OpenVMS Alpha V8.2 and TCPIP V5.5 seems to support your impression.&lt;BR /&gt;&lt;BR /&gt;Once I add 'client.node.domain user' to SYS$SYSDEVICE:[TCPIP$SSH.SSH2]SHOSTS.EQUIV on the server (after copying all required host key files), this user can login to all accounts on the host (using $ SSH -l username host) from the SSH client.&lt;BR /&gt;&lt;BR /&gt;There may be SSH options, which would prevent this, but I'm not yet familiar enough with all this stuff. The best docu I've found so far, does not seem to talk about this in enough detail:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/openvms/products/ssh/ssh.pdf" target="_blank"&gt;http://h71000.www7.hp.com/openvms/products/ssh/ssh.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Thu, 02 Mar 2006 13:05:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ssh-host-based-auth-quesion/m-p/3742866#M51721</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2006-03-02T13:05:41Z</dc:date>
    </item>
    <item>
      <title>Re: SSH host based auth. quesion</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ssh-host-based-auth-quesion/m-p/3742867#M51722</link>
      <description>Thomas,&lt;BR /&gt;&lt;BR /&gt;if you don't want a user on the client node to access all accounts on the server by creating an entry in TCPIP$SSH_DEVICE:[TCPIP$SSH]SHOSTS.EQUIV, you could use user-based SHOSTS. files.&lt;BR /&gt;&lt;BR /&gt;In the user's login directory on the SSH server, create a file SYS$LOGIN:SHOSTS. and add the ip name of the SSH client and the user name of the user on the SSH client, which should be allowed host based authenticated access to this user account on the SSH server.&lt;BR /&gt;&lt;BR /&gt;See the chapter: 'Customizing Host-Based Authentication on the Server' in the SSH documentation (page 36).&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Thu, 02 Mar 2006 13:36:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ssh-host-based-auth-quesion/m-p/3742867#M51722</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2006-03-02T13:36:46Z</dc:date>
    </item>
    <item>
      <title>Re: SSH host based auth. quesion</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ssh-host-based-auth-quesion/m-p/3742868#M51723</link>
      <description>Tom,&lt;BR /&gt;&lt;BR /&gt;I hope this is possible.&lt;BR /&gt;&lt;BR /&gt;Normally the hosts.equiv file is searched first, followed by the user's sys$login:shost/rhost file, if it exists. If any entry in the hosts file cannot override the hosts.equiv file. But there is exception to the system user in the order.&lt;BR /&gt;&lt;BR /&gt;So if you want restrict local account access to any specific ssh client user, edit that local user sys$login:shost/rhost file and enter the same entry you have now in your shosts.equiv file, such as  &lt;BR /&gt;"rfqdn rusername"&lt;BR /&gt;&lt;BR /&gt;This will allow the specific user remote user to have accesss only to the particular account and it deny access to the other accounts in the server.&lt;BR /&gt;&lt;BR /&gt;Archunan&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 02 Mar 2006 13:58:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ssh-host-based-auth-quesion/m-p/3742868#M51723</guid>
      <dc:creator>Arch_Muthiah</dc:creator>
      <dc:date>2006-03-02T13:58:42Z</dc:date>
    </item>
  </channel>
</rss>

