<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Totally Seamless SSHFS under Linux using Fuse and Autofs</title>
	<atom:link href="http://www.mccambridge.org/blog/2007/05/totally-seamless-sshfs-under-linux-using-fuse-and-autofs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mccambridge.org/blog/2007/05/totally-seamless-sshfs-under-linux-using-fuse-and-autofs/</link>
	<description>Thoughts, Projects, Happenings, Ideas</description>
	<lastBuildDate>Mon, 06 Feb 2012 19:37:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Vinh Nguyen</title>
		<link>http://www.mccambridge.org/blog/2007/05/totally-seamless-sshfs-under-linux-using-fuse-and-autofs/comment-page-1/#comment-2377</link>
		<dc:creator>Vinh Nguyen</dc:creator>
		<pubDate>Sun, 27 Nov 2011 23:44:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.mccambridge.org/blog/2007/05/totally-seamless-sshfs-under-linux-using-fuse-and-autofs/#comment-2377</guid>
		<description>Hi.

How does autofs + sshfs handle network disconnect and connect?  I suppose when I turn on the computer, I can access these mount points immediately.  What then happens if the network disconnects (cat5 cable is pulled)?  Is the mount point now empty?  If I reconnect to the network, is the mount point automatically fixed?</description>
		<content:encoded><![CDATA[<p>Hi.</p>
<p>How does autofs + sshfs handle network disconnect and connect?  I suppose when I turn on the computer, I can access these mount points immediately.  What then happens if the network disconnects (cat5 cable is pulled)?  Is the mount point now empty?  If I reconnect to the network, is the mount point automatically fixed?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zugriff auf entfernte Dateisysteme unter bestimmten Bedingungen</title>
		<link>http://www.mccambridge.org/blog/2007/05/totally-seamless-sshfs-under-linux-using-fuse-and-autofs/comment-page-1/#comment-2273</link>
		<dc:creator>Zugriff auf entfernte Dateisysteme unter bestimmten Bedingungen</dc:creator>
		<pubDate>Tue, 21 Jun 2011 22:22:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.mccambridge.org/blog/2007/05/totally-seamless-sshfs-under-linux-using-fuse-and-autofs/#comment-2273</guid>
		<description>[...] IRC-Gespräch wurde meine Aufmerksamkeit auf die Kombination von autofs und sshfs gelenkt, wie es hier und hier beschrieben ist. Leider musste ich nach einiger Zeit des Herumprobierens und der Lektüre [...]</description>
		<content:encoded><![CDATA[<p>[...] IRC-Gespräch wurde meine Aufmerksamkeit auf die Kombination von autofs und sshfs gelenkt, wie es hier und hier beschrieben ist. Leider musste ich nach einiger Zeit des Herumprobierens und der Lektüre [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russ</title>
		<link>http://www.mccambridge.org/blog/2007/05/totally-seamless-sshfs-under-linux-using-fuse-and-autofs/comment-page-1/#comment-2260</link>
		<dc:creator>Russ</dc:creator>
		<pubDate>Thu, 02 Jun 2011 00:13:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.mccambridge.org/blog/2007/05/totally-seamless-sshfs-under-linux-using-fuse-and-autofs/#comment-2260</guid>
		<description>Would you be interested in turning this into a simple script for a few hundred bucks? the only actual human inputs required are the folder to mount and the SSH credentials. I just have a lot of these to set up and lack the skill to create a simpler solution... let me know.</description>
		<content:encoded><![CDATA[<p>Would you be interested in turning this into a simple script for a few hundred bucks? the only actual human inputs required are the folder to mount and the SSH credentials. I just have a lot of these to set up and lack the skill to create a simpler solution&#8230; let me know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.mccambridge.org/blog/2007/05/totally-seamless-sshfs-under-linux-using-fuse-and-autofs/comment-page-1/#comment-2163</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Sun, 26 Dec 2010 15:58:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.mccambridge.org/blog/2007/05/totally-seamless-sshfs-under-linux-using-fuse-and-autofs/#comment-2163</guid>
		<description>Great stuff, works fine on Ubuntu 10.10</description>
		<content:encoded><![CDATA[<p>Great stuff, works fine on Ubuntu 10.10</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mount remote file systems via ssh &#171; James Reid</title>
		<link>http://www.mccambridge.org/blog/2007/05/totally-seamless-sshfs-under-linux-using-fuse-and-autofs/comment-page-1/#comment-1655</link>
		<dc:creator>mount remote file systems via ssh &#171; James Reid</dc:creator>
		<pubDate>Wed, 21 Jul 2010 14:48:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.mccambridge.org/blog/2007/05/totally-seamless-sshfs-under-linux-using-fuse-and-autofs/#comment-1655</guid>
		<description>[...] Totally Seamless SSHFS under Linux using Fuse and Autofs &#8212; Autofs and sshfs – the perfect [...]</description>
		<content:encoded><![CDATA[<p>[...] Totally Seamless SSHFS under Linux using Fuse and Autofs &#8212; Autofs and sshfs – the perfect [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sldevslnull</title>
		<link>http://www.mccambridge.org/blog/2007/05/totally-seamless-sshfs-under-linux-using-fuse-and-autofs/comment-page-1/#comment-1634</link>
		<dc:creator>sldevslnull</dc:creator>
		<pubDate>Mon, 14 Jun 2010 09:02:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.mccambridge.org/blog/2007/05/totally-seamless-sshfs-under-linux-using-fuse-and-autofs/#comment-1634</guid>
		<description>Thanks,  This worked like a charm, saved me lot of time.</description>
		<content:encoded><![CDATA[<p>Thanks,  This worked like a charm, saved me lot of time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: UbuntuUser</title>
		<link>http://www.mccambridge.org/blog/2007/05/totally-seamless-sshfs-under-linux-using-fuse-and-autofs/comment-page-1/#comment-1562</link>
		<dc:creator>UbuntuUser</dc:creator>
		<pubDate>Mon, 18 Jan 2010 22:37:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.mccambridge.org/blog/2007/05/totally-seamless-sshfs-under-linux-using-fuse-and-autofs/#comment-1562</guid>
		<description>Great timesaver!  Thanks so much for putting this together!</description>
		<content:encoded><![CDATA[<p>Great timesaver!  Thanks so much for putting this together!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sumant Oemrawsingh</title>
		<link>http://www.mccambridge.org/blog/2007/05/totally-seamless-sshfs-under-linux-using-fuse-and-autofs/comment-page-1/#comment-1520</link>
		<dc:creator>Sumant Oemrawsingh</dc:creator>
		<pubDate>Sun, 22 Nov 2009 23:14:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.mccambridge.org/blog/2007/05/totally-seamless-sshfs-under-linux-using-fuse-and-autofs/#comment-1520</guid>
		<description>Hum, something went wrong there. In /etc/auto.sshfs, there should &lt;strong&gt;not&lt;/strong&gt; be a newline after mountopts=&quot;-

Also, the line with the echo should be in the same file, it&#039;s not separate.

(Bad formatting on my part, sorry. Would be easier with a preview.)</description>
		<content:encoded><![CDATA[<p>Hum, something went wrong there. In /etc/auto.sshfs, there should <strong>not</strong> be a newline after mountopts=&#8221;-</p>
<p>Also, the line with the echo should be in the same file, it&#8217;s not separate.</p>
<p>(Bad formatting on my part, sorry. Would be easier with a preview.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sumant Oemrawsingh</title>
		<link>http://www.mccambridge.org/blog/2007/05/totally-seamless-sshfs-under-linux-using-fuse-and-autofs/comment-page-1/#comment-1519</link>
		<dc:creator>Sumant Oemrawsingh</dc:creator>
		<pubDate>Sun, 22 Nov 2009 23:10:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.mccambridge.org/blog/2007/05/totally-seamless-sshfs-under-linux-using-fuse-and-autofs/#comment-1519</guid>
		<description>Great! Thanks for the tutorial! It was of great help.

Of course I did some more digging... And even though I&#039;m the only one using this on my computers, I did find a way to accomplish this for a multi-user environment, using executable maps. It assumes that the different users on your local machine are also different users on each remote machine, which to me seems natural. Also, same as with the original method, I don&#039;t know how secure this is.

Anyway, in /etc/auto.master, I have:
&lt;code&gt;
/mnt/sshfs      /etc/auto.sshfs --timeout=60
&lt;/code&gt;

and in /etc/auto.sshfs, I have:
&lt;code&gt;
#!/bin/bash
# This file must be executable to work! chmod 755!
key=&quot;${1/%:/}&quot;
user=&quot;${key/@*/}&quot;
server=&quot;${key/*@/}&quot;
mountopts=&quot;-fstype=fuse,rw,nodev,nonempty,noatime,allow_other,max_read=65536,follow_symlinks,uid=\$UID,gid=\$GID,UserKnownHostsFile=\$HOME/.ssh/known_hosts,IdentityFile=\$HOME/.ssh/id_rsa&quot;

echo &quot;$mountopts :sshfs\#${user}@${server}\:&quot;
&lt;/code&gt;
Note the \$UID, \$GID and \$HOME (escaped so bash won&#039;t perform substitution), which will be replaced by autofs with the relevant parameters of the user that requested the automount.
Also note that /etc/auto.sshfs must be an executable map:
&lt;code&gt;
chmod 755 /etc/auto.sshfs
&lt;/code&gt;

Now, I can say as an ordinary user with local username soemraws:
&lt;code&gt;
cd /mnt/sshfs/remotename@some.remote.system.com
&lt;/code&gt;
and through the magic combination of executable maps and variable expansion, I have my homedir as user remotename on the system some.remote.system.com, with the local UID and GID. Note that I use id_rsa as the identity file of the calling user, so all users should do the same. Of course, you could tell your users to symlink their identity to ~/.ssh/identity and use that in IdentityFile.

In my local homedir, I can make symbolic links to /mnt/sshfs/... and other users can as well. As you see, as long as two different local users are also two different users on the remote system, there is no clash of directory names in /mnt/sshfs, since the key is user@remote.

If you require tunnels to be setup, you can expand /etc/auto.sshfs to look for specific files in the user&#039;s home dir. Since /etc/auto.sshfs is a bash script, the sky is the limit!</description>
		<content:encoded><![CDATA[<p>Great! Thanks for the tutorial! It was of great help.</p>
<p>Of course I did some more digging&#8230; And even though I&#8217;m the only one using this on my computers, I did find a way to accomplish this for a multi-user environment, using executable maps. It assumes that the different users on your local machine are also different users on each remote machine, which to me seems natural. Also, same as with the original method, I don&#8217;t know how secure this is.</p>
<p>Anyway, in /etc/auto.master, I have:<br />
<code><br />
/mnt/sshfs      /etc/auto.sshfs --timeout=60<br />
</code></p>
<p>and in /etc/auto.sshfs, I have:<br />
<code><br />
#!/bin/bash<br />
# This file must be executable to work! chmod 755!<br />
key="${1/%:/}"<br />
user="${key/@*/}"<br />
server="${key/*@/}"<br />
mountopts="-fstype=fuse,rw,nodev,nonempty,noatime,allow_other,max_read=65536,follow_symlinks,uid=\$UID,gid=\$GID,UserKnownHostsFile=\$HOME/.ssh/known_hosts,IdentityFile=\$HOME/.ssh/id_rsa"</p>
<p>echo "$mountopts :sshfs\#${user}@${server}\:"<br />
</code><br />
Note the \$UID, \$GID and \$HOME (escaped so bash won&#8217;t perform substitution), which will be replaced by autofs with the relevant parameters of the user that requested the automount.<br />
Also note that /etc/auto.sshfs must be an executable map:<br />
<code><br />
chmod 755 /etc/auto.sshfs<br />
</code></p>
<p>Now, I can say as an ordinary user with local username soemraws:<br />
<code><br />
cd /mnt/sshfs/remotename@some.remote.system.com<br />
</code><br />
and through the magic combination of executable maps and variable expansion, I have my homedir as user remotename on the system some.remote.system.com, with the local UID and GID. Note that I use id_rsa as the identity file of the calling user, so all users should do the same. Of course, you could tell your users to symlink their identity to ~/.ssh/identity and use that in IdentityFile.</p>
<p>In my local homedir, I can make symbolic links to /mnt/sshfs/&#8230; and other users can as well. As you see, as long as two different local users are also two different users on the remote system, there is no clash of directory names in /mnt/sshfs, since the key is user@remote.</p>
<p>If you require tunnels to be setup, you can expand /etc/auto.sshfs to look for specific files in the user&#8217;s home dir. Since /etc/auto.sshfs is a bash script, the sky is the limit!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: D-Rock</title>
		<link>http://www.mccambridge.org/blog/2007/05/totally-seamless-sshfs-under-linux-using-fuse-and-autofs/comment-page-1/#comment-1393</link>
		<dc:creator>D-Rock</dc:creator>
		<pubDate>Fri, 19 Jun 2009 21:22:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.mccambridge.org/blog/2007/05/totally-seamless-sshfs-under-linux-using-fuse-and-autofs/#comment-1393</guid>
		<description>This is a great help. Thank you! It seems much better than manually doing sshfs then having it flake out and hang my apps... I added two options which (I discovered with manual sshfs mounting) make the transfer from remote systems MUCH quicker (at the expense of some encryption security), and solve some permissions issues by adding the phrase:

Cipher=&quot;blowfish&quot;,idmap=user,

in between all the other options in each line in /etc/auto.sshfs

Grazie!</description>
		<content:encoded><![CDATA[<p>This is a great help. Thank you! It seems much better than manually doing sshfs then having it flake out and hang my apps&#8230; I added two options which (I discovered with manual sshfs mounting) make the transfer from remote systems MUCH quicker (at the expense of some encryption security), and solve some permissions issues by adding the phrase:</p>
<p>Cipher=&#8221;blowfish&#8221;,idmap=user,</p>
<p>in between all the other options in each line in /etc/auto.sshfs</p>
<p>Grazie!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

