Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#20740 - [encfs] Transport endpoint is not connected

Attached to Project: Community Packages
Opened by Green (The_Green_Arrow) - Saturday, 04 September 2010, 13:37 GMT
Last edited by Thomas Dziedzic (tomd123) - Tuesday, 07 September 2010, 13:05 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Dan Griffiths (Ghost1227)
Thomas Dziedzic (tomd123)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description: after upgrading encfs from 1.6-1 to 1.7.1-1, I've got this error when trying to access a mounted encrypted directory.

encfs ~/.Private.encrypted ~/Private
cd Private
cd: transport endpoint is not connected: Private

Additional info:
* encfs 1.7.1-1


Steps to reproduce: mount an encfs encrypted directory.
This task depends upon

Closed by  Thomas Dziedzic (tomd123)
Tuesday, 07 September 2010, 13:05 GMT
Reason for closing:  Fixed
Additional comments about closing:  1.7.2
Comment by Thomas Dziedzic (tomd123) - Saturday, 04 September 2010, 15:00 GMT
It works for me. It could be the fact that you created that encfs folder with < 1.7.1 but I wasn't able to reproduce it after having created it with 1.7.1

Could you possibly give me a more verbose output?
Comment by Thomas Dziedzic (tomd123) - Saturday, 04 September 2010, 15:03 GMT
Can you try it with encfs -s ?
Comment by Green (The_Green_Arrow) - Saturday, 04 September 2010, 15:49 GMT
The encfs folder was indeed created before 1.7.1 ;)
Same thing with -s option.
Here is a verbose output :
17:45:27 (main.cpp:523) Root directory: /home/user1//.Private.encrypted/
17:45:27 (main.cpp:524) Fuse arguments: (daemon) (threaded) (keyCheck) encfs /home/user1//Private -s -o use_ino -o default_permissions
17:45:27 (FileUtils.cpp:177) version = 20
17:45:27 (FileUtils.cpp:181) found new serialization format
17:45:27 (FileUtils.cpp:199) subVersion = 20100713
17:45:27 (Interface.cpp:165) checking if ssl/aes(3:0:2) implements ssl/aes(2:2:0)
17:45:27 (SSL_Cipher.cpp:370) allocated cipher ssl/aes, keySize 32, ivlength 16
17:45:27 (Interface.cpp:165) checking if ssl/aes(3:0:2) implements ssl/aes(2:2:0)
17:45:27 (SSL_Cipher.cpp:370) allocated cipher ssl/aes, keySize 32, ivlength 16
17:45:27 (FileUtils.cpp:1620) useStdin: 0
Password :
17:45:50 (Interface.cpp:165) checking if ssl/aes(3:0:2) implements ssl/aes(2:2:0)
17:45:50 (SSL_Cipher.cpp:370) allocated cipher ssl/aes, keySize 32, ivlength 16
17:45:53 (FileUtils.cpp:1628) cipher key size = 52
17:45:53 (Interface.cpp:165) checking if nameio/block(3:0:1) implements nameio/block(3:0:0)

Comment by Thomas Dziedzic (tomd123) - Saturday, 04 September 2010, 16:22 GMT
similar issue: http://groups.google.com/group/zfs-fuse/browse_thread/thread/dd71062e7902a2f5

can you try umounting everything like they described? can you try rebooting?
Comment by Green (The_Green_Arrow) - Saturday, 04 September 2010, 16:43 GMT
Even after the reboot it's the same thing ;)
With a new encrypted directory (created with 1.7.1), it works .... except in paranoid mode !
So normal mode is ok with 1.7.1, but not paranoid mode. And the directory I've created with 1.6 was in paranoid mode !
Comment by Thomas Dziedzic (tomd123) - Saturday, 04 September 2010, 16:58 GMT
Hmm, seems like a backwards incompatibility between 1.7.1 and 1.6. A suspicious change in 1.7.1 is:

"add new IV initialization mode to foil watermark attack - see this 2010-08 analysis. The old IV setup is kept for backwards compatibility."

It seems like the second part might have been implemented incorrectly. I'll let you do the honors and let you report this upstream.
Comment by Green (The_Green_Arrow) - Saturday, 04 September 2010, 17:38 GMT
reported > http://code.google.com/p/encfs/issues/detail?id=74
Comment by Marek Niklicek (Dogmeat) - Sunday, 05 September 2010, 20:29 GMT
I have the same issue. As a temporary solution I installed older version (encfs 1.6) from Arch Rollback Machine and added a comment to its bugtracker.
Comment by Green (The_Green_Arrow) - Monday, 06 September 2010, 07:59 GMT
Upstream bug fixed in encfs 1.7.2
Comment by Thomas Dziedzic (tomd123) - Tuesday, 07 September 2010, 05:30 GMT
does 1.7.2 work?
Comment by Green (The_Green_Arrow) - Tuesday, 07 September 2010, 06:23 GMT
Yes, I've just changed pkgver to 1.7.2 in the PKGBUILD and it works...

Loading...