[GH-ISSUE #241] Autocrypt support #202

Open
opened 2026-02-25 21:34:25 +03:00 by kerem · 5 comments
Owner

Originally created by @BuZZ-dEE on GitHub (Dec 22, 2017).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/241

Originally assigned to: @IrAlfred on GitHub.

Hi there, is Cypht planning to follow the path of other mail clients and implement Autocrypt? Seems like most major clients are planning on releasing support for it soon (K9, Thunderbird, Mailpile). Would be nice if Cypht follows and stays compatible.

Originally created by @BuZZ-dEE on GitHub (Dec 22, 2017). Original GitHub issue: https://github.com/cypht-org/cypht/issues/241 Originally assigned to: @IrAlfred on GitHub. Hi there, is Cypht planning to follow the path of other mail clients and implement [Autocrypt](https://autocrypt.org/)? Seems like most major clients are planning on releasing support for it soon (K9, Thunderbird, Mailpile). Would be nice if Cypht follows and stays compatible.
Author
Owner

@dumblob commented on GitHub (Dec 22, 2017):

It's very fresh and there is no RFC, not even the intent to submit one is to be found. But I really like the idea and after reading just a few posts and issues I'm confident the very few authors and contributors to Autocrypt are enough knowledgeable persons to make it happen.

So I'd suggest considering support for Autocrypt as a standardized opportunistic and extremely user-friendly end-to-end encryption in Cypht.

<!-- gh-comment-id:353614011 --> @dumblob commented on GitHub (Dec 22, 2017): It's very fresh and there is no RFC, not even the intent to submit one is to be found. But I really like the idea and after reading just a few posts and issues I'm confident the very few authors and contributors to Autocrypt are enough knowledgeable persons to make it happen. So I'd suggest considering support for Autocrypt as a standardized opportunistic and extremely user-friendly end-to-end encryption in Cypht.
Author
Owner

@jasonmunro commented on GitHub (Dec 22, 2017):

I skimmed the Level 1 doc here: https://autocrypt.org/level1.html Looks interesting. My take is this specification is more about key management and the ability to opt in to encrypted conversations without having deal with the keys yourself. The end result of using autocrypt is a standard PGP signed/encrypted message body. Just like with PGP support, one issue here is safely storing the private keys, since Cypht is generally hosted on a server. (The PGP module, assuming I ever get the time to get back to it, never lets the private key leave the user's device, all the encryption/signing is done in javascript).

Anyway, it's a neat idea, thanks @BuZZ-dEE for the suggestion. When I can, I will dig into the spec more and see what we can do!

<!-- gh-comment-id:353645765 --> @jasonmunro commented on GitHub (Dec 22, 2017): I skimmed the Level 1 doc here: https://autocrypt.org/level1.html Looks interesting. My take is this specification is more about key management and the ability to opt in to encrypted conversations without having deal with the keys yourself. The end result of using autocrypt is a standard PGP signed/encrypted message body. Just like with PGP support, one issue here is safely storing the private keys, since Cypht is generally hosted on a server. (The PGP module, assuming I ever get the time to get back to it, never lets the private key leave the user's device, all the encryption/signing is done in javascript). Anyway, it's a neat idea, thanks @BuZZ-dEE for the suggestion. When I can, I will dig into the spec more and see what we can do!
Author
Owner

@marclaporte commented on GitHub (Oct 7, 2022):

Autocrypt support is coming to Cypht.

Once it lands, we should test with the bot and get listed here:
https://autocrypt.org/dev-status.html

<!-- gh-comment-id:1271847710 --> @marclaporte commented on GitHub (Oct 7, 2022): Autocrypt support is coming to Cypht. Once it lands, we should test with the bot and get listed here: https://autocrypt.org/dev-status.html
Author
Owner

@marclaporte commented on GitHub (Nov 5, 2022):

Work in progress: https://github.com/jasonmunro/cypht/pull/652

<!-- gh-comment-id:1304399973 --> @marclaporte commented on GitHub (Nov 5, 2022): Work in progress: https://github.com/jasonmunro/cypht/pull/652
Author
Owner

@marclaporte commented on GitHub (May 3, 2024):

@henrique-borba is no longer available to complete the work on https://github.com/cypht-org/cypht/pull/652

We are looking for a volunteer to step up!

<!-- gh-comment-id:2091972574 --> @marclaporte commented on GitHub (May 3, 2024): @henrique-borba is no longer available to complete the work on https://github.com/cypht-org/cypht/pull/652 We are looking for a volunteer to step up!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/cypht#202
No description provided.