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

ably-java sometimes failing to decrypt Messages #531

Closed
SimonWoolf opened this issue Nov 22, 2019 · 2 comments
Closed

ably-java sometimes failing to decrypt Messages #531

SimonWoolf opened this issue Nov 22, 2019 · 2 comments
Labels
bug Something isn't working. It's clear that this does need to be fixed.

Comments

@SimonWoolf
Copy link
Member

Customer reports that encrypted messages are occasionally unable to be decrypted:

2019-11-22 11:48:20.515 E/ABLY_INTERNAL: decrypt()
2019-11-22 11:48:20.515 E/ABLY_INTERNAL: error:1e00007b:Cipher functions:OPENSSL_internal:WRONG_FINAL_BLOCK_LENGTH
2019-11-22 11:48:20.515 E/ABLY_INTERNAL: Unexpected exception: error:1e00007b:Cipher functions:OPENSSL_internal:WRONG_FINAL_BLOCK_LENGTH

It appears to be specific messages only, but those messages can apparently still sometimes be successfully decrypted, but not other times.

Unclear whether the messages in question were published from ably-java or ably-cocoa, but it is one or the other. Also unclear whether the problem is limited to messages published by only one of those client libs, or both. So may be an ably-cocoa bug.

See internal channels for example of a raw message that sometimes can't be decrypted

@SimonWoolf SimonWoolf added bug Something isn't working. It's clear that this does need to be fixed. important labels Nov 22, 2019
@amihaiemil
Copy link
Contributor

amihaiemil commented Nov 25, 2019

@SimonWoolf Can you please give more details about this Issue? What's the exact scenario when this happens (code flow?). Also, you say:

See internal channels for example of a raw message that sometimes can't be decrypted

What are the "internal channels"?

Also, if you can point to a test in the library, which is supposed to cover that case, it would be great :D

@SimonWoolf
Copy link
Member Author

What are the "internal channels"?

Sorry if that was unclear -- I just meant our internal company slack. It's a bug report from a customer, the message can't be made public for data privacy reasons.

Re a test case -- no, one does not exist now, once we figure out what happens well enough to write a test that consistently reproduces the issue we'll be most of the way towards solving it 🙂

@QuintinWillison is coordinating the response for this; liaise with him 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working. It's clear that this does need to be fixed.
Development

No branches or pull requests

3 participants