![]() ![]() Given that allow_other is a FUSE mount option and not specific to sshfs, I believe that this workaround would work for encfs as well. Root privileges on the file server side of things to get NFS or SMB. It seems better than the option of running a daemon which requires I am of course concerned about a setuid root binary lying around, but ![]() I will continue to experiment and follow up if it stops working. To be able to open and edit documents reliably on the mounted volume. You may simply need to add a folder to Alfreds default search scope, but in the case of a metadata warning or failure. So I marked my sshfs binary as setuid, and I added the -oĪllow_other mount option to my sshfs command line, and. Work as another user, or as root, to these files, and marking them as Kinds of jobs, perhaps the kernel is expecting to be able to do some 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. Boxcryptor uses asymmetric encryption, a combination of AES-256 and RSA. 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. SEC 310 Week 6 Lab Attached Files: Weekly Lab Report.docx (13.694 KB) 1. 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. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |