[MacPorts] #42257: EncFS on HFS+, data loss risk
#42257: EncFS on HFS+, data loss risk -------------------------+-------------------------------- Reporter: dnied@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: crypto,fuse | Port: encfs -------------------------+-------------------------------- 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). -- Ticket URL: <https://trac.macports.org/ticket/42257> MacPorts <http://www.macports.org/> Ports system for OS X
#42257: EncFS on HFS+, data loss risk ----------------------+------------------------------- Reporter: dnied@… | Owner: Markus.Ueberall@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: encfs | ----------------------+------------------------------- Changes (by cal@…): * owner: macports-tickets@… => Markus.Ueberall@… * cc: dnied@… (removed) * cc: cal@… (added) * keywords: crypto,fuse => Comment: 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? -- Ticket URL: <https://trac.macports.org/ticket/42257#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#42257: EncFS on HFS+, data loss risk ----------------------+------------------------------- Reporter: dnied@… | Owner: Markus.Ueberall@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: encfs | ----------------------+------------------------------- Comment (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 a HFS+. Problem solved for me. ---- ¹ http://code.google.com/p/encfs/downloads/list -- Ticket URL: <https://trac.macports.org/ticket/42257#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#42257: EncFS on HFS+, data loss risk ----------------------+------------------------------- Reporter: dnied@… | Owner: Markus.Ueberall@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: invalid | Keywords: Port: encfs | ----------------------+------------------------------- Changes (by larryv@…): * status: new => closed * resolution: => invalid -- Ticket URL: <https://trac.macports.org/ticket/42257#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
#42257: EncFS on HFS+, data loss risk ----------------------+------------------------------- Reporter: dnied@… | Owner: Markus.Ueberall@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: invalid | Keywords: Port: encfs | ----------------------+------------------------------- Comment (by cal@…): 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. -- Ticket URL: <https://trac.macports.org/ticket/42257#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts