E2E: Unsupported class: class javax.crypto.spec.IvParameterSpec when encrypting the private key.

[ardevd]

Using the latest version from Google Play, whenever I try to enable an encrypted folder, the app shows me a new recovery key phrase, and when proceeding I get an error saying "Keys could not be stored, please try again".

This is on a Pixel 2 XL running Android 8.1.0.

[ardevd]

02-09 23:12:30.829 28516  3071 D SetupEncryptionDialogFragment: public key successful downloaded for xxx@xxxxx
02-09 23:12:30.831 28516  3071 V ArbitraryDataProvider: Updating arbitrary data with cloud id: xxx@xxxx key: PUBLIC_KEY value: -----BEGIN CERTIFICATE-----
02-09 23:12:30.831 28516  3071 V ArbitraryDataProvider: <REDACTED>
02-09 23:12:30.831 28516  3071 V ArbitraryDataProvider: <REDACTED>
02-09 23:12:30.831 28516  3071 V ArbitraryDataProvider: <REDACTED>
02-09 23:12:30.831 28516  3071 V ArbitraryDataProvider: <REDACTED>
02-09 23:12:30.831 28516  3071 V ArbitraryDataProvider: <REDACTED>
02-09 23:12:30.831 28516  3071 V ArbitraryDataProvider: -----END CERTIFICATE-----
02-09 23:12:30.841 28516  3071 D OwnCloudClient #2: REQUEST GET /ocs/v2.php/apps/end_to_end_encryption/api/v1/private-key

[ardevd]

No related log entries on the server side which makes me suspect that the issue resides in the client. I'm assuming it's unable to create/store the keys on the device. Has this been tested with Android 8.1.0?

[tigernero79]

Some problem on Samsung s8 Nexus 6 and Nexus 6p, but ok on smartphone huawei

[ardevd]

This is where it fails for me.

RemoteOperationResult result = operation.execute(account, getContext(), true);

                if (result.isSuccess()) {
                    Log_OC.d(TAG, "public key success");

                    publicKey = (String) result.getData().get(0);
                } else {
                    keyResult = KEY_FAILED;
                    return "";
                }

operation.execute() is unsuccessful for some reason and hence the AsyncTask returns an empty string.

Stepping into SendCSROperation shows that the server returns status code 409. I've actually never encountered a 409 error before so I had to look it up. No idea what's causing it though. The POST request looks good and a seemingly proper CSR is being passed to the server.

The issue also occurs when using the Android Emulator (API 27).

[ardevd]

Reading through the E2E app docs the 409 error was caused by the fact that a public key already existed for my user. I deleted it, now the RemoteOperationResult returns 200 OK so now I can finally get to the actual cause of the problem, which is an unsupported KeySpec.

SetupEncryptionDialogFragment: Unsupported class: class javax.crypto.spec.IvParameterSpec

This is caused by EncryptionUtils.encryptPrivateKey(privatePemKeyString, keyPhrase);

[tigernero79]

great, I'm waiting for the solution is new release that fixes the bug. in fact I had another user on s8 and Nexus 6, but on Nexus 6p instead no, but I had an error.

[ardevd]

The offending bit of code: byte[] iv = cipher.getParameters().getParameterSpec(IvParameterSpec.class).getIV();

I'll see if I can make a PR that fixes this.

[ardevd]

PR created. The fix is seemingly pretty simple and works fine on my devices, but they all run Android 8.1.