Verification not successful

[ppar]

I'm not able to verify pantalaimon as a Device in Matrix, so encryption/decryption features are not working.

FWIW, I don't know if these are the right steps to follow. I've opened a separate issue about documenting the correct procedure: https://github.com/matrix-org/pantalaimon/issues/154

This is on version 0.10.5 installed using pip.

After configuring and starting pantalaimon, and connecting to it using https://github.com/quotient-im/Quaternion :

• I can see users and messages in unencrypted chats as expected
• Encrypted chats show lists of users and messages, but messages' contents show up as " Unable to decrypt: The sender's device has not sent us the keys for this message. "
• pantalaimon stderr output shows a lot of warnings like:

  [2023-02-04 16:12:37.667488] WARNING: pantalaimon: Error decrypting megolm event, no session found with session id XXXXXXYYYYY for room !XXXYYYZZZZ:DOMAIN.TLD

  And also some messages like:

  [2023-02-04 16:12:37.677732] WARNING: pantalaimon: Encrypted event is not a megolm event:
  {'age': 14947NNN,
  'content': {},
  'event_id': '$XXXXYYZZZZ',
  'origin_server_ts': 167403NNN,
  'redacted_because': {'age': 14946NNN,
                      'content': {},
                      'event_id': '$XXXXYYZZZZ',
                      'origin_server_ts': 167403NNN,
                      'redacts': '$XXXXYYZZZZ',
                      'room_id': '!XXXXYYZZZZ:DOMAIN.TLD',
                      'sender': '@signal_XXXYYYZZZ:DOMAIN.TLD',
                      'type': 'm.room.redaction',
                      'unsigned': {'age': 149NNNNN},
                      'user_id': '@signal_XXXYYYZZZ:DOMAIN.TLD'},
  'room_id': '!XXXYYYZZZ:DOMAIN.TLD',
  'sender': '@signal_XXXYYYZZZ:DOMAIN.TLD',
  'type': 'm.room.encrypted',
  ....

• My other Matrix clients (Element on Android and web) show a new unverified device named "pantalaimon"
• After clicking "Verify" next to the "pantalaimon" device in Element web UI, it prompts "To proceed, please accept the verification request on your other device" in a modal dialogue.
• Running accept-verification in panctl, its command completion feature offers my own username for both pan_user and user_id, and a bunch of options for device ID. Also some bridge users (Signal, Telegram, etc) present on the Matrix server are shown as users.
• Using my own username for both pan_user and user_id, and iterating through the different device IDs always results in:

  panctl> accept-verification @USER:MYDOMAIN.TLD @USER:MYDOMAIN.TLD XXXXYYYYZZZ
  Unknown transaction

[pickinanameainteasy]

Running into a similar issue. I logged in with curl and got an access token through pantalaimon. I tried to send a message to the room via curl and got this error:

{"errcode": "M_UNKNOWN", "error": "The pantalaimon client did not manage to sync with the server"}

According to documentation all you need to do to sync to the server is log in which i did.

So i opened the user in element, I also see 'pantalaimon' as unverified. I click 'verify'.

In panctl I run accept-verification @user-name:server-name device-id @user-name:server-name that is the only way to not get an error it just gives no output. I then run confirm-verification @user-name:server-name device-id @user-name:server-name again no output to show success, but i assumed that meant it worked. However, in element it still shows unverified.

I attempt to send another message via curl and but it fails.

Checking the logs of pantalaimon shows that the verification was declined because the client did not manage to sync with the server.

I tried doing start-verification @user-name:server-name device-id device-id-of-element and it gives this error: No device found for device-id and device-id-of-element

Better documentation is required as it doesn't really make sense currently

[Arnavion]

I also could not get it to work if I initiate the verification from another client, but initiating the verification from panctl works fine. I documented the whole process in https://github.com/matrix-org/pantalaimon/issues/154#issuecomment-1951591191