Benjamin Fleischer

All you have to do is pass the `-o volname=Name` parameter. This is not an FUSE bug. You are simply not providing a name for the mounted volume.

At least in some cases (`if (! init_backgrounded())` in `fuse_mount_kern()` in mount_bsd.c) the function `fuse_new()` might return before the filesystem is actually mounted on BSD, too. So I'm not sure...

Without having spend much time looking into this, I think we need to remove the double fork in fuse_mount_core. Would you agree or did I overlook something?

> Ok, the deadlock is fixed. Please test it. https://github.com/anatol/fuse/commit/339ee2d259837f31d3da955a30595c0a8f91c977 and if it is ok - pull these changes. I am going to look into de-initialization logic and clean it....

> I do not see any reason. fuse_main() function already dereferenced the > path (see fuse_helper_opt_proc()) there is no reason to dereference it > once again. Are you sure? When...

> > > I do not see any reason. fuse_main() function already dereferenced the > > > path (see fuse_helper_opt_proc()) there is no reason to dereference it > > >...

There is still no user space API for developing full-featured file systems on macOS. And even if there was, it would not solve the VeraCrypt issue you are mentioning. A...

@Unnameless The point of security audits is to discover vulnerabilities and making sure those vulnerabilities are addressed. This is usually achieved by publishing security issues after the developers have been...

@nirmit Currently there is no way for individuals to donate to the macFUSE project.

@nirmit Please drop me an email. You can find my email address on my GitHub Profile.