[E2E] [OSX] Client not accepting e2e encryption passphrase

[niwakame]

I created an encrypted folder with the iOS client, compiled the latest master ( 64cbc88 ) on OSX. When starting the client, it asks me for the E2E passphrase, but it's not accepting the input as correct.

Log output:

[OCC::ClientSideEncryption::getPublicKeyFromServer()::(anonymous class)::operator() 	Found Public key, requesting Private Key.

[OCC::ClientSideEncryption::getPrivateKeyFromServer 	Retrieving private key from server

[OCC::ClientSideEncryption::getPrivateKeyFromServer()::(anonymous class)::operator() 	"<LONG KEY>"

[OCC::ClientSideEncryption::getPrivateKeyFromServer()::(anonymous class)::operator() 	Found private key, lets decrypt it!

[OCC::ClientSideEncryption::decryptPrivateKey 	Got mnemonic: "you really dont think I would post the actual mnemonic here right question mark"

[OCC::ClientSideEncryption::decryptPrivateKey 	mnemonic: "youreallydontthinkIwouldposttheactualmnemonichererightquestionmark"

[OCC::EncryptionHelper::generatePassword 	Start encryption key generation!
[OCC::EncryptionHelper::generatePassword 	Encryption key generated!
[OCC::ClientSideEncryption::decryptPrivateKey 	Generated key: \blah \blah
[OCC::EncryptionHelper::decryptPrivateKey 	decryptStringSymmetric key: \blah \blah
[OCC::EncryptionHelper::decryptPrivateKey 	decryptStringSymmetric data: <LONG KEY>
[OCC::EncryptionHelper::decryptPrivateKey 	sep at 3052
[OCC::EncryptionHelper::decryptPrivateKey 	decryptStringSymmetric cipherTXT <LONG KEY>
[OCC::EncryptionHelper::decryptPrivateKey 	decryptStringSymmetric IV: <SOME IV>

[OCC::ClientSideEncryption::decryptPrivateKey 	Private key:  "-----BEGIN RSA PRIVATE KEY-----\n-----END RSA PRIVATE KEY-----\n"

And then the popup appears again. Any pointers?

[camilasan]

any idea @tcanabrava @dantti?
any changes on your side @tobiasKaminsky @mario that could have cause this?

thanks for the report @niwakame

[dantti]

When I tested this using a second user unix account it worked fine, would need to test again...

[dantti]

Just tested here and it worked fine, the last line

"-----BEGIN RSA PRIVATE KEY-----\n-----END RSA PRIVATE KEY-----\n"

had the key contents where you see just \n.

Now the obvious question, did you try with another client like Android? And are you sure the passphrase is right?

[niwakame]

Thanks for testing.

The passphrase is definitely right. I will try with an Android device later on and see if this makes a difference. And try vice versa desktop and mobile.

[niwakame]

Is there a way to delete the keys on the server, so I can start the key creation procedure again?

[messimuc]

same here with 64cbc8 on macOS - same log output @niwakame . encryted folder was created by stock iOS app - E2E decryption was possible with prereleases/E2E/Windows/ c04d1f on windows10

[tcanabrava]

hm... when you get the payload from the server you are receiving an empty metadata. I'll try the following: create an account in a linux box, test the download in another linux box. Expect test results and patches for today tomorrow.

…

On Sat, Apr 28, 2018 at 4:56 PM, Christian Messerschmidt < ***@***.***> wrote: same here with 64cbc8 on macOS - same log output @niwakame <https://github.com/niwakame> . encryted folder was created by iOS - E2E decryption was possible with prereleases/E2E/Windows/ on windows10 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#268 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AD1zUHqssIJuYfz2pH6JFfZeC2yElzMFks5ttIMdgaJpZM4TqcsZ> .

[niwakame]

Confirming @messimuc 's observations. It's fully working with iOS and Windows, yet OSX is failing.

[tcanabrava]

hm, please, now I'm confused. it's working or not with this client, in Windows?
the compiled code is the same in the OSX and it fails?
(just so I understand where I need to focus the bugfix)

[niwakame]

Windows (prerelease) and iOS working.
OSX ( 64cbc88 ) fails with above errors.

Haven't tested 64cbc88 in Windows, as I don't have the build env here.