-
-
Notifications
You must be signed in to change notification settings - Fork 79
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
Add a way to import peer public keys from .asc
files
#5698
Comments
isn't our vcard implementation, containing public keys, better than to invent another thing with commands etc? i did not follow previous discussions on that topic, however. did they take place? usually, we aim to agree with some devs before considering an enhancement, esp. the "self-assignment" looks as if that is already started :) |
The reason is that people often publish their PGP keys in
Not sure, but i think i'm not the only one. I had this problem only a couple of times before and used TB or K-9 to send an encrypted message. Quite annoying anyway |
Yesterday's user question btw: https://chaos.social/@waldschnecke/112647668730208369
|
Sometimes it happens to me that i need to message some new contact having their PGP key, but i can't do that with Delta Chat because there's no way to import a key from a file. (Btw, maybe i mistake and there IS a way? This doesn't look like i want smth uncommon.) Auto-importing keys from incoming messages was implemented quite a long ago, so i suggest to do the same from outgoing messages sent to the self-chat, e.g. you send a message
/deltachat-import EMAIL@ADDR
with a.asc
file attached and that's it. The/deltachat-
prefix here is to avoid triggering this logic occasionally. The email address is better to be specified explicitly, sometimes PGP keys have several uids/addresses and creating peerstates for them all may be redundant, and anyway then you should choose one of them. Then you can click on the email address in the sent message and start chatting. So, no need to even auto-create a contact. You can check that the key is imported successfully in the "Encryption Info" context menu as usual. Maybe all this sounds not user-friendly, but this solves the problem entirely in Core and actually is an advanced feature anyway. Also #5678 adds a way to replace the maps integration by sending a webxdc to the self-chat, so it looks somewhat similar UX-wise.The text was updated successfully, but these errors were encountered: