<?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 root login in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-root-login/m-p/3469789#M211480</link>
    <description>To see if you are locked out, enter this command from a console or a terminal:&lt;BR /&gt;&lt;BR /&gt;/usr/lbin/getprpw -m lockout "username"&lt;BR /&gt;any non-zero return indicates lockout.&lt;BR /&gt;&lt;BR /&gt;To clear the lock:&lt;BR /&gt;&lt;BR /&gt;/usr/lbin/modprpw -k "username"&lt;BR /&gt;&lt;BR /&gt;Jitao Yin&lt;BR /&gt;</description>
    <pubDate>Mon, 24 Jan 2005 13:43:59 GMT</pubDate>
    <dc:creator>Jitao Yin_2</dc:creator>
    <dc:date>2005-01-24T13:43:59Z</dc:date>
    <item>
      <title>SSH root login</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-root-login/m-p/3469784#M211475</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Having noticed that recent many logon attempts as root through SSH came on my server, I just wanted to ask for 2 questions:&lt;BR /&gt;- after an account (root, in this case) has been locked out (for too many attempts) is it possible to re-enable it from the command line ? Maybe with sudo ?&lt;BR /&gt;- I tried to inhibit root logons via SSH, adding a "deny file" to the sshd daemon. This works in general (even with the right password you cannot logon), but does not inhibit the registration mechanism of the accesses: that is, after n logon attempts (3 in my case) the user is definitely locked out from the machine. Is there a better mechanism ? Maybe /etc/securetty ?&lt;BR /&gt;&lt;BR /&gt;Thank you&lt;BR /&gt;&lt;BR /&gt;  -- Enrico&lt;BR /&gt;</description>
      <pubDate>Mon, 24 Jan 2005 12:51:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-root-login/m-p/3469784#M211475</guid>
      <dc:creator>enrico.nic</dc:creator>
      <dc:date>2005-01-24T12:51:23Z</dc:date>
    </item>
    <item>
      <title>Re: SSH root login</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-root-login/m-p/3469785#M211476</link>
      <description>Set PermitRootLogin No in /etc/ssh/sshd_config and better also have a /etc/securetty around.&lt;BR /&gt;&lt;BR /&gt;honestly I never had to re-enable a locked account, I guess simply doing a passwd will do, but You will have to do it at the console.</description>
      <pubDate>Mon, 24 Jan 2005 12:55:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-root-login/m-p/3469785#M211476</guid>
      <dc:creator>Florian Heigl (new acc)</dc:creator>
      <dc:date>2005-01-24T12:55:20Z</dc:date>
    </item>
    <item>
      <title>Re: SSH root login</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-root-login/m-p/3469786#M211477</link>
      <description>Sorry I forgot to mention that I would preferably re-enable the account from remote, without accessing the console.&lt;BR /&gt;Thank you</description>
      <pubDate>Mon, 24 Jan 2005 13:03:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-root-login/m-p/3469786#M211477</guid>
      <dc:creator>enrico.nic</dc:creator>
      <dc:date>2005-01-24T13:03:09Z</dc:date>
    </item>
    <item>
      <title>Re: SSH root login</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-root-login/m-p/3469787#M211478</link>
      <description>To reenable the root account after being locked out from too many login attempts, do so from the console.&lt;BR /&gt;&lt;BR /&gt;If you already have a window open with the root account active, can do so via SAM</description>
      <pubDate>Mon, 24 Jan 2005 13:06:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-root-login/m-p/3469787#M211478</guid>
      <dc:creator>Rick Garland</dc:creator>
      <dc:date>2005-01-24T13:06:51Z</dc:date>
    </item>
    <item>
      <title>Re: SSH root login</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-root-login/m-p/3469788#M211479</link>
      <description>Root account can be enabled two ways:&lt;BR /&gt;&lt;BR /&gt;console login.&lt;BR /&gt;&lt;BR /&gt;/usr/lbin/modprpw -l -k root&lt;BR /&gt;&lt;BR /&gt;How to do the second is rough unless you have a session already logged in.&lt;BR /&gt;&lt;BR /&gt;You can also boot single user mode and reset the passwrd portion of /etc/passwd or /etc/shadow for shadow systems or /tcb/files/auth/r/root &lt;BR /&gt;&lt;BR /&gt;SEP&lt;BR /&gt;</description>
      <pubDate>Mon, 24 Jan 2005 13:39:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-root-login/m-p/3469788#M211479</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2005-01-24T13:39:41Z</dc:date>
    </item>
    <item>
      <title>Re: SSH root login</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-root-login/m-p/3469789#M211480</link>
      <description>To see if you are locked out, enter this command from a console or a terminal:&lt;BR /&gt;&lt;BR /&gt;/usr/lbin/getprpw -m lockout "username"&lt;BR /&gt;any non-zero return indicates lockout.&lt;BR /&gt;&lt;BR /&gt;To clear the lock:&lt;BR /&gt;&lt;BR /&gt;/usr/lbin/modprpw -k "username"&lt;BR /&gt;&lt;BR /&gt;Jitao Yin&lt;BR /&gt;</description>
      <pubDate>Mon, 24 Jan 2005 13:43:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-root-login/m-p/3469789#M211480</guid>
      <dc:creator>Jitao Yin_2</dc:creator>
      <dc:date>2005-01-24T13:43:59Z</dc:date>
    </item>
    <item>
      <title>Re: SSH root login</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-root-login/m-p/3469790#M211481</link>
      <description>As most sysadmins have found out, any Unix box that is running SSH and also connectred to the open Internet (or their firewall permits SSH passthrough) has been regularly attacked from kiddie scripts run in Asia and also from Europe. root login via SSH should ALWAYS be disabled, especially if the systems have incoming Internet connections (look at syslog for sshd reporting DNS problems). The modprpw command will re-enable root but only when you are already a root user. This is where sudo is quite useful. /etc/securetty should also exist like this:&lt;BR /&gt; &lt;BR /&gt;echo console &amp;gt; /etc/securetty&lt;BR /&gt; &lt;BR /&gt;Now, telnet and terminals or modems on serial lines cannot login as root. NOTE: remsh and rexec, etc still work OK and could be used to run modprpw. Note that modprpw is located in a special place:&lt;BR /&gt; &lt;BR /&gt;rexec snoopy /usr/lbin/modprpw -k root&lt;BR /&gt;</description>
      <pubDate>Mon, 24 Jan 2005 16:04:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-root-login/m-p/3469790#M211481</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2005-01-24T16:04:26Z</dc:date>
    </item>
  </channel>
</rss>

