<?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: Users restriction? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/users-restriction/m-p/2465623#M15686</link>
    <description>If you can get hold of the IP-address instead you could use /var/adm/inetd.sec to control access.</description>
    <pubDate>Mon, 20 Nov 2000 10:21:27 GMT</pubDate>
    <dc:creator>Tommy Palo</dc:creator>
    <dc:date>2000-11-20T10:21:27Z</dc:date>
    <item>
      <title>Users restriction?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/users-restriction/m-p/2465620#M15683</link>
      <description>hello all,&lt;BR /&gt;    What are the diifferent ways to restrict users to log on to the system from a specific 'tty'.&lt;BR /&gt;eg. user--&amp;gt; should log from tty /dev/pty3 only.</description>
      <pubDate>Sat, 18 Nov 2000 03:54:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/users-restriction/m-p/2465620#M15683</guid>
      <dc:creator>ashwin</dc:creator>
      <dc:date>2000-11-18T03:54:32Z</dc:date>
    </item>
    <item>
      <title>Re: Users restriction?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/users-restriction/m-p/2465621#M15684</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;This may help for root&lt;BR /&gt;If the /etc/securetty file is present, login security is in effect.     &lt;BR /&gt;Only user root is allowed to log in successfully on the ttys listed in  &lt;BR /&gt;this file.  Restricted ttys are listed by device name, one per line.    &lt;BR /&gt;Valid tty names are dependent on installation.  An example is           &lt;BR /&gt;                                               console&lt;BR /&gt;tty01&lt;BR /&gt;&lt;BR /&gt;To control a user to a specificy tty you can put a short scrip in their .profile to pick up their tty and if no match to tty in .profile throw a exit at them, this has the ability to allow a user a range of login ttys.&lt;BR /&gt;&lt;BR /&gt;See man login&lt;BR /&gt; &lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;Paula</description>
      <pubDate>Sat, 18 Nov 2000 11:52:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/users-restriction/m-p/2465621#M15684</guid>
      <dc:creator>Paula J Frazer-Campbell</dc:creator>
      <dc:date>2000-11-18T11:52:04Z</dc:date>
    </item>
    <item>
      <title>Re: Users restriction?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/users-restriction/m-p/2465622#M15685</link>
      <description>While you can certainly modify /etc/profile to restrict access by user name, time of day, number of logins allowed per user, terminal port and so on, network logins are a bit more complicated.  Your example of a pty login, while possible to test, will likely be of no use as pty ports are assigned not by the requestor but as needed by the system.&lt;BR /&gt;&lt;BR /&gt;Thus, for any given login, the pty (now more likely, a streams pts device file) assigned will be essentially unpredictable.&lt;BR /&gt;&lt;BR /&gt;However, you can certainly test for the name or IP address of the incoming device using who -mur.</description>
      <pubDate>Sun, 19 Nov 2000 20:21:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/users-restriction/m-p/2465622#M15685</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2000-11-19T20:21:49Z</dc:date>
    </item>
    <item>
      <title>Re: Users restriction?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/users-restriction/m-p/2465623#M15686</link>
      <description>If you can get hold of the IP-address instead you could use /var/adm/inetd.sec to control access.</description>
      <pubDate>Mon, 20 Nov 2000 10:21:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/users-restriction/m-p/2465623#M15686</guid>
      <dc:creator>Tommy Palo</dc:creator>
      <dc:date>2000-11-20T10:21:27Z</dc:date>
    </item>
    <item>
      <title>Re: Users restriction?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/users-restriction/m-p/2465624#M15687</link>
      <description>thanks to all,&lt;BR /&gt;But what are other ways to restrict pertoculer user to login from /dev/tty3 other than putting a script in .profile.&lt;BR /&gt;&lt;BR /&gt;thankx once again to all.&lt;BR /&gt;</description>
      <pubDate>Wed, 22 Nov 2000 02:43:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/users-restriction/m-p/2465624#M15687</guid>
      <dc:creator>ashwin</dc:creator>
      <dc:date>2000-11-22T02:43:46Z</dc:date>
    </item>
    <item>
      <title>Re: Users restriction?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/users-restriction/m-p/2465625#M15688</link>
      <description>As mentioned, there is no way to predict what tty device the user will have.  However, the concept is simple.  Put the test in /etc/profile (.profile is under control of the user).  The test for the user ID and terminal as well as the incoming hostname or IP address can be combined in one command:&lt;BR /&gt;&lt;BR /&gt;who -muR&lt;BR /&gt;&lt;BR /&gt;Extract the fields like this:&lt;BR /&gt;&lt;BR /&gt;echo $(/usr/bin/who -muR) | awk '{print $1," " ,$2," ",$NF}' | read MYUID MYTTY MYPORT&lt;BR /&gt;&lt;BR /&gt;Now test $MYUID and $MYTTY or $MYPORT. If they don't meet your criteria, then just exit from /etc/profile (with an appropriate message).</description>
      <pubDate>Wed, 22 Nov 2000 03:04:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/users-restriction/m-p/2465625#M15688</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2000-11-22T03:04:27Z</dc:date>
    </item>
  </channel>
</rss>

