<?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 setup without root access in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/ssh-setup-without-root-access/m-p/4726200#M42666</link>
    <description>Replying to my own thread.  I have somewhat mitigated root access by creating a sim-specific user to use as a login account on the linux servers.  Now at least root access can be turned off.&lt;BR /&gt;&lt;BR /&gt;BUT, this still required password-based authentication which I still want to disable.&lt;BR /&gt;&lt;BR /&gt;Getting closer, Chris.</description>
    <pubDate>Tue, 14 Dec 2010 14:51:58 GMT</pubDate>
    <dc:creator>Chris Mosentine</dc:creator>
    <dc:date>2010-12-14T14:51:58Z</dc:date>
    <item>
      <title>ssh setup without root access</title>
      <link>https://community.hpe.com/t5/server-management-systems/ssh-setup-without-root-access/m-p/4726199#M42665</link>
      <description>I posted this question as part of another thread, but I think it deserves it's own thread.&lt;BR /&gt;&lt;BR /&gt;In configuring SIM access to my SUSE linux servers, I have had to open up ssh to allow root login via password, which I do not like to do, even on our network behind a good firewall.&lt;BR /&gt;&lt;BR /&gt;I can see possibly enabling root access for the initial setup, but what I don't understand is why root access in needed thereafter as certificate-based authentication should be working.  Below is my ssh_config file.&lt;BR /&gt;&lt;BR /&gt;Can you point out what I may be doing wrong?  Thanks, Chris.&lt;BR /&gt;&lt;BR /&gt;# The strategy used for options in the default sshd_config shipped with&lt;BR /&gt;# OpenSSH is to specify options with their default value where&lt;BR /&gt;# possible, but leave them commented.  Uncommented options change a&lt;BR /&gt;# default value.&lt;BR /&gt;&lt;BR /&gt;Port 22&lt;BR /&gt;Protocol 2&lt;BR /&gt;#AddressFamily any&lt;BR /&gt;#ListenAddress 0.0.0.0&lt;BR /&gt;#ListenAddress ::&lt;BR /&gt;&lt;BR /&gt;# HostKey for protocol version 1&lt;BR /&gt;#HostKey /etc/ssh/ssh_host_key&lt;BR /&gt;# HostKeys for protocol version 2&lt;BR /&gt;HostKey /etc/ssh/ssh_host_rsa_key&lt;BR /&gt;#HostKey /etc/ssh/ssh_host_dsa_key&lt;BR /&gt;&lt;BR /&gt;# Lifetime and size of ephemeral version 1 server key&lt;BR /&gt;#KeyRegenerationInterval 1h&lt;BR /&gt;#ServerKeyBits 768&lt;BR /&gt;&lt;BR /&gt;# Logging&lt;BR /&gt;# obsoletes QuietMode and FascistLogging&lt;BR /&gt;#SyslogFacility AUTH&lt;BR /&gt;#LogLevel INFO&lt;BR /&gt;&lt;BR /&gt;# Authentication:&lt;BR /&gt;&lt;BR /&gt;#LoginGraceTime 2m&lt;BR /&gt;PermitRootLogin yes&lt;BR /&gt;#StrictModes yes&lt;BR /&gt;#MaxAuthTries 6&lt;BR /&gt;&lt;BR /&gt;RSAAuthentication yes&lt;BR /&gt;PubkeyAuthentication yes&lt;BR /&gt;AuthorizedKeysFile .ssh/authorized_keys&lt;BR /&gt;&lt;BR /&gt;# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts&lt;BR /&gt;#RhostsRSAAuthentication yes&lt;BR /&gt;# similar for protocol version 2&lt;BR /&gt;HostbasedAuthentication yes &lt;BR /&gt;# Change to yes if you don't trust ~/.ssh/known_hosts for&lt;BR /&gt;HostbasedAuthentication yes &lt;BR /&gt;#IgnoreUserKnownHosts no&lt;BR /&gt;# Don't read the user's ~/.rhosts and ~/.shosts files&lt;BR /&gt;#IgnoreRhosts yes&lt;BR /&gt;&lt;BR /&gt;# To disable tunneled clear text passwords, change to no here!&lt;BR /&gt;PasswordAuthentication yes&lt;BR /&gt;PermitEmptyPasswords no&lt;BR /&gt;&lt;BR /&gt;# Change to no to disable s/key passwords&lt;BR /&gt;#ChallengeResponseAuthentication yes&lt;BR /&gt;&lt;BR /&gt;# Kerberos options&lt;BR /&gt;#KerberosAuthentication no&lt;BR /&gt;#KerberosOrLocalPasswd yes&lt;BR /&gt;#KerberosTicketCleanup yes&lt;BR /&gt;#KerberosGetAFSToken no&lt;BR /&gt;&lt;BR /&gt;# GSSAPI options&lt;BR /&gt;#GSSAPIAuthentication no&lt;BR /&gt;#GSSAPICleanupCredentials yes&lt;BR /&gt;&lt;BR /&gt;# Set this to 'yes' to enable support for the deprecated 'gssapi' authentication&lt;BR /&gt;# mechanism to OpenSSH 3.8p1. The newer 'gssapi-with-mic' mechanism is included&lt;BR /&gt;# in this release. The use of 'gssapi' is deprecated due to the presence of &lt;BR /&gt;# potential man-in-the-middle attacks, which 'gssapi-with-mic' is not susceptible to.&lt;BR /&gt;#GSSAPIEnableMITMAttack no&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;# Set this to 'yes' to enable PAM authentication, account processing, &lt;BR /&gt;# and session processing. If this is enabled, PAM authentication will &lt;BR /&gt;# be allowed through the ChallengeResponseAuthentication mechanism. &lt;BR /&gt;# Depending on your PAM configuration, this may bypass the setting of &lt;BR /&gt;# PasswordAuthentication, PermitEmptyPasswords, and &lt;BR /&gt;# "PermitRootLogin without-password". If you just want the PAM account and &lt;BR /&gt;# session checks to run without PAM authentication, then enable this but set &lt;BR /&gt;# ChallengeResponseAuthentication=no&lt;BR /&gt;UsePAM yes&lt;BR /&gt;&lt;BR /&gt;#AllowTcpForwarding yes&lt;BR /&gt;#GatewayPorts no&lt;BR /&gt;X11Forwarding yes &lt;BR /&gt;#X11DisplayOffset 10&lt;BR /&gt;#X11UseLocalhost yes&lt;BR /&gt;#PrintMotd yes&lt;BR /&gt;#PrintLastLog yes&lt;BR /&gt;#TCPKeepAlive yes&lt;BR /&gt;#UseLogin no&lt;BR /&gt;#UsePrivilegeSeparation yes&lt;BR /&gt;#PermitUserEnvironment no&lt;BR /&gt;#Compression delayed&lt;BR /&gt;#ClientAliveInterval 0&lt;BR /&gt;#ClientAliveCountMax 3&lt;BR /&gt;#UseDNS yes&lt;BR /&gt;#PidFile /var/run/sshd.pid&lt;BR /&gt;#MaxStartups 10&lt;BR /&gt;&lt;BR /&gt;# no default banner path&lt;BR /&gt;#Banner /some/path&lt;BR /&gt;&lt;BR /&gt;# override default of no subsystems&lt;BR /&gt;Subsystem sftp /usr/lib64/ssh/sftp-server&lt;BR /&gt;&lt;BR /&gt;# This enables accepting locale enviroment variables LC_* LANG, see sshd_config(5).&lt;BR /&gt;AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES &lt;BR /&gt;AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT &lt;BR /&gt;AcceptEnv LC_IDENTIFICATION LC_ALL&lt;BR /&gt;</description>
      <pubDate>Tue, 14 Dec 2010 14:00:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/ssh-setup-without-root-access/m-p/4726199#M42665</guid>
      <dc:creator>Chris Mosentine</dc:creator>
      <dc:date>2010-12-14T14:00:41Z</dc:date>
    </item>
    <item>
      <title>Re: ssh setup without root access</title>
      <link>https://community.hpe.com/t5/server-management-systems/ssh-setup-without-root-access/m-p/4726200#M42666</link>
      <description>Replying to my own thread.  I have somewhat mitigated root access by creating a sim-specific user to use as a login account on the linux servers.  Now at least root access can be turned off.&lt;BR /&gt;&lt;BR /&gt;BUT, this still required password-based authentication which I still want to disable.&lt;BR /&gt;&lt;BR /&gt;Getting closer, Chris.</description>
      <pubDate>Tue, 14 Dec 2010 14:51:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/ssh-setup-without-root-access/m-p/4726200#M42666</guid>
      <dc:creator>Chris Mosentine</dc:creator>
      <dc:date>2010-12-14T14:51:58Z</dc:date>
    </item>
  </channel>
</rss>

