OMEMO libsignal-protocol.js Invalid signature
See original GitHub issueHi Dev, I’ve just installed (from git) on VPS Debian Stretch, Prosody 0.11, Fail2ban 0.9.6-2, Shorewall 5.0.15.6-1, Apache 2.4.25, modsecurity 3.0.0-3, php7 7.0.33, Converse.js v4.2.0.
Then I’ve enabled OMEMO, as described from @licaon-kter here, the green padlock is present but trying to send in OMEMO mode I get the following error:
Error: Invalid signature libsignal-protocol.js:25278:28
and obviously the message does not start.
I’ve try to exit, re-enter in untrusted device mode and back in trusted device as suggested here with no changes.
Here my Converse installation.
Thanks!
Davide
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:19 (8 by maintainers)
Top Results From Across the Web
Smack 4.4.0: Omemo does not update the identity info of a ...
Thread.run(Thread.java:818) Caused by: org.whispersystems.libsignal.InvalidKeyException: Invalid signature on device key! at ...
Read more >plugins/omemo/store.js - Converse.js API Documentation Source
// example given in InMemorySignalProtocolStore. // Should be fine because the libsignal code doesn't; // actually call this method.
Read more >prosody-dev - The Mail Archive
... OMEMO libsignal-protocol.js Invalid signature Matthew Wild; 2019/04/22 Re: [prosody-dev] Converse.js and OMEMO libsignal-protocol.js Invalid signature ...
Read more >org.whispersystems.libsignal.state.PreKeyBundle Java Exaples
Source Project: libsignal-protocol-java Author: signalapp File: SessionBuilderTest.java ... throw new InvalidKeyException("Invalid signature on device key!
Read more >@privacyresearch/curve25519-typescript - npm
... curves used in [libsignal-protocol-javascript](https://github.com/signalapp ... `verify` returns `true` for invalid signatures throw new ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you @orbitz, that’s very helpful! I’m working on a commit to fix this.
I downgraded to 4.1.2 on my server and OMEMO messages send again. i think this was introduced in 4.2.0