Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wishlist: implement A/V call OMEMO verification #218

Open
realbiz21 opened this issue May 5, 2023 · 0 comments
Open

Wishlist: implement A/V call OMEMO verification #218

realbiz21 opened this issue May 5, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@realbiz21
Copy link

Is your feature request related to a problem? Please describe.
No, but it would improve assurance that a call is between OMEMO-trusted devices.

Describe the solution you'd like
Siskin supports OMEMO messaging and allows the user to mark another user's OMEMO fingerprint as trusted. This allows the user to know that messages and HTTP attachments are between trusted devices.

However, when jingle A/V calls are performed between two users with trusted OMEMO fingerprints, call setup provides no assurance that the DTLS fingerprints are authenticated by an OMEMO-trusted device.

I have not seen it mentioned searching previous issues, but this issue is to request the feasibility of implementing Conversations' http://gultsch.de/xmpp/drafts/omemo/dlts-srtp-verification.

Describe alternatives you've considered
N/A. The above spec is self-described as an incomplete solution:

... we are still a long road away from having OMEMO 0.5+ in general and any implementational experience with SCE for IQ based protocols in particular. The protocol proposed here is a hack that is hopefully not too dirty.

Therefore it is understandable if it may not be worth the effort, though other non-Conversations forks (like Dino) have implemented this protocol.

Additional context
Using: Siskin IM 7.3.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant