Package: encfs
Version: 1.2.5-1-1
Severity: important

Hi - I cannot get encfs to work on my thecus n2100 (arm cpu).

Once the encfs is mounted, any attempt to use it results in your 
processes hanging. E.g. ls -l will just sit there. 

Stracing an ls shows it stall on an lstat64 (attached is a partial 
strace)

[EMAIL PROTECTED]:~/encfs_exp$ /sbin/modinfo 
/lib/modules/2.6.18-3-iop32x/kernel/fs/fuse/fuse.ko
filename:       /lib/modules/2.6.18-3-iop32x/kernel/fs/fuse/fuse.ko
alias:          char-major-10-229
author:         Miklos Szeredi <[EMAIL PROTECTED]>
description:    Filesystem in Userspace
license:        GPL
vermagic:       2.6.18-3-iop32x mod_unload ARMv5 gcc-4.1
depends:


-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: arm (armv5tel)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-iop32x
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages encfs depends on:
ii  fuse-utils                   2.5.3-4.1   Filesystem in USErspace (utilities
ii  libc6                        2.3.6.ds1-8 GNU C Library: Shared libraries
ii  libfuse2                     2.5.3-4.1   Filesystem in USErspace library
ii  libgcc1                      1:4.1.1-19  GCC support library
ii  librlog1c2a                  1.3.7-1     flexible message logging library
ii  libssl0.9.8                  0.9.8c-3    SSL shared libraries
ii  libstdc++6                   4.1.1-19    The GNU Standard C++ Library v3

encfs recommends no packages.

-- no debconf information
...
close(4)                                = 0
socket(PF_FILE, SOCK_STREAM, 0)         = 4
fcntl64(4, F_GETFL)                     = 0x2 (flags O_RDWR)
fcntl64(4, F_SETFL, O_RDWR|O_NONBLOCK)  = 0
connect(4, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 112) = -1 ENOENT 
(No such file or directory)
close(4)                                = 0
socket(PF_FILE, SOCK_STREAM, 0)         = 4
fcntl64(4, F_GETFL)                     = 0x2 (flags O_RDWR)
fcntl64(4, F_SETFL, O_RDWR|O_NONBLOCK)  = 0
connect(4, {sa_family=AF_FILE, path="/var/run/nscd/socket"}, 112) = -1 ENOENT 
(No such file or directory)
close(4)                                = 0
open("/etc/group", O_RDONLY)            = 4
fcntl64(4, F_GETFD)                     = 0
fcntl64(4, F_SETFD, FD_CLOEXEC)         = 0
_llseek(4, 0, [0], SEEK_CUR)            = 0
fstat64(4, {st_mode=S_IFREG|0644, st_size=550, ...}) = 0
mmap2(NULL, 550, PROT_READ, MAP_SHARED, 4, 0) = 0x40016000
_llseek(4, 550, [550], SEEK_SET)        = 0
munmap(0x40016000, 550)                 = 0
close(4)                                = 0
lstat64("front", Killed

Script started on Tue 12 Dec 2006 20:09:27 GMT

mkdir front
[EMAIL PROTECTED]:~/encfs_exp$ 
[EMAIL PROTECTED]:~/encfs_exp$ mkdir front
[EMAIL PROTECTED]:~/encfs_exp$ mkdir back
[EMAIL PROTECTED]:~/encfs_exp$ encfs 
$(pwd)/{front,back}back,front}
Creating new encrypted volume.
Please choose from one of the following options:
 enter "x" for expert configuration mode,
 enter "p" for pre-configured paranoia mode,
 anything else, or an empty line will select standard mode.
?> 

Standard configuration selected.

Configuration finished.  The filesystem to be created has
the following properties:
Filesystem cipher: "ssl/blowfish", version 2:1:1
Filename encoding: "nameio/block", version 3:0:1
Key Size: 160 bits
Block Size: 512 bytes
Each file contains 8 byte header with unique IV data.
Filenames encoded using IV chaining mode.

Now you will need to enter a password for your filesystem.
You will need to remember this password, as there is absolutely
no recovery mechanism.  However, the password can be changed
later using encfsctl.

New Encfs Password: 
Verify Encfs Password: 
[EMAIL PROTECTED]:~/encfs_exp$ ls -l
Killed
[EMAIL PROTECTED]:~/encfs_exp$ 
Script done on Tue 12 Dec 2006 20:09:56 GMT

Reply via email to