fix(omemo): bootstrap device list on prosody servers (#169) #171

Open

jabber.developer2 wants to merge 1 commits from fix/omemo-prosody-bootstrap into master

Author	SHA1	Message	Date
jabber.developer2	61a5de6ab9	fix(omemo): bootstrap device list on prosody-class servers All checks were successful CI Code / Check coding style (pull_request) Successful in 29s Details CI Code / Linux (debian) (pull_request) Successful in 8m38s Details CI Code / Check spelling (pull_request) Successful in 14s Details CI Code / Linux (ubuntu) (pull_request) Successful in 4m40s Details CI Code / Linux (arch) (pull_request) Successful in 12m35s Details CI Code / Code Coverage (pull_request) Successful in 10m2s Details Two gaps kept /omemo gen from ever publishing on a fresh account: - _omemo_receive_devicelist() only recognised the legacy code='404' error attribute as "node does not exist". Prosody sends the RFC 6120 <item-not-found/> condition instead, so the empty-list bootstrap never ran. Accept the defined condition too, and log the expected bootstrap case at debug instead of error. - connection_request_features() disco'd only the server domain, but XEP-0163 PEP services (including pubsub#publish-options) announce their features on the account's bare JID. Query the bare JID as well, registering it in the feature table, so connection_supports() sees PEP features. Fixes #169	2026-07-21 09:14:59 +03:00

Author

SHA1

Message

Date

jabber.developer2

61a5de6ab9

fix(omemo): bootstrap device list on prosody-class servers

CI Code / Check coding style (pull_request) Successful in 29s

Details

CI Code / Linux (debian) (pull_request) Successful in 8m38s

Details

CI Code / Check spelling (pull_request) Successful in 14s

Details

CI Code / Linux (ubuntu) (pull_request) Successful in 4m40s

Details

CI Code / Linux (arch) (pull_request) Successful in 12m35s

Details

CI Code / Code Coverage (pull_request) Successful in 10m2s

Details

Two gaps kept /omemo gen from ever publishing on a fresh account:

- _omemo_receive_devicelist() only recognised the legacy code='404'
  error attribute as "node does not exist". Prosody sends the RFC 6120
  <item-not-found/> condition instead, so the empty-list bootstrap never
  ran. Accept the defined condition too, and log the expected bootstrap
  case at debug instead of error.

- connection_request_features() disco'd only the server domain, but
  XEP-0163 PEP services (including pubsub#publish-options) announce
  their features on the account's bare JID. Query the bare JID as well,
  registering it in the feature table, so connection_supports() sees
  PEP features.

Fixes #169

2026-07-21 09:14:59 +03:00

fix(omemo): bootstrap device list on prosody servers (#169) #171

1 Commits