Mar 27, 2021
Macfuse File System Is Not Available
As a user, installing the FUSE for macOS software package will let you use any third-party FUSE file system. Legacy MacFUSE file systems are supported through the optional MacFUSE compatibility layer. As a developer, you can use the FUSE SDK to write numerous types of new file systems as regular user space programs. My truecrypt files were mounting fine until today when I tried to mount it and I got the error: the OSXFUSE file system is not available (255). The weird thing is I honestly don’t know what I could have done on my computer since yesterday when there were no problems that would have caused this. The file system you are using might not be compatible with the latest version of FUSE or it might use a third party library, that needs to be updated. Without more context it is impossible to make an educated guess. MyopicPaideia commented on Nov 16. AVG Anti Virus stopped a couple Trojan Horses and several phishing files on Wednesday morning. I then proceeded to get to work and tried opening T.
10.4: A detailed look at MacFUSE and the SSH file system | 17 comments | Create New Account
Click here to return to the ‘10.4: A detailed look at MacFUSE and the SSH file system’ hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
1) You must secure *ALL* accounts with a password before enabling ssh ‘Remote Access’ or you are leaving your system open. Slot machines north carolina. Note, even though the sshd_config appears to prohibit empty passwords it’s a bug in pam support that Apple has know about for YEARS!
2) MacFusion has a serious security issues with textual passwords stored in the keychain for ssh mounts. MacFusion will happily disclose the password to any application/script running within your context.
3) SSHKeychain before 0.8.1 also had some major security issues that have been resolved.
The most secure way to do this is to use ssh keys to authenticate ( which you should be using anyways ) rather than plain text passwords.
10.4: A detailed look at MacFUSE and the SSH file system
Could the same thing be accomplished with this tool?:
http://www.gideonsoftworks.com/sshhelper.html
SSHhelper
It’s free, and says it makes it easy to generate new SSH keys, among other things..
Unfortunately, like so much of the under-the-hood aspects of OS X, I don’t fully understand SSH.. Is this also a possible solution for using a open wireless network (at a coffeeshop or something) to get a little better security when logging into password-protected services like webmail and the like?
10.4: A detailed look at MacFUSE and the SSH file system
No, but it might help. Where they say
Secure Shell helper alleviates the need to use the command line to configure a working OpenSSH system. It’s all point and click !
they’re forgetting that you need to have a way of actually doing something with SSH. That’s where MacFUSE and sshfs come in.
10.4: A detailed look at MacFUSE and the SSH file system
Whats the difference between this and ssh portforwarding and just using Connect to Server in the finder and mounting your remote drive that way?
Mtu 12v manual.
The answer is it lets you mount linux/solaris file systems, which AFP/SBM do not without special configuration.
You mention a firmware ‘upgrade’ as being tricky and then say it was far superior to the standard software. I am guessing that you installed a firmware hack and not a firmware upgrade? Is that true? If so, where did you get it and what benefits are there? Upgrades from Linksys are pretty easy.
dd-wrt has been pretty good to me. But I have one of the older, more hackable models.
I used DD-WRT. The router’s software wouldn’t let me assign a static IP to the target machine, but the new firmware gives you that and many more options than the standard didn’t.
Is there any significant advantage to using this instead of AFP/SMB over an SSH tunnel (TCP over TCP, but it requires no added software if you know how to configure the tunnel manually) or over hamachi (or similar UDP VPN)? Both of these options offer more options for NAT traversal and have more possible applications. Before I found hamachi, I used a series of ssh tunnels to connect to my home machines when I was away, and encrypted file transfers (as well as encrypted VNC and anything else I needed), and with the tunnel/VPN already running, file sharing is as easy as on a LAN.
— -
I was offered a penny for my thoughts, so I gave my two cents.. I got ripped off.
This is easier than the tunnel method because you don’t need to do anything special on the server — so long as it has ssh which is the real advantage of this, you can connect to any computer that has ssh and mount the filesystem as a harddrive.
Look at the ‘What else can MacFuse do?’ section and watch the demo there it gives you a much better description than I can do here.
‘This is easier than the tunnel method because you don’t need to do anything special on the server’
I don’t understand this comment. I’ve been tunneling port 548 over ssh for a long time and I never had to do anything special on the server end.
I’m sure Fuse has an application, but for OS X to OS X connections, I don’t see an incentive to change.
A.
‘I’m sure Fuse has an application, but for OS X to OS X connections, I don’t see an incentive to change.’
There’s your answer. But Web developers often have hosting on a remote Linux machine. They might be using MySQL and so have a use for mysqlfs. Content creators might like to explore and debug their master DVD content with DVDfs. FUSE unifies these under a single mechanism to support any data structure as a filesystem. This is the Unix philosophy: elegant.
The thing you’ve gotta watch with AFP is that it doesn’t work well with latent links. If you have a speedy connection from your desktop/laptop to your server then you should be ok.
I’ve worked at an ISP for 9 years and seen OS X come out and customers starting to use it.. The ones that call complaining about slow apple file transfers are almost always using AFP over TCP (and most of the time using it from CA to NY .. :-( stupid speed of light).
We’ve even done packet dumps (tcpdump etc..) of the AFP and it’s something about length of time between TCP resends and AFP error correction that doesn’t mesh. I mean after all I’m pretty sure AFP was developed as a LAN technology not a WAN technology.
10.4: HamachiX might be easier for connecting to a remote file server
I think MacFUSE, ssh and the ssh file system are nice, and very useful if the remote system is not a Mac and does not have an AFP or SMB/CIFS file server running. I personally use ssh at work and at home all the time and have it built into a lot of scripts that keep my systems alive and well.
However, for establishing secure file server connections across the internet, I find that HamachiX is a lot easier to setup and use.
http://hamachix.spaceants.net/
Install HamachiX on each Mac (can be more than 2 if you want).
Create a new network:
HamachiX -> Networks -> Add Network
Give the network a unique name of your choosing.
Give it a password.
Specify Create on Demand.
On the other Mac Repeat with the identical network name, password, and Create on Demain option. This can be done once and left up and running while you are away from home. You could even arrange for HamachiX to be one of your account Login Items.
You should now have a private secure VPN between your 2 Macs.
To connect to the remote Mac file server use:
HamachiX -> Networks -> Connect Using.. -> AFP
If you have more than 2 Macs in the VPN they can all share each other’s file systems.
Hamachi will deal with most firewalls, routers, ISP assigned DHCP IP addresses, etc.. seamlessly.
Bob Harris
10.4: A detailed look at MacFUSE and the SSH file system
I’ve been using MacFUSE for a while and found it to be a very convenient tool for accessing other machines with a nice GUI in Finder. In fact, I develop in TextMate over a connection made with sshfs, and gernally it works well. There’s also a GUI version, MacFusion that makes it even easier to use.
10.4: A detailed look at MacFUSE and the SSH file system
I have used MacFUSE and sshfs quite a bit to mount drives from my office to home in the evening (Mac to Mac). It’s a cool app. But a warning: if you have a drive mounted this way, and the connection times out or otherwise goes down, really bad things can happen, because the Finder can hang. In one case a hard restart was the only option, and when the machine came back a lot of my Library had been destroyed. So it’s not an application to run and casually let sit there open.
10.4: A detailed look at MacFUSE and the SSH file system
Macfusion worked for me running Leopard into an Ubuntu server that I use to store all my media files. However, I can’t make the connection except in terminal. Because of the latter I’m stumped since permissions seem ok. Any suggestions appreciated!
My woes began after rebuilding the server :(
Cheers
Gary. Macbook pro 2012 update to high sierra.
I tried out Fuse4x and sshfs for OSX, through Hombrew, this week-end. It should have been a piece of cake, but apparently the recipes aren’t very good about telling when another fuse package is installed.
As recommended, I did the install:$ brew install fuse4x sshfs
Homebrew cheerfully informs me that sshfs won't work unless I sudo copy a file, so I follow its instructions. Seems a bit strange to have to do this manually:$ sudo cp -rfX /usr/local/Cellar/fuse4x-kext/0.8.13/Library/Extensions/fuse4x.kext /System/Library/Extensions
$ sudo chmod +s /System/Library/Extensions/fuse4x.kext/Support/load_fuse4x
Alas, things just didn't work:
Macfuse File System Is Not Available
$ sshfs myname@mysite.me: ~/mnt/mysite.me
/Library/Filesystems/fusefs.fs/Support/fusefs.kext failed to load - (libkern/kext) link error; check the system/kernel logs for errors or try kextutil(8).
the MacFUSE file system is not available (71)
Well, actually, it looks like the kernel extension never even loaded. OSX is supposed to attempt to auto-load them when a fuse filesystem is mounted, but it doesn't look like it succeeded. I use kextunload and kextload to get it to load the extensions:
$ kextunload /System/Library/Extensions/fuse4x.kext/
(kernel) Kext org.fuse4x.kext.fuse4x not found for unload request.
Failed to unload org.fuse4x.kext.fuse4x - (libkern/kext) not found.$ kextload /System/Library/Extensions/fuse4x.kext/
Yet trying sshfs again gives the same error. What gives?
I look for more info on homebrew and fuse4x forums and bug lists. Wading through Web pages -- they all describing the solution to the link error as (to sum up) 'use fuse4x'. I *am* using fuse4x. One bug report on homebrew hinted at a possible cause to the problem.
It looks like at some point, I had a MacFuse installed, and it left an orphaned copy of /usr/local/lib/pkgconfig/fuse.pc:$ cat /usr/local/lib/pkgconfig/fuse.pc
prefix=/usr/local
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
includedir=${prefix}/include
Name: fuse
Description: File System in User Space (MacFUSE)
Version: 2.7.3
Libs: -L${libdir} -lfuse -pthread -liconv
Cflags: -I${includedir}/fuse -D__FreeBSD__=10 -D_FILE_OFFSET_BITS=64
So I brew uninstall fuse4x, remove the fuse.pc file, and brew install fuse4x.
The homebrew recipe symlinked to the correct fuse.pc file, and I hoped all was good.
It was not good. Same error. I check the system kernel error logs: kernel[0]: fuse4x: starting (version 0.8.13, Nov 11 2011, 17:54:24)
kernel[0]: kxld[com.google.filesystems.fusefs]: The following symbols are unresolved for this kext:
kernel[0]: kxld[com.google.filesystems.fusefs]: _OSRuntimeFinalizeCPP
kernel[0]: kxld[com.google.filesystems.fusefs]: _OSRuntimeInitializeCPP
kernel[0]: Can't load kext com.google.filesystems.fusefs - link failed.
kernel[0]: Failed to load executable for kext com.google.filesystems.fusefs.
kernel[0]: Kext com.google.filesystems.fusefs failed to load (0xdc008016).
kernel[0]: Failed to load kext com.google.filesystems.fusefs (error 0xdc008016).
Egads! Unresolved symbols? Something just isn't right. Looks like the same 32 bit MacFuse garbage.
At this point, I'm seriously doubting the sanity of the the homebrew fuse4x/sshfs recipes. Maybe someone thought they were working, as a coincidence of them already having a working fuse4x kernel extension installed.
Well, it turns out that the MacFuse code was not fully uninstalled, and the brew recipe simply accepts the existing files without complaint or comment:$ ls -ld /Library/Filesystems/fusefs.fs
drwxr-xr-x 4 root wheel 136 Dec 19 2008 /Library/Filesystems/fusefs.fs
The Macfuse File System Is Not Available
December of 2008 ???! That’s a little dated for a filesystem I installed today (Nov 2011). Even if it were unzipped from a file (which it wasn’t), the datestamps of an active project should be more recent than 2008.
My experience with the fuse4x recipe is that it doesn’t do squat for detecting previously installed files.. it just accepts them without complaint.
If you’ve got a previous install of anything remotely resembling MacFuse, clear it out, clean it out, and purge every remnant from your system before monkeying around with fuse4x.$ /Library/Filesystems/fusefs.fs/Support/uninstall-macfuse-core.sh
MacFUSE Uninstaller: Sudoing..
Password:
MacFUSE Uninstaller: Can not find the Archive.bom for MacFUSE Core package.
Alas, if you upgraded to OSX Lion and MacFuse was previously installed, a LOT of garbage was left around. Kind of makes you wonder, why Apple still has no package management system, but I digress..
$ brew uninstall fuse4x
$ brew uninstall sshfs
$ rm -rf /usr/local/include/fuse
$ rm /usr/local/lib/libfuse_*
$ sudo rm -rf /Library/Filesystems/fusefs.fs
$ sudo rm -rf /System/Library/Extensions/fuse4x.kext/
Hopefully, I’m not clobbering anything too important that actually worked before now. I check for anything else fuse related:
$ find / -name '*fuse*' -print
/Applications/Custom/expandrivencsu/ExpanDrive.app/Contents/ExpanDrive/fs/fstools/fuse.pyo
/Applications/Custom/expandrivencsu/ExpanDrive.app/Contents/Resources/com.expandrive.ExpanDrive.exfs.components/libfuse.dylib
/private/var/db/receipts/com.google.macfuse.bom
/private/var/db/receipts/com.google.macfuse.core.bom
/private/var/db/receipts/com.google.macfuse.core.plist
/private/var/db/receipts/com.google.macfuse.plist
AHA! That explains where my MacFuse install came from! It was a stowaway on a tool I had used to support a client project! Well, expandrive can be trashed with CleanApp. I plug the com.google.macfuse receipts as well:
$ sudo rm /private/var/db/receipts/com.google.macfuse.bom
$ sudo rm /private/var/db/receipts/com.google.macfuse.core.bom
$ sudo rm /private/var/db/receipts/com.google.macfuse.core.plist
$ sudo rm /private/var/db/receipts/com.google.macfuse.plist
$ brew install fuse4x
> Cloning https://github.com/fuse4x/fuse.git
Updating /Users/myname/Library/Caches/Homebrew/fuse4x--git
> Checking out tag fuse4x_0_8_13
> autoreconf --force --install
> ./configure --disable-debug --disable-static --prefix=/usr/local/Cellar/fuse4x/0.8.13
> make install
/usr/local/Cellar/fuse4x/0.8.13: 16 files, 728K, built in 35 seconds
$ brew install sshfs
> Cloning https://github.com/fuse4x/sshfs.git
Updating /Users/myname/Library/Caches/Homebrew/sshfs--git
> Checking out tag sshfs_2_3_0
> autoreconf --force --install
> ./configure --disable-debug --prefix=/usr/local/Cellar/sshfs/2.3.0
> make install
> Caveats
Make sure to follow the directions given by `brew info fuse4x-kext`before trying to use a FUSE-based filesystem.
> Summary
/usr/local/Cellar/sshfs/2.3.0: 6 files, 116K, built in 10 seconds
fuse4x-kext 0.8.13
/usr/local/Cellar/fuse4x-kext/0.8.13 (5 files, 304K)
In order for FUSE-based filesystems to work, the fuse4x kernel extension
sudo cp -rfX /usr/local/Cellar/fuse4x-kext/0.8.13/Library/Extensions/fuse4x.kext /System/Library/Extensions
sudo chmod +s /System/Library/Extensions/fuse4x.kext/Support/load_fuse4x
http://github.com/mxcl/homebrew/commits/master/Library/Formula/fuse4x-kext.rb
$ sudo cp -rfX /usr/local/Cellar/fuse4x-kext/0.8.13/Library/Extensions/fuse4x.kext /System/Library/Extensions
$ sudo chmod +s /System/Library/Extensions/fuse4x.kext/Support/load_fuse4x
$ sshfs myname@mysite.me: ~/mnt/mysite.me
