Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1.4.0 beta bug - Permission issue on Mac OS 10.13.4 #659

Closed
lassomagic opened this issue Apr 9, 2018 · 7 comments
Closed

1.4.0 beta bug - Permission issue on Mac OS 10.13.4 #659

lassomagic opened this issue Apr 9, 2018 · 7 comments
Labels
mount:fuse os:mac state:confirmed We are able to reproduce the reported behavior
Milestone

Comments

@lassomagic
Copy link

lassomagic commented Apr 9, 2018

Software Used During the Test

  • Cryptomator 1.4.0 Beta 1
  • macOS 10.13.4
  • Excel for Mac v15.13.3l/TextEdit

Description

  1. Create new test vault
  2. Unlock test vault.
  3. Open Excel/Text edit and create some text
  4. File>Save File and find the mounted test vault.
  5. Receive permission error:

screen shot 2018-04-09 at 2 49 59 am

and

"Your changes could not be saved to 'testing.xlsx', but were saved to a temporary document named '8ED1E910'. Close the existing document, then open the temporary document and save it under a new name."

In Text Edit:

"
The document “Untitled 3” could not be saved as “testing”. You don’t have permission.


To view or change permissions, select the item in the Finder and choose File > Get Info.
"

Note that dragging and dropping a file seems to save the file correctly. Just saving it in a program such as Excel or TextEdit does not seem to work.

@jonaskindler93
Copy link

jonaskindler93 commented Apr 9, 2018

I think that FUSE does not support Apples extended attributes.
I had the same issue copying a file via the Finder to a cryptomator vault (mounted via FUSE). When trying to copy the file via terminal it worked.

Also, removing the attributes from a file using
xattr -c {attribute_name}
will make copying via the finder possible.

@overheadhunter
Copy link
Member

We mount using the -oauto_xattr flag.

@overheadhunter overheadhunter added this to the 1.4.0 milestone Apr 10, 2018
@lassomagic
Copy link
Author

So is this a confirmed bug then? Since I can't save any files to the vault using any MacOS app? Thanks

@overheadhunter
Copy link
Member

Yes we can reproduce it using Excel and TextEdit.

@overheadhunter overheadhunter added the state:confirmed We are able to reproduce the reported behavior label Apr 12, 2018
@pos42
Copy link

pos42 commented Apr 12, 2018

Maybe I see the same error. Works perfect over webdav with 1.4.0 beta 1. At first it seem it is working ok with FUSE as well. But when saving I get these errors. Forcing, I at the end succeed to save it :)

screen shot 2018-04-13 at 01 24 56

screen shot 2018-04-13 at 01 25 10

screen shot 2018-04-13 at 01 25 26

screen shot 2018-04-13 at 01 26 02

As speed is important to me, I was going to switch over to gocryptfs. But then I saw FUSE was on the way with cryptomator... The automount without me buildng something on my own, and that it works from IOS is a plus. So if the FUSE will be stable soon I will continue with cryptomator and also donate :) Have already bought the IOS app...

@pos42
Copy link

pos42 commented Apr 12, 2018

Addition...
As I saw this is confirmed, will there be a beta 2 quickly? Asking as this is a major show stopper for even testing FUSE further on MAC.

@overheadhunter
Copy link
Member

We think we've got everything ready for beta 2. Not sure about the release date yet, because we're also trying to provide volumes on Windows via Dokany.

Saving documents works as expected with TextEdit (1.13) and Excel (16.14.1) with our latest development snapshot.

Anyway I consider this issue fixed. We will reopen this, if someone still experiences it with Cryptomator 1.4.0-beta2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mount:fuse os:mac state:confirmed We are able to reproduce the reported behavior
Projects
None yet
Development

No branches or pull requests

5 participants