Package: fuse-utils
Version: 2.8.1-1.2
Severity: normal

This is what I have, where ~/private1 is itself an fuse-mounted
directory:

polya:~/private1 $ encfs ~/.encprivate2 ~/private2
EncFS Password: 
fusermount: failed to open current directory: Permission denied
fuse failed.  Common problems:
 - fuse kernel module not installed (modprobe fuse)
 - invalid options -- see usage message

The source of the problem appears to be in util/fusermount.c, lines
599-605, where a check is performed to determine whether the current
directory (".") is readable.  It is not at all clear to me why this
should be necessary, as we are about to chdir to the mount point
anyway.  And in this case, it prevented me from doing something
eminently sensible.  (This check failed, I presume, because with an
euid of 0, the directory is not readable, as it is fusermounted.)  It
would appear that all that is necessary to fix this bug is simply to
delete these lines.  (There may be other corresponding checks
elsewhere in the code, too.)

   Julian

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages fuse-utils depends on:
ii  adduser                       3.112      add and remove users and groups
ii  libc6                         2.10.2-9   Embedded GNU C Library: Shared lib
ii  libfuse2                      2.8.1-1.2  Filesystem in USErspace library
ii  makedev                       2.3.1-89   creates device files in /dev
ii  sed                           4.2.1-7    The GNU sed stream editor
ii  udev                          154-1      /dev/ and hotplug management daemo

fuse-utils recommends no packages.

fuse-utils suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to