<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Chrooted SFTP on Ubuntu Hardy AMD64 using RSSH</title>
	<link>http://davelozier.com/2008/11/16/chroot-sftp-ubuntu-hardy-amd64/</link>
	<description>Listening to Black Sabath at 78 speed...</description>
	<pubDate>Tue, 07 Sep 2010 03:49:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Dave</title>
		<link>http://davelozier.com/2008/11/16/chroot-sftp-ubuntu-hardy-amd64/#comment-2080</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Mon, 13 Jul 2009 04:11:51 +0000</pubDate>
		<guid>http://davelozier.com/2008/11/16/chroot-sftp-ubuntu-hardy-amd64/#comment-2080</guid>
		<description>Hey Scott! Sorry for the late reply on this. If you set chrootpath to another destination it may possibly not have had the permissions to create the path structure. You can perhaps create them manually after the fact and see if that allows everything else to fall into place. Please let me know how it goes. Thanks!</description>
		<content:encoded><![CDATA[<p>Hey Scott! Sorry for the late reply on this. If you set chrootpath to another destination it may possibly not have had the permissions to create the path structure. You can perhaps create them manually after the fact and see if that allows everything else to fall into place. Please let me know how it goes. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://davelozier.com/2008/11/16/chroot-sftp-ubuntu-hardy-amd64/#comment-1975</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Thu, 09 Jul 2009 21:32:08 +0000</pubDate>
		<guid>http://davelozier.com/2008/11/16/chroot-sftp-ubuntu-hardy-amd64/#comment-1975</guid>
		<description>Dave

I followed your instruction but failed to get it to work. I suspect that the "~/mkchroot.sh" didn't quite get made executable successfully. I don't see the "$jail_dir" directory. I set the chrootpath to my desired rather than /home/chroot. Does the chrootpath have to be /home/chroot? How do I make sure that ~/mkchroot.sh gets made executable successfully?

Scott</description>
		<content:encoded><![CDATA[<p>Dave</p>
<p>I followed your instruction but failed to get it to work. I suspect that the &#8220;~/mkchroot.sh&#8221; didn&#8217;t quite get made executable successfully. I don&#8217;t see the &#8220;$jail_dir&#8221; directory. I set the chrootpath to my desired rather than /home/chroot. Does the chrootpath have to be /home/chroot? How do I make sure that ~/mkchroot.sh gets made executable successfully?</p>
<p>Scott</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://davelozier.com/2008/11/16/chroot-sftp-ubuntu-hardy-amd64/#comment-1065</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Wed, 10 Jun 2009 02:26:32 +0000</pubDate>
		<guid>http://davelozier.com/2008/11/16/chroot-sftp-ubuntu-hardy-amd64/#comment-1065</guid>
		<description>Hi Charlie,

You may possibly need a symbolic link to sftp-server.

sudo ln /home/chroot/usr/lib/openssh/sftp-server /home/chroot/usr/lib/

Check the path with rssh -v as well.

Please let me know if that cures it. Thanks!</description>
		<content:encoded><![CDATA[<p>Hi Charlie,</p>
<p>You may possibly need a symbolic link to sftp-server.</p>
<p>sudo ln /home/chroot/usr/lib/openssh/sftp-server /home/chroot/usr/lib/</p>
<p>Check the path with rssh -v as well.</p>
<p>Please let me know if that cures it. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charlie</title>
		<link>http://davelozier.com/2008/11/16/chroot-sftp-ubuntu-hardy-amd64/#comment-1045</link>
		<dc:creator>Charlie</dc:creator>
		<pubDate>Mon, 08 Jun 2009 01:50:12 +0000</pubDate>
		<guid>http://davelozier.com/2008/11/16/chroot-sftp-ubuntu-hardy-amd64/#comment-1045</guid>
		<description>I just followed your tutorial for a Hardy server running on Amazon's Elastic Compute Cloud, but I'm running in to trouble- my chrooted users can not log in: they get an error: "Fatal: unable to initialise SFTP on server: could not connect" while other users remain just fine. I'm having trouble finding the problem via Google, any ideas?</description>
		<content:encoded><![CDATA[<p>I just followed your tutorial for a Hardy server running on Amazon&#8217;s Elastic Compute Cloud, but I&#8217;m running in to trouble- my chrooted users can not log in: they get an error: &#8220;Fatal: unable to initialise SFTP on server: could not connect&#8221; while other users remain just fine. I&#8217;m having trouble finding the problem via Google, any ideas?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://davelozier.com/2008/11/16/chroot-sftp-ubuntu-hardy-amd64/#comment-564</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Tue, 19 May 2009 04:11:43 +0000</pubDate>
		<guid>http://davelozier.com/2008/11/16/chroot-sftp-ubuntu-hardy-amd64/#comment-564</guid>
		<description>Hey Corey!

The SFTP users will have access to everything in /home/chroot but they should not be able to leave the /home/chroot area. When trying to SSH in do you get disconnected with a notice that the account is limited to SFTP only? If so then that's a good sign things are working. (along with not being able to leave /home/chroot)

Cheers,
~Dave</description>
		<content:encoded><![CDATA[<p>Hey Corey!</p>
<p>The SFTP users will have access to everything in /home/chroot but they should not be able to leave the /home/chroot area. When trying to SSH in do you get disconnected with a notice that the account is limited to SFTP only? If so then that&#8217;s a good sign things are working. (along with not being able to leave /home/chroot)</p>
<p>Cheers,<br />
~Dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: corey</title>
		<link>http://davelozier.com/2008/11/16/chroot-sftp-ubuntu-hardy-amd64/#comment-561</link>
		<dc:creator>corey</dc:creator>
		<pubDate>Mon, 18 May 2009 23:26:56 +0000</pubDate>
		<guid>http://davelozier.com/2008/11/16/chroot-sftp-ubuntu-hardy-amd64/#comment-561</guid>
		<description>I followed your howto, but i keep stumbling onto one problem.  The sftp user has access to all the files from /home/chroot on up...  Including any additional users that you add later.  How did you go about restricting the users to their /home/chroot/home directory without breaking their ability to log into the sftp?

Please let me know.

Thanks

Corey</description>
		<content:encoded><![CDATA[<p>I followed your howto, but i keep stumbling onto one problem.  The sftp user has access to all the files from /home/chroot on up&#8230;  Including any additional users that you add later.  How did you go about restricting the users to their /home/chroot/home directory without breaking their ability to log into the sftp?</p>
<p>Please let me know.</p>
<p>Thanks</p>
<p>Corey</p>
]]></content:encoded>
	</item>
</channel>
</rss>
