start-verification - can't verify, the other client doesn't get the request

[Rutherther]

I've tried setting up pantalaimon. I followed the steps in #154 (comment), but when I execute start-verification @user:domain.tld @user:domain.tld <other-device-id> in panctl, although I get Successfully started the key verification request, the request is not seen in the other client. I got the id from the client itself, so I am sure I am requesting the correct device for verification.

I am using Conduit as the home server. I've tried multiple clients on the other side - Element in browser, FluffyChat or Element X on Android.

[alphapapa]

Since people have reported that it works correctly (at least, with master), I'd guess that using Conduit might be part of the problem (not necessarily that Conduit has a bug in this regard, but that it might not behave exactly the same as Synapse).

[sanderhollaar]

Same here. Nor start-verification from panctl to, or verification requests from element-desktop, cinny-desktop and Element X on Android trigger a response at the other side. Also connected the desktop clients to pantalaimon, and directly to the conduit homeserver. I'll try a different homeserver and report back.

[Hixer05]

I've tried to start the verification from the other device (from Settings -> Session -> Unverified ... -> Verify); and it says to accept the verification with the other device. So from panctl: accept-verification ... and it ouputs Unknown transaction; while the other is still waiting pantalaimon to accept

The server runs synapse though; and i'm using the latest master release

[sanderhollaar]

I tried with dendrite: same result, both start-verification from panctl to element-desktop, and Verify session from Element with accept-verification in panctl triggers no response.

I'm on NixOS, with dendrite as homeserver (clean install, new user) and caddy as proxy.

• stop pantalaimon.service
• remove pantalaimon config
• start pantalaimon.service
• remove Element config
• Element login to dendrite with new (and only) user
• create room (Encrypted, Private)
• in emacs: (ement-connect :uri-prefix "http://localhost:8448")
• login with same user
• Popup in Element New login. Was this you? -> confirm
• emacs: join room
• successfully send and receive messages in room from both clients
• in panctl verify-device to set Element Trust state to Verified
• in panctl start-verification of Element does not trigger a popup in Element
• in panctl Successfully cancel-verification
• in Element Verify session pantalaimon
• in panctl accept-verification: Unknown transaction

If I initiate the verification from Element, pantalaimon logs:

pantalaimon: Error validating event: 'sender_key' is a required property
pantalaimon: Failed validating 'required' in schema['properties']['content']:
pantalaimon:     {'type': 'object',
pantalaimon:      'properties': {'sender_key': {'type': 'string'},
pantalaimon:                     'algorithm': {'type': 'string'}},
pantalaimon:      'required': ['sender_key', 'algorithm']}
pantalaimon: On instance['content']:
pantalaimon:     {'from_device': 'Y33Nc4oo',
pantalaimon:      'methods': ['m.sas.v1', 'm.qr_code.show.v1', 'm.reciprocate.v1'],
pantalaimon:      'timestamp': 1736603877258,
pantalaimon:      'transaction_id': '69e44613bed24a768d6c53289bdb7ed5'}

If I cancel the verification in Element:

pantalaimon: Error validating event: 'sender_key' is a required property
pantalaimon: Failed validating 'required' in schema['properties']['content']:
pantalaimon:     {'type': 'object',
pantalaimon:      'properties': {'sender_key': {'type': 'string'},
pantalaimon:                     'algorithm': {'type': 'string'}},
pantalaimon:      'required': ['sender_key', 'algorithm']}
pantalaimon: On instance['content']:
pantalaimon:     {'code': 'm.user',
pantalaimon:      'reason': 'The user cancelled the verification.',
pantalaimon:      'transaction_id': '69e44613bed24a768d6c53289bdb7ed5'}
pantalaimon: Received key verification event with an unknown transaction id from @<redacted>:<redacted>

$ panctl --version
panctl, version 0.10.5

[Rutherther]

@Hixer05 that is reported as a separate issue, it is known that even with Synapse you need to initiate the verification process from pantalaimon

[sanderhollaar]

fwiw, I've tried again with a clean install of dendrite, and with clients fluffychat on linux and android, and cinny-desktop on (same) linux.

• All clients verified among each other
• Login with ement to http://localhost:8448, send and receive message in note to self room, and successfully verify all three clients with panctl.
• in android fluffychat Settings Devices, observe pantalaimon is Unverified
• panctl start-verification .. of android fluffychat -> no response in fluffychat
• android fluffychat Start Verification
• pantalaimon logs:Received unsupported Olm event of type m.key.verification.request
• Attempted to mark device <andoid fluffychat> of user <@user:domain> for Olm session unwedging, but a new session was created recently.
• panctl accept-verification -> Verification was started by us, can't accept offer
• panctl cancel-verification .. -> Successfully canceled the key verification request
• panctl accept-verification .. -> Unknown transaction
• android fluffychat Cancel
• pantalaimon logs:Received unsupported Olm event of type m.key.verification.cancel
• Attempted to mark device <andoid fluffychat> of user <@user:domain> for Olm session unwedging, but a new session was created recently.

[vampywiz17]

Hello there,

Any solution?

I try about 3 hour, that finally found these issue...

I use Matrix.org server i able to login any client with pantalaimon, but not pantalaimon itself...

If i send start-verification... element (native linux app) can not get it. also try element webapp but same result.

I would like to use it to proxy my Apprise but no luck...

Any idea?

[dogesking]

Same issue here with patalaimon and a matrix3 client on the web.
I can send unverified messages, but the pantcl start_verification don't trigger anything on the web client end.
And I'm receiving a timeout after exactly 1 minute.

[Thaodan]

I noticed the same issue on openSUSE with either ement and element as the other client.

[Thaodan]

I wonder if this is related to:
matrix-nio/matrix-nio#466

[mugcake]

I still don't know what the exact cause of the problem is. But in my case, start-verification from panctl to thunderbird [icedove] works!!
Must: First confirm-verification in pactl and then in the other client "They match" button; otherwise it doesn't work, and panctl returns Unknown transaction

[vampywiz17]

@mugcake

I try thunderbird, but not work.... The verification are runing well, it seems everything is ok i see the emoji, accept both side, but pantalaimon still unverified....

That i do step by step:

• Download thunderbird and login same user that i use with pantalaimon
• Verify Thunderbird with my account key (thunderbird client are verifiied)
• Start verification with pantalaimon side: start-verification @user:matrix.org @homeassistant_user:matrix.org wu0****H
• Thunderbird site got the notification and i accept it.
• pantalaimon side i type confirm-verification @user:matrix.org @homeassistant_user:matrix.org wu0****H
• Also Confirm it on thunderbird side
• pantalaimon say that: Device wu0****H of user @user:matrix.org successfully verified for pan user @user:matrix.org.

But in Thunderbird , pantalaimon still unverified and i can not able to send verified e2ee message....

[mugcake]

@vampywiz17

pantalaimon say that: Device wu0****H of user @user:matrix.org successfully verified for pan user @user:matrix.org.

After that, just follow the rest of the steps, they are not optional. Restart Pantalaimon, your client (in my case Emacs + ement.el) and Thunderbird.

At this point you should already see the encrypted conversations.

But in Thunderbird , pantalaimon still unverified and i can not able to send verified e2ee message....

Now, the first time you send messages to an encrypted conversation from the client, pantalaimon will notify on the terminal screen and in a pop-up notification (if you have this enabled) that there are unverified devices in that conversation. Just send-anyways command solves it. Or just click "send-anyways" button in the pop-up notification.

Sadly this is a temporary solution. The device will always appear unverified to all other devices in the conversation.