<?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: vsftpd chroot in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/vsftpd-chroot/m-p/4956512#M550347</link>
    <description>you're welcome, of course.  &lt;BR /&gt;&lt;BR /&gt;... and I should have apologised for not actually answering the original question:&lt;BR /&gt;No, I haven't managed to get vsftpd to work chroot-ed&lt;BR /&gt;&lt;BR /&gt;... and yes I agree that chroot-ing in general is harder than it should be.&lt;BR /&gt;&lt;BR /&gt;I am leaning more in the direction of  SELINUX, where you define a policy which severely restricts what a given executable can do.  Not being able to read or write a file outside the homedir, seems as close to chroot as makes no difference.&lt;BR /&gt;&lt;BR /&gt;p.s. should have mentioned that CoreFTP Lite *can* also be an sftp client, tho' that ain't what I use it for.&lt;BR /&gt;</description>
    <pubDate>Tue, 21 Feb 2006 15:50:50 GMT</pubDate>
    <dc:creator>Mike Keighley</dc:creator>
    <dc:date>2006-02-21T15:50:50Z</dc:date>
    <item>
      <title>vsftpd chroot</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vsftpd-chroot/m-p/4956504#M550339</link>
      <description>Has anyone else successfully made chroot work in vsftpd via the configuration file?</description>
      <pubDate>Wed, 01 Feb 2006 11:39:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vsftpd-chroot/m-p/4956504#M550339</guid>
      <dc:creator>Thom Cornwell</dc:creator>
      <dc:date>2006-02-01T11:39:04Z</dc:date>
    </item>
    <item>
      <title>Re: vsftpd chroot</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vsftpd-chroot/m-p/4956505#M550340</link>
      <description>Here is the supporting software that I have installed:&lt;BR /&gt;&lt;BR /&gt;openssh-4.2p1&lt;BR /&gt;openssl-0.9.8a&lt;BR /&gt;HP-UX Secure Shell: sftp.c,v A.04.20.004&lt;BR /&gt;what /usr/local/sbin/vsftpd&lt;BR /&gt;/usr/local/sbin/vsftpd:&lt;BR /&gt;        $Revision: 92453-07 linker linker crt0.o B.11.47 051005 $&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Feb 2006 11:44:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vsftpd-chroot/m-p/4956505#M550340</guid>
      <dc:creator>Thom Cornwell</dc:creator>
      <dc:date>2006-02-01T11:44:13Z</dc:date>
    </item>
    <item>
      <title>Re: vsftpd chroot</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vsftpd-chroot/m-p/4956506#M550341</link>
      <description>grep -v "^#" vsftpd.conf&lt;BR /&gt;anonymous_enable=YES&lt;BR /&gt;local_enable=YES&lt;BR /&gt;write_enable=YES&lt;BR /&gt;local_umask=022&lt;BR /&gt;dirmessage_enable=YES&lt;BR /&gt;connect_from_port_20=YES&lt;BR /&gt;xferlog_file=/var/log/vsftpd.log&lt;BR /&gt;ftpd_banner=VSFTPD Server 2.03&lt;BR /&gt;chroot_list_file=/etc/vsftpd.chroot_list&lt;BR /&gt;xferlog_std_format=NO&lt;BR /&gt;xferlog_enable=YES&lt;BR /&gt;log_ftp_protocol=YES&lt;BR /&gt;check_shell=NO&lt;BR /&gt;vsftpd_log_file=/var/log/vsftpd.log&lt;BR /&gt;userlist_enable=YES&lt;BR /&gt;userlist_file=/etc/vsftpd.user_list&lt;BR /&gt;userlist_deny=NO&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Feb 2006 13:37:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vsftpd-chroot/m-p/4956506#M550341</guid>
      <dc:creator>Thom Cornwell</dc:creator>
      <dc:date>2006-02-01T13:37:19Z</dc:date>
    </item>
    <item>
      <title>Re: vsftpd chroot</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vsftpd-chroot/m-p/4956507#M550342</link>
      <description>I don't see these parameters in you configuration file:&lt;BR /&gt;&lt;BR /&gt;chroot_local_user=YES&lt;BR /&gt;chroot_list_enable=YES</description>
      <pubDate>Wed, 01 Feb 2006 13:56:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vsftpd-chroot/m-p/4956507#M550342</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2006-02-01T13:56:25Z</dc:date>
    </item>
    <item>
      <title>Re: vsftpd chroot</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vsftpd-chroot/m-p/4956508#M550343</link>
      <description>chroot_list_file=/etc/vsftpd.chroot_list&lt;BR /&gt;The other two are disabled, as the documentation reads that having them enabled, then the list works in reverse.</description>
      <pubDate>Wed, 01 Feb 2006 14:07:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vsftpd-chroot/m-p/4956508#M550343</guid>
      <dc:creator>Thom Cornwell</dc:creator>
      <dc:date>2006-02-01T14:07:47Z</dc:date>
    </item>
    <item>
      <title>Re: vsftpd chroot</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vsftpd-chroot/m-p/4956509#M550344</link>
      <description>I have discovered that I am not getting to the vsftpd, but instead am getting to the ssh subsystem /opt/ssh/libexec/sftp-server when I sftp to the system.  What I need to know at this point is how to tell sshd not to start /opt/ssh/libexex/sftp-server, but instead use the inetd.conf entry I have for the vsftpd for requests coming to port 20.  During this process I have successfully compiled the version 2.04 of vsftpd, thinking the problem was in version 2.03.</description>
      <pubDate>Thu, 02 Feb 2006 10:34:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vsftpd-chroot/m-p/4956509#M550344</guid>
      <dc:creator>Thom Cornwell</dc:creator>
      <dc:date>2006-02-02T10:34:14Z</dc:date>
    </item>
    <item>
      <title>Re: vsftpd chroot</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vsftpd-chroot/m-p/4956510#M550345</link>
      <description>A bit of a misunderstanding here, I think.&lt;BR /&gt;&lt;BR /&gt;vsftpd is NOT a replacement sftp server (is it ?)&lt;BR /&gt;&lt;BR /&gt;rather it is a conventional ftp server (ports 21 and 20) which implements the "AUTH TLS" and "PROT P" extensions to the ftp protocol, thus encrypting command or data or both.&lt;BR /&gt;&lt;BR /&gt;so yes, a remote sftp client will connect to openssh/sftpd, not vsftpd.&lt;BR /&gt;&lt;BR /&gt;a decent client for talking to vsftpd might be e.g. CoreFTP lite.&lt;BR /&gt;</description>
      <pubDate>Tue, 21 Feb 2006 14:37:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vsftpd-chroot/m-p/4956510#M550345</guid>
      <dc:creator>Mike Keighley</dc:creator>
      <dc:date>2006-02-21T14:37:07Z</dc:date>
    </item>
    <item>
      <title>Re: vsftpd chroot</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vsftpd-chroot/m-p/4956511#M550346</link>
      <description>Yes it was me the confused person who was the source of the problem ;-)  I however am now trimming down what is needed versus what is not needed when you use the ssh_chroot_setup.sh.  There just has to be an easier way to set up a chroot jail house for sftp users.  Thank you for the information about a viable client.</description>
      <pubDate>Tue, 21 Feb 2006 14:45:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vsftpd-chroot/m-p/4956511#M550346</guid>
      <dc:creator>Thom Cornwell</dc:creator>
      <dc:date>2006-02-21T14:45:12Z</dc:date>
    </item>
    <item>
      <title>Re: vsftpd chroot</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vsftpd-chroot/m-p/4956512#M550347</link>
      <description>you're welcome, of course.  &lt;BR /&gt;&lt;BR /&gt;... and I should have apologised for not actually answering the original question:&lt;BR /&gt;No, I haven't managed to get vsftpd to work chroot-ed&lt;BR /&gt;&lt;BR /&gt;... and yes I agree that chroot-ing in general is harder than it should be.&lt;BR /&gt;&lt;BR /&gt;I am leaning more in the direction of  SELINUX, where you define a policy which severely restricts what a given executable can do.  Not being able to read or write a file outside the homedir, seems as close to chroot as makes no difference.&lt;BR /&gt;&lt;BR /&gt;p.s. should have mentioned that CoreFTP Lite *can* also be an sftp client, tho' that ain't what I use it for.&lt;BR /&gt;</description>
      <pubDate>Tue, 21 Feb 2006 15:50:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vsftpd-chroot/m-p/4956512#M550347</guid>
      <dc:creator>Mike Keighley</dc:creator>
      <dc:date>2006-02-21T15:50:50Z</dc:date>
    </item>
    <item>
      <title>Re: vsftpd chroot</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vsftpd-chroot/m-p/4956513#M550348</link>
      <description>User education helped clear up a misconception</description>
      <pubDate>Wed, 22 Feb 2006 09:19:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vsftpd-chroot/m-p/4956513#M550348</guid>
      <dc:creator>Thom Cornwell</dc:creator>
      <dc:date>2006-02-22T09:19:36Z</dc:date>
    </item>
  </channel>
</rss>

