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

sending works, but receiving does not work: Exception: org.signal.libsignal.protocol.InvalidMessageException: invalid Whisper message: decryption failed (ProtocolInvalidMessageException) #1532

Open
Wikinaut opened this issue May 21, 2024 · 6 comments

Comments

@Wikinaut
Copy link

  • signal-cli --version 0.12.8
  • Sending: works
  • Receiving: does not work

[After 108 days not running the receive command, ] now I see this when receiving a message:

How can I fix this issue?

signal-cli -u +YY receive
Envelope from: “X” +XX (device: 3) to +YY
Timestamp: 1716293968492 (2024-05-21T12:19:28.492Z)
Server timestamps: received: 1716293968558 (2024-05-21T12:19:28.558Z) delivered: 1716293968561 (2024-05-21T12:19:28.561Z)
Sent by unidentified/sealed sender
Exception: org.signal.libsignal.protocol.InvalidMessageException: invalid Whisper message: decryption failed (ProtocolInvalidMessageException)

Envelope from: “X” +XX (device: 3) to +YY
Timestamp: 1716293968853 (2024-05-21T12:19:28.853Z)
Server timestamps: received: 1716293969955 (2024-05-21T12:19:29.955Z) delivered: 1716293969957 (2024-05-21T12:19:29.957Z)
Received a receipt message
  When: 1716293969955 (2024-05-21T12:19:29.955Z)
  Is delivery receipt
  Timestamps:
  - 1716293968853 (2024-05-21T12:19:28.853Z)
@m-ueberall
Copy link

@Wikinaut: Depending on where you got your installation of signal-cli from, did you already try to switch to a current version (v13.3 at the time of writing)?

@Wikinaut
Copy link
Author

See my other issue which prevents running >= 13.0

@Wikinaut: Depending on where you got your installation of signal-cli from, did you already try to switch to a current version (v13.3 at the time of writing)?

#1531

@Wikinaut
Copy link
Author

Is there a way to restart the ratcheting....? I could not find a command.

@m-ueberall
Copy link

m-ueberall commented May 22, 2024

See my other issue which prevents running >= 13.0
#1531

Ah, I missed that. For Debian 12/Bookworm, you currently have two options (depending on your architecture, that is): Either upgrade to JDK21 using external packages (see, e.g., https://computingforgeeks.com/install-java-jdk-or-openjdk-21-on-debian/) or use a signal-cli binary produced with GraalVM (see https://github.com/AsamK/signal-cli/wiki/Binary-distributions).
For other/currently unsupported architectures, you best bet would be to backport Open JDK 21 based on testing/Trixie packages; on Ubuntu, a backport for 20.04/Focal exists since January (which suggests that it's not an impossible task).

@AsamK
Copy link
Owner

AsamK commented May 22, 2024

You can try to reset the session with send -e

@Wikinaut
Copy link
Author

You can try to reset the session with send -e

This worked from the server Y to my smartphone X (I see a message there that the secure session was reset).
But it did not help to receive.

I still got

Envelope from: “X" XX (device: 3) to Y
Timestamp: 1716389047416 (2024-05-22T14:44:07.416Z)
Server timestamps: received: 1716389047603 (2024-05-22T14:44:07.603Z) delivered: 1716389047605 (2024-05-22T14:44:07.605Z)
Sent by unidentified/sealed sender
Exception: org.signal.libsignal.protocol.InvalidMessageException: invalid Whisper message: decryption failed (ProtocolInvalidMessageException)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants