I thought to myself, OS X uses system users and system daemons for all As I just mentioned on the bug report upstream: I think I have a more persistent workaround for this rather than a command you need to run each time. Very specifically, I am not a security expert, and am not qualified to judge whether it opens any security holes (especially while it is running, and especially on shared machines). It works for me, but you rely on your own expertise in deciding whether to use it for yourself. It should be relatively easily adapted to other mount mechanisms, such as boxcryptor. It could be extended by reading encfs dir and mount point from the command line, but I prefer not to because typos might create security risks. Please find below a script I use for mounting encfs volumes it automatically solves the attribute problem, and also helps with remembering to close volumes. I don't know why apple don't appear to have a simple way to say "this volume is safe", but the problem is fairly easy to solve for encfs. If you're having this problem, post your details on that ticket. So I think this bug is specific to encfs – not to osxfuse in general.įor what it's worth, there is a ticket open on the osxfuse project for this exact problem. I tried compiling the osxfuse's sample loopback file system and putting the same "damaged" file on there and it opens just fine.
#Boxcryptor mac os x verification#
Signature verification is supposed to be applied to executables, and I still haven't figured out why it's bugging out in this situation.
The error message "_ is damaged and can't be opened" is actually a signature error (see here – about 3/4ths of the way down), meaning that GateKeeper can't verify a valid signature. This implies that it is actually Finder that is intervening to prevent opening the file. The first thing to note is that if you go into Keynote and choose File → Open, you can open the "damaged" file without any issues. I understand that the solution works, but I would like to know why it works.
But you have to do that repeatedly – every time you save a file it will have the quarantine flag added back to it.Īs you pointed out, there's a less safe but more convenient alternative: disable GateKeeper. Is correct: you can repair the file with xattr.
0 kommentar(er)
