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

What happens when seeing a new Autocrypt key for a verified contact? #32

Closed
azul opened this issue Apr 25, 2018 · 1 comment · Fixed by #79
Closed

What happens when seeing a new Autocrypt key for a verified contact? #32

azul opened this issue Apr 25, 2018 · 1 comment · Fixed by #79

Comments

@azul
Copy link
Member

azul commented Apr 25, 2018

I assume we still use the latest keys we see. If a new Autocrypt key shows up after the verification it would be used and remove the verified contact checkmark. Or is the verification 'sticky'? Is there a warning?
I don't think we have specified this yet.

@hpk42
Copy link
Collaborator

hpk42 commented May 2, 2018

In verified groups and verified 1:1 chats the verified key is to be used no matter if there are new opportunistic autocrypt keys. Delta's default channel is opportunistic, though. If you don't explicitely ask for a verified chat then autocrypt logic will be applied (new keys overriding the old). There are all kinds of UI considerations around this ... not sure we need to discuss them here in the countermitm repo.

azul added a commit that referenced this issue Nov 6, 2018
fixes #32.

Treat verified contacts as two people groups.

This is what delta.chat does in its UI.
Also clearly separates the considerations about verified keys
from the discussion of opportunistic keys.
@hpk42 hpk42 closed this as completed in #79 Nov 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants