INVALID KEY from libaxolotl when trying to build session from bundle

[aladar42]

Since I updated to 0.6.0, the encryption broke again. I made sure to log off of every other account, but that still didn't help.

(4:53:33 PM) There was an error encrypting the message and it was not sent. You can try again, or try to find the problem by looking at the debug log.

(16:53:15) util: Writing file prefs.xml to directory C:\Users\Aladar\AppData\Roaming\.purple
(16:53:15) util: Writing file C:\Users\Aladar\AppData\Roaming\.purple\prefs.xml
(16:53:15) jabber: Sending (ssl) (me@jabber.id/.): <message type='chat' id='purplea59e1680' to='recipient@jabber.id'><composing xmlns='http://jabber.org/protocol/chatstates'/></message>
(16:53:19) jabber: Sending (ssl) (me@jabber.id/.): <message type='chat' id='purplea59e1681' to='recipient@jabber.id'><active xmlns='http://jabber.org/protocol/chatstates'/></message>
(16:53:22) jabber: Sending (ssl) (me@jabber.id/.): <message type='chat' id='purplea59e1682' to='recipient@jabber.id'><composing xmlns='http://jabber.org/protocol/chatstates'/></message>
(16:53:24) jabber: Sending (ssl) (me@jabber.id/.): <message type='chat' id='purplea59e1683' to='recipient@jabber.id'><active xmlns='http://jabber.org/protocol/chatstates'/></message>
(16:53:27) jabber: Sending (ssl) (me@jabber.id/.): <message type='chat' id='purplea59e1684' to='recipient@jabber.id'><composing xmlns='http://jabber.org/protocol/chatstates'/></message>
(16:53:30) jabber: Sending (ssl) (me@jabber.id/.): <message type='chat' id='purplea59e1685' to='recipient@jabber.id'><active xmlns='http://jabber.org/protocol/chatstates'/></message>
(16:53:33) jabber: Sending (ssl) (me@jabber.id/.): <message type='chat' id='purplea59e1686' to='recipient@jabber.id'><composing xmlns='http://jabber.org/protocol/chatstates'/></message>
(16:53:33) lurch: retrieved devicelist for recipient@jabber.id:
<publish node="eu.siacs.conversations.axolotl.devicelist"><item><list
xmlns="eu.siacs.conversations.axolotl"><device id="154..." /></list></item></publish>

(16:53:33) lurch: retrieved own devicelist:
<publish node="eu.siacs.conversations.axolotl.devicelist"><item><list
xmlns="eu.siacs.conversations.axolotl"><device id="331..." /><device
id="102¨..." /></list></item></publish>

(16:53:33) lurch: lurch_msg_finalize_encryption: recipient@jabber.id has device without session 154..., requesting bundle
(16:53:33) lurch: lurch_bundle_request_do: me@jabber.id/ is requesting bundle from recipient@jabber.id:154...
(16:53:33) jabber: Sending (ssl) (me@jabber.id/.): <iq type='get' to='recipient@jabber.id' id='recipient@jabber.id#154...#638...'><pubsub xmlns='http://jabber.org/protocol/pubsub'><items node='eu.siacs.conversations.axolotl.bundles:154...' max_items='1'/></pubsub></iq>
(16:53:33) lurch: lurch_bundle_request_do: ...request sent
(16:53:33) g_log: xmlnode_to_str_helper: assertion `node != NULL' failed
(16:53:33) g_log: jabber_send_raw: assertion `data != NULL' failed
(16:53:33) jabber: Sending (ssl) (me@jabber.id/.): <message type='chat' id='purplea59e1689' to='recipient@jabber.id'><active xmlns='http://jabber.org/protocol/chatstates'/></message>
(16:53:33) jabber: Recv (ssl)(4095): <iq id='recipient@jabber.id#154...#638...' type='result' to='me@jabber.id/.' from='recipient@jabber.id'><pubsub xmlns='http://jabber.org/protocol/pubsub'><items node='eu.siacs.conversations.axolotl.bundles:154...'><item id='1'><bundle xmlns='eu.siacs.conversations.axolotl'><signedPreKeyPublic signedPreKeyId='2'>
</signedPreKeyPublic><signedPreKeySignature>
FmEjt6oaBA==
</signedPreKeySignature><identityKey>
</identityKey><prekeys><preKeyPublic 
(16:53:33) jabber: XML parser error for JabberStream 0524BCA8: Domain 3, code 100, level 1: xmlns: URI eu.siacs.conversations.axolotl is not absolute
(16:53:33) jabber: Recv (ssl)(4095): ol
</preKeyPublic><preKeyPublic preKeyId='190'>
(16:53:33) jabber: Recv (ssl)(2): N

(16:53:33) jabber: Recv (ssl)(1398): </preKeyPublic>
</preKeyPublic></prekeys></bundle></item></items></pubsub></iq>
(16:53:33) lurch: lurch_bundle_request_cb: me@jabber.id received bundle update from recipient@jabber.id:154...
(16:53:33) lurch: lurch_bundle_create_session: creating a session between me@jabber.id and recipient@jabber.id from a received bundle
(16:53:33) lurch: lurch_bundle_create_session: bundle's device id is 154...
(16:53:33) lurch: lurch_bundle_create_session: failed to create a session from a bundle (-1002)
(16:53:33) lurch: lurch_bundle_request_cb: failed to create a session (-1002)

[gkdr]

In 0.6.0 I only changed some display stuff when decrypting (I didn't expect messages coming from the own account because there was no carbons), it should not affect you.
Did you also delete the database, or why do you have to build the session again?

As I might have said before: -1002 is an error deep down from libaxolotl - INVALID KEY.
The function I use returns it in two cases:

1. The signature verification of the signed prekey failed.
2. Neither a signed nor an unsigned key was given to the function.

So I'm not entirely sure it's the fault of this plugin. (It could be though since for various reasons I use a legacy version of libsignal - but then it wouldn't have worked the last time.)

Which client does your conversation partner use? What happens if he messages you first?

[gkdr]

@aladar42 Does the issue still persist?

[aladar42]

Sorry, I had some issues and couldn't make it to PC. It's fine now, at least from Pidgin to Conversations.