[Pkg-xmpp-devel] Bug#1026430: more bugs to account for than upstream is aware of

[debbug.1026430 at sideload.33mail.com]

Package: profanity
Version: 0.13.1-1~bpo11+1
Followup-For: Bug #1026430
X-Debbugs-Cc: debbug.1026430 at sideload.33mail.com

The scenario captured in bug 1026430 actually expands into 4 bugs. Upstream bug report 1615¹ seems to capture sub bug 1 (the mere fact that fingerprints are lost) but not sub bugs 2—4.

If upstream bug 1615 is resolved by merely mitigating the key loss, what happens when there is no key for someone to begin with?  Or when a key expires?  More guard conditionals are needed to ensure a msg doesn’t go out to a group without everyone’s pubkey first being completely resolved. This check should ideally be performed before the sender even begins typing a msg.

1. https://github.com/profanity-im/profanity/issues/1615