Issues with XMPP proofs - Debian 11 / Prosody 0.11.9 #110

Open
opened 1 month ago by lazyteddy · 7 comments

Hi

I just upgraded my home server to Debian 11, which updated Prosody to 0.11.9. Since then XMPP proofs don't seem to work anymore. I tried publishing my info using Pidgin, Gajim, and Psi, then I went back to the Keyoxide instructions, which I hadn't looked at in a while, and saw that there's now a recommendation to use mov.im, so I tried that, too, and found that the profile information is already there. Still no luck.

I checked the new Prosody configuration against the one from Debian 10 / Prosody 0.11.2, and there is a difference in the modules_enabled section concerning user profiles / vcards. Here's the old version, which is still running on my VPS, where XMPP proofs work as expected:

"vcard"; -- Allow users to set vCards

And in the new one:

"vcard"; -- Allow users to set vCards
"vcard_legacy"; -- Conversion between legacy vCard and PEP Avatar, vcard

Is it possible that this is causing issues in the way XMPP proofs work?

Hi I just upgraded my home server to Debian 11, which updated Prosody to 0.11.9. Since then XMPP proofs don't seem to work anymore. I tried publishing my info using Pidgin, Gajim, and Psi, then I went back to the Keyoxide instructions, which I hadn't looked at in a while, and saw that there's now a recommendation to use mov.im, so I tried that, too, and found that the profile information is already there. Still no luck. I checked the new Prosody configuration against the one from Debian 10 / Prosody 0.11.2, and there is a difference in the modules_enabled section concerning user profiles / vcards. Here's the old version, which is still running on my VPS, where XMPP proofs work as expected: ``` "vcard"; -- Allow users to set vCards ``` And in the new one: ``` "vcard"; -- Allow users to set vCards "vcard_legacy"; -- Conversion between legacy vCard and PEP Avatar, vcard ``` Is it possible that this is causing issues in the way XMPP proofs work?
Owner

Sorry for not getting to this issue earlier.

So you are suspecting that sometimes, the proofs are stored in vcard_legacy, a place where Keyoxide doesn't look?

Could you (privately if you wish, email: yarmo@keyoxide.org, matrix or something else?) send me the jabber id of an account for which this is happening?

Sorry for not getting to this issue earlier. So you are suspecting that sometimes, the proofs are stored in `vcard_legacy`, a place where Keyoxide doesn't look? Could you (privately if you wish, email: yarmo@keyoxide.org, matrix or something else?) send me the jabber id of an account for which this is happening?
yarmo added the
bug
label 2 weeks ago
Poster

Sorry, didn't see this until now. I just sent you the key in question in an e-mail, thanks for providing that.

I re-added the XMPP proof; I had removed because I didn't want an unverified proof to show. It's still not showing, though, although the profile information is there.

I don't really understand how any of this works, it's just that that's the one difference that stands out between my two servers.

Sorry, didn't see this until now. I just sent you the key in question in an e-mail, thanks for providing that. I re-added the XMPP proof; I had removed because I didn't want an unverified proof to show. It's still not showing, though, although the profile information is there. I don't really understand how any of this works, it's just that that's the one difference that stands out between my two servers.
Owner

Well, the XMPP protocol is not my forte so I'm also discovering as we go.

Thanks for sending me the key in question. You may remove the notation again if you wish, I have all the info I need to debug.

Working on it as we speak. Just in case, a basic check: currently, using mov.im or other tools you mentioned, the vcard information is still present on your account?

Edit: never mind, you confirmed that in your last message. Ok, going on a search for the missing vcard information.

Well, the XMPP protocol is not my forte so I'm also discovering as we go. Thanks for sending me the key in question. You may remove the notation again if you wish, I have all the info I need to debug. Working on it as we speak. Just in case, a basic check: currently, using mov.im or other tools you mentioned, the vcard information is still present on your account? Edit: never mind, you confirmed that in your last message. Ok, going on a search for the missing vcard information.
Owner

The only vCard information I am receiving on my end is that your first name is "Hello". Can you confirm whether this is information you have inputted somewhere? If not, it could be some default information I'm not interested in (I think).

~~The only vCard information I am receiving on my end is that your first name is "Hello". Can you confirm whether this is information you have inputted somewhere? If not, it could be some default information I'm not interested in (I think).~~
Owner

The more I work on this, the less I understand. Yay.

I have found the prosody modules you refer to:

The vcard module is supposed to add support for XEP-0054: vcard-temp.

The vcard_legacy module is supposed to... Convert between vCard, vCard4 and PEP?

So I can fetch your vcard information, but it's completely empty. Which is strange.

Could you try disabling the vcard_legacy module?

The more I work on this, the less I understand. Yay. I have found the prosody modules you refer to: - vcard -> https://prosody.im/doc/modules/mod_vcard - vcard_legacy -> https://prosody.im/doc/modules/mod_vcard_legacy The `vcard` module is supposed to add support for [XEP-0054: vcard-temp](https://xmpp.org/extensions/xep-0054.html). The `vcard_legacy` module is supposed to... Convert between vCard, vCard4 and PEP? So I can fetch your vcard information, but it's completely empty. Which is strange. Could you try disabling the `vcard_legacy` module?
Poster

Sorry for not getting back to you earlier; busy week around here.

Just in case, a basic check: currently, using mov.im or other tools you mentioned, the vcard information is still present on your account?

Yes. I even updated the website just now from Gajim, and the change went through, and I can still see the old "About" info (even though Gajim doesn't seem to have that anymore.)

Edit: never mind, you confirmed that in your last message.

Thought I'd check anyway.

Could you try disabling the vcard_legacy module?

Done. No change in Keyoxide, though.

Edit: Huh! I'll be darned. I just updated my profile information yet again, this time from Pidgin, and suddenly it works in Keyoxide.

I'm wondering if this is more of an XMPP issue instead of Keyoxide.

Sorry for not getting back to you earlier; busy week around here. > Just in case, a basic check: currently, using mov.im or other tools you mentioned, the vcard information is still present on your account? Yes. I even updated the website just now from Gajim, and the change went through, and I can still see the old "About" info (even though Gajim doesn't seem to have that anymore.) > Edit: never mind, you confirmed that in your last message. Thought I'd check anyway. > Could you try disabling the vcard_legacy module? Done. No change in Keyoxide, though. Edit: Huh! I'll be darned. I just updated my profile information yet again, this time from Pidgin, and suddenly it works in Keyoxide. I'm wondering if this is more of an XMPP issue instead of Keyoxide.
Poster

Thanks for taking the time to look into this, even though this (quite likely) may not have been related to Keyoxide.

Thanks for taking the time to look into this, even though this (quite likely) may not have been related to Keyoxide.
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.