Colin Constable

I will test

After digging into the problem that causes the issue is in :- https://github.com/atsign-foundation/at_client_sdk/blob/trunk/at_client/lib/src/transformer/response_transformer/get_response_transformer.dart lines 38/39 ``` // For public and cached public keys, data is not encrypted. // Decrypt the...

Although that fixes things it is probably not the ideal solution.. Would appreciate your thoughts on the best way to fix the bug. @VJag @gkc @murali-shris @kalluriramkumar

With this 'fix' in place still get plenty of errors from the contact lib @sarika01 / @murali-shris My guess is that these are contact entries that we used to be...

As a side note... I see this odd cached key in the public space which I do not think it should ever be public. ``` cconstab@cally:~$ openssl s_client -tls1_2 -ign_eof...

Any update on this issue ?

I think we should just stick with one aes key as it's tough to manage 1 let alone X. So we need some where to offer a mutex for aes...

We do not cut the key on the server instead we use it to manage a mutex.

Yes for sure it is

Checked and not able to reproduce with new client code