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

Cryptomator 1.6.11 doesn't remember the password stored in macOS keychain #2374

Closed
2 tasks done
visnetje opened this issue Aug 4, 2022 · 6 comments
Closed
2 tasks done
Labels
type:bug Something isn't working
Milestone

Comments

@visnetje
Copy link

visnetje commented Aug 4, 2022

Please agree to the following

Summary

Previously macOS Keychain stored vault password not recognized by Cryptomator 1.6.11

What software is involved?

  • Operating System: macOS Monterey 12.5
  • Cryptomator: 1.6.11 (Apple Silicon)
  • FUSE: 4.4.0
  • Using macOS Keychain to store passwords

Volume Type

FUSE

Steps to Reproduce

  1. Create vault in pre v1.6.11 of Cryptomator
  2. Store vault password in macOS Keychain
  3. Upgrade Cryptomator to 1.6.11 (by downloading latest DMG from the website)
  4. Open Cryptomator
  5. Unlock the vault from the menu icon or Cryptomator interface
  6. Cryptomator now asks for the vault password, even though it's (still) stored in the macOS Keychain

Expected Behavior

I expected to be able to automatically unlock the vault with the already stored vault password from the macOS Keychain.

Actual Behavior

When unlocking the vault, Cryptomator asks for the password.

Reproducibility

Always

Relevant Log Output

No response

Anything else?

Screenshot 2022-08-04 at 16 53 32

@visnetje visnetje added the type:bug Something isn't working label Aug 4, 2022
@purejava
Copy link
Contributor

purejava commented Aug 4, 2022

I can confirm this. In my case it's the INTEL dmg.
I recently updated Cryptomator from 1.6.8 to 1.6.11. 1.6.11 doesn't load the vault password from the keychain stored there before with an earlier version.

The debug log does not contain anything meaningful.
After installing 1.6.8 again, the password can be read (from 1.6.8, not from 1.6.11).

Crating a new vault on 1.6.11 stores the password in the keychain and reads it too (with 1.6.11).

EDIT: added more specific info

@purejava
Copy link
Contributor

purejava commented Aug 5, 2022

On creating a vault with 1.6.10 and storing its vault password in the keychain, 1.6.8 and 1.6.10 do read the vault password from the keychain, whereas 1.6.11 does not.

@overheadhunter
Copy link
Member

We believe that we found the problem (incorrect String length calculation in C). This will require us to implement a little workaround in the next release.

The password is not lost, though. You can still look it up in your Keychain Access.app.

Telling Cryptomator again to remember it will work reliably from now on.

@overheadhunter
Copy link
Member

Depends on cryptomator/integrations-mac#13.

@overheadhunter overheadhunter added this to the 1.6.13 milestone Aug 5, 2022
@overheadhunter
Copy link
Member

Please update to version 1.6.13, which fixes this issue.

@MustardLighthouse
Copy link

@overheadhunter - Is there a way to utilize biometrics i.e. fingerprint to fill in the password versus it just being remembered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants