mirror of
https://github.com/cypht-org/cypht.git
synced 2026-04-25 04:56:03 +03:00
[GH-ISSUE #241] Autocrypt support #202
Labels
No labels
2fa
I18N
PGP
Security
Security
account
advanced_search
advanced_search
announcement
api_login
authentication
awaiting feedback
blocker
bug
bug
bug
calendar
config
contacts
core
core
devops
docker
docs
duplicate
dynamic_login
enhancement
epic
feature
feeds
framework
github
github
gmail_contacts
good first issue
help wanted
history
history
imap
imap_folders
inline_message
installation
keyboard_shortcuts
keyboard_shortcuts
ldap_contacts
mobile
need-ssh-access
new module set
nux
pop3
profiles
pull-request
question
refactor
release
research
saved_searches
smtp
strategic
tags
tests
themes
website
wordpress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cypht#202
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
@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.
@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!
@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
@marclaporte commented on GitHub (Nov 5, 2022):
Work in progress: https://github.com/jasonmunro/cypht/pull/652
@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!