<?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: After setup /etc/securetty file, generating message in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/after-setup-etc-securetty-file-generating-message/m-p/4448722#M358385</link>
    <description>The standard /usr/bin/login does not have the facilities to create customized rejection messages.&lt;BR /&gt;&lt;BR /&gt;Instead, you might use /etc/issue (for serial-attached terminals) or banner files (for network connections; see the man page of your network connection server daemon) to announce this to *everyone* logging in.&lt;BR /&gt;&lt;BR /&gt;If the server knows in advance that an authentication attempt is inevitably going to fail (i.e. the user chose the username "root"), it is more secure to allow the user to go through the motions of the standard authentication procedure and *then* kick the user out, *without* telling him/her exactly what was wrong. &lt;BR /&gt;&lt;BR /&gt;This way a potential intruder cannot gather information on what is allowed and what isn't, and may spend some time making useless attempts. That allows the sysadmin more time and evidence to detect the intrusion attempt.&lt;BR /&gt;&lt;BR /&gt;MK</description>
    <pubDate>Mon, 29 Jun 2009 09:20:33 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2009-06-29T09:20:33Z</dc:date>
    <item>
      <title>After setup /etc/securetty file, generating message</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/after-setup-etc-securetty-file-generating-message/m-p/4448721#M358384</link>
      <description>I setup /etc/securetty file to inhibit access as root user. &lt;BR /&gt;&lt;BR /&gt;I want to generate information message when the user try to login with root user.&lt;BR /&gt;&lt;BR /&gt;It's just a sample message.&lt;BR /&gt;"The root user is prohobited to login.&lt;BR /&gt;You must login with other users."&lt;BR /&gt;&lt;BR /&gt;How can I generate above message?&lt;BR /&gt;Thanks in advance.</description>
      <pubDate>Mon, 29 Jun 2009 01:16:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/after-setup-etc-securetty-file-generating-message/m-p/4448721#M358384</guid>
      <dc:creator>Byun Hee Joong</dc:creator>
      <dc:date>2009-06-29T01:16:39Z</dc:date>
    </item>
    <item>
      <title>Re: After setup /etc/securetty file, generating message</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/after-setup-etc-securetty-file-generating-message/m-p/4448722#M358385</link>
      <description>The standard /usr/bin/login does not have the facilities to create customized rejection messages.&lt;BR /&gt;&lt;BR /&gt;Instead, you might use /etc/issue (for serial-attached terminals) or banner files (for network connections; see the man page of your network connection server daemon) to announce this to *everyone* logging in.&lt;BR /&gt;&lt;BR /&gt;If the server knows in advance that an authentication attempt is inevitably going to fail (i.e. the user chose the username "root"), it is more secure to allow the user to go through the motions of the standard authentication procedure and *then* kick the user out, *without* telling him/her exactly what was wrong. &lt;BR /&gt;&lt;BR /&gt;This way a potential intruder cannot gather information on what is allowed and what isn't, and may spend some time making useless attempts. That allows the sysadmin more time and evidence to detect the intrusion attempt.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Mon, 29 Jun 2009 09:20:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/after-setup-etc-securetty-file-generating-message/m-p/4448722#M358385</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2009-06-29T09:20:33Z</dc:date>
    </item>
    <item>
      <title>Re: After setup /etc/securetty file, generating message</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/after-setup-etc-securetty-file-generating-message/m-p/4448723#M358386</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;I would use /etc/issue as well.&lt;BR /&gt;&lt;BR /&gt;Or not use /etc/securetty and build some code into /etc/profile to display the message.&lt;BR /&gt;&lt;BR /&gt;/etc/issue and your current changes is the most secure way to prevent direct root login.&lt;BR /&gt;&lt;BR /&gt;You might also try public key only ssh login for root, it is very secure and convenient for administrators.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.hpux.ws/?p=19" target="_blank"&gt;http://www.hpux.ws/?p=19&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 29 Jun 2009 09:46:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/after-setup-etc-securetty-file-generating-message/m-p/4448723#M358386</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2009-06-29T09:46:15Z</dc:date>
    </item>
  </channel>
</rss>

