[Bug 192563] New: [sysutils/fusefs-encfs] May not be possible to create a file if encfs_create returns ENOSYS

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192563

            Bug ID: 192563
           Summary: [sysutils/fusefs-encfs] May not be possible to create
                    a file if encfs_create returns ENOSYS
           Product: Ports Tree
           Version: Latest
          Hardware: Any
                OS: Any
            Status: Needs Triage
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: software-freebsd at interfasys.ch

Created attachment 145627
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=145627&action=edit
This is a simple patch to implement encfs_create by just calling mknod then
open

I was looking at how EncFS was implemented on FreeBSD and read the recent
updates made to the port.

Since the the port includes modifications added to FreeBSD 10, I'm wondering if
it's subject to the same problem described here:
https://code.google.com/p/encfs/issues/detail?id=204

"Using encfs on FreeBSD 10.0 compiles okay, mounts the encrypted filesystem,
and even lets you create, list and delete directories. Attempting to create a
file (even with something simple like "touch") returns ENOSYS. The problem can
be traced to FreeBSD 10's kernel implementation of FUSE. Older FUSE
implementations could handle encfs_create being undefined, they'd fall back on
calling encfs_mknod then encfs_open. In FreeBSD 10, it tries calling
encfs_create which returns ENOSYS and fails to create the file."

The submitter also included a patch, attached here.

I didn't see any mention of this bug, but thought I'd mention it.

-- 
You are receiving this mail because:
You are the assignee for the bug.