<?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 Restricted User Access in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/restricted-user-access/m-p/5058528#M436249</link>
    <description>Hi Friends&lt;BR /&gt;&lt;BR /&gt;I got the requirement to create user account in my Rx server that running HP-UX 11.23 and that user only can access a particular folder only (/oracle/bscs/CDR)&lt;BR /&gt;&lt;BR /&gt;So I create a user with default shell as /usr/sbin/rsh and change user account home directory as (/oracle/bscs/CDR)&lt;BR /&gt;&lt;BR /&gt;So my requirement is that the user only allow to access this folder contains only. When I implement this he can't go to parent directory as expected, but he couldn't able to go child directories also . &lt;BR /&gt;&lt;BR /&gt;So how can I overcome this problem (allow him to go to child directories of CDR ) and implement above requirement?&lt;BR /&gt;&lt;BR /&gt;Thanks &amp;amp; Regards&lt;BR /&gt;&lt;BR /&gt;Dhananjaya Amarakoon&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 17 Jul 2007 08:42:48 GMT</pubDate>
    <dc:creator>Dhananjaya Amarakoon</dc:creator>
    <dc:date>2007-07-17T08:42:48Z</dc:date>
    <item>
      <title>Restricted User Access</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/restricted-user-access/m-p/5058528#M436249</link>
      <description>Hi Friends&lt;BR /&gt;&lt;BR /&gt;I got the requirement to create user account in my Rx server that running HP-UX 11.23 and that user only can access a particular folder only (/oracle/bscs/CDR)&lt;BR /&gt;&lt;BR /&gt;So I create a user with default shell as /usr/sbin/rsh and change user account home directory as (/oracle/bscs/CDR)&lt;BR /&gt;&lt;BR /&gt;So my requirement is that the user only allow to access this folder contains only. When I implement this he can't go to parent directory as expected, but he couldn't able to go child directories also . &lt;BR /&gt;&lt;BR /&gt;So how can I overcome this problem (allow him to go to child directories of CDR ) and implement above requirement?&lt;BR /&gt;&lt;BR /&gt;Thanks &amp;amp; Regards&lt;BR /&gt;&lt;BR /&gt;Dhananjaya Amarakoon&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 17 Jul 2007 08:42:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/restricted-user-access/m-p/5058528#M436249</guid>
      <dc:creator>Dhananjaya Amarakoon</dc:creator>
      <dc:date>2007-07-17T08:42:48Z</dc:date>
    </item>
    <item>
      <title>Re: Restricted User Access</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/restricted-user-access/m-p/5058529#M436250</link>
      <description>With a restricted shell, changing the directory is not permitted.&lt;BR /&gt;&lt;BR /&gt;Ideally, setting up a system like this requires only a good system-wide permissions design. &lt;BR /&gt;&lt;BR /&gt;"Can access nothing but /oracle/bscs/CDR" very seldom means exactly that: if the user does not have read access to /etc, things like UID-&amp;gt;username mapping and DNS resolving stop working for that user. If /dev/null is not accessible, many commands work strangely or not at all. If /usr or /lib is not readable, almost all commands become non-functional, because either the command binaries or the libraries they need are not available.&lt;BR /&gt;&lt;BR /&gt;You could create specific groups for all sub-sets of your data according to access requirements, then join your user and application accounts to various groups as needed. &lt;BR /&gt;&lt;BR /&gt;With a traditional Unix permissions model, a file belongs to one group only, but an user can be a member of multiple groups simultaneously. When the users get their access permissions via group memberships, you can "chmod o-rx" the data directories.&lt;BR /&gt;&lt;BR /&gt;This kind of permission scheme is easiest to set up in a new system: changing an old system to use a new permission scheme is usually a lot of work.&lt;BR /&gt;&lt;BR /&gt;With some careful pre-planning, you can satisfy all but the most complicated access needs; if you need more, you can use ACLs to fine-tune the permissions.&lt;BR /&gt;&lt;BR /&gt;If you use ACLs, ensure your backup system can backup and restore the ACL information too. If your backup system does not handle ACLs on HP-UX filesystems, you should keep your ACL setup as simple and well-documented as possible, and write+test a script that can correctly re-generate the necessary ACLs on restore.&lt;BR /&gt;&lt;BR /&gt;A different possibility would be to set up a chroot jail for that user. A chroot jail makes the jailed user see the jail directory (e.g. /oracle/bscs/CDR) as the root directory "/", so the things "above" the jail directory simply won't exist in that user's viewpoint.&lt;BR /&gt;&lt;BR /&gt;This is easier to do if the requirement is for FTP or SFTP access only: if the user needs full shell access, you must provide (suitably limited) copies of essential directory trees like /dev, /etc, /lib and /usr as /oracle/bscs/CDR/dev and so on. &lt;BR /&gt;&lt;BR /&gt;Symbolic links won't work in this case: if you create a link like&lt;BR /&gt;&lt;BR /&gt;ln -s /dev /oracle/bscs/CDR/dev&lt;BR /&gt;&lt;BR /&gt;it will just point to itself when viewed inside a chrooted environment.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Tue, 17 Jul 2007 09:35:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/restricted-user-access/m-p/5058529#M436250</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2007-07-17T09:35:34Z</dc:date>
    </item>
    <item>
      <title>Re: Restricted User Access</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/restricted-user-access/m-p/5058530#M436251</link>
      <description>He should not need to cd to child directories as he can specify the commands and reference the files using the paths.&lt;BR /&gt;&lt;BR /&gt;You should also consider the use of SSH and chroot, please see:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.docs.hp.com/en/T1471-90011/ch01s12.html" target="_blank"&gt;http://www.docs.hp.com/en/T1471-90011/ch01s12.html&lt;/A&gt;</description>
      <pubDate>Tue, 17 Jul 2007 10:55:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/restricted-user-access/m-p/5058530#M436251</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2007-07-17T10:55:01Z</dc:date>
    </item>
    <item>
      <title>Re: Restricted User Access</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/restricted-user-access/m-p/5058531#M436252</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;I would suggest a chroot environment.&lt;BR /&gt;&lt;BR /&gt;That will permit access.&lt;BR /&gt;&lt;BR /&gt;Use ssh.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/T1471-90015/ch01s15.html" target="_blank"&gt;http://docs.hp.com/en/T1471-90015/ch01s15.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 17 Jul 2007 11:16:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/restricted-user-access/m-p/5058531#M436252</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2007-07-17T11:16:00Z</dc:date>
    </item>
    <item>
      <title>Re: Restricted User Access</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/restricted-user-access/m-p/5058532#M436253</link>
      <description>Hi Matti Kurkela,Ivan Ferreira and Steven E. Protter&lt;BR /&gt;&lt;BR /&gt;Thanks for the guide me. As you suggested I will go to impliment chroot environment for this user.&lt;BR /&gt;&lt;BR /&gt;Thanks &amp;amp; Regards&lt;BR /&gt;&lt;BR /&gt;Dhananjaya Amarakoon.</description>
      <pubDate>Wed, 18 Jul 2007 00:28:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/restricted-user-access/m-p/5058532#M436253</guid>
      <dc:creator>Dhananjaya Amarakoon</dc:creator>
      <dc:date>2007-07-18T00:28:51Z</dc:date>
    </item>
  </channel>
</rss>

