<?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: chroot not working in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124837#M151776</link>
    <description>John,&lt;BR /&gt;&lt;BR /&gt;On my Linux ftp server which uses ftpaccess and has an ftpusers group just like you are trying to use, I have an entry in my ftpaccess file like this:&lt;BR /&gt;&lt;BR /&gt;class ftpusers guest *&lt;BR /&gt;&lt;BR /&gt;Give it a try with this line and with the guestgroup ftpusers uncommented.&lt;BR /&gt;&lt;BR /&gt;JP&lt;BR /&gt;</description>
    <pubDate>Thu, 20 Nov 2003 10:30:38 GMT</pubDate>
    <dc:creator>John Poff</dc:creator>
    <dc:date>2003-11-20T10:30:38Z</dc:date>
    <item>
      <title>chroot not working</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124822#M151761</link>
      <description>2 questons actually&lt;BR /&gt;I set up the user in the /etc/password file as such:&lt;BR /&gt;&lt;BR /&gt;villaeri:password:21959:101:Name,location,,:/usr/sap/trans/./:/usr/bin/ksh&lt;BR /&gt;&lt;BR /&gt;and when i ftp he goes to the correct directory "/usr/sap/trans" but is able to "cd .." to /usr/sap which is what i want to prevent.  &lt;BR /&gt;&lt;BR /&gt;on another note.  when i use /etc/ftponly (or anthying i set up to do an exit 0) it won't let him log in.  I don't seem to have an /etc/shells file either.  could this be a problem?  I want to prevent him from telnetting in &amp;amp; only want him to be able to ftp into the box</description>
      <pubDate>Thu, 20 Nov 2003 09:08:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124822#M151761</guid>
      <dc:creator>John Meissner</dc:creator>
      <dc:date>2003-11-20T09:08:57Z</dc:date>
    </item>
    <item>
      <title>Re: chroot not working</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124823#M151762</link>
      <description>Hi John!&lt;BR /&gt;&lt;BR /&gt;What does your ftpaccess file look like?  That is where you'll need to setup the account to be restricted with chroot.&lt;BR /&gt;&lt;BR /&gt;You will need an /etc/shells file to use /etc/ftponly.  I would try creating /etc/shells first, with the /etc/ftponly entry, change his shell to ftponly, and try it again.&lt;BR /&gt;&lt;BR /&gt;JP&lt;BR /&gt;</description>
      <pubDate>Thu, 20 Nov 2003 09:13:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124823#M151762</guid>
      <dc:creator>John Poff</dc:creator>
      <dc:date>2003-11-20T09:13:38Z</dc:date>
    </item>
    <item>
      <title>Re: chroot not working</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124824#M151763</link>
      <description>Hi,&lt;BR /&gt;i do not see where you set up the chroot..&lt;BR /&gt;&lt;BR /&gt;/usr/sap/trans and /usr/sap are both accessible to a used belonging to the sapsys group, if you want to prevent this, you should really use the chroot, but doing so you will loose the chance of doing transports, because to won't find TPPARAM.&lt;BR /&gt;&lt;BR /&gt;Maybe using rsh (restricted sheel) can help, but i'm not sure.&lt;BR /&gt;&lt;BR /&gt;Better will bve to create a simple script that offers the user a manu of what to do, disabling ctrl+c using the trap command.&lt;BR /&gt;&lt;BR /&gt;To prevent the user to login, you must first create the /etc/shell, the put therein all valid shells (sh, csh, ksh, /sbin/sh, false)&lt;BR /&gt;then setup /bin/false as his/her shell.&lt;BR /&gt;&lt;BR /&gt;  Massimo&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 20 Nov 2003 09:14:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124824#M151763</guid>
      <dc:creator>Massimo Bianchi</dc:creator>
      <dc:date>2003-11-20T09:14:19Z</dc:date>
    </item>
    <item>
      <title>Re: chroot not working</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124825#M151764</link>
      <description>John,&lt;BR /&gt;&lt;BR /&gt;I do not know if this is the only way but this works:&lt;BR /&gt;Configure /etc/ftpd/ftpaccess and adjust the inetd.conf  to start ftpd -a. copy usr/bin/ls to the chrooted home dir of the user.&lt;BR /&gt;&lt;BR /&gt;Gideon&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 20 Nov 2003 09:17:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124825#M151764</guid>
      <dc:creator>G. Vrijhoeven</dc:creator>
      <dc:date>2003-11-20T09:17:38Z</dc:date>
    </item>
    <item>
      <title>Re: chroot not working</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124826#M151765</link>
      <description>Theres also an ftpaccess file that may help not allowing the person to go back a directory.&lt;BR /&gt;&lt;BR /&gt;/usr/newconfig/etc/ftpd/examples/ftpaccess is a sample ftpaccess file&lt;BR /&gt;&lt;BR /&gt;Dave&lt;BR /&gt;</description>
      <pubDate>Thu, 20 Nov 2003 09:18:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124826#M151765</guid>
      <dc:creator>Dave Hutton</dc:creator>
      <dc:date>2003-11-20T09:18:53Z</dc:date>
    </item>
    <item>
      <title>Re: chroot not working</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124827#M151766</link>
      <description>I'm not sure if i did it correctly but by setting up "class readonly ftpusers and making the user in the group ftpusers... and also later in the file putting "upload  /usr/sap/trans  *       no      readonly" I was trying to set it up as readonly for this user... what did i do wrong?&lt;BR /&gt;here is what my /etc/ftpd/ftpaccess file looks like:&lt;BR /&gt;&lt;BR /&gt;loginfails 2&lt;BR /&gt;&lt;BR /&gt;class    all real *&lt;BR /&gt;class   readonly        ftpusers&lt;BR /&gt;&lt;BR /&gt;limit   local   20  Any                 /etc/msgs/msg.toomany&lt;BR /&gt;limit   remote  100 SaSu|Any1800-0600   /etc/msgs/msg.toomany&lt;BR /&gt;limit   remote  60  Any                 /etc/msgs/msg.toomany&lt;BR /&gt;&lt;BR /&gt;readme  README*    login&lt;BR /&gt;readme  README*    cwd=*&lt;BR /&gt;&lt;BR /&gt;message /welcome.msg            login&lt;BR /&gt;message .message                cwd=*&lt;BR /&gt;&lt;BR /&gt;compress        yes             local remote&lt;BR /&gt;tar             yes             local remote&lt;BR /&gt;&lt;BR /&gt;# allow use of private file for SITE GROUP and SITE GPASS?&lt;BR /&gt;private         yes&lt;BR /&gt;&lt;BR /&gt;# passwd-check  &lt;NONE&gt;  [&lt;ENFORCE&gt;]&lt;BR /&gt;passwd-check    rfc822  warn&lt;BR /&gt;&lt;BR /&gt;log commands real&lt;BR /&gt;log transfers anonymous,real,ftpusers inbound,outbound&lt;BR /&gt;shutdown /etc/shutmsg&lt;BR /&gt;&lt;BR /&gt;# all the following default to "yes" for everybody&lt;BR /&gt;delete          no      guest,anonymous         # delete permission?&lt;BR /&gt;overwrite       no      guest,anonymous         # overwrite permission?&lt;BR /&gt;rename                  no              guest,anonymous # rename permission?&lt;BR /&gt;chmod           no      anonymous               # chmod permission?&lt;BR /&gt;umask           no      anonymous               # umask permission?&lt;BR /&gt;&lt;BR /&gt;# specify the upload directory information&lt;BR /&gt;upload  /var/ftp  *             no&lt;BR /&gt;upload  /var/ftp  /incoming     yes     root    daemon  0600 dirs&lt;BR /&gt;upload  /var/ftp  /bin          no&lt;BR /&gt;upload  /var/ftp  /etc          no&lt;BR /&gt;upload  /usr/sap/trans  *       no      readonly&lt;BR /&gt;# directory aliases&lt;BR /&gt;alias   inc    /incoming&lt;BR /&gt;# cdpath&lt;BR /&gt;cdpath  /incoming&lt;BR /&gt;cdpath  /pub&lt;BR /&gt;cdpath  /&lt;BR /&gt;&lt;BR /&gt;# path-filter...&lt;BR /&gt;path-filter  anonymous  /etc/pathmsg  ^[-A-Za-z0-9_\.]*$  ^\.  ^-&lt;BR /&gt;path-filter  guest      /etc/pathmsg  ^[-A-Za-z0-9_\.]*$  ^\.  ^-&lt;BR /&gt;&lt;BR /&gt;# specify which group of users will be treated as "guests".&lt;BR /&gt;#guestgroup ftpusers&lt;BR /&gt;&lt;BR /&gt;email user@hostname&lt;BR /&gt;&lt;/ENFORCE&gt;&lt;/NONE&gt;</description>
      <pubDate>Thu, 20 Nov 2003 09:23:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124827#M151766</guid>
      <dc:creator>John Meissner</dc:creator>
      <dc:date>2003-11-20T09:23:56Z</dc:date>
    </item>
    <item>
      <title>Re: chroot not working</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124828#M151767</link>
      <description>Yes... i added the -a in the inetd.conf file... and did an inetd -c ... i used the sample file as my basis for setting the ftpaccess up but i probably didn't do it correctly.</description>
      <pubDate>Thu, 20 Nov 2003 09:25:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124828#M151767</guid>
      <dc:creator>John Meissner</dc:creator>
      <dc:date>2003-11-20T09:25:32Z</dc:date>
    </item>
    <item>
      <title>Re: chroot not working</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124829#M151768</link>
      <description>Hi,&lt;BR /&gt;long time no see...&lt;BR /&gt;You need to specify in /etc/ftpd/ftpaccess  that the user in question is a member of the guestgroup. That is at least one explanation why the restrictions do no apply. A simple test for checking is to look at what happens when the ftp session is esablished. If the phrase: "Access restrictions apply" appears at login for the user, the restrictions are active. If not, they are disregarded.&lt;BR /&gt; &lt;BR /&gt;regards,&lt;BR /&gt;John K.&lt;BR /&gt;</description>
      <pubDate>Thu, 20 Nov 2003 09:34:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124829#M151768</guid>
      <dc:creator>john korterman</dc:creator>
      <dc:date>2003-11-20T09:34:16Z</dc:date>
    </item>
    <item>
      <title>Re: chroot not working</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124830#M151769</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;provide the user with ls, check /var/adm/syslog.log for messages..&lt;BR /&gt;&lt;BR /&gt;Shell must can be /bin/false, but you must put it in /etc/shells&lt;BR /&gt;&lt;BR /&gt;Gideon&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 20 Nov 2003 09:37:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124830#M151769</guid>
      <dc:creator>G. Vrijhoeven</dc:creator>
      <dc:date>2003-11-20T09:37:28Z</dc:date>
    </item>
    <item>
      <title>Re: chroot not working</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124831#M151770</link>
      <description>Hi... yeah.. i've been away for a while... "hi everyone"  ...&lt;BR /&gt;&lt;BR /&gt;The user is a member of the group ftpusers which is defined as their primary group.  I also specify ftpusers in the ftpaccess file... but am i doing it correctly?  or do i have to specify the user specifically?  and once i do ... how do i set their access to read only?  sorry for all the questions</description>
      <pubDate>Thu, 20 Nov 2003 09:37:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124831#M151770</guid>
      <dc:creator>John Meissner</dc:creator>
      <dc:date>2003-11-20T09:37:59Z</dc:date>
    </item>
    <item>
      <title>Re: chroot not working</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124832#M151771</link>
      <description>Hi,&lt;BR /&gt;just asked, as this looks uncommented:&lt;BR /&gt;#guestgroup ftpusers&lt;BR /&gt;in your ftpaccess file, meaning that no user group at all is regarded as a guestgroup.&lt;BR /&gt;BTW, remember to restart inetd after every change in ftpaccess.&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;John K.</description>
      <pubDate>Thu, 20 Nov 2003 09:44:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124832#M151771</guid>
      <dc:creator>john korterman</dc:creator>
      <dc:date>2003-11-20T09:44:25Z</dc:date>
    </item>
    <item>
      <title>Re: chroot not working</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124833#M151772</link>
      <description>Yes... it was commented out becuase when i leave it uncommented i get the following error:&lt;BR /&gt;&lt;BR /&gt;530 User villaeri access denied....&lt;BR /&gt;Login failed.&lt;BR /&gt;Remote system type is UNIX.&lt;BR /&gt;Using binary mode to transfer files.&lt;BR /&gt;&lt;BR /&gt;but when i comment it out the log in works.  &lt;BR /&gt;</description>
      <pubDate>Thu, 20 Nov 2003 09:49:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124833#M151772</guid>
      <dc:creator>John Meissner</dc:creator>
      <dc:date>2003-11-20T09:49:40Z</dc:date>
    </item>
    <item>
      <title>Re: chroot not working</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124834#M151773</link>
      <description>Hi,&lt;BR /&gt;try changing the user config. of the home dir in /etc/passwd to e.g.:&lt;BR /&gt;.....:/usr/sap/trans/./vialeridir:/usr/bin/false&lt;BR /&gt;and create the valieridir under /usr/sap/trans, owned by valieri.&lt;BR /&gt;You would normally make a common ftp users dir, in this case /usr/sap/trans and then make each ftp user's dir below. I think that your current configuration tries to make the "normal" root dir valieri's home dir.&lt;BR /&gt;You also should uncomment the guestgroup line in ftpaccess and restart inetd.&lt;BR /&gt;Good luck.&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;John K.&lt;BR /&gt;</description>
      <pubDate>Thu, 20 Nov 2003 10:04:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124834#M151773</guid>
      <dc:creator>john korterman</dc:creator>
      <dc:date>2003-11-20T10:04:49Z</dc:date>
    </item>
    <item>
      <title>Re: chroot not working</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124835#M151774</link>
      <description>John... i got the same error... 530 user villaeri access denied...&lt;BR /&gt;&lt;BR /&gt;seems like it doesn't let anyone in guestgroup log in for some reason.  can i set him up in another mannor?</description>
      <pubDate>Thu, 20 Nov 2003 10:15:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124835#M151774</guid>
      <dc:creator>John Meissner</dc:creator>
      <dc:date>2003-11-20T10:15:35Z</dc:date>
    </item>
    <item>
      <title>Re: chroot not working</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124836#M151775</link>
      <description>setting up the other directory as you suggested and commenting the guestgroup out again did log him in to /usr/sap/trans/villaeri ... but i don't want to allow him to cd .. from /usr/sap trans... not sure why it's not working.&lt;BR /&gt;&lt;BR /&gt;I also have to make his access read only without changing the permissions of any files.  gotta love this stuff :(</description>
      <pubDate>Thu, 20 Nov 2003 10:18:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124836#M151775</guid>
      <dc:creator>John Meissner</dc:creator>
      <dc:date>2003-11-20T10:18:30Z</dc:date>
    </item>
    <item>
      <title>Re: chroot not working</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124837#M151776</link>
      <description>John,&lt;BR /&gt;&lt;BR /&gt;On my Linux ftp server which uses ftpaccess and has an ftpusers group just like you are trying to use, I have an entry in my ftpaccess file like this:&lt;BR /&gt;&lt;BR /&gt;class ftpusers guest *&lt;BR /&gt;&lt;BR /&gt;Give it a try with this line and with the guestgroup ftpusers uncommented.&lt;BR /&gt;&lt;BR /&gt;JP&lt;BR /&gt;</description>
      <pubDate>Thu, 20 Nov 2003 10:30:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124837#M151776</guid>
      <dc:creator>John Poff</dc:creator>
      <dc:date>2003-11-20T10:30:38Z</dc:date>
    </item>
    <item>
      <title>Re: chroot not working</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124838#M151777</link>
      <description>John.  That makes the chroot command work perfectly!  he ends up in the villaeri directory i created under /usr/sap/trans... and it sees /usr/sap/trans as /   ... the one problem is that when i do an ls nothing displays in /usr/sap/trans... any idea?</description>
      <pubDate>Thu, 20 Nov 2003 10:38:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124838#M151777</guid>
      <dc:creator>John Meissner</dc:creator>
      <dc:date>2003-11-20T10:38:40Z</dc:date>
    </item>
    <item>
      <title>Re: chroot not working</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124839#M151778</link>
      <description>Does he have permission to see any of those files?&lt;BR /&gt;&lt;BR /&gt;I saw your note about having to make it all be read-only.  I'm still thinking over that one.&lt;BR /&gt;&lt;BR /&gt;JP&lt;BR /&gt;</description>
      <pubDate>Thu, 20 Nov 2003 10:40:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124839#M151778</guid>
      <dc:creator>John Poff</dc:creator>
      <dc:date>2003-11-20T10:40:27Z</dc:date>
    </item>
    <item>
      <title>Re: chroot not working</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124840#M151779</link>
      <description>John - yes.  the permissions on almost all the files in the /usr/sap/trans are 755 so he does have read permissions on them - they are all directories</description>
      <pubDate>Thu, 20 Nov 2003 10:45:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124840#M151779</guid>
      <dc:creator>John Meissner</dc:creator>
      <dc:date>2003-11-20T10:45:33Z</dc:date>
    </item>
    <item>
      <title>Re: chroot not working</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124841#M151780</link>
      <description>What are , exaclty, uid and gid for villaeri ?&lt;BR /&gt;What are the permissions for /usr/sap and /usr/sap/trans, /usr/sap/trans/villaeri ?&lt;BR /&gt;&lt;BR /&gt;  Massimo&lt;BR /&gt;</description>
      <pubDate>Thu, 20 Nov 2003 10:46:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/chroot-not-working/m-p/3124841#M151780</guid>
      <dc:creator>Massimo Bianchi</dc:creator>
      <dc:date>2003-11-20T10:46:26Z</dc:date>
    </item>
  </channel>
</rss>

