Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#42257 closed update (invalid)

EncFS on HFS+, data loss risk

Reported by: dnied@… Owned by: Markus.Ueberall@…
Priority: Normal Milestone:
Component: ports Version: 2.2.1
Keywords: Cc: neverpanic (Clemens Lang), cooljeanius (Eric Gallager)
Port: encfs

Description

I recommend switching to the latest SVN revision of encfs, because it includes provisions in order to work correctly on case-insensitive filesystems (such as the Mac's HFS+).

Versions up to 1.7.4_1 appear to work with case-insensitive filesystems, but they are in fact unaware of possible name collisions, since they assume case sensitivity. This may lead to data loss, with probability proportional to the number of files stored in an encfs volume (speaking from personal experience and subsequent research).

Change History (6)

comment:1 Changed 11 years ago by dnied@…

Cc: dnied@… added

Cc Me!

comment:2 Changed 11 years ago by neverpanic (Clemens Lang)

Cc: cal@… added; dnied@… removed
Keywords: crypto fuse removed
Owner: changed from macports-tickets@… to Markus.Ueberall@…

You don't need to Cc yourself if you're the reporter. Please make sure to Cc the maintainer of a port, if any. I have done this for you now.

EncFS has been updated to a 1.7.5-series release in r116237 following #40893 3 days ago. Is this still a problem with 1.7.5?

comment:3 Changed 11 years ago by cooljeanius (Eric Gallager)

Cc: egall@… added

Cc Me!

comment:4 Changed 11 years ago by dnied@…

There's no 1.7.5 on the encfs site¹, so I'm wondering where it came from. Regardless, I tested MacPorts' 1.7.5 and saw it's got the new base32 filename encoding option, so this version should be fine on HFS+. Problem solved for me.


¹ http://code.google.com/p/encfs/downloads/list

Last edited 11 years ago by dnied@… (previous) (diff)

comment:5 Changed 11 years ago by larryv (Lawrence Velázquez)

Resolution: invalid
Status: newclosed

comment:6 Changed 11 years ago by neverpanic (Clemens Lang)

There is no 1.7.5 release yet. The update to a pre-release version was necessary because prior versions wouldn't build against libc++ and thus not on Mavericks.

So in a way we've already done what you proposed, but for a different reason.

Note: See TracTickets for help on using tickets.