mirror of
https://github.com/ArcaneChat/android.git
synced 2026-07-03 14:05:24 +02:00
update local help
This commit is contained in:
@@ -36,27 +36,23 @@
|
||||
<li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#encryption-and-security">Encryption and Security</a>
|
||||
<li><a href="#e2ee">Encryption and Security</a>
|
||||
<ul>
|
||||
<li><a href="#which-standards-are-used-for-end-to-end-encryption">Which standards are used for end-to-end encryption?</a></li>
|
||||
<li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I get guaranteed end-to-end encryption and green checkmarks?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark and “guaranteed end-to-end encryption” mean?</a></li>
|
||||
<li><a href="#nocryptanymore">A contact “sent a message from another device”, what can i do?</a></li>
|
||||
<li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
|
||||
<li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li>
|
||||
<li><a href="#openpgp-secure">Is OpenPGP secure?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end -encryption?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
|
||||
<li><a href="#is-delta-chat-vulnerable-to-efail">Is Delta Chat vulnerable to EFAIL?</a></li>
|
||||
<li><a href="#tls">Is a message exposed in cleartext if end-to-end encryption is not available?</a></li>
|
||||
<li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
|
||||
<li><a href="#message-metadata">How does Delta Chat protect metadata in messages?</a></li>
|
||||
<li><a href="#device-seizure">How to protect metadata and contacts when a device is seized?</a></li>
|
||||
<li><a href="#how-can-i-check-encryption-information">How can i check encryption information?</a></li>
|
||||
<li><a href="#how-can-i-check-the-encryption-status-of-messages">How can I check the encryption status of messages?</a></li>
|
||||
<li><a href="#why-do-i-see-unencrypted-messages">Why do I see unencrypted messages?</a></li>
|
||||
<li><a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app?</a></li>
|
||||
<li><a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion">How can I ensure message end-to-end encryption and deletion?</a></li>
|
||||
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
|
||||
<li><a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">Is end-to-end encryption of Delta Chat as safe as Signal?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#importkey">Lze znovu použít můj stávající soukromý klíč?</a></li>
|
||||
<li><a href="#security-audits">Was Delta Chat independently audited for security vulnerabilities?</a></li>
|
||||
</ul>
|
||||
@@ -722,10 +718,10 @@ that achieves “instant delivery” of messages for all chatmail servers
|
||||
including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>.
|
||||
Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p>
|
||||
|
||||
<h2 id="encryption-and-security">
|
||||
<h2 id="e2ee">
|
||||
|
||||
|
||||
Encryption and Security <a href="#encryption-and-security" class="anchor"></a>
|
||||
Encryption and Security <a href="#e2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h2>
|
||||
@@ -738,18 +734,26 @@ Welcome to the power of the interoperable and massive chatmail and e-mail system
|
||||
|
||||
</h3>
|
||||
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption with contacts and group chats.
|
||||
Autocrypt uses a limited and <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>.
|
||||
End-to-End encrypted messages are marked with a padlock
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
|
||||
<p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
|
||||
to provide automatic end-to-end encryption using these protocols:</p>
|
||||
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
|
||||
are used for establishing chats with guaranteed end-to-end encryption
|
||||
which protects against network attacks and compromised servers.
|
||||
Chats marked with a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
guarantee end-to-end encrypted messages.</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
|
||||
to exchange encryption setup information through QR-code scanning or “invite links”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption between contacts and all members of a group chat.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
|
||||
chat</a>
|
||||
enables receivers to use end-to-end encryption with the contact.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
|
||||
|
||||
<h3 id="whene2e">
|
||||
|
||||
@@ -759,28 +763,37 @@ guarantee end-to-end encrypted messages.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>All end-to-end encrypted messages carry a padlock:</p>
|
||||
|
||||
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p>
|
||||
|
||||
<p>End-to-end encryption is guaranteed if there is a green checkmark next to the chat title:</p>
|
||||
|
||||
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
|
||||
<p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
|
||||
Since the Delta Chat Version 2 release series (July 2025)
|
||||
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
<h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
|
||||
|
||||
|
||||
How can I get guaranteed end-to-end encryption and green checkmarks? <a href="#howtoe2ee" class="anchor"></a>
|
||||
Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If you have a second communication channel with your chat partner,
|
||||
like a video chat or a different messenger,
|
||||
you can generate an invite link.</p>
|
||||
<p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
|
||||
it is impossible to receive or send messages without end-to-end encryption.</p>
|
||||
|
||||
<p>If you are together in person,
|
||||
you can show a QR code to your chat partner.</p>
|
||||
<p>If you instead create a profile using a classic e-mail server,
|
||||
you can send and receive messages without end-to-end encryption.
|
||||
Such messages lacking end-to-end encryption are marked with an e-mail icon
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
|
||||
|
||||
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You can send an invite link through another private chat,
|
||||
show an invitation QR code when next to each other or in a video call,
|
||||
or click on a “contact” that was shared in a chat.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
@@ -789,141 +802,60 @@ tap the chat group title to see its member list,
|
||||
and select “QR Invite code”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
tap the QR Code icon <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
|
||||
on the Delta Chat app main screen.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Let your chat partner scan the QR image
|
||||
<p>Ask your chat partner to scan the QR image
|
||||
with their Delta Chat app,
|
||||
or click “Copy” or “Share” to create an invite link
|
||||
and share it with your chat partner.</p>
|
||||
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">Secure-Join network messages are exchanged</a> between both devices.</p>
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>If both devices are online,
|
||||
both sides will eventually see a (group or direct) chat with a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
next to the title.</p>
|
||||
<p>If both sides are online, they will soon see a (group or direct) chat
|
||||
and can start messaging securely.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>If one of the devices is offline, the green checkmarks will only
|
||||
appear later when the device is internet-connected again
|
||||
and the Secure-Join network protocol completed.</p>
|
||||
<p>If one side is offline or in bad network,
|
||||
the ability to chat is delayed until connectivity is restored.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Congratulations!
|
||||
You now will automatically use guaranteed end-to-end encryption
|
||||
with this contact and both of you can add each other to green-checkmarked groups
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />,
|
||||
thereby automatically spreading guaranteed end-to-end encryption among its members.</p>
|
||||
You now will automatically use end-to-end encryption
|
||||
with this contact.
|
||||
If you add each other to chat groups,
|
||||
end-to-end encryption will be established among all members.</p>
|
||||
|
||||
<h3 id="e2eeguarantee">
|
||||
|
||||
|
||||
What does the green checkmark and “guaranteed end-to-end encryption” mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Chat titles with green checkmarks
|
||||
<p>A contact profile might show a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
mean that all messages in the chat will be end-to-end encrypted
|
||||
and can not be read or altered by compromised e-mail servers or Internet providers.
|
||||
Joining green-checkmarked group chats
|
||||
safely spreads everybody’s encryption information (and green checkmarks)
|
||||
in a manner that guarantees end-to-end encryption in the group and among members.</p>
|
||||
|
||||
<p>Contact profiles with green checkmarks
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
mean that messaging a contact is currently guaranteed to be end-to-end encrypted.
|
||||
and an “Introduced by” line.
|
||||
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
|
||||
or was introduced by a another green-checkmarked contact.
|
||||
Introductions happen automatically when adding members to groups.
|
||||
Whoever adds a contact to a green-checkmarked group becomes an introducer
|
||||
to those members who didn’t yet know about the added contact.
|
||||
Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
|
||||
becomes an introducer.
|
||||
In a contact profile you can tap on the “Introduced by …” text repeatedly
|
||||
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
|
||||
|
||||
<p>Note that in a contact profile you may see and tap introducers
|
||||
but there is no green checkmark in the profile title.
|
||||
This usually means that the contact <a href="#nocryptanymore">“sent a message from another device”</a>.</p>
|
||||
|
||||
<p>For more in-depth discussion of “guaranteed end-to-end encryption”
|
||||
please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
|
||||
and specifically read about “Verified Groups”, the technical term
|
||||
of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p>
|
||||
|
||||
<h3 id="nocryptanymore">
|
||||
|
||||
|
||||
A contact “sent a message from another device”, what can i do? <a href="#nocryptanymore" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Your chat with a contact lost guaranteed end-to-end encryption.
|
||||
The green checkmark was removed for this chat and contact when you see this warning.
|
||||
<strong>If you find the sudden drop of guaranteed end-to-end encryption
|
||||
surprising for this contact then don’t accept the warning!</strong>
|
||||
Instead check with your contact through a second channel
|
||||
like a video call, other messenger or a phone call,
|
||||
to find out what happened.</p>
|
||||
|
||||
<p>If your contact actually caused the drop of guaranteed end-to-end encryption
|
||||
please see the next paragraphs for common reasons and their mitigations.
|
||||
Regardless, all other green-checkmarked chats remain guaranteed end-to-end encrypted
|
||||
even if the contact is a member there.</p>
|
||||
|
||||
<p><strong>Your contact is using Delta Chat on a second device (phone or laptop)</strong></p>
|
||||
|
||||
<p>If they have another device with a Delta Chat app running,
|
||||
they should remove the profile from the new device
|
||||
and add it <a href="#multiclient">as a second device as described here</a>.
|
||||
As soon as they message you afterwards, the warning will be gone
|
||||
and guaranteed encryption is established with both devices of your contact.</p>
|
||||
|
||||
<p><strong>Your contact reinstalled Delta Chat using their old account login</strong></p>
|
||||
|
||||
<p>If they have <a href="#backup">a backup file</a>,
|
||||
they should remove the profile from the new device
|
||||
and rather import the backup file to re-create their profile.
|
||||
As soon as they message you afterwards, the warning will be gone
|
||||
and guaranteed encryption is re-established for this contact.</p>
|
||||
|
||||
<p>If they don’t have a backup file, it’s best to perform a <a href="#howtoe2ee">QR scan</a>
|
||||
with your chat partner to re-establish guaranteed end-to-end encryption.</p>
|
||||
|
||||
<p><strong>Your contact sent a mail through a webmail interface or another e-mail app
|
||||
and will get back to using Delta Chat soon again.</strong></p>
|
||||
|
||||
<p>If you are sure that the contact sometimes uses webmail,
|
||||
or another mail app lacking end-to-end encryption,
|
||||
then you may accept the warning.
|
||||
As soon as your contact uses Delta Chat again,
|
||||
guaranteed end-to-end encryption will be automatically re-established.</p>
|
||||
|
||||
<p><strong>Your contact stopped using Delta Chat entirely</strong></p>
|
||||
|
||||
<p>Sometimes remaining in contact is more important than end-to-end encryption.
|
||||
<a href="#tls">“Transport Layer Encryption” (TLS)</a> may still meaningfully protect
|
||||
the confidentiality of your messages between your device and the e-mail server.
|
||||
But without end-to-end encryption you and your contact are trusting your e-mail server
|
||||
to not read or manipulate your messages, and to not hand them to third parties.</p>
|
||||
|
||||
<p>In any case, you can not do much else than accept the warning.
|
||||
Please also remove the contact from any active green-checkmarked group
|
||||
which you can find in “Chats in Common” in the Contact profile.
|
||||
This spares your contact from getting “unreadable” messages.</p>
|
||||
|
||||
<p>If the contact removed Delta Chat because of buggy or undesirable behaviour,
|
||||
please consider posting to our <a href="https://support.delta.chat">support forum</a>
|
||||
to help us identify and address common problems. Thanks!</p>
|
||||
|
||||
<h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted">
|
||||
|
||||
|
||||
@@ -948,8 +880,7 @@ and attachment metadata such as filenames.</p>
|
||||
</h3>
|
||||
|
||||
<p>Yes, Delta Chat uses a secure subset of OpenPGP
|
||||
and only displays a padlock security indicator on a message
|
||||
if the whole message is properly encrypted and signed.
|
||||
requiring the whole message to be properly encrypted and signed.
|
||||
For example, “Detached signatures” are not treated as secure.</p>
|
||||
|
||||
<p>OpenPGP is not insecure by itself.
|
||||
@@ -970,7 +901,7 @@ which was thankfully adopted in summer 2023.</p>
|
||||
<h3 id="openpgp-alternatives">
|
||||
|
||||
|
||||
Did you consider using alternatives to OpenPGP for end-to-end -encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -1013,17 +944,15 @@ as defined by the Autocrypt Level 1 specification.</p>
|
||||
<h3 id="tls">
|
||||
|
||||
|
||||
Is a message exposed in cleartext if end-to-end encryption is not available? <a href="#tls" class="anchor"></a>
|
||||
Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Even if your messages are not guaranteed to be end-to-end encrypted,
|
||||
they are still protected from Internet providers like cell or cable companies.
|
||||
However, your and your recipient’s e-mail providers
|
||||
may read, analyze or even modify your messages,
|
||||
including any attachments,
|
||||
if they are not end-to-end encrypted.</p>
|
||||
<p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
|
||||
they are still protected from cell or cable companies who can not read or modify your e-mail messages.
|
||||
But both your and your recipient’s e-mail providers
|
||||
may read, analyze or modify your messages, including any attachments.</p>
|
||||
|
||||
<p>Delta Chat by default uses strict
|
||||
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a>
|
||||
@@ -1035,10 +964,6 @@ If the involved e-mail servers support <a href="https://datatracker.ietf.org/doc
|
||||
then transport encryption will be enforced between e-mail providers
|
||||
in which case Delta Chat communications will never be exposed in cleartext to the Internet
|
||||
even if the message was not end-to-end encrypted.</p>
|
||||
|
||||
<p>Note that <a href="#howtoe2ee">maintaining guaranteed end-to-end encryption</a> on top of TLS encryption
|
||||
provides pervasive safety between your and the recipient’s devices.
|
||||
Not even your e-mail or Internet provider will be able to read or modify your messages.</p>
|
||||
|
||||
<h3 id="message-metadata">
|
||||
|
||||
@@ -1101,74 +1026,6 @@ Delta Chat shows two fingerprints there.
|
||||
If the same fingerprints appear on your own and your contact’s device,
|
||||
the connection is safe.</p>
|
||||
|
||||
<h3 id="how-can-i-check-the-encryption-status-of-messages">
|
||||
|
||||
|
||||
How can I check the encryption status of messages? <a href="#how-can-i-check-the-encryption-status-of-messages" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>A little <strong>padlock</strong> in a message bubble denotes
|
||||
that the message was properly end-to-end encrypted from the given sender.
|
||||
If there is <strong>no padlock</strong>, the message was not properly end-to-end encrypted
|
||||
most likely because the sender uses an app or webmail interface
|
||||
without support for end-to-end–encryption.</p>
|
||||
|
||||
<h3 id="why-do-i-see-unencrypted-messages">
|
||||
|
||||
|
||||
Why do I see unencrypted messages? <a href="#why-do-i-see-unencrypted-messages" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If a contact uses a non-Autocrypt e-mail app,
|
||||
all messages involving this contact (in a group or 1:1 chat)
|
||||
will not be end-to-end encrypted, and thus not show a “padlock” with messages.
|
||||
Note that even if your contacts use Delta Chat on their account,
|
||||
they might also use a non-Autocrypt e-mail app on that account
|
||||
which then may cause intermittently unencrypted messages.
|
||||
Replying unencrypted to unencrypted messages is mandated by Autocrypt
|
||||
to prevent unreadable messages on the side of your contacts
|
||||
and their non-Autocrypt e-mail app.</p>
|
||||
|
||||
<h3 id="how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">
|
||||
|
||||
|
||||
How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app? <a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If you need a safely end-to-end encrypted chat with a contact
|
||||
who is using their e-mail account both with Delta Chat and non-Autocrypt apps (e.g. webmail),
|
||||
it’s best to setup <a href="#howtoe2ee">guaranteed end-to-end encryption with them</a>
|
||||
and then create a guaranteed end-to-end encrypted group chat with you two as members.
|
||||
In this group chat all messages will be end-to-end encrypted
|
||||
even if the direct chat between you two has a
|
||||
<a href="#nocryptanymore">“… sent a message from another device”</a> warning.</p>
|
||||
|
||||
<h3 id="how-can-i-ensure-message-end-to-end-encryption-and-deletion">
|
||||
|
||||
|
||||
How can I ensure message end-to-end encryption and deletion? <a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>The best way to ensure every message is end-to-end encrypted,
|
||||
and metadata deleted as quickly as possible
|
||||
is <a href="#howtoe2ee">using chats with guaranteed end-to-end encryption</a>
|
||||
and turning on <a href="#ephemeralmsgs">disappearing messages</a>.</p>
|
||||
|
||||
<p>Guaranteed end-to-end encrypted chats protect against <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM attacks</a>
|
||||
and turning on disappearing messages deletes the messages
|
||||
on the server after a user-configured time.</p>
|
||||
|
||||
<p>If you don’t need a longer-lived copy of your messages on the server,
|
||||
you can also turn on <a href="#delold">“delete messages from server automatically”</a>.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
|
||||
@@ -1177,45 +1034,35 @@ you can also turn on <a href="#delold">“delete messages from server automatica
|
||||
|
||||
</h3>
|
||||
|
||||
<p>No, Delta Chat doesn’t support Perfect Forward Secrecy (PFS).
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
|
||||
This means that if your Delta Chat private decryption key is leaked,
|
||||
and someone has collected your prior in-transit messages,
|
||||
they will be able to decrypt and read them using the leaked decryption key.</p>
|
||||
|
||||
<p>Note, however, that if anyone obtains to your decryption keys,
|
||||
they will typically also be able to obtain your messages,
|
||||
irrespective if Perfect Forward Secrecy is in place or not.
|
||||
The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
<p>Note however, that Forward Secrecy only increases your security
|
||||
if you delete messages or use ephemeral deletion timers.
|
||||
Otherwise, if anyone obtains your decryption keys,
|
||||
they are typically also able to get all your non-deleted messages
|
||||
and don’t need to decrypt any previously collected messages.</p>
|
||||
|
||||
<p>It is possible that Delta Chat evolves to support Perfect Forward Secrecy,
|
||||
because OpenPGP is just a container for encrypted messages
|
||||
but encryption key management (and thus key rotation or key “ratcheting”)
|
||||
could be organized in flexible ways.
|
||||
See <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouia’s PFS prototype</a>
|
||||
for existing experiments in the OpenPGP implementor community.</p>
|
||||
<p>The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we also discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
|
||||
<h3 id="is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
|
||||
|
||||
Is end-to-end encryption of Delta Chat as safe as Signal? <a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal" class="anchor"></a>
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>It depends on what is important to you.
|
||||
Delta Chat <a href="#pfs">does not support PFS</a> like Signal does
|
||||
but it provides <a href="#e2eeguarantee">guaranteed end-to-end encrypted chats</a>
|
||||
that are safe against compromised servers or corrupted networks.
|
||||
Signal and most other PFS-supporting messengers do not provide
|
||||
a practical scheme for protecting chat groups from network attacks
|
||||
which are arguably more worrisome
|
||||
than a potential attacker who seizes your phone and private encryption setup
|
||||
but somehow not your messages, yet has a full record of all
|
||||
past encrypted messages.</p>
|
||||
<p>Yes.</p>
|
||||
|
||||
<p>In any case, Delta Chat’s end-to-end encryption uses a <a href="#openpgp-secure">secure subset of OpenPGP</a>
|
||||
which has been <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">independently security-audited</a>.</p>
|
||||
<p>We devised a forward secrecy scheme that withstood initial scrutiny from cryptographers and usable security experts.
|
||||
Our tentative scheme is designed to reliably work in federated messaging networks and with multi-device usage.
|
||||
However, an implementation has not been scheduled yet (as of Mid 2025).</p>
|
||||
|
||||
<h3 id="importkey">
|
||||
|
||||
@@ -1250,7 +1097,7 @@ from most recent to older:</p>
|
||||
<li>
|
||||
<p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of
|
||||
rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place.
|
||||
rPGP serves as the end-to-end encyption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
|
||||
rPGP serves as the end-to-end encryption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
|
||||
Two advisories were released related to the findings of this audit:</p>
|
||||
|
||||
<ul>
|
||||
@@ -1643,6 +1490,11 @@ DeltaChat. To je něco co za běžných okolností dělá Delta Chat sám.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Note:
|
||||
Changing email addresses is temporarily disabled
|
||||
because of ongoing changes to the DeltaChat core.
|
||||
It should be available again in a few months.</p>
|
||||
|
||||
<ol>
|
||||
<li>
|
||||
<p>Change your address in “Settings → Advanced → Password and Account” and
|
||||
|
||||
+111
-242
@@ -36,27 +36,23 @@
|
||||
<li><a href="#warum-integriert-sich-delta-chat-in-zentralisierte-proprietäre-applegoogle-push-dienste">Warum integriert sich Delta Chat in zentralisierte, proprietäre Apple/Google-Push-Dienste?</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#verschlüsselung-und-sicherheit">Verschlüsselung und Sicherheit</a>
|
||||
<li><a href="#e2ee">Verschlüsselung und Sicherheit</a>
|
||||
<ul>
|
||||
<li><a href="#welche-standards-werden-für-die-ende-zu-ende-verschlüsselung-verwendet">Welche Standards werden für die Ende-zu-Ende-Verschlüsselung verwendet?</a></li>
|
||||
<li><a href="#whene2e">Wie kann ich wissen, ob Nachrichten Ende-zu-Ende-verschlüsselt sind?</a></li>
|
||||
<li><a href="#howtoe2ee">Wie kann ich garantierte Ende-zu-Ende-Verschlüsselung und grüne Häkchen erhalten?</a></li>
|
||||
<li><a href="#e2eeguarantee">Was bedeuten das “Grüne Häkchen” und die “garantierte Ende-zu-Ende-Verschlüsselung”?</a></li>
|
||||
<li><a href="#nocryptanymore">Ein Kontakt hat eine Nachricht von einem anderen Gerät gesendet”, was kann ich tun?</a></li>
|
||||
<li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
|
||||
<li><a href="#sind-anhänge-bilder-dateien-audio-usw-ende-zu-ende-verschlüsselt">Sind Anhänge (Bilder, Dateien, Audio usw.) Ende-zu-Ende-verschlüsselt?</a></li>
|
||||
<li><a href="#openpgp-secure">Ist OpenPGP sicher?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Wurden Alternativen zu OpenPGP für die Ende-zu-Ende-Verschlüsselung in Betracht gezogen?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
|
||||
<li><a href="#ist-delta-chat-anfällig-für-efail">Ist Delta Chat anfällig für EFAIL?</a></li>
|
||||
<li><a href="#tls">Wird eine Nachricht im Klartext gesendet, wenn keine Ende-zu-Ende-Verschlüsselung verfügbar ist?</a></li>
|
||||
<li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
|
||||
<li><a href="#message-metadata">Wie schützt Delta Chat Metadaten in Nachrichten?</a></li>
|
||||
<li><a href="#device-seizure">Wie schützt man Metadaten und Kontakte, wenn ein Gerät beschlagnahmt wird?</a></li>
|
||||
<li><a href="#wie-kann-ich-die-verschlüsselungsinformationen-überprüfen">Wie kann ich die Verschlüsselungsinformationen überprüfen?</a></li>
|
||||
<li><a href="#wie-kann-ich-den-verschlüsselungsstatus-von-nachrichten-überprüfen">Wie kann ich den Verschlüsselungsstatus von Nachrichten überprüfen?</a></li>
|
||||
<li><a href="#warum-sehe-ich-unverschlüsselte-nachrichten">Warum sehe ich unverschlüsselte Nachrichten?</a></li>
|
||||
<li><a href="#wie-kann-ich-einen-ende-zu-ende-verschlüsselten-chat-mit-einem-delta-chat-kontakt-führen-der-manchmal-webmail-oder-eine-andere-e-mail-anwendung-ohne-autocrypt-verwendet">Wie kann ich einen Ende-zu-Ende-verschlüsselten Chat mit einem Delta-Chat-Kontakt führen, der manchmal Webmail oder eine andere E-Mail-Anwendung ohne Autocrypt verwendet?</a></li>
|
||||
<li><a href="#wie-kann-ich-ende-zu-ende-verschlüsselung-und-löschen-von-nachrichten-sicherstellen">Wie kann ich Ende-zu-Ende-Verschlüsselung und Löschen von Nachrichten sicherstellen?</a></li>
|
||||
<li><a href="#pfs">Unterstützt Delta Chat “Perfect Forward Secrecy”?</a></li>
|
||||
<li><a href="#ist-die-ende-zu-ende-verschlüsselung-von-delta-chat-genauso-sicher-wie-die-von-signal">Ist die Ende-zu-Ende-Verschlüsselung von Delta Chat genauso sicher wie die von Signal?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#importkey">Kann ich meinen existierenden privaten Schlüssel weiter verwenden?</a></li>
|
||||
<li><a href="#security-audits">Wurde Delta Chat unabhängig auf Sicherheitslücken geprüft?</a></li>
|
||||
</ul>
|
||||
@@ -681,10 +677,10 @@ hat, das eine „sofortige Zustellung“ von Nachrichten für alle Chatmail-Serv
|
||||
Einschließlich dem Chatmail-Server, <a href="https://delta.chat/chatmail#selfhosted">den Sie selbst ohne unsere Erlaubnis einrichten könnten</a>.
|
||||
Willkommen bei der Macht des interoperablen und massiven Chatmail- und E-Mail-Systems :)</p>
|
||||
|
||||
<h2 id="verschlüsselung-und-sicherheit">
|
||||
<h2 id="e2ee">
|
||||
|
||||
|
||||
Verschlüsselung und Sicherheit <a href="#verschlüsselung-und-sicherheit" class="anchor"></a>
|
||||
Verschlüsselung und Sicherheit <a href="#e2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h2>
|
||||
@@ -697,17 +693,26 @@ Willkommen bei der Macht des interoperablen und massiven Chatmail- und E-Mail-Sy
|
||||
|
||||
</h3>
|
||||
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> wird verwendet, um automatisch
|
||||
eine Ende-zu-Ende-Verschlüsselung mit Kontakten und Gruppenchats herzustellen.
|
||||
Autocrypt verwendet eine begrenzte und <a href="#openpgp-secure">sichere Untermenge des OpenPGP-Standards</a>.
|
||||
Ende-zu-Ende-verschlüsselte Nachrichten sind mit einem Vorhängeschloss gekennzeichnet <img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" /></p>
|
||||
<p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
|
||||
to provide automatic end-to-end encryption using these protocols:</p>
|
||||
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join-Protokolle</a>
|
||||
werden für Chats mit garantierter Ende-zu-Ende-Verschlüsselung verwendet,
|
||||
die vor Netzwerkangriffen und kompromittierten Servern schützt.
|
||||
Chats, die mit einem grünen Häkchen markiert sind
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
garantieren Ende-zu-Ende-verschlüsselte Nachrichten.</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
|
||||
to exchange encryption setup information through QR-code scanning or “invite links”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption between contacts and all members of a group chat.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
|
||||
chat</a>
|
||||
enables receivers to use end-to-end encryption with the contact.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
|
||||
|
||||
<h3 id="whene2e">
|
||||
|
||||
@@ -717,28 +722,37 @@ garantieren Ende-zu-Ende-verschlüsselte Nachrichten.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Ende-zu-Ende-verschlüsselten Nachrichten sind mit einem Vorhängeschloss versehen:</p>
|
||||
|
||||
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p>
|
||||
|
||||
<p>Die Ende-zu-Ende-Verschlüsselung ist garantiert, wenn neben dem Chat-Titel ein grünes Häkchen zu sehen ist:</p>
|
||||
|
||||
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
|
||||
<p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
|
||||
Since the Delta Chat Version 2 release series (July 2025)
|
||||
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
<h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
|
||||
|
||||
|
||||
Wie kann ich garantierte Ende-zu-Ende-Verschlüsselung und grüne Häkchen erhalten? <a href="#howtoe2ee" class="anchor"></a>
|
||||
Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Wenn Sie einen zweiten Kommunikationskanal mit Ihrem Chatpartner haben,
|
||||
wie einen Video-Chat oder einen anderen Messenger,
|
||||
können Sie einen Einladungslink erstellen.</p>
|
||||
<p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
|
||||
it is impossible to receive or send messages without end-to-end encryption.</p>
|
||||
|
||||
<p>Wenn Sie persönlich zusammen sind,
|
||||
können Sie Ihrem Chat-Partner einen QR-Code zeigen.</p>
|
||||
<p>If you instead create a profile using a classic e-mail server,
|
||||
you can send and receive messages without end-to-end encryption.
|
||||
Such messages lacking end-to-end encryption are marked with an e-mail icon
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
|
||||
|
||||
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You can send an invite link through another private chat,
|
||||
show an invitation QR code when next to each other or in a video call,
|
||||
or click on a “contact” that was shared in a chat.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
@@ -747,133 +761,60 @@ tippen Sie auf den Titel der Gruppe, um die Mitgliederliste anzuzeigen,
|
||||
und wählen Sie „QR-Einladungscode“.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Für <strong>Direktchat-Einladungen</strong>,
|
||||
tippen Sie auf das QR-Code-Symbol <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
|
||||
auf dem Hauptbildschirm der Delta-Chat-App.</p>
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
tap the QR Code icon <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
|
||||
on the Delta Chat app main screen.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Lassen Sie Ihren Chat-Partner den QR-Code mit der Delta-Chat-App scannen.
|
||||
Oder Sie klicken auf „Kopieren“ oder „Teilen“, um einen Einladungslink zu erstellen und diesen mit Ihrem Chat-Partner zu teilen.</p>
|
||||
<p>Ask your chat partner to scan the QR image
|
||||
with their Delta Chat app,
|
||||
or click “Copy” or “Share” to create an invite link
|
||||
and share it with your chat partner.</p>
|
||||
|
||||
<p>Warten Sie nun, während das <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">Secure-Join-Protokoll</a> zwischen beiden Geräten abläuft.</p>
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>Wenn beide Geräte online sind,
|
||||
sehen beide Seiten schließlich einen Gruppen- oder Direkt-Chat mit einem grünen Häkchen
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
neben dem Titel.</p>
|
||||
<p>If both sides are online, they will soon see a (group or direct) chat
|
||||
and can start messaging securely.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Wenn eines der Geräte offline ist, erscheinen die grünen Häkchen erst
|
||||
später, wenn das Gerät wieder mit dem Internet verbunden ist
|
||||
und das Secure-Join-Protokoll abgeschlossen werden kann.</p>
|
||||
<p>If one side is offline or in bad network,
|
||||
the ability to chat is delayed until connectivity is restored.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Herzlichen Glückwunsch! 🎉
|
||||
Sie verwenden nun eine garantierte Ende-zu-Ende-Verschlüsselung
|
||||
mit diesem Kontakt und Sie beide können sich gegenseitig zu grün markierten Gruppen hinzufügen
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />,
|
||||
Dadurch wird die garantierte Ende-zu-Ende-Verschlüsselung automatisch unter den Mitgliedern dieser Gruppe verbreitet.</p>
|
||||
<p>Congratulations!
|
||||
You now will automatically use end-to-end encryption
|
||||
with this contact.
|
||||
If you add each other to chat groups,
|
||||
end-to-end encryption will be established among all members.</p>
|
||||
|
||||
<h3 id="e2eeguarantee">
|
||||
|
||||
|
||||
Was bedeuten das “Grüne Häkchen” und die “garantierte Ende-zu-Ende-Verschlüsselung”? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p><strong>Chat-Titel mit grünen Häkchen</strong>
|
||||
<p>A contact profile might show a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
bedeuten, dass alle Nachrichten im Chat Ende-zu-Ende-verschlüsselt werden
|
||||
und nicht von kompromittierten E-Mail-Servern oder Internet-Providern gelesen oder verändert werden können.
|
||||
Beim Beitritt zu Gruppenchats mit grünen Häkchen
|
||||
werden Verschlüsselungsinformationen (und die grünen Häkchen) aller Teilnehmer sicher so weitergegeben,
|
||||
dass die Ende-zu-Ende-Verschlüsselung in der Gruppe und zwischen den Mitgliedern garantiert werden kann.</p>
|
||||
|
||||
<p><strong>Kontaktprofile mit grünen Häkchen</strong>
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
bedeuten, dass die Nachrichtenübermittlung an einen Kontakt derzeit garantiert Ende-zu-Ende-verschlüsselt ist.
|
||||
Jeder grün markierte Kontakt hat entweder einen direkten <a href="#howtoe2ee">QR-Scan</a> mit Ihnen durchgeführt
|
||||
oder wurde von einem anderen Kontakt mit grünem Häkchen eingeführt.
|
||||
Das Einführen geschieht automatisch, wenn Sie Mitglieder zu Gruppen hinzufügen.
|
||||
Wer einen Kontakt zu einer Gruppe mit grünem Häkchen hinzufügt, wird zum Einführenden
|
||||
für die Mitglieder, die noch nichts von dem hinzugefügten Kontakt wussten.
|
||||
In einem Kontaktprofil können Sie wiederholt auf den Text “Eingeführt von …” tippen
|
||||
bis Sie zu demjenigen gelangen, mit dem Sie einen direkten <a href="#howtoe2ee">QR-Scan</a> gemacht haben.</p>
|
||||
|
||||
<p>Beachten Sie, dass Sie in einem Kontaktprofil unter Umständen Einführende sehen und antippen können, aber kein grünes Häkchen im Profiltitel vorhanden ist.
|
||||
Dies bedeutet normalerweise, dass der Kontakt <a href="#nocryptanymore">“eine Nachricht von einem anderen Gerät gesendet hat”</a>.</p>
|
||||
and an “Introduced by” line.
|
||||
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
|
||||
or was introduced by a another green-checkmarked contact.
|
||||
Introductions happen automatically when adding members to groups.
|
||||
Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
|
||||
becomes an introducer.
|
||||
In a contact profile you can tap on the “Introduced by …” text repeatedly
|
||||
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
|
||||
|
||||
<p>Für eine ausführlichere Diskussion der “Garantierten Ende-zu-Ende-Verschlüsselung”,
|
||||
siehe <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join-Protokolle</a>
|
||||
und dort speziell den Abschnitt zu “Verified Groups”, dem technischen Begriff
|
||||
für “Chats mit grünem Häkchen” oder “Garantierter Ende-zu-Ende-Verschlüsselung”.</p>
|
||||
|
||||
<h3 id="nocryptanymore">
|
||||
|
||||
|
||||
Ein Kontakt hat eine Nachricht von einem anderen Gerät gesendet”, was kann ich tun? <a href="#nocryptanymore" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Wenn Sie diese Warnung sehen, wurde das grüne Häkchen entfernt, da für den Kontakt die Ende-zu-Ende-Verschlüsselung nicht mehr garantiert werden kann.
|
||||
<strong>Wenn Sie den Wegfall der garantierten Ende-zu-Ende-Verschlüsselung
|
||||
für diesen Kontakt überraschend finden, akzeptieren Sie die Warnung nicht!</strong>
|
||||
Versuchen Sie stattdessen mit Ihrem Kontakt über einen zweiten Kanal (z.B. Videoanruf, Telefon oder ein anderer Messenger) herauszufinden, was passiert ist.</p>
|
||||
|
||||
<p>Wenn Ihr Kontakt tatsächlich den Ausfall der garantierten Ende-zu-Ende-Verschlüsselung verursacht hat,
|
||||
finden Sie in den nächsten Abschnitten häufige Gründe und Abhilfe.
|
||||
Unabhängig davon bleiben alle anderen Chats mit einem grünen Häkchen garantiert Ende-zu-Ende-verschlüsselt,
|
||||
auch wenn der Kontakt dort Mitglied ist.</p>
|
||||
|
||||
<p><strong>Ihr Kontakt verwendet Delta Chat auf einem zweiten Gerät (Smartphone oder Laptop)</strong></p>
|
||||
|
||||
<p>Wenn Ihr Kontakt ein weiteres Gerät mit Delta Chat eingerichtet hat,
|
||||
sollte das Konto von dem neuen Gerät entfernen werden und <a href="#multiclient">als zweites Gerät, wie hier beschrieben</a>, erneut hinzugefügt werden.
|
||||
Sobald sie sich danach schreiben, wird die Warnung verschwinden
|
||||
und die Verschlüsselung ist mit beiden Geräten Ihres Kontakts garantiert.</p>
|
||||
|
||||
<p><strong>Ihr Kontakt hat Delta Chat mit seinem alten Login neu installiert</strong></p>
|
||||
|
||||
<p>Wenn Ihr Kontakt <a href="#backup">ein Backup</a> hat,
|
||||
sollte das Profil auf dem neuen Gerät
|
||||
entfernt werden und stattdessen das Backup importiert werden, um das Konto neu zu erstellen.
|
||||
Sobald sie sich danach schreiben, wird die Warnung verschwinden
|
||||
und die garantierte Verschlüsselung wird für diesen Kontakt wiederhergestellt.</p>
|
||||
|
||||
<p>Wenn Ihr Kontakt kein Backup hat, ist es am besten, einen <a href="#howtoe2ee">QR-Code-Scan</a>
|
||||
mit Ihrem Chat-Partner durchzuführen, um die garantierte Ende-zu-Ende-Verschlüsselung wiederherzustellen.</p>
|
||||
|
||||
<p><strong>Ihr Kontakt hat eine E-Mail über Webmail oder eine andere E-Mail-Anwendung gesendet,
|
||||
wird Delta Chat aber bald wieder benutzen.</strong></p>
|
||||
|
||||
<p>Wenn Sie wissen, dass der Kontakt manchmal Webmail,
|
||||
oder andere E-Mail-Anwendungen ohne Ende-zu-Ende-Verschlüsselung verwendet,
|
||||
dann können Sie die Warnung akzeptieren.
|
||||
Sobald Ihr Kontakt Delta Chat wieder benutzt,
|
||||
wird die garantierte Ende-zu-Ende-Verschlüsselung automatisch wiederhergestellt.</p>
|
||||
|
||||
<p><strong>Ihr Kontakt hat die Nutzung von Delta Chat komplett eingestellt</strong></p>
|
||||
|
||||
<p>Manchmal ist es wichtiger, in Kontakt zu bleiben als eine Ende-zu-Ende-Verschlüsselung zu haben;
|
||||
die <a href="#tls">“Transport Layer Encryption” (TLS)</a> kann die Vertraulichkeit
|
||||
Ihrer Nachrichten zwischen Ihrem Gerät und dem E-Mail-Server dennoch schützen.
|
||||
Ohne Ende-zu-Ende-Verschlüsselung vertrauen Sie und Ihr Chat-Partner jedoch darauf, dass Ihr E-Mail-Server Nachrichten nicht liest oder manipuliert und sie nicht an Dritte weitergibt.</p>
|
||||
|
||||
<p>In jedem Fall können Sie nicht viel mehr tun, als die Warnung zu akzeptieren.
|
||||
Bitte entfernen Sie den Kontakt auch aus allen aktiven, grün markierten Gruppen
|
||||
die Sie unter “Gemeinsame Chats” im Profil des Kontakts finden können.
|
||||
So vermeiden Sie, dass Ihr Kontakt “unlesbare” Nachrichten erhält.</p>
|
||||
|
||||
<p>Wenn der Kontakt Delta Chat aufgrund von Fehlern oder Bugs nicht mehr verwendet,
|
||||
können Sie diese in unser <a href="https://support.delta.chat">Support-Forum</a> schreiben,
|
||||
und uns so dabei helfen, häufige Probleme zu identifizieren und zu lösen. Vielen Dank!</p>
|
||||
|
||||
<h3 id="sind-anhänge-bilder-dateien-audio-usw-ende-zu-ende-verschlüsselt">
|
||||
|
||||
|
||||
@@ -897,10 +838,9 @@ und Anhang-Metadaten wie Dateinamen.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Ja, Delta Chat verwendet eine sichere Untermenge von OpenPGP
|
||||
und zeigt nur dann ein Vorhängeschloss auf einer Nachricht an,
|
||||
wenn die gesamte Nachricht ordnungsgemäß verschlüsselt und signiert ist.
|
||||
Zum Beispiel werden “Detached Signatures” nicht als sicher betrachtet.</p>
|
||||
<p>Yes, Delta Chat uses a secure subset of OpenPGP
|
||||
requiring the whole message to be properly encrypted and signed.
|
||||
For example, “Detached signatures” are not treated as secure.</p>
|
||||
|
||||
<p>Die meisten öffentlich diskutierten OpenPGP-Probleme
|
||||
resultieren in Wirklichkeit aus schlechter Usability oder schlechter Implementierung von Tools oder Anwendungen - oder beidem.
|
||||
@@ -918,7 +858,7 @@ die Sicherheitseigenschaften durch das im Sommer 2023 angenommene
|
||||
<h3 id="openpgp-alternatives">
|
||||
|
||||
|
||||
Wurden Alternativen zu OpenPGP für die Ende-zu-Ende-Verschlüsselung in Betracht gezogen? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -961,16 +901,15 @@ so wie in der Autocrypt-Level-1-Spezifikation definiert.</p>
|
||||
<h3 id="tls">
|
||||
|
||||
|
||||
Wird eine Nachricht im Klartext gesendet, wenn keine Ende-zu-Ende-Verschlüsselung verfügbar ist? <a href="#tls" class="anchor"></a>
|
||||
Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Auch wenn Ihre Nachrichten nicht Ende-zu-Ende-verschlüsselt sind,
|
||||
sind sie dennoch vor Internetanbietern wie Mobilfunk- oder Telefongesellschaften geschützt.
|
||||
Allerdings können Ihr E-Mail-Provider und der des Empfängers
|
||||
Ihre Nachrichten lesen, analysieren oder sogar verändern,
|
||||
wenn sie nicht Ende-zu-Ende-verschlüsselt sind.</p>
|
||||
<p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
|
||||
they are still protected from cell or cable companies who can not read or modify your e-mail messages.
|
||||
But both your and your recipient’s e-mail providers
|
||||
may read, analyze or modify your messages, including any attachments.</p>
|
||||
|
||||
<p>Delta Chat verwendet standardmäßig strikte
|
||||
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS-Verschlüsselung</a>,
|
||||
@@ -982,10 +921,6 @@ Wenn die beteiligten E-Mail-Server <a href="https://datatracker.ietf.org/doc/htm
|
||||
wird TLS zwischen den E-Mail-Anbietern durchgesetzt.
|
||||
In diesem Fall wird die Delta-Chat-Kommunikation niemals im Klartext ins Internet gelangen
|
||||
selbst wenn die Nachricht nicht Ende-zu-Ende-verschlüsselt war.</p>
|
||||
|
||||
<p>Beachten Sie, dass die <a href="#howtoe2ee">Beibehaltung der garantierten Ende-zu-Ende-Verschlüsselung</a> zusätzlich zur TLS-Verschlüsselung
|
||||
eine allumfassende Sicherheit zwischen Ihrem Gerät und dem des Empfängers bietet.
|
||||
Nicht einmal Ihr E-Mail- oder Internet-Provider wird in der Lage sein, Ihre Nachrichten zu lesen oder zu verändern.</p>
|
||||
|
||||
<h3 id="message-metadata">
|
||||
|
||||
@@ -1046,70 +981,6 @@ Delta Chat zeigt dort zwei Fingerabdrücke an.
|
||||
Wenn die gleichen Fingerabdrücke auf Ihrem eigenen Gerät und auf dem Gerät Ihres Kontakts erscheinen,
|
||||
ist die Verbindung sicher.</p>
|
||||
|
||||
<h3 id="wie-kann-ich-den-verschlüsselungsstatus-von-nachrichten-überprüfen">
|
||||
|
||||
|
||||
Wie kann ich den Verschlüsselungsstatus von Nachrichten überprüfen? <a href="#wie-kann-ich-den-verschlüsselungsstatus-von-nachrichten-überprüfen" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Ein kleines <strong>Vorhängeschloss</strong> in einer Nachrichten zeigt an,
|
||||
dass die Nachricht vom Absender korrekt Ende-zu-Ende-verschlüsselt wurde.
|
||||
Wenn <strong>kein Vorhängeschloss</strong> vorhanden ist, wurde die Nachricht nicht oder nicht korrekt Ende-zu-Ende-verschlüsselt.
|
||||
Höchstwahrscheinlich, weil der Absender ein Webmail-Interface oder eine App
|
||||
ohne Ende-zu-Ende-Unterstützung verwendet.</p>
|
||||
|
||||
<h3 id="warum-sehe-ich-unverschlüsselte-nachrichten">
|
||||
|
||||
|
||||
Warum sehe ich unverschlüsselte Nachrichten? <a href="#warum-sehe-ich-unverschlüsselte-nachrichten" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Wenn ein Kontakt keine Autocrypt-fähige App verwendet,
|
||||
werden alle Nachrichten, die diesen Kontakt betreffen (in Gruppen- oder Direkt-Chats),
|
||||
nicht Ende-zu-Ende-verschlüsselt und zeigen daher kein “Vorhängeschloss”.
|
||||
Beachten Sie, auch Kontakte, die primär Delta Chat verwenden,
|
||||
können gleichzeitig auch nicht-Autocrypt-fähige Apps verwenden.
|
||||
Das unverschlüsselte Antworten auf unverschlüsselte Nachrichten wird von Autocrypt vorgeschrieben
|
||||
um zu verhindern, dass unlesbare Nachrichten auf der Seite Ihrer Kontakte ankommen.</p>
|
||||
|
||||
<h3 id="wie-kann-ich-einen-ende-zu-ende-verschlüsselten-chat-mit-einem-delta-chat-kontakt-führen-der-manchmal-webmail-oder-eine-andere-e-mail-anwendung-ohne-autocrypt-verwendet">
|
||||
|
||||
|
||||
Wie kann ich einen Ende-zu-Ende-verschlüsselten Chat mit einem Delta-Chat-Kontakt führen, der manchmal Webmail oder eine andere E-Mail-Anwendung ohne Autocrypt verwendet? <a href="#wie-kann-ich-einen-ende-zu-ende-verschlüsselten-chat-mit-einem-delta-chat-kontakt-führen-der-manchmal-webmail-oder-eine-andere-e-mail-anwendung-ohne-autocrypt-verwendet" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Wenn Sie einen sicheren Ende-zu-Ende-verschlüsselten Chat mit einem Kontakt benötigen,
|
||||
der sowohl Delta Chat als auch Nicht-Autocrypt-Anwendungen nutzt,
|
||||
können Sie eine <a href="#howtoe2ee">garantierte Ende-zu-Ende-Verschlüsselung</a> einrichten, mit einer Gruppe mit Ihnen beiden als Mitgliedern.
|
||||
In diesem Gruppenchat werden alle Nachrichten Ende-zu-Ende verschlüsselt werdejn,
|
||||
auch wenn im Direkt-Chat eine
|
||||
<a href="#nocryptanymore">“Nachricht von einem anderen Gerät gesendet”</a> wurde.</p>
|
||||
|
||||
<h3 id="wie-kann-ich-ende-zu-ende-verschlüsselung-und-löschen-von-nachrichten-sicherstellen">
|
||||
|
||||
|
||||
Wie kann ich Ende-zu-Ende-Verschlüsselung und Löschen von Nachrichten sicherstellen? <a href="#wie-kann-ich-ende-zu-ende-verschlüsselung-und-löschen-von-nachrichten-sicherstellen" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Der beste Weg, um sicherzustellen, dass alle Nachrichten Ende-zu-Ende-verschlüsselt sind
|
||||
und Metadaten so schnell wie möglich gelöscht werden,
|
||||
ist <a href="#howtoe2ee">die Verwendung von Chats mit garantierter Ende-zu-Ende-Verschlüsselung</a>
|
||||
und die Aktivierung von <a href="#ephemeralmsgs">verschwindenden Nachrichten</a>.</p>
|
||||
|
||||
<p>Garantierte Ende-zu-Ende-Verschlüsselung schützt vor <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM-Angriffen</a>
|
||||
und das Aktivieren von “Verschwindende Nachrichten” löscht die Nachrichten
|
||||
auf dem Server und Lokal nach einer vom Benutzer eingestellten Zeit.</p>
|
||||
|
||||
<p>Wenn Sie die Nachrichten auf Ihrem Gerät, aber nicht auf dem Server benötigen, können Sie auch in der Gruppe vereinbaren, <a href="#delold">“Nachrichten automatisch vom Server löschen”</a> einzuschalten.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
|
||||
@@ -1118,42 +989,35 @@ auf dem Server und Lokal nach einer vom Benutzer eingestellten Zeit.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Nein, Delta Chat unterstützt kein “Perfect Forward Secrecy” (PFS).
|
||||
Das bedeutet, wenn Ihr privater Delta-Chat-Schlüssel durchgesickert ist
|
||||
und jemand Ihre vorherigen In-Transit-Nachrichten gesammelt hat,
|
||||
können diese mit dem veröffentlichtem Schlüssel entschlüsselt werden.</p>
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>Beachten Sie jedoch, dass jemand, der in den Besitz Ihrer privaten Schlüssel gelangt, in der Regel auch in der Lage sein wird, Ihre Nachrichten zu lesen - unabhängig davon, ob Perfect Forward Secrecy nun verwendet wird oder nicht.
|
||||
Die typische, reale Situation für durchgesickerte private Schlüssel, ist die <a href="#device-seizure">Beschlagnahme von Geräten</a>.</p>
|
||||
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
|
||||
This means that if your Delta Chat private decryption key is leaked,
|
||||
and someone has collected your prior in-transit messages,
|
||||
they will be able to decrypt and read them using the leaked decryption key.</p>
|
||||
|
||||
<p>Es ist möglich, dass Delta Chat eine Tages “Perfect Forward Secrecy” unterstützt -
|
||||
OpenPGP ist nur ein Container für verschlüsselte Nachrichten mit dem
|
||||
die Verwaltung der Schlüssel (und damit die Schlüsselrotation oder das Schlüssel-“Ratcheting”)
|
||||
auf flexible Weise organisiert werden kann.
|
||||
Siehe <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouias PFS-Prototyp</a>
|
||||
für bestehende Experimente in der OpenPGP-Community.</p>
|
||||
<p>Note however, that Forward Secrecy only increases your security
|
||||
if you delete messages or use ephemeral deletion timers.
|
||||
Otherwise, if anyone obtains your decryption keys,
|
||||
they are typically also able to get all your non-deleted messages
|
||||
and don’t need to decrypt any previously collected messages.</p>
|
||||
|
||||
<p>The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we also discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
|
||||
<h3 id="ist-die-ende-zu-ende-verschlüsselung-von-delta-chat-genauso-sicher-wie-die-von-signal">
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
|
||||
|
||||
Ist die Ende-zu-Ende-Verschlüsselung von Delta Chat genauso sicher wie die von Signal? <a href="#ist-die-ende-zu-ende-verschlüsselung-von-delta-chat-genauso-sicher-wie-die-von-signal" class="anchor"></a>
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Das hängt davon ab, was für Sie wichtig ist.
|
||||
Delta Chat <a href="#pfs">unterstützt kein PFS</a>,
|
||||
bietet aber <a href="#e2eeguarantee">garantierte Ende-zu-Ende-Verschlüsselung</a>,
|
||||
die vor kompromittierten Servern oder korrupten Netzwerken schützt.
|
||||
Signal und die meisten anderen PFS-unterstützenden Messenger bieten kein
|
||||
praktisches System zum Schutz von Chatgruppen vor Netzwerkangriffen.
|
||||
Diese sind besorgniserregender und realer
|
||||
als ein potenzieller Angreifer, der zwar Ihr Telefon und Ihre privaten Schlüssel beschlagnahmt,
|
||||
aber irgendwie nicht Ihre Nachrichten - gleichzeitig aber eine vollständige Aufzeichnung aller
|
||||
vergangenen verschlüsselten Nachrichten hat.</p>
|
||||
<p>Ja.</p>
|
||||
|
||||
<p>In jedem Fall verwendet die Ende-zu-Ende-Verschlüsselung von Delta Chat eine <a href="#openpgp-secure">sichere Untermenge von OpenPGP</a>
|
||||
das <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">unabhängig sicherheitsgeprüft</a> wurde.</p>
|
||||
<p>We devised a forward secrecy scheme that withstood initial scrutiny from cryptographers and usable security experts.
|
||||
Our tentative scheme is designed to reliably work in federated messaging networks and with multi-device usage.
|
||||
However, an implementation has not been scheduled yet (as of Mid 2025).</p>
|
||||
|
||||
<h3 id="importkey">
|
||||
|
||||
@@ -1490,6 +1354,11 @@ forum</a> veröffentlicht und diskutiert.</li>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Note:
|
||||
Changing email addresses is temporarily disabled
|
||||
because of ongoing changes to the DeltaChat core.
|
||||
It should be available again in a few months.</p>
|
||||
|
||||
<ol>
|
||||
<li>
|
||||
<p>Ändern Sie Ihre E-Mail-Adresse unter “Einstellungen → Erweitert → Passwort und E-Mail-Konto” und
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 349 B |
@@ -36,27 +36,23 @@
|
||||
<li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#encryption-and-security">Encryption and Security</a>
|
||||
<li><a href="#e2ee">Encryption and Security</a>
|
||||
<ul>
|
||||
<li><a href="#which-standards-are-used-for-end-to-end-encryption">Which standards are used for end-to-end encryption?</a></li>
|
||||
<li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I get guaranteed end-to-end encryption and green checkmarks?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark and “guaranteed end-to-end encryption” mean?</a></li>
|
||||
<li><a href="#nocryptanymore">A contact “sent a message from another device”, what can i do?</a></li>
|
||||
<li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
|
||||
<li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li>
|
||||
<li><a href="#openpgp-secure">Is OpenPGP secure?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end -encryption?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
|
||||
<li><a href="#is-delta-chat-vulnerable-to-efail">Is Delta Chat vulnerable to EFAIL?</a></li>
|
||||
<li><a href="#tls">Is a message exposed in cleartext if end-to-end encryption is not available?</a></li>
|
||||
<li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
|
||||
<li><a href="#message-metadata">How does Delta Chat protect metadata in messages?</a></li>
|
||||
<li><a href="#device-seizure">How to protect metadata and contacts when a device is seized?</a></li>
|
||||
<li><a href="#how-can-i-check-encryption-information">How can i check encryption information?</a></li>
|
||||
<li><a href="#how-can-i-check-the-encryption-status-of-messages">How can I check the encryption status of messages?</a></li>
|
||||
<li><a href="#why-do-i-see-unencrypted-messages">Why do I see unencrypted messages?</a></li>
|
||||
<li><a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app?</a></li>
|
||||
<li><a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion">How can I ensure message end-to-end encryption and deletion?</a></li>
|
||||
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
|
||||
<li><a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">Is end-to-end encryption of Delta Chat as safe as Signal?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#importkey">Can I reuse my existing private key?</a></li>
|
||||
<li><a href="#security-audits">Was Delta Chat independently audited for security vulnerabilities?</a></li>
|
||||
</ul>
|
||||
@@ -726,10 +722,10 @@ that achieves “instant delivery” of messages for all chatmail servers
|
||||
including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>.
|
||||
Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p>
|
||||
|
||||
<h2 id="encryption-and-security">
|
||||
<h2 id="e2ee">
|
||||
|
||||
|
||||
Encryption and Security <a href="#encryption-and-security" class="anchor"></a>
|
||||
Encryption and Security <a href="#e2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h2>
|
||||
@@ -742,18 +738,26 @@ Welcome to the power of the interoperable and massive chatmail and e-mail system
|
||||
|
||||
</h3>
|
||||
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption with contacts and group chats.
|
||||
Autocrypt uses a limited and <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>.
|
||||
End-to-End encrypted messages are marked with a padlock
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
|
||||
<p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
|
||||
to provide automatic end-to-end encryption using these protocols:</p>
|
||||
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
|
||||
are used for establishing chats with guaranteed end-to-end encryption
|
||||
which protects against network attacks and compromised servers.
|
||||
Chats marked with a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
guarantee end-to-end encrypted messages.</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
|
||||
to exchange encryption setup information through QR-code scanning or “invite links”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption between contacts and all members of a group chat.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
|
||||
chat</a>
|
||||
enables receivers to use end-to-end encryption with the contact.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
|
||||
|
||||
<h3 id="whene2e">
|
||||
|
||||
@@ -763,28 +767,37 @@ guarantee end-to-end encrypted messages.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>All end-to-end encrypted messages carry a padlock:</p>
|
||||
|
||||
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p>
|
||||
|
||||
<p>End-to-end encryption is guaranteed if there is a green checkmark next to the chat title:</p>
|
||||
|
||||
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
|
||||
<p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
|
||||
Since the Delta Chat Version 2 release series (July 2025)
|
||||
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
<h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
|
||||
|
||||
|
||||
How can I get guaranteed end-to-end encryption and green checkmarks? <a href="#howtoe2ee" class="anchor"></a>
|
||||
Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If you have a second communication channel with your chat partner,
|
||||
like a video chat or a different messenger,
|
||||
you can generate an invite link.</p>
|
||||
<p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
|
||||
it is impossible to receive or send messages without end-to-end encryption.</p>
|
||||
|
||||
<p>If you are together in person,
|
||||
you can show a QR code to your chat partner.</p>
|
||||
<p>If you instead create a profile using a classic e-mail server,
|
||||
you can send and receive messages without end-to-end encryption.
|
||||
Such messages lacking end-to-end encryption are marked with an e-mail icon
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
|
||||
|
||||
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You can send an invite link through another private chat,
|
||||
show an invitation QR code when next to each other or in a video call,
|
||||
or click on a “contact” that was shared in a chat.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
@@ -793,141 +806,60 @@ tap the chat group title to see its member list,
|
||||
and select “QR Invite code”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
tap the QR Code icon <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
|
||||
on the Delta Chat app main screen.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Let your chat partner scan the QR image
|
||||
<p>Ask your chat partner to scan the QR image
|
||||
with their Delta Chat app,
|
||||
or click “Copy” or “Share” to create an invite link
|
||||
and share it with your chat partner.</p>
|
||||
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">Secure-Join network messages are exchanged</a> between both devices.</p>
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>If both devices are online,
|
||||
both sides will eventually see a (group or direct) chat with a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
next to the title.</p>
|
||||
<p>If both sides are online, they will soon see a (group or direct) chat
|
||||
and can start messaging securely.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>If one of the devices is offline, the green checkmarks will only
|
||||
appear later when the device is internet-connected again
|
||||
and the Secure-Join network protocol completed.</p>
|
||||
<p>If one side is offline or in bad network,
|
||||
the ability to chat is delayed until connectivity is restored.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Congratulations!
|
||||
You now will automatically use guaranteed end-to-end encryption
|
||||
with this contact and both of you can add each other to green-checkmarked groups
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />,
|
||||
thereby automatically spreading guaranteed end-to-end encryption among its members.</p>
|
||||
You now will automatically use end-to-end encryption
|
||||
with this contact.
|
||||
If you add each other to chat groups,
|
||||
end-to-end encryption will be established among all members.</p>
|
||||
|
||||
<h3 id="e2eeguarantee">
|
||||
|
||||
|
||||
What does the green checkmark and “guaranteed end-to-end encryption” mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Chat titles with green checkmarks
|
||||
<p>A contact profile might show a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
mean that all messages in the chat will be end-to-end encrypted
|
||||
and can not be read or altered by compromised e-mail servers or Internet providers.
|
||||
Joining green-checkmarked group chats
|
||||
safely spreads everybody’s encryption information (and green checkmarks)
|
||||
in a manner that guarantees end-to-end encryption in the group and among members.</p>
|
||||
|
||||
<p>Contact profiles with green checkmarks
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
mean that messaging a contact is currently guaranteed to be end-to-end encrypted.
|
||||
and an “Introduced by” line.
|
||||
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
|
||||
or was introduced by a another green-checkmarked contact.
|
||||
Introductions happen automatically when adding members to groups.
|
||||
Whoever adds a contact to a green-checkmarked group becomes an introducer
|
||||
to those members who didn’t yet know about the added contact.
|
||||
Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
|
||||
becomes an introducer.
|
||||
In a contact profile you can tap on the “Introduced by …” text repeatedly
|
||||
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
|
||||
|
||||
<p>Note that in a contact profile you may see and tap introducers
|
||||
but there is no green checkmark in the profile title.
|
||||
This usually means that the contact <a href="#nocryptanymore">“sent a message from another device”</a>.</p>
|
||||
|
||||
<p>For more in-depth discussion of “guaranteed end-to-end encryption”
|
||||
please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
|
||||
and specifically read about “Verified Groups”, the technical term
|
||||
of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p>
|
||||
|
||||
<h3 id="nocryptanymore">
|
||||
|
||||
|
||||
A contact “sent a message from another device”, what can i do? <a href="#nocryptanymore" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Your chat with a contact lost guaranteed end-to-end encryption.
|
||||
The green checkmark was removed for this chat and contact when you see this warning.
|
||||
<strong>If you find the sudden drop of guaranteed end-to-end encryption
|
||||
surprising for this contact then don’t accept the warning!</strong>
|
||||
Instead check with your contact through a second channel
|
||||
like a video call, other messenger or a phone call,
|
||||
to find out what happened.</p>
|
||||
|
||||
<p>If your contact actually caused the drop of guaranteed end-to-end encryption
|
||||
please see the next paragraphs for common reasons and their mitigations.
|
||||
Regardless, all other green-checkmarked chats remain guaranteed end-to-end encrypted
|
||||
even if the contact is a member there.</p>
|
||||
|
||||
<p><strong>Your contact is using Delta Chat on a second device (phone or laptop)</strong></p>
|
||||
|
||||
<p>If they have another device with a Delta Chat app running,
|
||||
they should remove the profile from the new device
|
||||
and add it <a href="#multiclient">as a second device as described here</a>.
|
||||
As soon as they message you afterwards, the warning will be gone
|
||||
and guaranteed encryption is established with both devices of your contact.</p>
|
||||
|
||||
<p><strong>Your contact reinstalled Delta Chat using their old account login</strong></p>
|
||||
|
||||
<p>If they have <a href="#backup">a backup file</a>,
|
||||
they should remove the profile from the new device
|
||||
and rather import the backup file to re-create their profile.
|
||||
As soon as they message you afterwards, the warning will be gone
|
||||
and guaranteed encryption is re-established for this contact.</p>
|
||||
|
||||
<p>If they don’t have a backup file, it’s best to perform a <a href="#howtoe2ee">QR scan</a>
|
||||
with your chat partner to re-establish guaranteed end-to-end encryption.</p>
|
||||
|
||||
<p><strong>Your contact sent a mail through a webmail interface or another e-mail app
|
||||
and will get back to using Delta Chat soon again.</strong></p>
|
||||
|
||||
<p>If you are sure that the contact sometimes uses webmail,
|
||||
or another mail app lacking end-to-end encryption,
|
||||
then you may accept the warning.
|
||||
As soon as your contact uses Delta Chat again,
|
||||
guaranteed end-to-end encryption will be automatically re-established.</p>
|
||||
|
||||
<p><strong>Your contact stopped using Delta Chat entirely</strong></p>
|
||||
|
||||
<p>Sometimes remaining in contact is more important than end-to-end encryption.
|
||||
<a href="#tls">“Transport Layer Encryption” (TLS)</a> may still meaningfully protect
|
||||
the confidentiality of your messages between your device and the e-mail server.
|
||||
But without end-to-end encryption you and your contact are trusting your e-mail server
|
||||
to not read or manipulate your messages, and to not hand them to third parties.</p>
|
||||
|
||||
<p>In any case, you can not do much else than accept the warning.
|
||||
Please also remove the contact from any active green-checkmarked group
|
||||
which you can find in “Chats in Common” in the Contact profile.
|
||||
This spares your contact from getting “unreadable” messages.</p>
|
||||
|
||||
<p>If the contact removed Delta Chat because of buggy or undesirable behaviour,
|
||||
please consider posting to our <a href="https://support.delta.chat">support forum</a>
|
||||
to help us identify and address common problems. Thanks!</p>
|
||||
|
||||
<h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted">
|
||||
|
||||
|
||||
@@ -952,8 +884,7 @@ and attachment metadata such as filenames.</p>
|
||||
</h3>
|
||||
|
||||
<p>Yes, Delta Chat uses a secure subset of OpenPGP
|
||||
and only displays a padlock security indicator on a message
|
||||
if the whole message is properly encrypted and signed.
|
||||
requiring the whole message to be properly encrypted and signed.
|
||||
For example, “Detached signatures” are not treated as secure.</p>
|
||||
|
||||
<p>OpenPGP is not insecure by itself.
|
||||
@@ -974,7 +905,7 @@ which was thankfully adopted in summer 2023.</p>
|
||||
<h3 id="openpgp-alternatives">
|
||||
|
||||
|
||||
Did you consider using alternatives to OpenPGP for end-to-end -encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -1017,17 +948,15 @@ as defined by the Autocrypt Level 1 specification.</p>
|
||||
<h3 id="tls">
|
||||
|
||||
|
||||
Is a message exposed in cleartext if end-to-end encryption is not available? <a href="#tls" class="anchor"></a>
|
||||
Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Even if your messages are not guaranteed to be end-to-end encrypted,
|
||||
they are still protected from Internet providers like cell or cable companies.
|
||||
However, your and your recipient’s e-mail providers
|
||||
may read, analyze or even modify your messages,
|
||||
including any attachments,
|
||||
if they are not end-to-end encrypted.</p>
|
||||
<p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
|
||||
they are still protected from cell or cable companies who can not read or modify your e-mail messages.
|
||||
But both your and your recipient’s e-mail providers
|
||||
may read, analyze or modify your messages, including any attachments.</p>
|
||||
|
||||
<p>Delta Chat by default uses strict
|
||||
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a>
|
||||
@@ -1039,10 +968,6 @@ If the involved e-mail servers support <a href="https://datatracker.ietf.org/doc
|
||||
then transport encryption will be enforced between e-mail providers
|
||||
in which case Delta Chat communications will never be exposed in cleartext to the Internet
|
||||
even if the message was not end-to-end encrypted.</p>
|
||||
|
||||
<p>Note that <a href="#howtoe2ee">maintaining guaranteed end-to-end encryption</a> on top of TLS encryption
|
||||
provides pervasive safety between your and the recipient’s devices.
|
||||
Not even your e-mail or Internet provider will be able to read or modify your messages.</p>
|
||||
|
||||
<h3 id="message-metadata">
|
||||
|
||||
@@ -1105,74 +1030,6 @@ Delta Chat shows two fingerprints there.
|
||||
If the same fingerprints appear on your own and your contact’s device,
|
||||
the connection is safe.</p>
|
||||
|
||||
<h3 id="how-can-i-check-the-encryption-status-of-messages">
|
||||
|
||||
|
||||
How can I check the encryption status of messages? <a href="#how-can-i-check-the-encryption-status-of-messages" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>A little <strong>padlock</strong> in a message bubble denotes
|
||||
that the message was properly end-to-end encrypted from the given sender.
|
||||
If there is <strong>no padlock</strong>, the message was not properly end-to-end encrypted
|
||||
most likely because the sender uses an app or webmail interface
|
||||
without support for end-to-end–encryption.</p>
|
||||
|
||||
<h3 id="why-do-i-see-unencrypted-messages">
|
||||
|
||||
|
||||
Why do I see unencrypted messages? <a href="#why-do-i-see-unencrypted-messages" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If a contact uses a non-Autocrypt e-mail app,
|
||||
all messages involving this contact (in a group or 1:1 chat)
|
||||
will not be end-to-end encrypted, and thus not show a “padlock” with messages.
|
||||
Note that even if your contacts use Delta Chat on their account,
|
||||
they might also use a non-Autocrypt e-mail app on that account
|
||||
which then may cause intermittently unencrypted messages.
|
||||
Replying unencrypted to unencrypted messages is mandated by Autocrypt
|
||||
to prevent unreadable messages on the side of your contacts
|
||||
and their non-Autocrypt e-mail app.</p>
|
||||
|
||||
<h3 id="how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">
|
||||
|
||||
|
||||
How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app? <a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If you need a safely end-to-end encrypted chat with a contact
|
||||
who is using their e-mail account both with Delta Chat and non-Autocrypt apps (e.g. webmail),
|
||||
it’s best to setup <a href="#howtoe2ee">guaranteed end-to-end encryption with them</a>
|
||||
and then create a guaranteed end-to-end encrypted group chat with you two as members.
|
||||
In this group chat all messages will be end-to-end encrypted
|
||||
even if the direct chat between you two has a
|
||||
<a href="#nocryptanymore">“… sent a message from another device”</a> warning.</p>
|
||||
|
||||
<h3 id="how-can-i-ensure-message-end-to-end-encryption-and-deletion">
|
||||
|
||||
|
||||
How can I ensure message end-to-end encryption and deletion? <a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>The best way to ensure every message is end-to-end encrypted,
|
||||
and metadata deleted as quickly as possible
|
||||
is <a href="#howtoe2ee">using chats with guaranteed end-to-end encryption</a>
|
||||
and turning on <a href="#ephemeralmsgs">disappearing messages</a>.</p>
|
||||
|
||||
<p>Guaranteed end-to-end encrypted chats protect against <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM attacks</a>
|
||||
and turning on disappearing messages deletes the messages
|
||||
on the server after a user-configured time.</p>
|
||||
|
||||
<p>If you don’t need a longer-lived copy of your messages on the server,
|
||||
you can also turn on <a href="#delold">“delete messages from server automatically”</a>.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
|
||||
@@ -1181,45 +1038,35 @@ you can also turn on <a href="#delold">“delete messages from server automatica
|
||||
|
||||
</h3>
|
||||
|
||||
<p>No, Delta Chat doesn’t support Perfect Forward Secrecy (PFS).
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
|
||||
This means that if your Delta Chat private decryption key is leaked,
|
||||
and someone has collected your prior in-transit messages,
|
||||
they will be able to decrypt and read them using the leaked decryption key.</p>
|
||||
|
||||
<p>Note, however, that if anyone obtains to your decryption keys,
|
||||
they will typically also be able to obtain your messages,
|
||||
irrespective if Perfect Forward Secrecy is in place or not.
|
||||
The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
<p>Note however, that Forward Secrecy only increases your security
|
||||
if you delete messages or use ephemeral deletion timers.
|
||||
Otherwise, if anyone obtains your decryption keys,
|
||||
they are typically also able to get all your non-deleted messages
|
||||
and don’t need to decrypt any previously collected messages.</p>
|
||||
|
||||
<p>It is possible that Delta Chat evolves to support Perfect Forward Secrecy,
|
||||
because OpenPGP is just a container for encrypted messages
|
||||
but encryption key management (and thus key rotation or key “ratcheting”)
|
||||
could be organized in flexible ways.
|
||||
See <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouia’s PFS prototype</a>
|
||||
for existing experiments in the OpenPGP implementor community.</p>
|
||||
<p>The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we also discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
|
||||
<h3 id="is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
|
||||
|
||||
Is end-to-end encryption of Delta Chat as safe as Signal? <a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal" class="anchor"></a>
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>It depends on what is important to you.
|
||||
Delta Chat <a href="#pfs">does not support PFS</a> like Signal does
|
||||
but it provides <a href="#e2eeguarantee">guaranteed end-to-end encrypted chats</a>
|
||||
that are safe against compromised servers or corrupted networks.
|
||||
Signal and most other PFS-supporting messengers do not provide
|
||||
a practical scheme for protecting chat groups from network attacks
|
||||
which are arguably more worrisome
|
||||
than a potential attacker who seizes your phone and private encryption setup
|
||||
but somehow not your messages, yet has a full record of all
|
||||
past encrypted messages.</p>
|
||||
<p>Yes.</p>
|
||||
|
||||
<p>In any case, Delta Chat’s end-to-end encryption uses a <a href="#openpgp-secure">secure subset of OpenPGP</a>
|
||||
which has been <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">independently security-audited</a>.</p>
|
||||
<p>We devised a forward secrecy scheme that withstood initial scrutiny from cryptographers and usable security experts.
|
||||
Our tentative scheme is designed to reliably work in federated messaging networks and with multi-device usage.
|
||||
However, an implementation has not been scheduled yet (as of Mid 2025).</p>
|
||||
|
||||
<h3 id="importkey">
|
||||
|
||||
@@ -1254,7 +1101,7 @@ from most recent to older:</p>
|
||||
<li>
|
||||
<p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of
|
||||
rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place.
|
||||
rPGP serves as the end-to-end encyption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
|
||||
rPGP serves as the end-to-end encryption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
|
||||
Two advisories were released related to the findings of this audit:</p>
|
||||
|
||||
<ul>
|
||||
|
||||
+114
-237
@@ -6,7 +6,7 @@
|
||||
<li><a href="#cuáles-son-las-ventajas-de-delta-chat-comparado-con-otras-aplicaciones-de-mensajería">¿Cuáles son las ventajas de Delta Chat comparado con otras aplicaciones de mensajería?</a></li>
|
||||
<li><a href="#qué-pasa-si-espero-un-mensaje-de-alguien-a-quien-no-le-escribí-en-el-pasado">¿Qué pasa si espero un mensaje de alguien a quien no le escribí en el pasado?</a></li>
|
||||
<li><a href="#delta-chat-soporta-envío-de-imágenes-videos-documentos-y-otros-archivos">¿Delta Chat soporta envío de imágenes, videos, documentos y otros archivos?</a></li>
|
||||
<li><a href="#multiple-accounts">What are profiles? How can I switch between them?</a></li>
|
||||
<li><a href="#multiple-accounts">¿Qué son los perfiles? ¿Cómo puedo cambiar entre ellos?</a></li>
|
||||
<li><a href="#quién-ve-mi-foto-de-perfil">¿Quién ve mi foto de perfil?</a></li>
|
||||
<li><a href="#signature">¿Puedo establecer un texto de firma con Delta Chat?</a></li>
|
||||
<li><a href="#qué-significa-fijar-mutear-archivar">¿Qué significa fijar, mutear, archivar?</a></li>
|
||||
@@ -36,27 +36,23 @@
|
||||
<li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#cifrado-y-seguridad">Cifrado y seguridad</a>
|
||||
<li><a href="#e2ee">Cifrado y seguridad</a>
|
||||
<ul>
|
||||
<li><a href="#qué-estándares-se-utilizan-para-el-cifrado-de-extremo-a-extremo">¿Qué estándares se utilizan para el cifrado de extremo a extremo?</a></li>
|
||||
<li><a href="#whene2e">¿Cómo puedo saber si los mensajes están cifrados de extremo a extremo?</a></li>
|
||||
<li><a href="#howtoe2ee">¿Cómo puedo obtener cifrado de extremo a extremo garantizado y estampillas verdes?</a></li>
|
||||
<li><a href="#e2eeguarantee">¿Qué significa la estampilla verde y “cifrado de extremo a extremo garantizado”?</a></li>
|
||||
<li><a href="#nocryptanymore">Un contacto “envió un mensaje desde otro dispositivo”, ¿qué puedo hacer?</a></li>
|
||||
<li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
|
||||
<li><a href="#los-adjuntos-imágenes-archivos-audio-etc-están-cifrados-de-extremo-a-extremo">¿Los adjuntos (imágenes, archivos, audio, etc.) están cifrados de extremo a extremo?</a></li>
|
||||
<li><a href="#openpgp-secure">¿Es OpenPGP seguro?</a></li>
|
||||
<li><a href="#openpgp-alternatives">¿Consideraron usar alternativas a OpenPGP para el cifrado de extremo a extremo?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
|
||||
<li><a href="#es-delta-chat-vulnerable-a-efail">¿Es Delta Chat vulnerable a EFAIL?</a></li>
|
||||
<li><a href="#tls">¿Se expone un mensaje en texto claro si no está disponible el cifrado de extremo a extremo?</a></li>
|
||||
<li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
|
||||
<li><a href="#message-metadata">¿Cómo Delta Chat protege los metadatos en los mensajes?</a></li>
|
||||
<li><a href="#device-seizure">¿Cómo proteger los metadatos y los contactos cuando se incauta un dispositivo?</a></li>
|
||||
<li><a href="#cómo-puedo-verificar-la-información-de-cifrado">¿Cómo puedo verificar la información de cifrado?</a></li>
|
||||
<li><a href="#cómo-puedo-verificar-el-estado-de-cifrado-de-los-mensajes">¿Cómo puedo verificar el estado de cifrado de los mensajes?</a></li>
|
||||
<li><a href="#por-qué-veo-mensajes-sin-cifrar">¿Por qué veo mensajes sin cifrar?</a></li>
|
||||
<li><a href="#cómo-puedo-obtener-un-chat-cifrado-de-extremo-a-extremo-con-un-contacto-de-delta-chat-que-a-veces-utiliza-webmail-u-otra-aplicación-de-correo-electrónico-no-autocrypt">¿Cómo puedo obtener un chat cifrado de extremo a extremo con un contacto de Delta Chat que a veces utiliza webmail u otra aplicación de correo electrónico no Autocrypt?</a></li>
|
||||
<li><a href="#cómo-puedo-asegurar-el-cifrado-de-extremo-a-extremo-y-la-eliminación-de-mensajes">¿Cómo puedo asegurar el cifrado de extremo a extremo y la eliminación de mensajes?</a></li>
|
||||
<li><a href="#pfs">¿Soporta Delta Chat Perfect Forward Secrecy?</a></li>
|
||||
<li><a href="#es-el-cifrado-de-extremo-a-extremo-de-delta-chat-tan-seguro-como-el-de-signal">¿Es el cifrado de extremo a extremo de Delta Chat tan seguro como el de Signal?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#importkey">¿Puedo reutilizar mi clave privada existente?</a></li>
|
||||
<li><a href="#security-audits">¿Se auditó Delta Chat de forma independiente en busca de vulnerabilidades de seguridad?</a></li>
|
||||
</ul>
|
||||
@@ -154,8 +150,8 @@ aunque el destinatario no utilice Delta Chat.</p>
|
||||
</h3>
|
||||
|
||||
<ul>
|
||||
<li>Anonymous chat profiles with fast, secure and interoperable <a href="https://delta.chat/chatmail">chatmail servers</a>
|
||||
which offer instant Push Notifications for iOS and Android devices.</li>
|
||||
<li>Perfiles de chat anónimos con <a href="https://delta.chat/chatmail">servidores de chatmail</a> rápidos, seguros e interoperables
|
||||
que ofrecen notificaciones Push instantáneas para dispositivos con iOS y Android.</li>
|
||||
</ul>
|
||||
|
||||
<p>Soporte omnipresente, <a href="#multiple-accounts">múltiples perfiles</a> y múltiples dispositivos en todas las plataformas. </p>
|
||||
@@ -166,9 +162,9 @@ which offer instant Push Notifications for iOS and Android devices.</li>
|
||||
seguro contra ataques a la red y al servidor.</p>
|
||||
|
||||
<ul>
|
||||
<li>Free and Open Source software, both app and server side.
|
||||
Built on <a href="https://github.com/chatmail/core/blob/main/standards.md#standards-used-in-delta-chat">E-mail and Web Internet Standards</a>,
|
||||
<a href="https://xkcd.com/927/">to avoid “yet another standard syndrome (xkcd 927)”</a></li>
|
||||
<li>Software libre y de código abierto, tanto para aplicaciones como para servidores.
|
||||
Basado en <a href="https://github.com/chatmail/core/blob/main/standards.md#standards-used-in-delta-chat">Estándares de Internet para correo electrónico y web</a>,
|
||||
<a href="https://xkcd.com/927/">para evitar el “síndrome de otro estándar más (xkcd 927)”</a></li>
|
||||
</ul>
|
||||
|
||||
<h3 id="qué-pasa-si-espero-un-mensaje-de-alguien-a-quien-no-le-escribí-en-el-pasado">
|
||||
@@ -213,7 +209,7 @@ Built on <a href="https://github.com/chatmail/core/blob/main/standards.md#standa
|
||||
<h3 id="multiple-accounts">
|
||||
|
||||
|
||||
What are profiles? How can I switch between them? <a href="#multiple-accounts" class="anchor"></a>
|
||||
¿Qué son los perfiles? ¿Cómo puedo cambiar entre ellos? <a href="#multiple-accounts" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -718,10 +714,10 @@ that achieves “instant delivery” of messages for all chatmail servers
|
||||
including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>.
|
||||
Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p>
|
||||
|
||||
<h2 id="cifrado-y-seguridad">
|
||||
<h2 id="e2ee">
|
||||
|
||||
|
||||
Cifrado y seguridad <a href="#cifrado-y-seguridad" class="anchor"></a>
|
||||
Cifrado y seguridad <a href="#e2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h2>
|
||||
@@ -734,18 +730,26 @@ Welcome to the power of the interoperable and massive chatmail and e-mail system
|
||||
|
||||
</h3>
|
||||
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption with contacts and group chats.
|
||||
Autocrypt uses a limited and <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>.
|
||||
End-to-End encrypted messages are marked with a padlock
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
|
||||
<p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
|
||||
to provide automatic end-to-end encryption using these protocols:</p>
|
||||
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Protocolos de Secure-Join</a>
|
||||
se utilizan para establecer chats con cifrado de extremo a extremo garantizado
|
||||
que protege contra ataques de red y servidores comprometidos.
|
||||
Los chats marcados con una estampilla verde
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
garantizan mensajes cifrados de extremo a extremo.</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
|
||||
to exchange encryption setup information through QR-code scanning or “invite links”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption between contacts and all members of a group chat.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
|
||||
chat</a>
|
||||
enables receivers to use end-to-end encryption with the contact.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
|
||||
|
||||
<h3 id="whene2e">
|
||||
|
||||
@@ -755,28 +759,37 @@ garantizan mensajes cifrados de extremo a extremo.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Todos los mensajes cifrados de extremo a extremo tienen un candado:</p>
|
||||
|
||||
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p>
|
||||
|
||||
<p>El cifrado de extremo a extremo está garantizado si hay una estampilla verde cerca del nombre del chat:</p>
|
||||
|
||||
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
|
||||
<p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
|
||||
Since the Delta Chat Version 2 release series (July 2025)
|
||||
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
<h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
|
||||
|
||||
|
||||
¿Cómo puedo obtener cifrado de extremo a extremo garantizado y estampillas verdes? <a href="#howtoe2ee" class="anchor"></a>
|
||||
Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If you have a second communication channel with your chat partner,
|
||||
like a video chat or a different messenger,
|
||||
you can generate an invite link.</p>
|
||||
<p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
|
||||
it is impossible to receive or send messages without end-to-end encryption.</p>
|
||||
|
||||
<p>If you are together in person,
|
||||
you can show a QR code to your chat partner.</p>
|
||||
<p>If you instead create a profile using a classic e-mail server,
|
||||
you can send and receive messages without end-to-end encryption.
|
||||
Such messages lacking end-to-end encryption are marked with an e-mail icon
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
|
||||
|
||||
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You can send an invite link through another private chat,
|
||||
show an invitation QR code when next to each other or in a video call,
|
||||
or click on a “contact” that was shared in a chat.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
@@ -785,125 +798,57 @@ tap the chat group title to see its member list,
|
||||
and select “QR Invite code”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
tap the QR Code icon <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
|
||||
on the Delta Chat app main screen.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Let your chat partner scan the QR image
|
||||
<p>Ask your chat partner to scan the QR image
|
||||
with their Delta Chat app,
|
||||
or click “Copy” or “Share” to create an invite link
|
||||
and share it with your chat partner.</p>
|
||||
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">Secure-Join network messages are exchanged</a> between both devices.</p>
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>Si ambos dispositivos están en línea,
|
||||
ambas partes eventualmente verán un chat (grupal o directo) con una estampilla verde
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
junto al título.</p>
|
||||
<p>If both sides are online, they will soon see a (group or direct) chat
|
||||
and can start messaging securely.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Si uno de los dispositivos está sin conexión, las estampillas verdes solo aparecerán más tarde cuando el dispositivo vuelva a estar conectado a Internet y se complete el protocolo de red Secure-Join.</p>
|
||||
<p>If one side is offline or in bad network,
|
||||
the ability to chat is delayed until connectivity is restored.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>¡Felicitaciones!
|
||||
Ahora utilizarás automáticamente el cifrado de extremo a extremo garantizado
|
||||
con este contacto y ambos pueden agregarse mutuamente a grupos con estampilla verde
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />,
|
||||
de esta manera se propagará automáticamente el cifrado de extremo a extremo garantizado entre sus miembros.</p>
|
||||
<p>Congratulations!
|
||||
You now will automatically use end-to-end encryption
|
||||
with this contact.
|
||||
If you add each other to chat groups,
|
||||
end-to-end encryption will be established among all members.</p>
|
||||
|
||||
<h3 id="e2eeguarantee">
|
||||
|
||||
|
||||
¿Qué significa la estampilla verde y “cifrado de extremo a extremo garantizado”? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Títulos de chat con estampillas verdes
|
||||
<p>A contact profile might show a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
significan que todos los mensajes en el chat estarán cifrados de extremo a extremo
|
||||
y no pueden ser leídos o alterados por servidores de correo electrónico o proveedores de Internet comprometidos.
|
||||
Unirse a chats grupales con estampillas verdes
|
||||
difunde de manera segura la información de cifrado de todos (y las estampillas verdes)
|
||||
de una manera que garantiza el cifrado de extremo a extremo en el grupo y entre los miembros.</p>
|
||||
|
||||
<p>Perfiles de contacto con estampillas verdes
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
significa que el envío de mensajes a un contacto está actualmente garantizado que está cifrado de extremo a extremo.
|
||||
Cada contacto con estampilla verde hizo un escaneo directo de <a href="#howtoe2ee">QR</a> contigo
|
||||
o fue presentado por otro contacto con estampilla verde.
|
||||
Las presentaciones ocurren automáticamente al agregar miembros a grupos.
|
||||
Quien agregue un contacto a un grupo con estampilla verde se convierte en un presentador
|
||||
para aquellos miembros que aún no conocían al contacto agregado.
|
||||
En un perfil de contacto, puedes tocar repetidamente el texto “Presentado por …”
|
||||
hasta llegar al que hizo un escaneo directo de <a href="#howtoe2ee">QR</a> contigo.</p>
|
||||
|
||||
<p>Ten en cuenta que en un perfil de contacto puedes ver y tocar a las personas que te presentaron a ese contacto, pero puede pasar que no haya una estampilla verde en el título del perfil. Esto generalmente significa que el contacto <a href="#nocryptanymore">“envió un mensaje desde otro dispositivo”</a>.</p>
|
||||
and an “Introduced by” line.
|
||||
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
|
||||
or was introduced by a another green-checkmarked contact.
|
||||
Introductions happen automatically when adding members to groups.
|
||||
Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
|
||||
becomes an introducer.
|
||||
In a contact profile you can tap on the “Introduced by …” text repeatedly
|
||||
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
|
||||
|
||||
<p>Para obtener una discusión más detallada sobre “cifrado de extremo a extremo garantizado”, por favor consulta los <a href="https://securejoin.delta.chat/en/latest/new.html">protocolos Secure-Join</a> y lee específicamente sobre “Grupos Verificados”, el término técnico de lo que aquí se llama chats “marcados con una estampilla verde” o “cifrados de extremo a extremo garantizado”.</p>
|
||||
|
||||
<h3 id="nocryptanymore">
|
||||
|
||||
|
||||
Un contacto “envió un mensaje desde otro dispositivo”, ¿qué puedo hacer? <a href="#nocryptanymore" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Tu chat con un contacto perdió el cifrado de extremo a extremo garantizado.
|
||||
La estampilla verde fue eliminada para este chat y contacto cuando veas esta advertencia.
|
||||
<strong>Si encuentras sorprendente la repentina pérdida de cifrado de extremo a extremo garantizado
|
||||
para este contacto, ¡no aceptes la advertencia!</strong>
|
||||
En su lugar, verifica con tu contacto a través de un segundo canal
|
||||
como una videollamada, otra app de chat o una llamada telefónica,
|
||||
para averiguar qué sucedió.</p>
|
||||
|
||||
<p>Si tu contacto realmente causó la caída del cifrado de extremo a extremo garantizado, por favor vea los siguientes párrafos para conocer las razones comunes y sus mitigaciones. Sin embargo, todos los demás chats marcados con una estampilla verde siguen estando cifrados de extremo a extremo garantizado, incluso si el contacto es miembro allí.</p>
|
||||
|
||||
<p><strong>Tu contacto está usando Delta Chat en un segundo dispositivo (teléfono o computadora portátil)</strong></p>
|
||||
|
||||
<p>Si tienen otro dispositivo con la aplicación Delta Chat en funcionamiento,
|
||||
deben eliminar la cuenta del nuevo dispositivo
|
||||
y agregarla <a href="#multiclient">como un segundo dispositivo según se describe aquí</a>.
|
||||
Tan pronto como te envíen un mensaje después, la advertencia desaparecerá
|
||||
y se establecerá el cifrado garantizado con ambos dispositivos de tu contacto.</p>
|
||||
|
||||
<p><strong>Tu contacto reinstaló Delta Chat utilizando su antiguo inicio de sesión de cuenta</strong></p>
|
||||
|
||||
<p>Si tienen <a href="#backup">un archivo de respaldo</a>,
|
||||
deben eliminar la cuenta del nuevo dispositivo
|
||||
y en su lugar importar el archivo de respaldo para recrear su cuenta.
|
||||
Tan pronto como te envíen un mensaje después, la advertencia desaparecerá
|
||||
y se restablecerá el cifrado garantizado para este contacto.</p>
|
||||
|
||||
<p>Si no tienen un archivo de respaldo, es mejor realizar un <a href="#howtoe2ee">escaneo QR</a> con tu compañero de chat para restablecer el cifrado de extremo a extremo garantizado.</p>
|
||||
|
||||
<p><strong>Tu contacto envió un correo a través de una interfaz de correo web o otra aplicación de correo electrónico y volverá a usar Delta Chat pronto.</strong></p>
|
||||
|
||||
<p>Si estás seguro de que el contacto a veces utiliza webmail,
|
||||
o alguna otra aplicación de correo que carece de cifrado de extremo a extremo,
|
||||
entonces puedes aceptar la advertencia.
|
||||
Tan pronto como tu contacto vuelva a utilizar Delta Chat,
|
||||
el cifrado de extremo a extremo garantizado se restablecerá automáticamente.</p>
|
||||
|
||||
<p><strong>Tus contactos dejaron de usar Delta Chat completamente</strong></p>
|
||||
|
||||
<p>A veces, mantenerse en contacto es más importante que el cifrado de extremo a extremo. El cifrado de capa de transporte <a href="#tls">(“Transport Layer Encryption” o TLS)</a> puede proteger de manera significativa la confidencialidad de tus mensajes entre tu dispositivo y el servidor de correo electrónico. Pero sin el cifrado de extremo a extremo, tú y tu contacto están confiando en que el servidor de correo electrónico no lea ni manipule tus mensajes, y que no los entregue a terceros.</p>
|
||||
|
||||
<p>En cualquier caso, no puedes hacer mucho más que aceptar la advertencia.
|
||||
Por favor, también elimina el contacto de cualquier grupo activo con estampilla verde
|
||||
que puedas encontrar en “Chats compartidos” en el perfil del contacto.
|
||||
Esto evitará que tu contacto reciba mensajes “ilegibles”.</p>
|
||||
|
||||
<p>Si el contacto eliminó Delta Chat debido a un comportamiento defectuoso o indeseable,
|
||||
por favor considera publicar en nuestro <a href="https://support.delta.chat">foro de soporte</a>
|
||||
para ayudarnos a identificar y solucionar problemas comunes. ¡Gracias!</p>
|
||||
|
||||
<h3 id="los-adjuntos-imágenes-archivos-audio-etc-están-cifrados-de-extremo-a-extremo">
|
||||
|
||||
|
||||
@@ -927,10 +872,9 @@ y los metadatos de los archivos adjuntos, como los nombres de archivo.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Sí, Delta Chat utiliza un subconjunto seguro de OpenPGP
|
||||
y solo muestra un indicador de seguridad de candado en un mensaje
|
||||
si todo el mensaje está correctamente cifrado y firmado.
|
||||
Por ejemplo, las “firmas desvinculadas” no se consideran seguras.</p>
|
||||
<p>Yes, Delta Chat uses a secure subset of OpenPGP
|
||||
requiring the whole message to be properly encrypted and signed.
|
||||
For example, “Detached signatures” are not treated as secure.</p>
|
||||
|
||||
<p>OpenPGP is not insecure by itself.
|
||||
Most publicly discussed OpenPGP security problems
|
||||
@@ -950,7 +894,7 @@ which was thankfully adopted in summer 2023.</p>
|
||||
<h3 id="openpgp-alternatives">
|
||||
|
||||
|
||||
¿Consideraron usar alternativas a OpenPGP para el cifrado de extremo a extremo? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -993,17 +937,15 @@ as defined by the Autocrypt Level 1 specification.</p>
|
||||
<h3 id="tls">
|
||||
|
||||
|
||||
¿Se expone un mensaje en texto claro si no está disponible el cifrado de extremo a extremo? <a href="#tls" class="anchor"></a>
|
||||
Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Even if your messages are not guaranteed to be end-to-end encrypted,
|
||||
they are still protected from Internet providers like cell or cable companies.
|
||||
However, your and your recipient’s e-mail providers
|
||||
may read, analyze or even modify your messages,
|
||||
including any attachments,
|
||||
if they are not end-to-end encrypted.</p>
|
||||
<p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
|
||||
they are still protected from cell or cable companies who can not read or modify your e-mail messages.
|
||||
But both your and your recipient’s e-mail providers
|
||||
may read, analyze or modify your messages, including any attachments.</p>
|
||||
|
||||
<p>Delta Chat by default uses strict
|
||||
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a>
|
||||
@@ -1015,8 +957,6 @@ If the involved e-mail servers support <a href="https://datatracker.ietf.org/doc
|
||||
then transport encryption will be enforced between e-mail providers
|
||||
in which case Delta Chat communications will never be exposed in cleartext to the Internet
|
||||
even if the message was not end-to-end encrypted.</p>
|
||||
|
||||
<p>Ten en cuenta que <a href="#howtoe2ee">mantener un cifrado de extremo a extremo garantizado</a> sobre el cifrado TLS proporciona seguridad generalizada entre tus dispositivos y los del destinatario. Ni siquiera tu proveedor de correo electrónico o de Internet podrá leer o modificar tus mensajes.</p>
|
||||
|
||||
<h3 id="message-metadata">
|
||||
|
||||
@@ -1074,64 +1014,6 @@ phone numbers in chat groups which in turn are often associated with legal ident
|
||||
|
||||
<p>Puede verificar manualmente el estado de cifrado de extremo a extremo en el diálogo “Cifrado” (perfil de usuario en Android/iOS o hacer clic derecho en el elemento de lista de chat de un usuario en el escritorio). Delta Chat muestra dos huellas digitales allí. Si las mismas huellas digitales aparecen en su propio dispositivo y en el dispositivo de su contacto, la conexión es segura.</p>
|
||||
|
||||
<h3 id="cómo-puedo-verificar-el-estado-de-cifrado-de-los-mensajes">
|
||||
|
||||
|
||||
¿Cómo puedo verificar el estado de cifrado de los mensajes? <a href="#cómo-puedo-verificar-el-estado-de-cifrado-de-los-mensajes" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Un pequeño <strong>candado</strong> en una burbuja de mensaje indica que el mensaje fue correctamente cifrado de extremo a extremo por el remitente dado. Si no hay <strong>candado</strong>, es probable que el mensaje no esté correctamente cifrado de extremo a extremo, ya que el remitente utiliza una aplicación o interfaz de correo web sin soporte para el cifrado de extremo a extremo.</p>
|
||||
|
||||
<h3 id="por-qué-veo-mensajes-sin-cifrar">
|
||||
|
||||
|
||||
¿Por qué veo mensajes sin cifrar? <a href="#por-qué-veo-mensajes-sin-cifrar" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If a contact uses a non-Autocrypt e-mail app,
|
||||
all messages involving this contact (in a group or 1:1 chat)
|
||||
will not be end-to-end encrypted, and thus not show a “padlock” with messages.
|
||||
Note that even if your contacts use Delta Chat on their account,
|
||||
they might also use a non-Autocrypt e-mail app on that account
|
||||
which then may cause intermittently unencrypted messages.
|
||||
Replying unencrypted to unencrypted messages is mandated by Autocrypt
|
||||
to prevent unreadable messages on the side of your contacts
|
||||
and their non-Autocrypt e-mail app.</p>
|
||||
|
||||
<h3 id="cómo-puedo-obtener-un-chat-cifrado-de-extremo-a-extremo-con-un-contacto-de-delta-chat-que-a-veces-utiliza-webmail-u-otra-aplicación-de-correo-electrónico-no-autocrypt">
|
||||
|
||||
|
||||
¿Cómo puedo obtener un chat cifrado de extremo a extremo con un contacto de Delta Chat que a veces utiliza webmail u otra aplicación de correo electrónico no Autocrypt? <a href="#cómo-puedo-obtener-un-chat-cifrado-de-extremo-a-extremo-con-un-contacto-de-delta-chat-que-a-veces-utiliza-webmail-u-otra-aplicación-de-correo-electrónico-no-autocrypt" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Si necesitas un chat cifrado de extremo a extremo de forma segura con un contacto que está utilizando su cuenta tanto con Delta Chat como con aplicaciones no-Autocrypt (por ejemplo, webmail), lo mejor es configurar <a href="#howtoe2ee">cifrado de extremo a extremo garantizado con ellos</a> y luego crear un grupo cifrado de extremo a extremo garantizado con ustedes dos como miembros. En este chat de grupo, todos los mensajes estarán cifrados de extremo a extremo, incluso si el chat directo entre ustedes dos tiene una advertencia de <a href="#nocryptanymore">“… envió un mensaje desde otro dispositivo”</a>.</p>
|
||||
|
||||
<h3 id="cómo-puedo-asegurar-el-cifrado-de-extremo-a-extremo-y-la-eliminación-de-mensajes">
|
||||
|
||||
|
||||
¿Cómo puedo asegurar el cifrado de extremo a extremo y la eliminación de mensajes? <a href="#cómo-puedo-asegurar-el-cifrado-de-extremo-a-extremo-y-la-eliminación-de-mensajes" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>La mejor manera de asegurar que cada mensaje esté cifrado de extremo a extremo
|
||||
y que los metadatos se borren lo más rápido posible
|
||||
es <a href="#howtoe2ee">utilizando chats con cifrado de extremo a extremo garantizado</a>
|
||||
y activando la <a href="#ephemeralmsgs">desaparición de mensajes</a>.</p>
|
||||
|
||||
<p>Los chats con cifrado de extremo a extremo garantizado protegen contra ataques <a href="https://es.wikipedia.org/wiki/Ataque_de_intermediario">MITM</a>
|
||||
y al activar “mensajes efímeros” se borran los mensajes
|
||||
en el servidor después de un tiempo configurado por el usuario.</p>
|
||||
|
||||
<p>Si no necesitas una copia de tus mensajes en el servidor durante más tiempo,
|
||||
también puedes activar <a href="#delold">“eliminar mensajes del servidor automáticamente”</a>.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
|
||||
@@ -1140,45 +1022,35 @@ también puedes activar <a href="#delold">“eliminar mensajes del servidor auto
|
||||
|
||||
</h3>
|
||||
|
||||
<p>No, Delta Chat no soporta Perfect Forward Secrecy (PFS).
|
||||
Esto significa que si se filtra tu clave privada de descifrado de Delta Chat,
|
||||
y alguien ha recopilado tus mensajes previos en tránsito,
|
||||
podrán descifrarlos y leerlos utilizando la clave de descifrado filtrada.</p>
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>Ten en cuenta, sin embargo, que si alguien obtiene tus claves de descifrado,
|
||||
también podrán obtener tus mensajes,
|
||||
independientemente de si se implementa o no el Perfect Forward Secrecy.
|
||||
La situación típica en el mundo real para las claves de descifrado filtradas es la incautación del dispositivo,
|
||||
que discutimos en nuestra respuesta <a href="#device-seizure">sobre metadatos e incautación de dispositivos</a>.</p>
|
||||
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
|
||||
This means that if your Delta Chat private decryption key is leaked,
|
||||
and someone has collected your prior in-transit messages,
|
||||
they will be able to decrypt and read them using the leaked decryption key.</p>
|
||||
|
||||
<p>It is possible that Delta Chat evolves to support Perfect Forward Secrecy,
|
||||
because OpenPGP is just a container for encrypted messages
|
||||
but encryption key management (and thus key rotation or key “ratcheting”)
|
||||
could be organized in flexible ways.
|
||||
See <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouia’s PFS prototype</a>
|
||||
for existing experiments in the OpenPGP implementor community.</p>
|
||||
<p>Note however, that Forward Secrecy only increases your security
|
||||
if you delete messages or use ephemeral deletion timers.
|
||||
Otherwise, if anyone obtains your decryption keys,
|
||||
they are typically also able to get all your non-deleted messages
|
||||
and don’t need to decrypt any previously collected messages.</p>
|
||||
|
||||
<p>The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we also discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
|
||||
<h3 id="es-el-cifrado-de-extremo-a-extremo-de-delta-chat-tan-seguro-como-el-de-signal">
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
|
||||
|
||||
¿Es el cifrado de extremo a extremo de Delta Chat tan seguro como el de Signal? <a href="#es-el-cifrado-de-extremo-a-extremo-de-delta-chat-tan-seguro-como-el-de-signal" class="anchor"></a>
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>It depends on what is important to you.
|
||||
Delta Chat <a href="#pfs">does not support PFS</a> like Signal does
|
||||
but it provides <a href="#e2eeguarantee">guaranteed end-to-end encrypted chats</a>
|
||||
that are safe against compromised servers or corrupted networks.
|
||||
Signal and most other PFS-supporting messengers do not provide
|
||||
a practical scheme for protecting chat groups from network attacks
|
||||
which are arguably more worrisome
|
||||
than a potential attacker who seizes your phone and private encryption setup
|
||||
but somehow not your messages, yet has a full record of all
|
||||
past encrypted messages.</p>
|
||||
<p>Yes.</p>
|
||||
|
||||
<p>In any case, Delta Chat’s end-to-end encryption uses a <a href="#openpgp-secure">secure subset of OpenPGP</a>
|
||||
which has been <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">independently security-audited</a>.</p>
|
||||
<p>We devised a forward secrecy scheme that withstood initial scrutiny from cryptographers and usable security experts.
|
||||
Our tentative scheme is designed to reliably work in federated messaging networks and with multi-device usage.
|
||||
However, an implementation has not been scheduled yet (as of Mid 2025).</p>
|
||||
|
||||
<h3 id="importkey">
|
||||
|
||||
@@ -1213,7 +1085,7 @@ from most recent to older:</p>
|
||||
<li>
|
||||
<p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of
|
||||
rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place.
|
||||
rPGP serves as the end-to-end encyption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
|
||||
rPGP serves as the end-to-end encryption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
|
||||
Two advisories were released related to the findings of this audit:</p>
|
||||
|
||||
<ul>
|
||||
@@ -1604,6 +1476,11 @@ a message, but also appears on the map.</li>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Note:
|
||||
Changing email addresses is temporarily disabled
|
||||
because of ongoing changes to the DeltaChat core.
|
||||
It should be available again in a few months.</p>
|
||||
|
||||
<ol>
|
||||
<li>
|
||||
<p>Change your address in “Settings → Advanced → Password and Account” and
|
||||
|
||||
@@ -36,27 +36,23 @@
|
||||
<li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#encryption-and-security">Encryption and Security</a>
|
||||
<li><a href="#e2ee">Encryption and Security</a>
|
||||
<ul>
|
||||
<li><a href="#which-standards-are-used-for-end-to-end-encryption">Which standards are used for end-to-end encryption?</a></li>
|
||||
<li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I get guaranteed end-to-end encryption and green checkmarks?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark and “guaranteed end-to-end encryption” mean?</a></li>
|
||||
<li><a href="#nocryptanymore">A contact “sent a message from another device”, what can i do?</a></li>
|
||||
<li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
|
||||
<li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li>
|
||||
<li><a href="#openpgp-secure">Is OpenPGP secure?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end -encryption?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
|
||||
<li><a href="#is-delta-chat-vulnerable-to-efail">Is Delta Chat vulnerable to EFAIL?</a></li>
|
||||
<li><a href="#tls">Is a message exposed in cleartext if end-to-end encryption is not available?</a></li>
|
||||
<li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
|
||||
<li><a href="#message-metadata">How does Delta Chat protect metadata in messages?</a></li>
|
||||
<li><a href="#device-seizure">How to protect metadata and contacts when a device is seized?</a></li>
|
||||
<li><a href="#how-can-i-check-encryption-information">How can i check encryption information?</a></li>
|
||||
<li><a href="#how-can-i-check-the-encryption-status-of-messages">How can I check the encryption status of messages?</a></li>
|
||||
<li><a href="#why-do-i-see-unencrypted-messages">Why do I see unencrypted messages?</a></li>
|
||||
<li><a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app?</a></li>
|
||||
<li><a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion">How can I ensure message end-to-end encryption and deletion?</a></li>
|
||||
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
|
||||
<li><a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">Is end-to-end encryption of Delta Chat as safe as Signal?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#importkey">Puis-je ré-utiliser ma clé privée existante ?</a></li>
|
||||
<li><a href="#security-audits">Est-ce qu’un audit indépendant des failles de sécurité a été réalisé sur Delta Chat ?</a></li>
|
||||
</ul>
|
||||
@@ -700,10 +696,10 @@ that achieves “instant delivery” of messages for all chatmail servers
|
||||
including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>.
|
||||
Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p>
|
||||
|
||||
<h2 id="encryption-and-security">
|
||||
<h2 id="e2ee">
|
||||
|
||||
|
||||
Encryption and Security <a href="#encryption-and-security" class="anchor"></a>
|
||||
Encryption and Security <a href="#e2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h2>
|
||||
@@ -716,18 +712,26 @@ Welcome to the power of the interoperable and massive chatmail and e-mail system
|
||||
|
||||
</h3>
|
||||
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption with contacts and group chats.
|
||||
Autocrypt uses a limited and <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>.
|
||||
End-to-End encrypted messages are marked with a padlock
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
|
||||
<p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
|
||||
to provide automatic end-to-end encryption using these protocols:</p>
|
||||
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
|
||||
are used for establishing chats with guaranteed end-to-end encryption
|
||||
which protects against network attacks and compromised servers.
|
||||
Chats marked with a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
guarantee end-to-end encrypted messages.</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
|
||||
to exchange encryption setup information through QR-code scanning or “invite links”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption between contacts and all members of a group chat.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
|
||||
chat</a>
|
||||
enables receivers to use end-to-end encryption with the contact.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
|
||||
|
||||
<h3 id="whene2e">
|
||||
|
||||
@@ -737,28 +741,37 @@ guarantee end-to-end encrypted messages.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>All end-to-end encrypted messages carry a padlock:</p>
|
||||
|
||||
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p>
|
||||
|
||||
<p>End-to-end encryption is guaranteed if there is a green checkmark next to the chat title:</p>
|
||||
|
||||
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
|
||||
<p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
|
||||
Since the Delta Chat Version 2 release series (July 2025)
|
||||
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
<h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
|
||||
|
||||
|
||||
How can I get guaranteed end-to-end encryption and green checkmarks? <a href="#howtoe2ee" class="anchor"></a>
|
||||
Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If you have a second communication channel with your chat partner,
|
||||
like a video chat or a different messenger,
|
||||
you can generate an invite link.</p>
|
||||
<p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
|
||||
it is impossible to receive or send messages without end-to-end encryption.</p>
|
||||
|
||||
<p>If you are together in person,
|
||||
you can show a QR code to your chat partner.</p>
|
||||
<p>If you instead create a profile using a classic e-mail server,
|
||||
you can send and receive messages without end-to-end encryption.
|
||||
Such messages lacking end-to-end encryption are marked with an e-mail icon
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
|
||||
|
||||
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You can send an invite link through another private chat,
|
||||
show an invitation QR code when next to each other or in a video call,
|
||||
or click on a “contact” that was shared in a chat.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
@@ -767,141 +780,60 @@ tap the chat group title to see its member list,
|
||||
and select “QR Invite code”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
tap the QR Code icon <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
|
||||
on the Delta Chat app main screen.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Let your chat partner scan the QR image
|
||||
<p>Ask your chat partner to scan the QR image
|
||||
with their Delta Chat app,
|
||||
or click “Copy” or “Share” to create an invite link
|
||||
and share it with your chat partner.</p>
|
||||
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">Secure-Join network messages are exchanged</a> between both devices.</p>
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>If both devices are online,
|
||||
both sides will eventually see a (group or direct) chat with a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
next to the title.</p>
|
||||
<p>If both sides are online, they will soon see a (group or direct) chat
|
||||
and can start messaging securely.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>If one of the devices is offline, the green checkmarks will only
|
||||
appear later when the device is internet-connected again
|
||||
and the Secure-Join network protocol completed.</p>
|
||||
<p>If one side is offline or in bad network,
|
||||
the ability to chat is delayed until connectivity is restored.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Congratulations!
|
||||
You now will automatically use guaranteed end-to-end encryption
|
||||
with this contact and both of you can add each other to green-checkmarked groups
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />,
|
||||
thereby automatically spreading guaranteed end-to-end encryption among its members.</p>
|
||||
You now will automatically use end-to-end encryption
|
||||
with this contact.
|
||||
If you add each other to chat groups,
|
||||
end-to-end encryption will be established among all members.</p>
|
||||
|
||||
<h3 id="e2eeguarantee">
|
||||
|
||||
|
||||
What does the green checkmark and “guaranteed end-to-end encryption” mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Chat titles with green checkmarks
|
||||
<p>A contact profile might show a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
mean that all messages in the chat will be end-to-end encrypted
|
||||
and can not be read or altered by compromised e-mail servers or Internet providers.
|
||||
Joining green-checkmarked group chats
|
||||
safely spreads everybody’s encryption information (and green checkmarks)
|
||||
in a manner that guarantees end-to-end encryption in the group and among members.</p>
|
||||
|
||||
<p>Contact profiles with green checkmarks
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
mean that messaging a contact is currently guaranteed to be end-to-end encrypted.
|
||||
and an “Introduced by” line.
|
||||
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
|
||||
or was introduced by a another green-checkmarked contact.
|
||||
Introductions happen automatically when adding members to groups.
|
||||
Whoever adds a contact to a green-checkmarked group becomes an introducer
|
||||
to those members who didn’t yet know about the added contact.
|
||||
Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
|
||||
becomes an introducer.
|
||||
In a contact profile you can tap on the “Introduced by …” text repeatedly
|
||||
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
|
||||
|
||||
<p>Note that in a contact profile you may see and tap introducers
|
||||
but there is no green checkmark in the profile title.
|
||||
This usually means that the contact <a href="#nocryptanymore">“sent a message from another device”</a>.</p>
|
||||
|
||||
<p>For more in-depth discussion of “guaranteed end-to-end encryption”
|
||||
please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
|
||||
and specifically read about “Verified Groups”, the technical term
|
||||
of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p>
|
||||
|
||||
<h3 id="nocryptanymore">
|
||||
|
||||
|
||||
A contact “sent a message from another device”, what can i do? <a href="#nocryptanymore" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Your chat with a contact lost guaranteed end-to-end encryption.
|
||||
The green checkmark was removed for this chat and contact when you see this warning.
|
||||
<strong>If you find the sudden drop of guaranteed end-to-end encryption
|
||||
surprising for this contact then don’t accept the warning!</strong>
|
||||
Instead check with your contact through a second channel
|
||||
like a video call, other messenger or a phone call,
|
||||
to find out what happened.</p>
|
||||
|
||||
<p>If your contact actually caused the drop of guaranteed end-to-end encryption
|
||||
please see the next paragraphs for common reasons and their mitigations.
|
||||
Regardless, all other green-checkmarked chats remain guaranteed end-to-end encrypted
|
||||
even if the contact is a member there.</p>
|
||||
|
||||
<p><strong>Your contact is using Delta Chat on a second device (phone or laptop)</strong></p>
|
||||
|
||||
<p>If they have another device with a Delta Chat app running,
|
||||
they should remove the profile from the new device
|
||||
and add it <a href="#multiclient">as a second device as described here</a>.
|
||||
As soon as they message you afterwards, the warning will be gone
|
||||
and guaranteed encryption is established with both devices of your contact.</p>
|
||||
|
||||
<p><strong>Your contact reinstalled Delta Chat using their old account login</strong></p>
|
||||
|
||||
<p>If they have <a href="#backup">a backup file</a>,
|
||||
they should remove the profile from the new device
|
||||
and rather import the backup file to re-create their profile.
|
||||
As soon as they message you afterwards, the warning will be gone
|
||||
and guaranteed encryption is re-established for this contact.</p>
|
||||
|
||||
<p>If they don’t have a backup file, it’s best to perform a <a href="#howtoe2ee">QR scan</a>
|
||||
with your chat partner to re-establish guaranteed end-to-end encryption.</p>
|
||||
|
||||
<p><strong>Your contact sent a mail through a webmail interface or another e-mail app
|
||||
and will get back to using Delta Chat soon again.</strong></p>
|
||||
|
||||
<p>If you are sure that the contact sometimes uses webmail,
|
||||
or another mail app lacking end-to-end encryption,
|
||||
then you may accept the warning.
|
||||
As soon as your contact uses Delta Chat again,
|
||||
guaranteed end-to-end encryption will be automatically re-established.</p>
|
||||
|
||||
<p><strong>Your contact stopped using Delta Chat entirely</strong></p>
|
||||
|
||||
<p>Sometimes remaining in contact is more important than end-to-end encryption.
|
||||
<a href="#tls">“Transport Layer Encryption” (TLS)</a> may still meaningfully protect
|
||||
the confidentiality of your messages between your device and the e-mail server.
|
||||
But without end-to-end encryption you and your contact are trusting your e-mail server
|
||||
to not read or manipulate your messages, and to not hand them to third parties.</p>
|
||||
|
||||
<p>In any case, you can not do much else than accept the warning.
|
||||
Please also remove the contact from any active green-checkmarked group
|
||||
which you can find in “Chats in Common” in the Contact profile.
|
||||
This spares your contact from getting “unreadable” messages.</p>
|
||||
|
||||
<p>If the contact removed Delta Chat because of buggy or undesirable behaviour,
|
||||
please consider posting to our <a href="https://support.delta.chat">support forum</a>
|
||||
to help us identify and address common problems. Thanks!</p>
|
||||
|
||||
<h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted">
|
||||
|
||||
|
||||
@@ -926,8 +858,7 @@ and attachment metadata such as filenames.</p>
|
||||
</h3>
|
||||
|
||||
<p>Yes, Delta Chat uses a secure subset of OpenPGP
|
||||
and only displays a padlock security indicator on a message
|
||||
if the whole message is properly encrypted and signed.
|
||||
requiring the whole message to be properly encrypted and signed.
|
||||
For example, “Detached signatures” are not treated as secure.</p>
|
||||
|
||||
<p>OpenPGP is not insecure by itself.
|
||||
@@ -948,7 +879,7 @@ which was thankfully adopted in summer 2023.</p>
|
||||
<h3 id="openpgp-alternatives">
|
||||
|
||||
|
||||
Did you consider using alternatives to OpenPGP for end-to-end -encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -991,17 +922,15 @@ as defined by the Autocrypt Level 1 specification.</p>
|
||||
<h3 id="tls">
|
||||
|
||||
|
||||
Is a message exposed in cleartext if end-to-end encryption is not available? <a href="#tls" class="anchor"></a>
|
||||
Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Even if your messages are not guaranteed to be end-to-end encrypted,
|
||||
they are still protected from Internet providers like cell or cable companies.
|
||||
However, your and your recipient’s e-mail providers
|
||||
may read, analyze or even modify your messages,
|
||||
including any attachments,
|
||||
if they are not end-to-end encrypted.</p>
|
||||
<p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
|
||||
they are still protected from cell or cable companies who can not read or modify your e-mail messages.
|
||||
But both your and your recipient’s e-mail providers
|
||||
may read, analyze or modify your messages, including any attachments.</p>
|
||||
|
||||
<p>Delta Chat by default uses strict
|
||||
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a>
|
||||
@@ -1013,10 +942,6 @@ If the involved e-mail servers support <a href="https://datatracker.ietf.org/doc
|
||||
then transport encryption will be enforced between e-mail providers
|
||||
in which case Delta Chat communications will never be exposed in cleartext to the Internet
|
||||
even if the message was not end-to-end encrypted.</p>
|
||||
|
||||
<p>Note that <a href="#howtoe2ee">maintaining guaranteed end-to-end encryption</a> on top of TLS encryption
|
||||
provides pervasive safety between your and the recipient’s devices.
|
||||
Not even your e-mail or Internet provider will be able to read or modify your messages.</p>
|
||||
|
||||
<h3 id="message-metadata">
|
||||
|
||||
@@ -1079,74 +1004,6 @@ Delta Chat shows two fingerprints there.
|
||||
If the same fingerprints appear on your own and your contact’s device,
|
||||
the connection is safe.</p>
|
||||
|
||||
<h3 id="how-can-i-check-the-encryption-status-of-messages">
|
||||
|
||||
|
||||
How can I check the encryption status of messages? <a href="#how-can-i-check-the-encryption-status-of-messages" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>A little <strong>padlock</strong> in a message bubble denotes
|
||||
that the message was properly end-to-end encrypted from the given sender.
|
||||
If there is <strong>no padlock</strong>, the message was not properly end-to-end encrypted
|
||||
most likely because the sender uses an app or webmail interface
|
||||
without support for end-to-end–encryption.</p>
|
||||
|
||||
<h3 id="why-do-i-see-unencrypted-messages">
|
||||
|
||||
|
||||
Why do I see unencrypted messages? <a href="#why-do-i-see-unencrypted-messages" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If a contact uses a non-Autocrypt e-mail app,
|
||||
all messages involving this contact (in a group or 1:1 chat)
|
||||
will not be end-to-end encrypted, and thus not show a “padlock” with messages.
|
||||
Note that even if your contacts use Delta Chat on their account,
|
||||
they might also use a non-Autocrypt e-mail app on that account
|
||||
which then may cause intermittently unencrypted messages.
|
||||
Replying unencrypted to unencrypted messages is mandated by Autocrypt
|
||||
to prevent unreadable messages on the side of your contacts
|
||||
and their non-Autocrypt e-mail app.</p>
|
||||
|
||||
<h3 id="how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">
|
||||
|
||||
|
||||
How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app? <a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If you need a safely end-to-end encrypted chat with a contact
|
||||
who is using their e-mail account both with Delta Chat and non-Autocrypt apps (e.g. webmail),
|
||||
it’s best to setup <a href="#howtoe2ee">guaranteed end-to-end encryption with them</a>
|
||||
and then create a guaranteed end-to-end encrypted group chat with you two as members.
|
||||
In this group chat all messages will be end-to-end encrypted
|
||||
even if the direct chat between you two has a
|
||||
<a href="#nocryptanymore">“… sent a message from another device”</a> warning.</p>
|
||||
|
||||
<h3 id="how-can-i-ensure-message-end-to-end-encryption-and-deletion">
|
||||
|
||||
|
||||
How can I ensure message end-to-end encryption and deletion? <a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>The best way to ensure every message is end-to-end encrypted,
|
||||
and metadata deleted as quickly as possible
|
||||
is <a href="#howtoe2ee">using chats with guaranteed end-to-end encryption</a>
|
||||
and turning on <a href="#ephemeralmsgs">disappearing messages</a>.</p>
|
||||
|
||||
<p>Guaranteed end-to-end encrypted chats protect against <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM attacks</a>
|
||||
and turning on disappearing messages deletes the messages
|
||||
on the server after a user-configured time.</p>
|
||||
|
||||
<p>If you don’t need a longer-lived copy of your messages on the server,
|
||||
you can also turn on <a href="#delold">“delete messages from server automatically”</a>.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
|
||||
@@ -1155,45 +1012,35 @@ you can also turn on <a href="#delold">“delete messages from server automatica
|
||||
|
||||
</h3>
|
||||
|
||||
<p>No, Delta Chat doesn’t support Perfect Forward Secrecy (PFS).
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
|
||||
This means that if your Delta Chat private decryption key is leaked,
|
||||
and someone has collected your prior in-transit messages,
|
||||
they will be able to decrypt and read them using the leaked decryption key.</p>
|
||||
|
||||
<p>Note, however, that if anyone obtains to your decryption keys,
|
||||
they will typically also be able to obtain your messages,
|
||||
irrespective if Perfect Forward Secrecy is in place or not.
|
||||
The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
<p>Note however, that Forward Secrecy only increases your security
|
||||
if you delete messages or use ephemeral deletion timers.
|
||||
Otherwise, if anyone obtains your decryption keys,
|
||||
they are typically also able to get all your non-deleted messages
|
||||
and don’t need to decrypt any previously collected messages.</p>
|
||||
|
||||
<p>It is possible that Delta Chat evolves to support Perfect Forward Secrecy,
|
||||
because OpenPGP is just a container for encrypted messages
|
||||
but encryption key management (and thus key rotation or key “ratcheting”)
|
||||
could be organized in flexible ways.
|
||||
See <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouia’s PFS prototype</a>
|
||||
for existing experiments in the OpenPGP implementor community.</p>
|
||||
<p>The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we also discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
|
||||
<h3 id="is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
|
||||
|
||||
Is end-to-end encryption of Delta Chat as safe as Signal? <a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal" class="anchor"></a>
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>It depends on what is important to you.
|
||||
Delta Chat <a href="#pfs">does not support PFS</a> like Signal does
|
||||
but it provides <a href="#e2eeguarantee">guaranteed end-to-end encrypted chats</a>
|
||||
that are safe against compromised servers or corrupted networks.
|
||||
Signal and most other PFS-supporting messengers do not provide
|
||||
a practical scheme for protecting chat groups from network attacks
|
||||
which are arguably more worrisome
|
||||
than a potential attacker who seizes your phone and private encryption setup
|
||||
but somehow not your messages, yet has a full record of all
|
||||
past encrypted messages.</p>
|
||||
<p>Oui.</p>
|
||||
|
||||
<p>In any case, Delta Chat’s end-to-end encryption uses a <a href="#openpgp-secure">secure subset of OpenPGP</a>
|
||||
which has been <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">independently security-audited</a>.</p>
|
||||
<p>We devised a forward secrecy scheme that withstood initial scrutiny from cryptographers and usable security experts.
|
||||
Our tentative scheme is designed to reliably work in federated messaging networks and with multi-device usage.
|
||||
However, an implementation has not been scheduled yet (as of Mid 2025).</p>
|
||||
|
||||
<h3 id="importkey">
|
||||
|
||||
@@ -1228,7 +1075,7 @@ from most recent to older:</p>
|
||||
<li>
|
||||
<p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of
|
||||
rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place.
|
||||
rPGP serves as the end-to-end encyption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
|
||||
rPGP serves as the end-to-end encryption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
|
||||
Two advisories were released related to the findings of this audit:</p>
|
||||
|
||||
<ul>
|
||||
@@ -1589,6 +1436,11 @@ a message, but also appears on the map.</li>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Note:
|
||||
Changing email addresses is temporarily disabled
|
||||
because of ongoing changes to the DeltaChat core.
|
||||
It should be available again in a few months.</p>
|
||||
|
||||
<ol>
|
||||
<li>
|
||||
<p>Change your address in “Settings → Advanced → Password and Account” and
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 2.2 KiB |
@@ -36,27 +36,23 @@
|
||||
<li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#encryption-and-security">Encryption and Security</a>
|
||||
<li><a href="#e2ee">Encryption and Security</a>
|
||||
<ul>
|
||||
<li><a href="#which-standards-are-used-for-end-to-end-encryption">Which standards are used for end-to-end encryption?</a></li>
|
||||
<li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I get guaranteed end-to-end encryption and green checkmarks?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark and “guaranteed end-to-end encryption” mean?</a></li>
|
||||
<li><a href="#nocryptanymore">A contact “sent a message from another device”, what can i do?</a></li>
|
||||
<li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
|
||||
<li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li>
|
||||
<li><a href="#openpgp-secure">Is OpenPGP secure?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end -encryption?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
|
||||
<li><a href="#is-delta-chat-vulnerable-to-efail">Is Delta Chat vulnerable to EFAIL?</a></li>
|
||||
<li><a href="#tls">Is a message exposed in cleartext if end-to-end encryption is not available?</a></li>
|
||||
<li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
|
||||
<li><a href="#message-metadata">How does Delta Chat protect metadata in messages?</a></li>
|
||||
<li><a href="#device-seizure">How to protect metadata and contacts when a device is seized?</a></li>
|
||||
<li><a href="#how-can-i-check-encryption-information">How can i check encryption information?</a></li>
|
||||
<li><a href="#how-can-i-check-the-encryption-status-of-messages">How can I check the encryption status of messages?</a></li>
|
||||
<li><a href="#why-do-i-see-unencrypted-messages">Why do I see unencrypted messages?</a></li>
|
||||
<li><a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app?</a></li>
|
||||
<li><a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion">How can I ensure message end-to-end encryption and deletion?</a></li>
|
||||
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
|
||||
<li><a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">Is end-to-end encryption of Delta Chat as safe as Signal?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#importkey">Can I reuse my existing private key?</a></li>
|
||||
<li><a href="#security-audits">Was Delta Chat independently audited for security vulnerabilities?</a></li>
|
||||
</ul>
|
||||
@@ -726,10 +722,10 @@ that achieves “instant delivery” of messages for all chatmail servers
|
||||
including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>.
|
||||
Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p>
|
||||
|
||||
<h2 id="encryption-and-security">
|
||||
<h2 id="e2ee">
|
||||
|
||||
|
||||
Encryption and Security <a href="#encryption-and-security" class="anchor"></a>
|
||||
Encryption and Security <a href="#e2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h2>
|
||||
@@ -742,18 +738,26 @@ Welcome to the power of the interoperable and massive chatmail and e-mail system
|
||||
|
||||
</h3>
|
||||
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption with contacts and group chats.
|
||||
Autocrypt uses a limited and <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>.
|
||||
End-to-End encrypted messages are marked with a padlock
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
|
||||
<p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
|
||||
to provide automatic end-to-end encryption using these protocols:</p>
|
||||
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
|
||||
are used for establishing chats with guaranteed end-to-end encryption
|
||||
which protects against network attacks and compromised servers.
|
||||
Chats marked with a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
guarantee end-to-end encrypted messages.</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
|
||||
to exchange encryption setup information through QR-code scanning or “invite links”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption between contacts and all members of a group chat.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
|
||||
chat</a>
|
||||
enables receivers to use end-to-end encryption with the contact.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
|
||||
|
||||
<h3 id="whene2e">
|
||||
|
||||
@@ -763,28 +767,37 @@ guarantee end-to-end encrypted messages.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>All end-to-end encrypted messages carry a padlock:</p>
|
||||
|
||||
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p>
|
||||
|
||||
<p>End-to-end encryption is guaranteed if there is a green checkmark next to the chat title:</p>
|
||||
|
||||
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
|
||||
<p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
|
||||
Since the Delta Chat Version 2 release series (July 2025)
|
||||
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
<h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
|
||||
|
||||
|
||||
How can I get guaranteed end-to-end encryption and green checkmarks? <a href="#howtoe2ee" class="anchor"></a>
|
||||
Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If you have a second communication channel with your chat partner,
|
||||
like a video chat or a different messenger,
|
||||
you can generate an invite link.</p>
|
||||
<p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
|
||||
it is impossible to receive or send messages without end-to-end encryption.</p>
|
||||
|
||||
<p>If you are together in person,
|
||||
you can show a QR code to your chat partner.</p>
|
||||
<p>If you instead create a profile using a classic e-mail server,
|
||||
you can send and receive messages without end-to-end encryption.
|
||||
Such messages lacking end-to-end encryption are marked with an e-mail icon
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
|
||||
|
||||
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You can send an invite link through another private chat,
|
||||
show an invitation QR code when next to each other or in a video call,
|
||||
or click on a “contact” that was shared in a chat.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
@@ -793,141 +806,60 @@ tap the chat group title to see its member list,
|
||||
and select “QR Invite code”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
tap the QR Code icon <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
|
||||
on the Delta Chat app main screen.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Let your chat partner scan the QR image
|
||||
<p>Ask your chat partner to scan the QR image
|
||||
with their Delta Chat app,
|
||||
or click “Copy” or “Share” to create an invite link
|
||||
and share it with your chat partner.</p>
|
||||
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">Secure-Join network messages are exchanged</a> between both devices.</p>
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>If both devices are online,
|
||||
both sides will eventually see a (group or direct) chat with a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
next to the title.</p>
|
||||
<p>If both sides are online, they will soon see a (group or direct) chat
|
||||
and can start messaging securely.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>If one of the devices is offline, the green checkmarks will only
|
||||
appear later when the device is internet-connected again
|
||||
and the Secure-Join network protocol completed.</p>
|
||||
<p>If one side is offline or in bad network,
|
||||
the ability to chat is delayed until connectivity is restored.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Congratulations!
|
||||
You now will automatically use guaranteed end-to-end encryption
|
||||
with this contact and both of you can add each other to green-checkmarked groups
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />,
|
||||
thereby automatically spreading guaranteed end-to-end encryption among its members.</p>
|
||||
You now will automatically use end-to-end encryption
|
||||
with this contact.
|
||||
If you add each other to chat groups,
|
||||
end-to-end encryption will be established among all members.</p>
|
||||
|
||||
<h3 id="e2eeguarantee">
|
||||
|
||||
|
||||
What does the green checkmark and “guaranteed end-to-end encryption” mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Chat titles with green checkmarks
|
||||
<p>A contact profile might show a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
mean that all messages in the chat will be end-to-end encrypted
|
||||
and can not be read or altered by compromised e-mail servers or Internet providers.
|
||||
Joining green-checkmarked group chats
|
||||
safely spreads everybody’s encryption information (and green checkmarks)
|
||||
in a manner that guarantees end-to-end encryption in the group and among members.</p>
|
||||
|
||||
<p>Contact profiles with green checkmarks
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
mean that messaging a contact is currently guaranteed to be end-to-end encrypted.
|
||||
and an “Introduced by” line.
|
||||
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
|
||||
or was introduced by a another green-checkmarked contact.
|
||||
Introductions happen automatically when adding members to groups.
|
||||
Whoever adds a contact to a green-checkmarked group becomes an introducer
|
||||
to those members who didn’t yet know about the added contact.
|
||||
Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
|
||||
becomes an introducer.
|
||||
In a contact profile you can tap on the “Introduced by …” text repeatedly
|
||||
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
|
||||
|
||||
<p>Note that in a contact profile you may see and tap introducers
|
||||
but there is no green checkmark in the profile title.
|
||||
This usually means that the contact <a href="#nocryptanymore">“sent a message from another device”</a>.</p>
|
||||
|
||||
<p>For more in-depth discussion of “guaranteed end-to-end encryption”
|
||||
please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
|
||||
and specifically read about “Verified Groups”, the technical term
|
||||
of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p>
|
||||
|
||||
<h3 id="nocryptanymore">
|
||||
|
||||
|
||||
A contact “sent a message from another device”, what can i do? <a href="#nocryptanymore" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Your chat with a contact lost guaranteed end-to-end encryption.
|
||||
The green checkmark was removed for this chat and contact when you see this warning.
|
||||
<strong>If you find the sudden drop of guaranteed end-to-end encryption
|
||||
surprising for this contact then don’t accept the warning!</strong>
|
||||
Instead check with your contact through a second channel
|
||||
like a video call, other messenger or a phone call,
|
||||
to find out what happened.</p>
|
||||
|
||||
<p>If your contact actually caused the drop of guaranteed end-to-end encryption
|
||||
please see the next paragraphs for common reasons and their mitigations.
|
||||
Regardless, all other green-checkmarked chats remain guaranteed end-to-end encrypted
|
||||
even if the contact is a member there.</p>
|
||||
|
||||
<p><strong>Your contact is using Delta Chat on a second device (phone or laptop)</strong></p>
|
||||
|
||||
<p>If they have another device with a Delta Chat app running,
|
||||
they should remove the profile from the new device
|
||||
and add it <a href="#multiclient">as a second device as described here</a>.
|
||||
As soon as they message you afterwards, the warning will be gone
|
||||
and guaranteed encryption is established with both devices of your contact.</p>
|
||||
|
||||
<p><strong>Your contact reinstalled Delta Chat using their old account login</strong></p>
|
||||
|
||||
<p>If they have <a href="#backup">a backup file</a>,
|
||||
they should remove the profile from the new device
|
||||
and rather import the backup file to re-create their profile.
|
||||
As soon as they message you afterwards, the warning will be gone
|
||||
and guaranteed encryption is re-established for this contact.</p>
|
||||
|
||||
<p>If they don’t have a backup file, it’s best to perform a <a href="#howtoe2ee">QR scan</a>
|
||||
with your chat partner to re-establish guaranteed end-to-end encryption.</p>
|
||||
|
||||
<p><strong>Your contact sent a mail through a webmail interface or another e-mail app
|
||||
and will get back to using Delta Chat soon again.</strong></p>
|
||||
|
||||
<p>If you are sure that the contact sometimes uses webmail,
|
||||
or another mail app lacking end-to-end encryption,
|
||||
then you may accept the warning.
|
||||
As soon as your contact uses Delta Chat again,
|
||||
guaranteed end-to-end encryption will be automatically re-established.</p>
|
||||
|
||||
<p><strong>Your contact stopped using Delta Chat entirely</strong></p>
|
||||
|
||||
<p>Sometimes remaining in contact is more important than end-to-end encryption.
|
||||
<a href="#tls">“Transport Layer Encryption” (TLS)</a> may still meaningfully protect
|
||||
the confidentiality of your messages between your device and the e-mail server.
|
||||
But without end-to-end encryption you and your contact are trusting your e-mail server
|
||||
to not read or manipulate your messages, and to not hand them to third parties.</p>
|
||||
|
||||
<p>In any case, you can not do much else than accept the warning.
|
||||
Please also remove the contact from any active green-checkmarked group
|
||||
which you can find in “Chats in Common” in the Contact profile.
|
||||
This spares your contact from getting “unreadable” messages.</p>
|
||||
|
||||
<p>If the contact removed Delta Chat because of buggy or undesirable behaviour,
|
||||
please consider posting to our <a href="https://support.delta.chat">support forum</a>
|
||||
to help us identify and address common problems. Thanks!</p>
|
||||
|
||||
<h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted">
|
||||
|
||||
|
||||
@@ -952,8 +884,7 @@ and attachment metadata such as filenames.</p>
|
||||
</h3>
|
||||
|
||||
<p>Yes, Delta Chat uses a secure subset of OpenPGP
|
||||
and only displays a padlock security indicator on a message
|
||||
if the whole message is properly encrypted and signed.
|
||||
requiring the whole message to be properly encrypted and signed.
|
||||
For example, “Detached signatures” are not treated as secure.</p>
|
||||
|
||||
<p>OpenPGP is not insecure by itself.
|
||||
@@ -974,7 +905,7 @@ which was thankfully adopted in summer 2023.</p>
|
||||
<h3 id="openpgp-alternatives">
|
||||
|
||||
|
||||
Did you consider using alternatives to OpenPGP for end-to-end -encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -1017,17 +948,15 @@ as defined by the Autocrypt Level 1 specification.</p>
|
||||
<h3 id="tls">
|
||||
|
||||
|
||||
Is a message exposed in cleartext if end-to-end encryption is not available? <a href="#tls" class="anchor"></a>
|
||||
Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Even if your messages are not guaranteed to be end-to-end encrypted,
|
||||
they are still protected from Internet providers like cell or cable companies.
|
||||
However, your and your recipient’s e-mail providers
|
||||
may read, analyze or even modify your messages,
|
||||
including any attachments,
|
||||
if they are not end-to-end encrypted.</p>
|
||||
<p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
|
||||
they are still protected from cell or cable companies who can not read or modify your e-mail messages.
|
||||
But both your and your recipient’s e-mail providers
|
||||
may read, analyze or modify your messages, including any attachments.</p>
|
||||
|
||||
<p>Delta Chat by default uses strict
|
||||
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a>
|
||||
@@ -1039,10 +968,6 @@ If the involved e-mail servers support <a href="https://datatracker.ietf.org/doc
|
||||
then transport encryption will be enforced between e-mail providers
|
||||
in which case Delta Chat communications will never be exposed in cleartext to the Internet
|
||||
even if the message was not end-to-end encrypted.</p>
|
||||
|
||||
<p>Note that <a href="#howtoe2ee">maintaining guaranteed end-to-end encryption</a> on top of TLS encryption
|
||||
provides pervasive safety between your and the recipient’s devices.
|
||||
Not even your e-mail or Internet provider will be able to read or modify your messages.</p>
|
||||
|
||||
<h3 id="message-metadata">
|
||||
|
||||
@@ -1105,74 +1030,6 @@ Delta Chat shows two fingerprints there.
|
||||
If the same fingerprints appear on your own and your contact’s device,
|
||||
the connection is safe.</p>
|
||||
|
||||
<h3 id="how-can-i-check-the-encryption-status-of-messages">
|
||||
|
||||
|
||||
How can I check the encryption status of messages? <a href="#how-can-i-check-the-encryption-status-of-messages" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>A little <strong>padlock</strong> in a message bubble denotes
|
||||
that the message was properly end-to-end encrypted from the given sender.
|
||||
If there is <strong>no padlock</strong>, the message was not properly end-to-end encrypted
|
||||
most likely because the sender uses an app or webmail interface
|
||||
without support for end-to-end–encryption.</p>
|
||||
|
||||
<h3 id="why-do-i-see-unencrypted-messages">
|
||||
|
||||
|
||||
Why do I see unencrypted messages? <a href="#why-do-i-see-unencrypted-messages" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If a contact uses a non-Autocrypt e-mail app,
|
||||
all messages involving this contact (in a group or 1:1 chat)
|
||||
will not be end-to-end encrypted, and thus not show a “padlock” with messages.
|
||||
Note that even if your contacts use Delta Chat on their account,
|
||||
they might also use a non-Autocrypt e-mail app on that account
|
||||
which then may cause intermittently unencrypted messages.
|
||||
Replying unencrypted to unencrypted messages is mandated by Autocrypt
|
||||
to prevent unreadable messages on the side of your contacts
|
||||
and their non-Autocrypt e-mail app.</p>
|
||||
|
||||
<h3 id="how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">
|
||||
|
||||
|
||||
How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app? <a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If you need a safely end-to-end encrypted chat with a contact
|
||||
who is using their e-mail account both with Delta Chat and non-Autocrypt apps (e.g. webmail),
|
||||
it’s best to setup <a href="#howtoe2ee">guaranteed end-to-end encryption with them</a>
|
||||
and then create a guaranteed end-to-end encrypted group chat with you two as members.
|
||||
In this group chat all messages will be end-to-end encrypted
|
||||
even if the direct chat between you two has a
|
||||
<a href="#nocryptanymore">“… sent a message from another device”</a> warning.</p>
|
||||
|
||||
<h3 id="how-can-i-ensure-message-end-to-end-encryption-and-deletion">
|
||||
|
||||
|
||||
How can I ensure message end-to-end encryption and deletion? <a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>The best way to ensure every message is end-to-end encrypted,
|
||||
and metadata deleted as quickly as possible
|
||||
is <a href="#howtoe2ee">using chats with guaranteed end-to-end encryption</a>
|
||||
and turning on <a href="#ephemeralmsgs">disappearing messages</a>.</p>
|
||||
|
||||
<p>Guaranteed end-to-end encrypted chats protect against <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM attacks</a>
|
||||
and turning on disappearing messages deletes the messages
|
||||
on the server after a user-configured time.</p>
|
||||
|
||||
<p>If you don’t need a longer-lived copy of your messages on the server,
|
||||
you can also turn on <a href="#delold">“delete messages from server automatically”</a>.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
|
||||
@@ -1181,45 +1038,35 @@ you can also turn on <a href="#delold">“delete messages from server automatica
|
||||
|
||||
</h3>
|
||||
|
||||
<p>No, Delta Chat doesn’t support Perfect Forward Secrecy (PFS).
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
|
||||
This means that if your Delta Chat private decryption key is leaked,
|
||||
and someone has collected your prior in-transit messages,
|
||||
they will be able to decrypt and read them using the leaked decryption key.</p>
|
||||
|
||||
<p>Note, however, that if anyone obtains to your decryption keys,
|
||||
they will typically also be able to obtain your messages,
|
||||
irrespective if Perfect Forward Secrecy is in place or not.
|
||||
The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
<p>Note however, that Forward Secrecy only increases your security
|
||||
if you delete messages or use ephemeral deletion timers.
|
||||
Otherwise, if anyone obtains your decryption keys,
|
||||
they are typically also able to get all your non-deleted messages
|
||||
and don’t need to decrypt any previously collected messages.</p>
|
||||
|
||||
<p>It is possible that Delta Chat evolves to support Perfect Forward Secrecy,
|
||||
because OpenPGP is just a container for encrypted messages
|
||||
but encryption key management (and thus key rotation or key “ratcheting”)
|
||||
could be organized in flexible ways.
|
||||
See <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouia’s PFS prototype</a>
|
||||
for existing experiments in the OpenPGP implementor community.</p>
|
||||
<p>The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we also discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
|
||||
<h3 id="is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
|
||||
|
||||
Is end-to-end encryption of Delta Chat as safe as Signal? <a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal" class="anchor"></a>
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>It depends on what is important to you.
|
||||
Delta Chat <a href="#pfs">does not support PFS</a> like Signal does
|
||||
but it provides <a href="#e2eeguarantee">guaranteed end-to-end encrypted chats</a>
|
||||
that are safe against compromised servers or corrupted networks.
|
||||
Signal and most other PFS-supporting messengers do not provide
|
||||
a practical scheme for protecting chat groups from network attacks
|
||||
which are arguably more worrisome
|
||||
than a potential attacker who seizes your phone and private encryption setup
|
||||
but somehow not your messages, yet has a full record of all
|
||||
past encrypted messages.</p>
|
||||
<p>Yes.</p>
|
||||
|
||||
<p>In any case, Delta Chat’s end-to-end encryption uses a <a href="#openpgp-secure">secure subset of OpenPGP</a>
|
||||
which has been <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">independently security-audited</a>.</p>
|
||||
<p>We devised a forward secrecy scheme that withstood initial scrutiny from cryptographers and usable security experts.
|
||||
Our tentative scheme is designed to reliably work in federated messaging networks and with multi-device usage.
|
||||
However, an implementation has not been scheduled yet (as of Mid 2025).</p>
|
||||
|
||||
<h3 id="importkey">
|
||||
|
||||
@@ -1254,7 +1101,7 @@ from most recent to older:</p>
|
||||
<li>
|
||||
<p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of
|
||||
rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place.
|
||||
rPGP serves as the end-to-end encyption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
|
||||
rPGP serves as the end-to-end encryption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
|
||||
Two advisories were released related to the findings of this audit:</p>
|
||||
|
||||
<ul>
|
||||
@@ -1648,6 +1495,11 @@ would be done by the Delta Chat app.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Note:
|
||||
Changing email addresses is temporarily disabled
|
||||
because of ongoing changes to the DeltaChat core.
|
||||
It should be available again in a few months.</p>
|
||||
|
||||
<ol>
|
||||
<li>
|
||||
<p>Change your address in “Settings → Advanced → Password and Account” and
|
||||
|
||||
+119
-262
@@ -36,27 +36,23 @@
|
||||
<li><a href="#perché-delta-chat-si-integra-con-i-servizi-push-centralizzati-proprietari-di-applegoogle">Perché Delta Chat si integra con i servizi push centralizzati proprietari di Apple/Google?</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#crittografia-e-sicurezza">Crittografia e Sicurezza</a>
|
||||
<li><a href="#e2ee">Crittografia e Sicurezza</a>
|
||||
<ul>
|
||||
<li><a href="#quali-standards-vengono-utilizzati-per-la-crittografia-end-to-end">Quali standards vengono utilizzati per la crittografia end-to-end?</a></li>
|
||||
<li><a href="#whene2e">Come posso sapere se i messaggi sono crittografati end-to-end?</a></li>
|
||||
<li><a href="#howtoe2ee">Come posso ottenere la crittografia end-to-end garantita e i segni di spunta verdi?</a></li>
|
||||
<li><a href="#e2eeguarantee">Cosa significano il segno di spunta verde e la “crittografia end-to-end garantita”?</a></li>
|
||||
<li><a href="#nocryptanymore">Un contatto “ha inviato un messaggio da un altro dispositivo”, cosa posso fare?</a></li>
|
||||
<li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
|
||||
<li><a href="#gli-allegati-immagini-file-audio-ecc-sono-crittografati-end-to-end">Gli allegati (immagini, file, audio, ecc.) sono crittografati end-to-end?</a></li>
|
||||
<li><a href="#openpgp-secure">OpenPGP è sicuro?</a></li>
|
||||
<li><a href="#openpgp-alternative">Avete considerato l’utilizzo di alternative a OpenPGP per la crittografia end-to-end?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
|
||||
<li><a href="#delta-chat-è-vulnerabile-agli-efail">Delta Chat è vulnerabile agli EFAIL?</a></li>
|
||||
<li><a href="#tls">Un messaggio viene esposto in chiaro se la crittografia end-to-end non è disponibile?</a></li>
|
||||
<li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
|
||||
<li><a href="#message-metadata">In che modo Delta Chat protegge i metadati nei messaggi?</a></li>
|
||||
<li><a href="#device-seizure">Come proteggere i metadati e contatti quando un dispositivo viene sequestrato?</a></li>
|
||||
<li><a href="#come-posso-verificare-le-informazioni-di-crittografia">Come posso verificare le informazioni di crittografia?</a></li>
|
||||
<li><a href="#come-posso-verificare-lo-stato-di-crittografia-dei-messaggi">Come posso verificare lo stato di crittografia dei messaggi?</a></li>
|
||||
<li><a href="#perché-vedo-messaggi-non-crittografati">Perché vedo messaggi non crittografati?</a></li>
|
||||
<li><a href="#come-posso-ottenere-una-chat-crittografata-end-to-end-con-un-contatto-delta-chat-che-a-volte-utilizza-la-webmail-o-unaltra-app-e-mail-non-autocrypt">Come posso ottenere una chat crittografata end-to-end con un contatto Delta Chat che a volte utilizza la webmail o un’altra app e-mail non Autocrypt?</a></li>
|
||||
<li><a href="#come-posso-garantire-la-crittografia-e-leliminazione-end-to-end-dei-messaggi">Come posso garantire la crittografia e l’eliminazione end-to-end dei messaggi?</a></li>
|
||||
<li><a href="#pfs">Delta Chat supporta Perfect Forward Secrecy?</a></li>
|
||||
<li><a href="#la-crittografia-end-to-end-di-delta-chat-è-sicura-quanto-quella-di-signal">La crittografia end-to-end di Delta Chat è sicura quanto quella di Signal?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#importkey">Posso riutilizzare la mia chiave privata esistente?</a></li>
|
||||
<li><a href="#security-audits">Delta Chat è stata verificata in modo indipendente per le vulnerabilità di sicurezza?</a></li>
|
||||
</ul>
|
||||
@@ -90,7 +86,7 @@
|
||||
<ul>
|
||||
<li><a href="#di-quali-autorizzazioni-ha-bisogno-delta-chat">Di quali autorizzazioni ha bisogno Delta Chat?</a></li>
|
||||
<li><a href="#delta-chat-funziona-con-il-mio-fornitore-e-mail">Delta Chat funziona con il <em>mio</em> fornitore e-mail?</a></li>
|
||||
<li><a href="#i-want-to-manage-my-own-server-for-delta-chat-what-do-you-recommend">I want to manage my own server for Delta Chat. What do you recommend?</a></li>
|
||||
<li><a href="#vorrei-gestire-il-mio-server-per-delta-chat-cosa-mi-consigliate">Vorrei gestire il mio server per Delta Chat. Cosa mi consigliate?</a></li>
|
||||
<li><a href="#perché-devo-inserire-la-mia-password-e-mail-in-delta-chat-è-sicuro">Perché devo inserire la mia password E-Mail in Delta Chat? È sicuro?</a></li>
|
||||
<li><a href="#quali-messaggi-vengono-mostrati-in-delta-chat">Quali messaggi vengono mostrati in Delta Chat?</a></li>
|
||||
<li><a href="#delta-chat-supporta-le-e-mail-html">Delta Chat supporta le e-mail HTML?</a></li>
|
||||
@@ -719,10 +715,10 @@ che consente la “consegna istantanea” dei messaggi a tutti i server chatmail
|
||||
incluso uno potenziale <a href="https://delta.chat/chatmail#selfhosted">potresti configurarlo tu stesso senza la nostra autorizzazione</a>.
|
||||
Benvenuti nella potenza del sistema interoperabile e massiccio di chatmail ed e-mail :)</p>
|
||||
|
||||
<h2 id="crittografia-e-sicurezza">
|
||||
<h2 id="e2ee">
|
||||
|
||||
|
||||
Crittografia e Sicurezza <a href="#crittografia-e-sicurezza" class="anchor"></a>
|
||||
Crittografia e Sicurezza <a href="#e2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h2>
|
||||
@@ -735,15 +731,26 @@ Benvenuti nella potenza del sistema interoperabile e massiccio di chatmail ed e-
|
||||
|
||||
</h3>
|
||||
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> viene utilizzato automaticamente per stabilire la crittografia end-to-end con contatti e chat di gruppo. Autocrypt utilizza un <a href="#openpgp-secure">sottoinsieme limitato e sicuro dello standard OpenPGP</a>. I messaggi crittografati end-to-end sono contrassegnati da un lucchetto
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
|
||||
<p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
|
||||
to provide automatic end-to-end encryption using these protocols:</p>
|
||||
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Protocolli Secure-Join</a>
|
||||
vengono utilizzati per stabilire chat con crittografia end-to-end garantita
|
||||
che protegge dagli attacchi di rete e dai server compromessi.
|
||||
Chat contrassegnata da un segno di spunta verde
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
garantisce messaggi crittografati end-to-end.</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
|
||||
to exchange encryption setup information through QR-code scanning or “invite links”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption between contacts and all members of a group chat.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
|
||||
chat</a>
|
||||
enables receivers to use end-to-end encryption with the contact.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
|
||||
|
||||
<h3 id="whene2e">
|
||||
|
||||
@@ -753,28 +760,37 @@ garantisce messaggi crittografati end-to-end.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Tutti i messaggi crittografati end-to-end portano un lucchetto:</p>
|
||||
|
||||
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p>
|
||||
|
||||
<p>La crittografia end-to-end è garantita se è presente un segno di spunta verde accanto al titolo della chat:</p>
|
||||
|
||||
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
|
||||
<p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
|
||||
Since the Delta Chat Version 2 release series (July 2025)
|
||||
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
<h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
|
||||
|
||||
|
||||
Come posso ottenere la crittografia end-to-end garantita e i segni di spunta verdi? <a href="#howtoe2ee" class="anchor"></a>
|
||||
Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Se disponi di un secondo canale di comunicazione con il tuo partner di chat,
|
||||
come una chat video o un altro messenger,
|
||||
puoi generare un link d’invito.</p>
|
||||
<p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
|
||||
it is impossible to receive or send messages without end-to-end encryption.</p>
|
||||
|
||||
<p>Se siete insieme di persona,
|
||||
puoi mostrare un codice QR al tuo partner di chat.</p>
|
||||
<p>If you instead create a profile using a classic e-mail server,
|
||||
you can send and receive messages without end-to-end encryption.
|
||||
Such messages lacking end-to-end encryption are marked with an e-mail icon
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
|
||||
|
||||
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You can send an invite link through another private chat,
|
||||
show an invitation QR code when next to each other or in a video call,
|
||||
or click on a “contact” that was shared in a chat.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
@@ -783,139 +799,60 @@ tocca il titolo del gruppo di chat per vedere l’elenco dei membri,
|
||||
e seleziona “Codice QR di Invito”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Per <strong>inviti diretti alla chat 1:1</strong>,
|
||||
tocca l’icona del codice QR <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
|
||||
nella schermata principale dell’app Delta Chat.</p>
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
tap the QR Code icon <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
|
||||
on the Delta Chat app main screen.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Lascia che il tuo partner di chat esegua la scansione dell’immagine QR
|
||||
con la loro app Delta Chat,
|
||||
oppure fai clic su “Copia” o “Condividi” per creare un collegamento di invito
|
||||
e condividilo con il tuo partner di chat.</p>
|
||||
<p>Ask your chat partner to scan the QR image
|
||||
with their Delta Chat app,
|
||||
or click “Copy” or “Share” to create an invite link
|
||||
and share it with your chat partner.</p>
|
||||
|
||||
<p>Ora attendi che <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">i messaggi di rete Secure-Join vengano scambiati</a> tra entrambi i dispositivi.</p>
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>Se entrambi i dispositivi sono online,
|
||||
entrambe le parti vedranno eventualmente una chat (di gruppo o diretta) con un segno di spunta verde
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
accanto al titolo.</p>
|
||||
<p>If both sides are online, they will soon see a (group or direct) chat
|
||||
and can start messaging securely.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Se uno dei dispositivi è offline, verranno visualizzati solo i segni di spunta verdi
|
||||
verranno visualizzati in seguito quando il dispositivo sarà nuovamente connesso a Internet
|
||||
e il protocollo di rete Secure-Join è stato completato.</p>
|
||||
<p>If one side is offline or in bad network,
|
||||
the ability to chat is delayed until connectivity is restored.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Congratulazioni!
|
||||
Ora utilizzerai automaticamente la crittografia end-to-end garantita
|
||||
con questo contatto potete aggiungervi a vicenda nei gruppi contrassegnati da un segno di spunta verde
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />,
|
||||
diffondendo così automaticamente la crittografia end-to-end garantita tra i suoi membri.</p>
|
||||
<p>Congratulations!
|
||||
You now will automatically use end-to-end encryption
|
||||
with this contact.
|
||||
If you add each other to chat groups,
|
||||
end-to-end encryption will be established among all members.</p>
|
||||
|
||||
<h3 id="e2eeguarantee">
|
||||
|
||||
|
||||
Cosa significano il segno di spunta verde e la “crittografia end-to-end garantita”? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Titoli di chat con segni di spunta verde
|
||||
<p>A contact profile might show a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
significa che tutti i messaggi nella chat saranno crittografati end-to-end
|
||||
e non possono essere letti o modificati da server di e-mail o provider Internet compromessi.
|
||||
Partecipare alle chat di gruppo contrassegnate da un segno di spunta verde diffonde in modo sicuro le informazioni di crittografia di tutti (e i segni di spunta verdi)
|
||||
in modo da garantire la crittografia end-to-end nel gruppo e tra i membri.</p>
|
||||
|
||||
<p>Profili di contatto con segni di spunta verdi
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
significa che attualmente è garantita la crittografia end-to-end dei messaggi a un contatto.
|
||||
Ogni contatto contrassegnato dal segno di spunta verde ha effettuato una <a href="#howtoe2ee">scansione QR</a> diretta con te
|
||||
o è stato presentato da un altro contatto contrassegnato da un segno di spunta verde.
|
||||
Le presentazioni avvengono automaticamente quando si aggiungono membri ai gruppi.
|
||||
Chi aggiunge un contatto a un gruppo contrassegnato da un segno di spunta verde diventa un introduttore
|
||||
a quei membri che non erano ancora a conoscenza del contatto aggiunto. In un profilo di contatto è possibile toccare ripetutamente il testo “Presentato da…”.
|
||||
fino ad arrivare a quello con cui hai effettuato direttamente una <a href="#howtoe2ee">scansione QR</a>.</p>
|
||||
|
||||
<p>Tieni presente che nel profilo di un contatto potresti vedere e toccare gli introduttori
|
||||
ma non c’è il segno di spunta verde nel titolo del profilo.
|
||||
Questo di solito significa che il contatto <a href="#nocryptanymore">“ha inviato un messaggio da un altro dispositivo”</a>.</p>
|
||||
and an “Introduced by” line.
|
||||
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
|
||||
or was introduced by a another green-checkmarked contact.
|
||||
Introductions happen automatically when adding members to groups.
|
||||
Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
|
||||
becomes an introducer.
|
||||
In a contact profile you can tap on the “Introduced by …” text repeatedly
|
||||
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
|
||||
|
||||
<p>Per una discussione più approfondita sulla “crittografia end-to-end garantita”
|
||||
consultare <a href="https://securejoin.delta.chat/en/latest/new.html">Protocolli Secure-Join</a>
|
||||
e leggi nello specifico i “Gruppi Verificati”, il termine tecnico
|
||||
di quelle che qui vengono chiamate chat “con segno di spunta verde” o “crittografate end-to-end garantite”.</p>
|
||||
|
||||
<h3 id="nocryptanymore">
|
||||
|
||||
|
||||
Un contatto “ha inviato un messaggio da un altro dispositivo”, cosa posso fare? <a href="#nocryptanymore" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>La tua chat con un contatto che ha perso la crittografia end-to-end garantita.
|
||||
Il segno di spunta verde è stato rimosso per questa chat e per questo contatto quando vedi questo avviso.
|
||||
<strong>Se riscontri l’improvvisa rimozione della crittografia end-to-end garantita
|
||||
inaspettatamente per questo contatto allora non accettare l’avviso!</strong>
|
||||
Verifica invece con il tuo contatto attraverso un secondo canale
|
||||
come una videochiamata, un altro messenger o una telefonata,
|
||||
per scoprire cosa è successo.</p>
|
||||
|
||||
<p>Se il tuo contatto ha effettivamente causato la rimozione della crittografia end-to-end garantita
|
||||
consultare i paragrafi successivi per i motivi comuni e le relative attenuazioni.
|
||||
Indipendentemente da ciò, tutte le altre chat contrassegnate da un segno di spunta verde rimangono garantite con crittografia end-to-end
|
||||
anche se il contatto è un membro.</p>
|
||||
|
||||
<p><strong>Il tuo contatto sta utilizzando Delta Chat su un secondo dispositivo (telefono o laptop)</strong></p>
|
||||
|
||||
<p>Se hanno un altro dispositivo con l’app Delta Chat in esecuzione,
|
||||
dovrebbero rimuovere il profilo dal nuovo dispositivo
|
||||
e aggiungerlo <a href="#multiclient">come secondo dispositivo come descritto qui</a>.
|
||||
Non appena ti invieranno un messaggio, l’avviso scomparirà
|
||||
e la crittografia garantita viene stabilita con entrambi i dispositivi del tuo contatto.</p>
|
||||
|
||||
<p><strong>Il tuo contatto ha reinstallato Delta Chat utilizzando il vecchio login del profilo</strong></p>
|
||||
|
||||
<p>Se hanno <a href="#backup">un file di backup</a>,
|
||||
dovrebbero rimuovere il profilo dal nuovo dispositivo
|
||||
e piuttosto importare il file di backup per ricreare il proprio profilo.
|
||||
Non appena ti invieranno un messaggio, l’avviso scomparirà
|
||||
e la crittografia garantita viene ristabilita per questo contatto.</p>
|
||||
|
||||
<p>Se non hanno un file di backup, è meglio eseguire una <a href="#howtoe2ee">scansione QR</a>
|
||||
con il tuo partner di chat per ristabilire la crittografia end-to-end garantita.</p>
|
||||
|
||||
<p><strong>Il tuo contatto ha inviato un’e-mail tramite un’interfaccia webmail o un’altra app di posta elettronica
|
||||
e presto tornerà a utilizzare Delta Chat.</strong></p>
|
||||
|
||||
<p>Se sei sicuro che il contatto a volte utilizza la webmail,
|
||||
o un’altra app di posta priva di crittografia end-to-end,
|
||||
allora puoi accettare l’avvertimento.
|
||||
Non appena il tuo contatto utilizzerà nuovamente Delta Chat,
|
||||
la crittografia end-to-end garantita verrà ristabilita automaticamente.</p>
|
||||
|
||||
<p><strong>Il tuo contatto ha smesso completamente di utilizzare Delta Chat</strong></p>
|
||||
|
||||
<p>A volte rimanere in contatto è più importante della crittografia end-to-end.
|
||||
<a href="#tls">“Transport Layer Encryption” (TLS)</a> può comunque proteggere in modo significativo
|
||||
la riservatezza dei tuoi messaggi tra il tuo dispositivo e il server di posta elettronica.
|
||||
Ma senza la crittografia end-to-end tu e il tuo contratto vi fidate del vostro server di posta elettronica
|
||||
a non leggere o manipolare i tuoi messaggi e a non trasmetterli a terzi.</p>
|
||||
|
||||
<p>In ogni caso, non puoi fare molto altro che accettare l’avvertimento.
|
||||
Rimuovi anche il contatto da qualsiasi gruppo attivo contrassegnato da un segno di spunta verde
|
||||
che puoi trovare in “Chat condivise” nel profilo dei contatti.
|
||||
Ciò evita che il tuo contatto riceva messaggi “illeggibili”.</p>
|
||||
|
||||
<p>Se il contatto ha rimosso Delta Chat a causa di bug o di comportamenti indesiderati,
|
||||
ti invitiamo a pubblicare post sul nostro <a href="https://support.delta.chat">forum di supporto</a>
|
||||
per aiutarci a identificare e affrontare i problemi comuni. Grazie!</p>
|
||||
|
||||
<h3 id="gli-allegati-immagini-file-audio-ecc-sono-crittografati-end-to-end">
|
||||
|
||||
|
||||
@@ -939,10 +876,9 @@ e metadati degli allegati come i nomi dei file.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Sì, Delta Chat utilizza un sottoinsieme sicuro di OpenPGP
|
||||
e visualizza solo un indicatore di sicurezza lucchetto su un messaggio
|
||||
se l’intero messaggio è crittografato e firmato correttamente.
|
||||
Ad esempio, le “Firme distaccate” non sono considerate sicure.</p>
|
||||
<p>Yes, Delta Chat uses a secure subset of OpenPGP
|
||||
requiring the whole message to be properly encrypted and signed.
|
||||
For example, “Detached signatures” are not treated as secure.</p>
|
||||
|
||||
<p>OpenPGP non è insicuro di per sé.
|
||||
La maggior parte dei problemi di sicurezza di OpenPGP discussi pubblicamentederivano in realtà da una cattiva usabilità o da cattive implementazioni di strumenti o app (o entrambi).
|
||||
@@ -957,10 +893,10 @@ e <a href="#security-audits">verificato per la sicurezza nel 2019 e nel 2024</a>
|
||||
per migliorare ulteriormente le caratteristiche di sicurezza implementando il
|
||||
<a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-crypto-refresh/">nuovo aggiornamento crittografico IETF OpenPGP</a> che per fortuna è stato adottato nell’estate 2023.</p>
|
||||
|
||||
<h3 id="openpgp-alternative">
|
||||
<h3 id="openpgp-alternatives">
|
||||
|
||||
|
||||
Avete considerato l’utilizzo di alternative a OpenPGP per la crittografia end-to-end? <a href="#openpgp-alternative" class="anchor"></a>
|
||||
Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -1003,17 +939,15 @@ come definito dalla specifica Autocrypt Level 1.</p>
|
||||
<h3 id="tls">
|
||||
|
||||
|
||||
Un messaggio viene esposto in chiaro se la crittografia end-to-end non è disponibile? <a href="#tls" class="anchor"></a>
|
||||
Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Anche se non è garantito che i tuoi messaggi siano crittografati end-to-end,
|
||||
sono ancora protetti dai fornitori di Internet come le società di telefonia mobile o via cavo.
|
||||
Tuttavia, i provider di posta elettronica tuoi e del destinatario
|
||||
potranno leggere, analizzare o addirittura modificare i tuoi messaggi,
|
||||
compresi eventuali allegati,
|
||||
se non sono crittografati end-to-end.</p>
|
||||
<p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
|
||||
they are still protected from cell or cable companies who can not read or modify your e-mail messages.
|
||||
But both your and your recipient’s e-mail providers
|
||||
may read, analyze or modify your messages, including any attachments.</p>
|
||||
|
||||
<p>Delta Chat per impostazione predefinita utilizza
|
||||
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">Crittografia TLS</a> rigorosa
|
||||
@@ -1025,10 +959,6 @@ Se i server e-mail coinvolti supportano <a href="https://datatracker.ietf.org/do
|
||||
verrà applicata la crittografia del trasporto tra i provider e-mail
|
||||
in tal caso le comunicazioni Delta Chat non verranno mai esposte in chiaro su Internet
|
||||
anche se il messaggio non sarà crittografato end-to-end.</p>
|
||||
|
||||
<p>Tieni presente che <a href="#howtoe2ee">mantenere la crittografia end-to-end garantita</a> oltre alla crittografia TLS
|
||||
fornisce una sicurezza pervasiva tra i tuoi dispositivi e quelli del destinatario.
|
||||
Nemmeno il tuo provider e-mail o Internet sarà in grado di leggere o modificare i tuoi messaggi.</p>
|
||||
|
||||
<h3 id="message-metadata">
|
||||
|
||||
@@ -1091,74 +1021,6 @@ Delta Chat mostra due impronte digitali.
|
||||
Se sul tuo dispositivo e su quello del tuo contatto vengono visualizzate le stesse impronte digitali,
|
||||
la connessione è sicura.</p>
|
||||
|
||||
<h3 id="come-posso-verificare-lo-stato-di-crittografia-dei-messaggi">
|
||||
|
||||
|
||||
Come posso verificare lo stato di crittografia dei messaggi? <a href="#come-posso-verificare-lo-stato-di-crittografia-dei-messaggi" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Un piccolo <strong>lucchetto</strong> in un fumetto denota
|
||||
che il messaggio è stato correttamente crittografato end-to-end dal mittente specificato.
|
||||
Se <strong>non è presente alcun lucchetto</strong>, il messaggio non è stato crittografato correttamente end-to-end
|
||||
molto probabilmente perché il mittente utilizza un’app o un’interfaccia webmail
|
||||
senza supporto per la crittografia end-to-end.</p>
|
||||
|
||||
<h3 id="perché-vedo-messaggi-non-crittografati">
|
||||
|
||||
|
||||
Perché vedo messaggi non crittografati? <a href="#perché-vedo-messaggi-non-crittografati" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Se un contatto utilizza un’app e-mail non Autocrypt,
|
||||
tutti i messaggi che coinvolgono questo contatto (in un gruppo o in una chat 1:1)
|
||||
non sarà crittografato end-to-end e quindi non mostrerà un “lucchetto” con i messaggi.
|
||||
Tieni presente che anche se i tuoi contatti utilizzano Delta Chat sul proprio profilo,
|
||||
potrebbero anche utilizzare un’app di posta elettronica non Autocrypt su quel profilo
|
||||
che quindi potrebbe causare messaggi non crittografati in modo intermittente.
|
||||
La risposta non crittografata a messaggi non crittografati è richiesta da Autocrypt
|
||||
per evitare messaggi illeggibili tra i tuoi contatti
|
||||
e la loro app e-mail non Autocrypt.</p>
|
||||
|
||||
<h3 id="come-posso-ottenere-una-chat-crittografata-end-to-end-con-un-contatto-delta-chat-che-a-volte-utilizza-la-webmail-o-unaltra-app-e-mail-non-autocrypt">
|
||||
|
||||
|
||||
Come posso ottenere una chat crittografata end-to-end con un contatto Delta Chat che a volte utilizza la webmail o un’altra app e-mail non Autocrypt? <a href="#come-posso-ottenere-una-chat-crittografata-end-to-end-con-un-contatto-delta-chat-che-a-volte-utilizza-la-webmail-o-unaltra-app-e-mail-non-autocrypt" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Se hai bisogno di una chat crittografata end-to-end sicura con un contatto
|
||||
chi utilizza il proprio profilo sia con Delta Chat che con app non Autocrypt (ad esempio webmail),
|
||||
è meglio configurare <a href="#howtoe2ee">la crittografia end-to-end garantita con loro</a>
|
||||
e quindi crea una chat di gruppo crittografata end-to-end garantita con voi due come membri.
|
||||
In questa chat di gruppo tutti i messaggi verranno crittografati end-to-end
|
||||
anche se la chat diretta tra voi due ha a
|
||||
<a href="#nocryptanymore">“… inviato un messaggio da un altro dispositivo”</a> avviso.</p>
|
||||
|
||||
<h3 id="come-posso-garantire-la-crittografia-e-leliminazione-end-to-end-dei-messaggi">
|
||||
|
||||
|
||||
Come posso garantire la crittografia e l’eliminazione end-to-end dei messaggi? <a href="#come-posso-garantire-la-crittografia-e-leliminazione-end-to-end-dei-messaggi" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Il modo migliore per garantire che ogni messaggio sia crittografato end-to-end,
|
||||
e i metadati vengono eliminati il più rapidamente possibile
|
||||
è <a href="#howtoe2ee">utilizzare chat con crittografia end-to-end garantita</a>
|
||||
e l’attivazione dei <a href="#ephemeralmsgs">messaggi a scomparsa</a>.</p>
|
||||
|
||||
<p>Le chat crittografate end-to-end garantiscono la protezione dagli <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">attacchi MITM</a>
|
||||
e l’attivazione dei “messaggi che scompaiono” elimina i messaggi
|
||||
sul server dopo un tempo configurato dall’utente.</p>
|
||||
|
||||
<p>Se non hai bisogno di una copia più longeva dei tuoi messaggi sul server,
|
||||
puoi anche attivare <a href="#delold">“elimina messaggi dal server”</a>.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
|
||||
@@ -1167,45 +1029,35 @@ puoi anche attivare <a href="#delold">“elimina messaggi dal server”</a>.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>No, Delta Chat non supporta Perfect Forward Secrecy (PFS).
|
||||
Ciò significa che se la tua chiave di cifratura privata Delta Chat viene divulgata,
|
||||
e qualcuno ha raccolto i tuoi precedenti messaggi in transito,
|
||||
sarà in grado di decifrarli e leggerli utilizzando la chiave di cifratura trapelata.</p>
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>Tieni presente, tuttavia, che se qualcuno ottiene le tue chiavi di decrittazione,
|
||||
in genere saranno anche in grado di ricevere i tuoi messaggi,
|
||||
indipendentemente dal fatto che Perfect Forward Secrecy sia attivo o meno.
|
||||
La tipica situazione reale in caso di fuga di chiavi di decrittazione è il sequestro del dispositivo
|
||||
di cui discutiamo nella nostra risposta <a href="#device-seizure">sui metadati e sul sequestro dei dispositivi</a>.</p>
|
||||
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
|
||||
This means that if your Delta Chat private decryption key is leaked,
|
||||
and someone has collected your prior in-transit messages,
|
||||
they will be able to decrypt and read them using the leaked decryption key.</p>
|
||||
|
||||
<p>È possibile che Delta Chat si evolva per supportare Perfect Forward Secrecy,
|
||||
perché OpenPGP è solo un contenitore per messaggi crittografati
|
||||
ma la gestione delle chiavi di crittografia (e quindi la rotazione delle chiavi o “cricchetto”)
|
||||
potrebbero essere organizzati in modo flessibile.
|
||||
Vedi <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">prototipo PFS di Seqouia</a>
|
||||
per gli esperimenti esistenti nella comunità degli implementatori di OpenPGP.</p>
|
||||
<p>Note however, that Forward Secrecy only increases your security
|
||||
if you delete messages or use ephemeral deletion timers.
|
||||
Otherwise, if anyone obtains your decryption keys,
|
||||
they are typically also able to get all your non-deleted messages
|
||||
and don’t need to decrypt any previously collected messages.</p>
|
||||
|
||||
<p>The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we also discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
|
||||
<h3 id="la-crittografia-end-to-end-di-delta-chat-è-sicura-quanto-quella-di-signal">
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
|
||||
|
||||
La crittografia end-to-end di Delta Chat è sicura quanto quella di Signal? <a href="#la-crittografia-end-to-end-di-delta-chat-è-sicura-quanto-quella-di-signal" class="anchor"></a>
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Dipende da cosa è importante per te.
|
||||
Delta Chat <a href="#pfs">non supporta PFS</a> come fa Signal
|
||||
ma fornisce <a href="#e2eeguarantee">chat crittografate end-to-end garantite</a>
|
||||
che sono sicuri contro server compromessi o reti danneggiate.
|
||||
Signal e la maggior parte degli altri servizi di messaggistica che supportano PFS non forniscono
|
||||
uno schema pratico per proteggere i gruppi di chat dagli attacchi di rete
|
||||
che sono probabilmente più preoccupanti
|
||||
di un potenziale utente malintenzionato che si impadronisce del tuo telefono e della configurazione di crittografia privata
|
||||
ma in qualche modo non i tuoi messaggi, ma ha un registro completo di tutti
|
||||
messaggi crittografati precedenti.</p>
|
||||
<p>Sì.</p>
|
||||
|
||||
<p>In ogni caso, la crittografia end-to-end di Delta Chat utilizza un <a href="#openpgp-secure">sottoinsieme sicuro di OpenPGP</a>
|
||||
che è stato <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">controllato in modo indipendente sulla sicurezza</a>.</p>
|
||||
<p>We devised a forward secrecy scheme that withstood initial scrutiny from cryptographers and usable security experts.
|
||||
Our tentative scheme is designed to reliably work in federated messaging networks and with multi-device usage.
|
||||
However, an implementation has not been scheduled yet (as of Mid 2025).</p>
|
||||
|
||||
<h3 id="importkey">
|
||||
|
||||
@@ -1631,6 +1483,11 @@ verrebbe eseguito dall’app Delta Chat.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Note:
|
||||
Changing email addresses is temporarily disabled
|
||||
because of ongoing changes to the DeltaChat core.
|
||||
It should be available again in a few months.</p>
|
||||
|
||||
<ol>
|
||||
<li>
|
||||
<p>Cambia il tuo indirizzo in “Impostazioni → Avanzate → Password e Profilo” e
|
||||
@@ -1715,19 +1572,19 @@ Tuttavia, alcuni provider necessitano di opzioni speciali per funzionare corrett
|
||||
vedi <a href="https://providers.delta.chat">Panoramica fornitore</a></li>
|
||||
</ul>
|
||||
|
||||
<h3 id="i-want-to-manage-my-own-server-for-delta-chat-what-do-you-recommend">
|
||||
<h3 id="vorrei-gestire-il-mio-server-per-delta-chat-cosa-mi-consigliate">
|
||||
|
||||
|
||||
I want to manage my own server for Delta Chat. What do you recommend? <a href="#i-want-to-manage-my-own-server-for-delta-chat-what-do-you-recommend" class="anchor"></a>
|
||||
Vorrei gestire il mio server per Delta Chat. Cosa mi consigliate? <a href="#vorrei-gestire-il-mio-server-per-delta-chat-cosa-mi-consigliate" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<ul>
|
||||
<li>Most mail servers will work well. But what we personally recommend is a
|
||||
chatmail relay server, as described <a href="https://delta.chat/en/2023-12-13-chatmail">in this
|
||||
blogpost</a>.</li>
|
||||
<li>You can find an <a href="https://github.com/chatmail/relay">installation guide on GitHub</a>.</li>
|
||||
<li>La maggior parte dei server di posta funzionerà bene. Ma quello che personalmente consigliamo è un
|
||||
server relay di chatmail, come descritto <a href="https://delta.chat/en/2023-12-13-chatmail">in questo
|
||||
articolo del blog</a>.</li>
|
||||
<li>Puoi trovare una <a href="https://github.com/chatmail/relay">guida all’installazione su GitHub</a>.</li>
|
||||
</ul>
|
||||
|
||||
<h3 id="perché-devo-inserire-la-mia-password-e-mail-in-delta-chat-è-sicuro">
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 2.2 KiB |
@@ -36,27 +36,23 @@
|
||||
<li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#beveiliging-en-versleuteling">Beveiliging en versleuteling</a>
|
||||
<li><a href="#e2ee">Beveiliging en versleuteling</a>
|
||||
<ul>
|
||||
<li><a href="#welke-standaarden-worden-gebruikt-bij-eind-tot-eindversleuteling">Welke standaarden worden gebruikt bij eind-tot-eindversleuteling?</a></li>
|
||||
<li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I get guaranteed end-to-end encryption and green checkmarks?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark and “guaranteed end-to-end encryption” mean?</a></li>
|
||||
<li><a href="#nocryptanymore">A contact “sent a message from another device”, what can i do?</a></li>
|
||||
<li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
|
||||
<li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li>
|
||||
<li><a href="#openpgp-secure">Is OpenPGP secure?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end -encryption?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
|
||||
<li><a href="#is-delta-chat-vulnerable-to-efail">Is Delta Chat vulnerable to EFAIL?</a></li>
|
||||
<li><a href="#tls">Is a message exposed in cleartext if end-to-end encryption is not available?</a></li>
|
||||
<li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
|
||||
<li><a href="#message-metadata">How does Delta Chat protect metadata in messages?</a></li>
|
||||
<li><a href="#device-seizure">How to protect metadata and contacts when a device is seized?</a></li>
|
||||
<li><a href="#how-can-i-check-encryption-information">How can i check encryption information?</a></li>
|
||||
<li><a href="#how-can-i-check-the-encryption-status-of-messages">How can I check the encryption status of messages?</a></li>
|
||||
<li><a href="#why-do-i-see-unencrypted-messages">Why do I see unencrypted messages?</a></li>
|
||||
<li><a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app?</a></li>
|
||||
<li><a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion">How can I ensure message end-to-end encryption and deletion?</a></li>
|
||||
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
|
||||
<li><a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">Is end-to-end encryption of Delta Chat as safe as Signal?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#importkey">Kan ik mijn bestaande privésleutel hergebruiken?</a></li>
|
||||
<li><a href="#security-audits">Heeft Delta Chat ooit onafhankelijke beveiligingscontroles ondergaan?</a></li>
|
||||
</ul>
|
||||
@@ -719,10 +715,10 @@ that achieves “instant delivery” of messages for all chatmail servers
|
||||
including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>.
|
||||
Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p>
|
||||
|
||||
<h2 id="beveiliging-en-versleuteling">
|
||||
<h2 id="e2ee">
|
||||
|
||||
|
||||
Beveiliging en versleuteling <a href="#beveiliging-en-versleuteling" class="anchor"></a>
|
||||
Beveiliging en versleuteling <a href="#e2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h2>
|
||||
@@ -735,18 +731,26 @@ Welcome to the power of the interoperable and massive chatmail and e-mail system
|
||||
|
||||
</h3>
|
||||
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption with contacts and group chats.
|
||||
Autocrypt uses a limited and <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>.
|
||||
End-to-End encrypted messages are marked with a padlock
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
|
||||
<p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
|
||||
to provide automatic end-to-end encryption using these protocols:</p>
|
||||
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
|
||||
are used for establishing chats with guaranteed end-to-end encryption
|
||||
which protects against network attacks and compromised servers.
|
||||
Chats marked with a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
guarantee end-to-end encrypted messages.</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
|
||||
to exchange encryption setup information through QR-code scanning or “invite links”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption between contacts and all members of a group chat.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
|
||||
chat</a>
|
||||
enables receivers to use end-to-end encryption with the contact.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
|
||||
|
||||
<h3 id="whene2e">
|
||||
|
||||
@@ -756,28 +760,37 @@ guarantee end-to-end encrypted messages.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>All end-to-end encrypted messages carry a padlock:</p>
|
||||
|
||||
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p>
|
||||
|
||||
<p>End-to-end encryption is guaranteed if there is a green checkmark next to the chat title:</p>
|
||||
|
||||
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
|
||||
<p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
|
||||
Since the Delta Chat Version 2 release series (July 2025)
|
||||
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
<h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
|
||||
|
||||
|
||||
How can I get guaranteed end-to-end encryption and green checkmarks? <a href="#howtoe2ee" class="anchor"></a>
|
||||
Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If you have a second communication channel with your chat partner,
|
||||
like a video chat or a different messenger,
|
||||
you can generate an invite link.</p>
|
||||
<p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
|
||||
it is impossible to receive or send messages without end-to-end encryption.</p>
|
||||
|
||||
<p>If you are together in person,
|
||||
you can show a QR code to your chat partner.</p>
|
||||
<p>If you instead create a profile using a classic e-mail server,
|
||||
you can send and receive messages without end-to-end encryption.
|
||||
Such messages lacking end-to-end encryption are marked with an e-mail icon
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
|
||||
|
||||
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You can send an invite link through another private chat,
|
||||
show an invitation QR code when next to each other or in a video call,
|
||||
or click on a “contact” that was shared in a chat.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
@@ -786,141 +799,60 @@ tap the chat group title to see its member list,
|
||||
and select “QR Invite code”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
tap the QR Code icon <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
|
||||
on the Delta Chat app main screen.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Let your chat partner scan the QR image
|
||||
<p>Ask your chat partner to scan the QR image
|
||||
with their Delta Chat app,
|
||||
or click “Copy” or “Share” to create an invite link
|
||||
and share it with your chat partner.</p>
|
||||
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">Secure-Join network messages are exchanged</a> between both devices.</p>
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>If both devices are online,
|
||||
both sides will eventually see a (group or direct) chat with a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
next to the title.</p>
|
||||
<p>If both sides are online, they will soon see a (group or direct) chat
|
||||
and can start messaging securely.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>If one of the devices is offline, the green checkmarks will only
|
||||
appear later when the device is internet-connected again
|
||||
and the Secure-Join network protocol completed.</p>
|
||||
<p>If one side is offline or in bad network,
|
||||
the ability to chat is delayed until connectivity is restored.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Congratulations!
|
||||
You now will automatically use guaranteed end-to-end encryption
|
||||
with this contact and both of you can add each other to green-checkmarked groups
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />,
|
||||
thereby automatically spreading guaranteed end-to-end encryption among its members.</p>
|
||||
You now will automatically use end-to-end encryption
|
||||
with this contact.
|
||||
If you add each other to chat groups,
|
||||
end-to-end encryption will be established among all members.</p>
|
||||
|
||||
<h3 id="e2eeguarantee">
|
||||
|
||||
|
||||
What does the green checkmark and “guaranteed end-to-end encryption” mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Chat titles with green checkmarks
|
||||
<p>A contact profile might show a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
mean that all messages in the chat will be end-to-end encrypted
|
||||
and can not be read or altered by compromised e-mail servers or Internet providers.
|
||||
Joining green-checkmarked group chats
|
||||
safely spreads everybody’s encryption information (and green checkmarks)
|
||||
in a manner that guarantees end-to-end encryption in the group and among members.</p>
|
||||
|
||||
<p>Contact profiles with green checkmarks
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
mean that messaging a contact is currently guaranteed to be end-to-end encrypted.
|
||||
and an “Introduced by” line.
|
||||
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
|
||||
or was introduced by a another green-checkmarked contact.
|
||||
Introductions happen automatically when adding members to groups.
|
||||
Whoever adds a contact to a green-checkmarked group becomes an introducer
|
||||
to those members who didn’t yet know about the added contact.
|
||||
Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
|
||||
becomes an introducer.
|
||||
In a contact profile you can tap on the “Introduced by …” text repeatedly
|
||||
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
|
||||
|
||||
<p>Note that in a contact profile you may see and tap introducers
|
||||
but there is no green checkmark in the profile title.
|
||||
This usually means that the contact <a href="#nocryptanymore">“sent a message from another device”</a>.</p>
|
||||
|
||||
<p>For more in-depth discussion of “guaranteed end-to-end encryption”
|
||||
please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
|
||||
and specifically read about “Verified Groups”, the technical term
|
||||
of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p>
|
||||
|
||||
<h3 id="nocryptanymore">
|
||||
|
||||
|
||||
A contact “sent a message from another device”, what can i do? <a href="#nocryptanymore" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Your chat with a contact lost guaranteed end-to-end encryption.
|
||||
The green checkmark was removed for this chat and contact when you see this warning.
|
||||
<strong>If you find the sudden drop of guaranteed end-to-end encryption
|
||||
surprising for this contact then don’t accept the warning!</strong>
|
||||
Instead check with your contact through a second channel
|
||||
like a video call, other messenger or a phone call,
|
||||
to find out what happened.</p>
|
||||
|
||||
<p>If your contact actually caused the drop of guaranteed end-to-end encryption
|
||||
please see the next paragraphs for common reasons and their mitigations.
|
||||
Regardless, all other green-checkmarked chats remain guaranteed end-to-end encrypted
|
||||
even if the contact is a member there.</p>
|
||||
|
||||
<p><strong>Your contact is using Delta Chat on a second device (phone or laptop)</strong></p>
|
||||
|
||||
<p>If they have another device with a Delta Chat app running,
|
||||
they should remove the profile from the new device
|
||||
and add it <a href="#multiclient">as a second device as described here</a>.
|
||||
As soon as they message you afterwards, the warning will be gone
|
||||
and guaranteed encryption is established with both devices of your contact.</p>
|
||||
|
||||
<p><strong>Your contact reinstalled Delta Chat using their old account login</strong></p>
|
||||
|
||||
<p>If they have <a href="#backup">a backup file</a>,
|
||||
they should remove the profile from the new device
|
||||
and rather import the backup file to re-create their profile.
|
||||
As soon as they message you afterwards, the warning will be gone
|
||||
and guaranteed encryption is re-established for this contact.</p>
|
||||
|
||||
<p>If they don’t have a backup file, it’s best to perform a <a href="#howtoe2ee">QR scan</a>
|
||||
with your chat partner to re-establish guaranteed end-to-end encryption.</p>
|
||||
|
||||
<p><strong>Your contact sent a mail through a webmail interface or another e-mail app
|
||||
and will get back to using Delta Chat soon again.</strong></p>
|
||||
|
||||
<p>If you are sure that the contact sometimes uses webmail,
|
||||
or another mail app lacking end-to-end encryption,
|
||||
then you may accept the warning.
|
||||
As soon as your contact uses Delta Chat again,
|
||||
guaranteed end-to-end encryption will be automatically re-established.</p>
|
||||
|
||||
<p><strong>Your contact stopped using Delta Chat entirely</strong></p>
|
||||
|
||||
<p>Sometimes remaining in contact is more important than end-to-end encryption.
|
||||
<a href="#tls">“Transport Layer Encryption” (TLS)</a> may still meaningfully protect
|
||||
the confidentiality of your messages between your device and the e-mail server.
|
||||
But without end-to-end encryption you and your contact are trusting your e-mail server
|
||||
to not read or manipulate your messages, and to not hand them to third parties.</p>
|
||||
|
||||
<p>In any case, you can not do much else than accept the warning.
|
||||
Please also remove the contact from any active green-checkmarked group
|
||||
which you can find in “Chats in Common” in the Contact profile.
|
||||
This spares your contact from getting “unreadable” messages.</p>
|
||||
|
||||
<p>If the contact removed Delta Chat because of buggy or undesirable behaviour,
|
||||
please consider posting to our <a href="https://support.delta.chat">support forum</a>
|
||||
to help us identify and address common problems. Thanks!</p>
|
||||
|
||||
<h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted">
|
||||
|
||||
|
||||
@@ -945,8 +877,7 @@ and attachment metadata such as filenames.</p>
|
||||
</h3>
|
||||
|
||||
<p>Yes, Delta Chat uses a secure subset of OpenPGP
|
||||
and only displays a padlock security indicator on a message
|
||||
if the whole message is properly encrypted and signed.
|
||||
requiring the whole message to be properly encrypted and signed.
|
||||
For example, “Detached signatures” are not treated as secure.</p>
|
||||
|
||||
<p>OpenPGP is not insecure by itself.
|
||||
@@ -967,7 +898,7 @@ which was thankfully adopted in summer 2023.</p>
|
||||
<h3 id="openpgp-alternatives">
|
||||
|
||||
|
||||
Did you consider using alternatives to OpenPGP for end-to-end -encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -1010,17 +941,15 @@ as defined by the Autocrypt Level 1 specification.</p>
|
||||
<h3 id="tls">
|
||||
|
||||
|
||||
Is a message exposed in cleartext if end-to-end encryption is not available? <a href="#tls" class="anchor"></a>
|
||||
Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Even if your messages are not guaranteed to be end-to-end encrypted,
|
||||
they are still protected from Internet providers like cell or cable companies.
|
||||
However, your and your recipient’s e-mail providers
|
||||
may read, analyze or even modify your messages,
|
||||
including any attachments,
|
||||
if they are not end-to-end encrypted.</p>
|
||||
<p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
|
||||
they are still protected from cell or cable companies who can not read or modify your e-mail messages.
|
||||
But both your and your recipient’s e-mail providers
|
||||
may read, analyze or modify your messages, including any attachments.</p>
|
||||
|
||||
<p>Delta Chat by default uses strict
|
||||
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a>
|
||||
@@ -1032,10 +961,6 @@ If the involved e-mail servers support <a href="https://datatracker.ietf.org/doc
|
||||
then transport encryption will be enforced between e-mail providers
|
||||
in which case Delta Chat communications will never be exposed in cleartext to the Internet
|
||||
even if the message was not end-to-end encrypted.</p>
|
||||
|
||||
<p>Note that <a href="#howtoe2ee">maintaining guaranteed end-to-end encryption</a> on top of TLS encryption
|
||||
provides pervasive safety between your and the recipient’s devices.
|
||||
Not even your e-mail or Internet provider will be able to read or modify your messages.</p>
|
||||
|
||||
<h3 id="message-metadata">
|
||||
|
||||
@@ -1098,74 +1023,6 @@ Delta Chat shows two fingerprints there.
|
||||
If the same fingerprints appear on your own and your contact’s device,
|
||||
the connection is safe.</p>
|
||||
|
||||
<h3 id="how-can-i-check-the-encryption-status-of-messages">
|
||||
|
||||
|
||||
How can I check the encryption status of messages? <a href="#how-can-i-check-the-encryption-status-of-messages" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>A little <strong>padlock</strong> in a message bubble denotes
|
||||
that the message was properly end-to-end encrypted from the given sender.
|
||||
If there is <strong>no padlock</strong>, the message was not properly end-to-end encrypted
|
||||
most likely because the sender uses an app or webmail interface
|
||||
without support for end-to-end–encryption.</p>
|
||||
|
||||
<h3 id="why-do-i-see-unencrypted-messages">
|
||||
|
||||
|
||||
Why do I see unencrypted messages? <a href="#why-do-i-see-unencrypted-messages" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If a contact uses a non-Autocrypt e-mail app,
|
||||
all messages involving this contact (in a group or 1:1 chat)
|
||||
will not be end-to-end encrypted, and thus not show a “padlock” with messages.
|
||||
Note that even if your contacts use Delta Chat on their account,
|
||||
they might also use a non-Autocrypt e-mail app on that account
|
||||
which then may cause intermittently unencrypted messages.
|
||||
Replying unencrypted to unencrypted messages is mandated by Autocrypt
|
||||
to prevent unreadable messages on the side of your contacts
|
||||
and their non-Autocrypt e-mail app.</p>
|
||||
|
||||
<h3 id="how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">
|
||||
|
||||
|
||||
How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app? <a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If you need a safely end-to-end encrypted chat with a contact
|
||||
who is using their e-mail account both with Delta Chat and non-Autocrypt apps (e.g. webmail),
|
||||
it’s best to setup <a href="#howtoe2ee">guaranteed end-to-end encryption with them</a>
|
||||
and then create a guaranteed end-to-end encrypted group chat with you two as members.
|
||||
In this group chat all messages will be end-to-end encrypted
|
||||
even if the direct chat between you two has a
|
||||
<a href="#nocryptanymore">“… sent a message from another device”</a> warning.</p>
|
||||
|
||||
<h3 id="how-can-i-ensure-message-end-to-end-encryption-and-deletion">
|
||||
|
||||
|
||||
How can I ensure message end-to-end encryption and deletion? <a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>The best way to ensure every message is end-to-end encrypted,
|
||||
and metadata deleted as quickly as possible
|
||||
is <a href="#howtoe2ee">using chats with guaranteed end-to-end encryption</a>
|
||||
and turning on <a href="#ephemeralmsgs">disappearing messages</a>.</p>
|
||||
|
||||
<p>Guaranteed end-to-end encrypted chats protect against <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM attacks</a>
|
||||
and turning on disappearing messages deletes the messages
|
||||
on the server after a user-configured time.</p>
|
||||
|
||||
<p>If you don’t need a longer-lived copy of your messages on the server,
|
||||
you can also turn on <a href="#delold">“delete messages from server automatically”</a>.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
|
||||
@@ -1174,45 +1031,35 @@ you can also turn on <a href="#delold">“delete messages from server automatica
|
||||
|
||||
</h3>
|
||||
|
||||
<p>No, Delta Chat doesn’t support Perfect Forward Secrecy (PFS).
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
|
||||
This means that if your Delta Chat private decryption key is leaked,
|
||||
and someone has collected your prior in-transit messages,
|
||||
they will be able to decrypt and read them using the leaked decryption key.</p>
|
||||
|
||||
<p>Note, however, that if anyone obtains to your decryption keys,
|
||||
they will typically also be able to obtain your messages,
|
||||
irrespective if Perfect Forward Secrecy is in place or not.
|
||||
The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
<p>Note however, that Forward Secrecy only increases your security
|
||||
if you delete messages or use ephemeral deletion timers.
|
||||
Otherwise, if anyone obtains your decryption keys,
|
||||
they are typically also able to get all your non-deleted messages
|
||||
and don’t need to decrypt any previously collected messages.</p>
|
||||
|
||||
<p>It is possible that Delta Chat evolves to support Perfect Forward Secrecy,
|
||||
because OpenPGP is just a container for encrypted messages
|
||||
but encryption key management (and thus key rotation or key “ratcheting”)
|
||||
could be organized in flexible ways.
|
||||
See <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouia’s PFS prototype</a>
|
||||
for existing experiments in the OpenPGP implementor community.</p>
|
||||
<p>The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we also discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
|
||||
<h3 id="is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
|
||||
|
||||
Is end-to-end encryption of Delta Chat as safe as Signal? <a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal" class="anchor"></a>
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>It depends on what is important to you.
|
||||
Delta Chat <a href="#pfs">does not support PFS</a> like Signal does
|
||||
but it provides <a href="#e2eeguarantee">guaranteed end-to-end encrypted chats</a>
|
||||
that are safe against compromised servers or corrupted networks.
|
||||
Signal and most other PFS-supporting messengers do not provide
|
||||
a practical scheme for protecting chat groups from network attacks
|
||||
which are arguably more worrisome
|
||||
than a potential attacker who seizes your phone and private encryption setup
|
||||
but somehow not your messages, yet has a full record of all
|
||||
past encrypted messages.</p>
|
||||
<p>Yes.</p>
|
||||
|
||||
<p>In any case, Delta Chat’s end-to-end encryption uses a <a href="#openpgp-secure">secure subset of OpenPGP</a>
|
||||
which has been <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">independently security-audited</a>.</p>
|
||||
<p>We devised a forward secrecy scheme that withstood initial scrutiny from cryptographers and usable security experts.
|
||||
Our tentative scheme is designed to reliably work in federated messaging networks and with multi-device usage.
|
||||
However, an implementation has not been scheduled yet (as of Mid 2025).</p>
|
||||
|
||||
<h3 id="importkey">
|
||||
|
||||
@@ -1247,7 +1094,7 @@ from most recent to older:</p>
|
||||
<li>
|
||||
<p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of
|
||||
rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place.
|
||||
rPGP serves as the end-to-end encyption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
|
||||
rPGP serves as the end-to-end encryption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
|
||||
Two advisories were released related to the findings of this audit:</p>
|
||||
|
||||
<ul>
|
||||
@@ -1640,6 +1487,11 @@ Normaal doet de Delta Chat-app dit uit zichzelf.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Note:
|
||||
Changing email addresses is temporarily disabled
|
||||
because of ongoing changes to the DeltaChat core.
|
||||
It should be available again in a few months.</p>
|
||||
|
||||
<ol>
|
||||
<li>
|
||||
<p>Change your address in “Settings → Advanced → Password and Account” and
|
||||
|
||||
+117
-136
@@ -36,27 +36,23 @@
|
||||
<li><a href="#dlaczego-delta-chat-integruje-się-ze-scentralizowanymi-zastrzeżonymi-usługami-push-applegoogle">Dlaczego Delta Chat integruje się ze scentralizowanymi, zastrzeżonymi usługami push Apple/Google?</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#szyfrowanie-i-bezpieczeństwo">Szyfrowanie i bezpieczeństwo</a>
|
||||
<li><a href="#e2ee">Szyfrowanie i bezpieczeństwo</a>
|
||||
<ul>
|
||||
<li><a href="#jakie-standardy-są-stosowane-do-szyfrowania-end-to-end">Jakie standardy są stosowane do szyfrowania end-to-end?</a></li>
|
||||
<li><a href="#whene2e">Skąd mogę wiedzieć, czy wiadomości są szyfrowane metodą e2e?</a></li>
|
||||
<li><a href="#howtoe2ee">Jak mogę uzyskać gwarancję kompleksowego szyfrowania i zielone znaczniki wyboru?</a></li>
|
||||
<li><a href="#e2eeguarantee">Co oznacza zielony znacznik wyboru i „gwarantowane kompleksowe szyfrowanie”?</a></li>
|
||||
<li><a href="#nocryptanymore">Kontakt „wysłał wiadomość z innego urządzenia”, co mogę zrobić?</a></li>
|
||||
<li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
|
||||
<li><a href="#czy-załączniki-zdjęcia-pliki-pliki-audio-itp-są-szyfrowane-metodą-end-to-end">Czy załączniki (zdjęcia, pliki, pliki audio itp.) są szyfrowane metodą end-to-end?</a></li>
|
||||
<li><a href="#openpgp-secure">Czy OpenPGP jest bezpieczny?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Czy rozważałeś użycie alternatyw dla OpenPGP do szyfrowania typu end-to-end?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
|
||||
<li><a href="#czy-delta-chat-jest-podatny-na-efail">Czy Delta Chat jest podatny na EFAIL?</a></li>
|
||||
<li><a href="#tls">Czy wiadomość jest udostępniana w postaci zwykłego tekstu, jeśli szyfrowanie end-to-end nie jest dostępne?</a></li>
|
||||
<li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
|
||||
<li><a href="#message-metadata">W jaki sposób Delta Chat chroni metadane w wiadomościach?</a></li>
|
||||
<li><a href="#device-seizure">Jak chronić metadane i kontakty w przypadku przejęcia urządzenia?</a></li>
|
||||
<li><a href="#jak-mogę-sprawdzić-informacje-o-szyfrowaniu">Jak mogę sprawdzić informacje o szyfrowaniu?</a></li>
|
||||
<li><a href="#jak-mogę-sprawdzić-stan-szyfrowania-wiadomości">Jak mogę sprawdzić stan szyfrowania wiadomości?</a></li>
|
||||
<li><a href="#dlaczego-widzę-niezaszyfrowane-wiadomości">Dlaczego widzę niezaszyfrowane wiadomości?</a></li>
|
||||
<li><a href="#jak-mogę-uzyskać-zaszyfrowany-ened-to-end-czat-z-kontaktem-delta-chat-który-czasami-korzysta-z-poczty-internetowej-lub-innej-aplikacji-e-mail-bez-autocrypt">Jak mogę uzyskać zaszyfrowany ened-to-end czat z kontaktem Delta Chat, który czasami korzysta z poczty internetowej lub innej aplikacji e-mail bez Autocrypt?</a></li>
|
||||
<li><a href="#jak-mogę-zapewnić-kompleksowe-szyfrowanie-i-usuwanie-wiadomości">Jak mogę zapewnić kompleksowe szyfrowanie i usuwanie wiadomości?</a></li>
|
||||
<li><a href="#pfs">Czy Delta Chat obsługuje funkcję Perfect Forward Secrecy?</a></li>
|
||||
<li><a href="#czy-szyfrowanie-end-to-end-delta-chat-jest-tak-samo-bezpieczne-jak-signal">Czy szyfrowanie end-to-end Delta Chat jest tak samo bezpieczne jak Signal?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#importkey">Czy mogę ponownie wykorzystać mój istniejący klucz prywatny?</a></li>
|
||||
<li><a href="#security-audits">Czy Delta Chat był niezależnie kontrolowany pod kątem luk w zabezpieczeniach?</a></li>
|
||||
</ul>
|
||||
@@ -90,7 +86,7 @@
|
||||
<ul>
|
||||
<li><a href="#jakich-uprawnień-potrzebuje-delta-chat">Jakich uprawnień potrzebuje Delta Chat?</a></li>
|
||||
<li><a href="#czy-delta-chat-działa-z-moim-dostawcą-poczty-e-mail">Czy Delta Chat działa z <em>moim</em> dostawcą poczty e-mail?</a></li>
|
||||
<li><a href="#i-want-to-manage-my-own-server-for-delta-chat-what-do-you-recommend">I want to manage my own server for Delta Chat. What do you recommend?</a></li>
|
||||
<li><a href="#chcę-zarządzać-własnym-serwerem-dla-delta-chat-co-polecacie">Chcę zarządzać własnym serwerem dla Delta Chat. Co polecacie?</a></li>
|
||||
<li><a href="#dlaczego-muszę-wpisać-moje-hasło-e-mail-do-delta-chat-czy-to-jest-bezpieczne">Dlaczego muszę wpisać moje hasło e-mail do Delta Chat? Czy to jest bezpieczne?</a></li>
|
||||
<li><a href="#jakie-wiadomości-pojawiają-się-w-delta-chat">Jakie wiadomości pojawiają się w Delta Chat?</a></li>
|
||||
<li><a href="#czy-delta-chat-obsługuje-wiadomości-e-mail-w-formacie-html">Czy Delta Chat obsługuje wiadomości e-mail w formacie HTML?</a></li>
|
||||
@@ -589,10 +585,10 @@ nadal będziesz mógł pisać, ale nie będziesz już powiadamiany o żadnych no
|
||||
|
||||
<p>Pamiętaj, że Delta Chat posiada <a href="#privacy-notifications">mały i chroniący prywatność system powiadomień push</a>, który zapewnia „natychmiastowe dostarczanie” wiadomości ze wszystkich serwerów chatmail, w tym potencjalnego, który <a href="https://delta.chat/chatmail#selfhosted">możesz skonfigurować samodzielnie bez naszej zgody</a>. Witamy w potędze interoperacyjnego i ogromnego systemu chatmail i e-mail :)</p>
|
||||
|
||||
<h2 id="szyfrowanie-i-bezpieczeństwo">
|
||||
<h2 id="e2ee">
|
||||
|
||||
|
||||
Szyfrowanie i bezpieczeństwo <a href="#szyfrowanie-i-bezpieczeństwo" class="anchor"></a>
|
||||
Szyfrowanie i bezpieczeństwo <a href="#e2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h2>
|
||||
@@ -605,9 +601,26 @@ nadal będziesz mógł pisać, ale nie będziesz już powiadamiany o żadnych no
|
||||
|
||||
</h3>
|
||||
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> służy do automatycznego ustanawiania szyfrowania end-to-end kontaktów i czatów grupowych. Autocrypt wykorzystuje ograniczony i <a href="#openpgp-secure">bezpieczny podzbiór standardu OpenPGP</a>. W pełni zaszyfrowane wiadomości są oznaczone kłódką <img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
|
||||
<p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
|
||||
to provide automatic end-to-end encryption using these protocols:</p>
|
||||
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Protokoły Secure-Join</a> służą do nawiązywania rozmów z gwarantowanym szyfrowaniem typu end-to-end, które chroni przed atakami sieciowymi i zagrożonymi serwerami. Czaty oznaczone zielonym znacznikiem wyboru <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> gwarantują szyfrowanie end-to-end wiadomości.</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
|
||||
to exchange encryption setup information through QR-code scanning or “invite links”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption between contacts and all members of a group chat.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
|
||||
chat</a>
|
||||
enables receivers to use end-to-end encryption with the contact.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
|
||||
|
||||
<h3 id="whene2e">
|
||||
|
||||
@@ -617,100 +630,94 @@ nadal będziesz mógł pisać, ale nie będziesz już powiadamiany o żadnych no
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Wszystkie całkowicie zaszyfrowane wiadomości są oznaczone kłódką:</p>
|
||||
|
||||
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p>
|
||||
|
||||
<p>Pełne szyfrowanie jest gwarantowane, jeśli obok tytułu czatu znajduje się zielony znacznik wyboru:</p>
|
||||
|
||||
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
|
||||
<p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
|
||||
Since the Delta Chat Version 2 release series (July 2025)
|
||||
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
<h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
|
||||
|
||||
|
||||
Jak mogę uzyskać gwarancję kompleksowego szyfrowania i zielone znaczniki wyboru? <a href="#howtoe2ee" class="anchor"></a>
|
||||
Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Jeśli masz drugi kanał komunikacji ze swoim partnerem na czacie, np. czat wideo lub inny komunikator, możesz wygenerować link zaproszenia.</p>
|
||||
<p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
|
||||
it is impossible to receive or send messages without end-to-end encryption.</p>
|
||||
|
||||
<p>Jeśli jesteście razem osobiście, możesz pokazać kod QR swojemu rozmówcy.</p>
|
||||
<p>If you instead create a profile using a classic e-mail server,
|
||||
you can send and receive messages without end-to-end encryption.
|
||||
Such messages lacking end-to-end encryption are marked with an e-mail icon
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
|
||||
|
||||
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You can send an invite link through another private chat,
|
||||
show an invitation QR code when next to each other or in a video call,
|
||||
or click on a “contact” that was shared in a chat.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>W przypadku <strong>zaproszeń grupowych</strong> dotknij tytułu czatu grupy, aby wyświetlić listę jej członków, i wybierz „Kod QR zaproszenia”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Aby uzyskać <strong>bezpośrednie zaproszenia na czat 1:1</strong>, dotknij ikony kodu QR <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" /> na ekranie głównym aplikacji Delta Chat.</p>
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
tap the QR Code icon <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
|
||||
on the Delta Chat app main screen.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Pozwól swojemu partnerowi czatu zeskanować obraz QR za pomocą aplikacji Delta Chat lub dotknij „Kopiuj” lub „Udostępnij”, aby utworzyć link zaproszenia i udostępnić go swojemu partnerowi czatu.</p>
|
||||
<p>Ask your chat partner to scan the QR image
|
||||
with their Delta Chat app,
|
||||
or click “Copy” or “Share” to create an invite link
|
||||
and share it with your chat partner.</p>
|
||||
|
||||
<p>Teraz poczekaj, aż między obydwoma urządzeniami <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">nastąpi wymiana wiadomości sieciowych Secure-Join</a>.</p>
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>Jeśli oba urządzenia są w trybie online, obie strony ostatecznie zobaczą czat (grupowy lub bezpośredni) z zielonym znacznikiem wyboru <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> obok tytułu.</p>
|
||||
<p>If both sides are online, they will soon see a (group or direct) chat
|
||||
and can start messaging securely.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Jeśli jedno z urządzeń jest w trybie offline, zielone znaczniki wyboru pojawią się później, dopiero gdy urządzenie zostanie ponownie połączone z Internetem i zostanie zrealizowany protokół sieciowy Secure-Join.</p>
|
||||
<p>If one side is offline or in bad network,
|
||||
the ability to chat is delayed until connectivity is restored.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Gratulacje! Teraz będziecie automatycznie korzystać z gwarantowanego kompleksowego szyfrowania tego kontaktu i oboje będziecie mogli dodawać się nawzajem do grup oznaczonych zielonym znacznikiem wyboru <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> , w ten sposób automatycznie rozpowszechniając gwarantowane kompleksowe szyfrowanie wśród swoich członków.</p>
|
||||
<p>Congratulations!
|
||||
You now will automatically use end-to-end encryption
|
||||
with this contact.
|
||||
If you add each other to chat groups,
|
||||
end-to-end encryption will be established among all members.</p>
|
||||
|
||||
<h3 id="e2eeguarantee">
|
||||
|
||||
|
||||
Co oznacza zielony znacznik wyboru i „gwarantowane kompleksowe szyfrowanie”? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Tytuły czatów z zielonymi znacznikami wyboru <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> oznaczają, że wszystkie wiadomości na czacie będą w pełni szyfrowane i nie będą mogły zostać odczytane ani zmodyfikowane przez zhakowane serwery poczty e-mail lub dostawców Internetu. Dołączanie do czatów grupowych oznaczonych zielonym znacznikiem bezpiecznie rozpowszechnia informacje o szyfrowaniu wszystkich osób (i zielone znaczniki wyboru) w sposób gwarantujący kompleksowe szyfrowanie w grupie i pomiędzy członkami.</p>
|
||||
|
||||
<p>Profile kontaktów z zielonymi znacznikami wyboru <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> oznaczają, że obecnie gwarantujemy, że wiadomości kontaktu będą szyfrowane metodą end-to-end. Każdy kontakt oznaczony zielonym znacznikiem albo wykonał z tobą bezpośrednie <a href="#howtoe2ee">skanowanie QR</a>, albo został zweryfikowany przez inny kontakt oznaczony zielonym znacznikiem. Weryfikacje odbywają się automatycznie podczas dodawania członków do grup. Ktokolwiek doda kontakt do grupy oznaczonej zielonym znacznikiem, staje się osobą weryfikującą dla tych członków, którzy jeszcze nie wiedzieli o dodanym kontakcie. W profilu kontaktu możesz wielokrotnie dotykać tekstu „Zweryfikowano przez…”, aż dojdziesz do osoby, z którą bezpośrednio wykonałeś <a href="#howtoe2ee">skanowanie QR</a>.</p>
|
||||
|
||||
<p>Pamiętaj, że w profilu kontaktu możesz widzieć i klikać osoby weryfikujące, ale w tytule profilu nie ma zielonego znacznika wyboru. Zwykle oznacza to, że kontakt <a href="#nocryptanymore">„wysłał wiadomość z innego urządzenia”</a>.</p>
|
||||
<p>A contact profile might show a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
and an “Introduced by” line.
|
||||
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
|
||||
or was introduced by a another green-checkmarked contact.
|
||||
Introductions happen automatically when adding members to groups.
|
||||
Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
|
||||
becomes an introducer.
|
||||
In a contact profile you can tap on the “Introduced by …” text repeatedly
|
||||
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
|
||||
|
||||
<p>Aby uzyskać bardziej szczegółowe omówienie „gwarantowanego szyfrowania typu end-to-end”, zobacz <a href="https://securejoin.delta.chat/en/latest/new.html">Protokoły Secure-Join</a>, a w szczególności przeczytaj o „zweryfikowanych grupach”, technicznym określeniu tak zwanego tutaj „zielonego znacznika wyboru” lub „gwarantowanego szyfrowania end-to-end” czatów.</p>
|
||||
|
||||
<h3 id="nocryptanymore">
|
||||
|
||||
|
||||
Kontakt „wysłał wiadomość z innego urządzenia”, co mogę zrobić? <a href="#nocryptanymore" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Twój czat z kontaktem utracił gwarantowane szyfrowanie typu end-to-end. Gdy zobaczysz to ostrzeżenie, zielony znacznik wyboru dla tego czatu i kontaktu został usunięty. <strong>Jeśli zdziwi cię nagły spadek gwarantowanego szyfrowania end-to-end tego kontaktu, nie akceptuj ostrzeżenia!</strong> Zamiast tego skontaktuj się ze swoim kontaktem za pośrednictwem drugiego kanału, takiego jak rozmowa wideo, inny komunikator lub rozmowa telefoniczna, aby dowiedzieć się, co się stało.</p>
|
||||
|
||||
<p>Jeśli twój kontakt rzeczywiście spowodował spadek gwarantowanego szyfrowania typu end-to-end, zapoznaj się z kolejnymi akapitami, aby poznać typowe przyczyny i sposoby ich łagodzenia. Niezależnie od tego, wszystkie inne czaty oznaczone zielonym znacznikiem są w pełni szyfrowane, nawet jeśli kontakt jest ich członkiem.</p>
|
||||
|
||||
<p><strong>Twój kontakt korzysta z Delta Chat na drugim urządzeniu (telefonie lub laptopie)</strong></p>
|
||||
|
||||
<p>Jeśli ma inne urządzenie z uruchomioną aplikacją Delta Chat, powinien usunąć konto z nowego urządzenia i dodać je <a href="#multiclient">jako drugie urządzenie zgodnie z opisem tutaj</a>. Gdy tylko skontaktuje się z tobą później, ostrzeżenie zniknie, a na obu urządzeniach twojego kontaktu zostanie ustanowione gwarantowane szyfrowanie.</p>
|
||||
|
||||
<p><strong>Twój kontakt ponownie zainstalował Delta Chat, używając swojego starego loginu do konta</strong></p>
|
||||
|
||||
<p>Jeśli ma <a href="#backup">plik kopii zapasowej</a>, powinien usunąć konto z nowego urządzenia i zamiast tego zaimportować plik kopii zapasowej, aby ponownie utworzyć konto. Gdy tylko skontaktuje się z tobą później, ostrzeżenie zniknie, a dla tego kontaktu zostanie przywrócone gwarantowane szyfrowanie.</p>
|
||||
|
||||
<p>Jeśli nie ma pliku kopii zapasowej, najlepiej wykonać <a href="#howtoe2ee">skanowanie QR</a> ze swoim partnerem czatu, aby przywrócić gwarantowane szyfrowanie end-to-end.</p>
|
||||
|
||||
<p><strong>Twój kontakt wysłał wiadomość e-mail za pośrednictwem interfejsu poczty internetowej lub innej aplikacji e-mail i wkrótce ponownie zacznie korzystać z Delta Chat.</strong></p>
|
||||
|
||||
<p>Jeśli masz pewność, że kontakt czasami korzysta z poczty internetowej lub innej aplikacji pocztowej, która nie zapewnia szyfrowania end-to-end, możesz zaakceptować ostrzeżenie. Gdy tylko twój kontakt ponownie skorzysta z Delta Chat, gwarantowane szyfrowanie end-to-end zostanie automatycznie przywrócone.</p>
|
||||
|
||||
<p><strong>Twój kontakt całkowicie przestał korzystać z Delta Chat</strong></p>
|
||||
|
||||
<p>Czasami utrzymanie kontaktu jest ważniejsze niż szyfrowanie end-to-end. <a href="#tls">„Szyfrowanie warstwy transportowej” (TLS)</a> może w dalszym ciągu w znaczący sposób chronić poufność wiadomości przesyłanych między urządzeniem a serwerem poczty e-mail. Jednak bez kompleksowego szyfrowania Ty i Twój kontakt ufacie swojemu serwerowi poczty e-mail, że nie będzie czytać ani manipulować waszymi wiadomościami i nie będzie przekazywać ich osobom trzecim.</p>
|
||||
|
||||
<p>W każdym razie nie możesz zrobić nic innego, jak zaakceptować ostrzeżenie. Usuń także kontakt z aktywnej grupy oznaczonej zielonym znacznikiem, którą znajdziesz w sekcji „Wspólne czaty” w profilu kontaktu. Dzięki temu twój kontakt nie otrzyma „nieczytelnych” wiadomości.</p>
|
||||
|
||||
<p>Jeśli kontakt usunął Delta Chat z powodu błędów lub niepożądanego zachowania, rozważ opublikowanie postu na naszym <a href="https://support.delta.chat">forum pomocy</a>, aby pomóc nam zidentyfikować i rozwiązać typowe problemy. Dzięki!</p>
|
||||
|
||||
<h3 id="czy-załączniki-zdjęcia-pliki-pliki-audio-itp-są-szyfrowane-metodą-end-to-end">
|
||||
|
||||
|
||||
@@ -731,7 +738,9 @@ nadal będziesz mógł pisać, ale nie będziesz już powiadamiany o żadnych no
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Tak, Delta Chat korzysta z bezpiecznego podzbioru OpenPGP i wyświetla wskaźnik bezpieczeństwa kłódki na wiadomości tylko wtedy, gdy cała wiadomość jest prawidłowo zaszyfrowana i podpisana. Na przykład „Odłączone podpisy” nie są traktowane jako bezpieczne.</p>
|
||||
<p>Yes, Delta Chat uses a secure subset of OpenPGP
|
||||
requiring the whole message to be properly encrypted and signed.
|
||||
For example, “Detached signatures” are not treated as secure.</p>
|
||||
|
||||
<p>OpenPGP samo w sobie nie jest niebezpieczne. Większość publicznie omawianych problemów związanych z bezpieczeństwem OpenPGP tak naprawdę wynika ze złej użyteczności lub złej implementacji narzędzi, lub aplikacji (lub obu). Szczególnie ważne jest rozróżnienie pomiędzy OpenPGP, standardem szyfrowania IETF, a GnuPG (GPG), narzędziem wiersza poleceń implementującym OpenPGP. Wiele publicznych komentarzy krytycznych na temat OpenPGP tak naprawdę omawia GnuPG, którego Delta Chat nigdy nie używał. Delta Chat korzysta raczej z implementacji OpenPGP Rust <a href="https://github.com/rpgp/rpgp">rPGP</a>, dostępnej jako <a href="https://crates.io/crates/pgp">niezależny pakiet „pgp”</a> i poddanej <a href="#security-audits">audytowi bezpieczeństwa w 2019 i 2024 roku</a>.</p>
|
||||
|
||||
@@ -740,7 +749,7 @@ nadal będziesz mógł pisać, ale nie będziesz już powiadamiany o żadnych no
|
||||
<h3 id="openpgp-alternatives">
|
||||
|
||||
|
||||
Czy rozważałeś użycie alternatyw dla OpenPGP do szyfrowania typu end-to-end? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -764,16 +773,17 @@ nadal będziesz mógł pisać, ale nie będziesz już powiadamiany o żadnych no
|
||||
<h3 id="tls">
|
||||
|
||||
|
||||
Czy wiadomość jest udostępniana w postaci zwykłego tekstu, jeśli szyfrowanie end-to-end nie jest dostępne? <a href="#tls" class="anchor"></a>
|
||||
Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Nawet jeśli nie ma gwarancji, że twoje wiadomości będą zaszyfrowane metodą end-to-end, nadal są chronione przed dostawcami Internetu, takimi jak operatorzy komórkowi lub telewizji kablowej. Jednakże dostawcy poczty e-mail zarówno twoi, jak i twojego odbiorcy mogą czytać, analizować, a nawet modyfikować twoje wiadomości, w tym wszelkie załączniki, jeśli nie są one w pełni zaszyfrowane.</p>
|
||||
<p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
|
||||
they are still protected from cell or cable companies who can not read or modify your e-mail messages.
|
||||
But both your and your recipient’s e-mail providers
|
||||
may read, analyze or modify your messages, including any attachments.</p>
|
||||
|
||||
<p>Delta Chat domyślnie korzysta ze ścisłego <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">szyfrowania TLS</a>, które zabezpiecza połączenia pomiędzy twoim urządzeniem a dostawcą poczty e-mail. Cała obsługa TLS Delta Chat została poddana niezależnemu <a href="#security-audits">audytowi bezpieczeństwa</a>. Co więcej, połączenie między tobą a dostawcą poczty e-mail odbiorcy będzie zazwyczaj również szyfrowane. Jeśli zaangażowane serwery poczty e-mail obsługują <a href="https://datatracker.ietf.org/doc/html/rfc8461">MTA-STS</a>, pomiędzy dostawcami poczty e-mail będzie egzekwowane szyfrowanie transportu. W takim przypadku komunikacja Delta Chat nigdy nie będzie udostępniana w Internecie w postaci zwykłego tekstu, nawet jeśli wiadomość nie została zaszyfrowana metodą end-to-end.</p>
|
||||
|
||||
<p>Pamiętaj, że <a href="#howtoe2ee">utrzymywanie gwarantowanego szyfrowania typu end-to-end</a> oprócz szyfrowania TLS zapewnia wszechstronne bezpieczeństwo między urządzeniami twoimi i odbiorców. Nawet twój dostawca poczty e-mail lub Internetu nie będzie w stanie przeczytać ani zmodyfikować twoich wiadomości.</p>
|
||||
|
||||
<h3 id="message-metadata">
|
||||
|
||||
@@ -818,50 +828,6 @@ nadal będziesz mógł pisać, ale nie będziesz już powiadamiany o żadnych no
|
||||
|
||||
<p>Możesz sprawdzić stan szyfrowania end-to-end ręcznie w oknie dialogowym „Szyfrowanie” (profil użytkownika w systemie Android/iOS lub kliknij prawym przyciskiem myszy element listy czatu użytkownika na komputerze). Delta Chat pokazuje tam dwa odciski palców. Jeśli te same odciski palców pojawią się u ciebie i urządzeniu twojego kontaktu, połączenie jest bezpieczne.</p>
|
||||
|
||||
<h3 id="jak-mogę-sprawdzić-stan-szyfrowania-wiadomości">
|
||||
|
||||
|
||||
Jak mogę sprawdzić stan szyfrowania wiadomości? <a href="#jak-mogę-sprawdzić-stan-szyfrowania-wiadomości" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Mała <strong>kłódka</strong> w dymku wiadomości oznacza, że wiadomość od danego nadawcy została prawidłowo zaszyfrowana. Jeśli <strong>nie ma kłódki</strong>, wiadomość nie została prawidłowo zaszyfrowana metodą end-to-end, najprawdopodobniej dlatego, że nadawca korzysta z aplikacji lub interfejsu poczty internetowej bez obsługi szyfrowania typu end-to-end.</p>
|
||||
|
||||
<h3 id="dlaczego-widzę-niezaszyfrowane-wiadomości">
|
||||
|
||||
|
||||
Dlaczego widzę niezaszyfrowane wiadomości? <a href="#dlaczego-widzę-niezaszyfrowane-wiadomości" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Jeśli kontakt korzysta z aplikacji e-mail bez Autocrypt, wszystkie wiadomości od tego kontaktu (w czacie grupowym lub 1:1) nie będą w pełni szyfrowane, w związku z czym nie będą wyświetlane z „kłódką” przy wiadomościach. Pamiętaj, że nawet jeśli twoje kontakty korzystają z Delta Chat na swoim koncie, mogą również używać na tym koncie aplikacji e-mail bez Autocrypt, co może powodować sporadyczne wysyłanie niezaszyfrowanych wiadomości. Odpowiadanie niezaszyfrowanych wiadomości na niezaszyfrowane wiadomości jest wymagane przez funkcję Autocrypt, aby zapobiec nieczytelnym wiadomościom po stronie twoich kontaktów i ich aplikacji e-mail bez Autocrypt.</p>
|
||||
|
||||
<h3 id="jak-mogę-uzyskać-zaszyfrowany-ened-to-end-czat-z-kontaktem-delta-chat-który-czasami-korzysta-z-poczty-internetowej-lub-innej-aplikacji-e-mail-bez-autocrypt">
|
||||
|
||||
|
||||
Jak mogę uzyskać zaszyfrowany ened-to-end czat z kontaktem Delta Chat, który czasami korzysta z poczty internetowej lub innej aplikacji e-mail bez Autocrypt? <a href="#jak-mogę-uzyskać-zaszyfrowany-ened-to-end-czat-z-kontaktem-delta-chat-który-czasami-korzysta-z-poczty-internetowej-lub-innej-aplikacji-e-mail-bez-autocrypt" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Jeśli potrzebujesz bezpiecznie, kompleksowo zaszyfrowanego czatu z kontaktem, który korzysta ze swojego konta zarówno w Delta Chat, jak i w aplikacjach bez Autocrypt (np. poczta internetowa), najlepiej skonfigurować z nim gwarantowane szyfrowanie typu end-to-end, a następnie utworzyć <a href="#howtoe2ee">gwarantowany zaszyfrowany end-to-end</a> czat grupowy z wami dwoma jako członkami. W tym czacie grupowym wszystkie wiadomości będą w pełni szyfrowane, nawet jeśli bezpośredni czat między wami zawiera ostrzeżenie <a href="#nocryptanymore">„…wysłano wiadomość z innego urządzenia”</a>.</p>
|
||||
|
||||
<h3 id="jak-mogę-zapewnić-kompleksowe-szyfrowanie-i-usuwanie-wiadomości">
|
||||
|
||||
|
||||
Jak mogę zapewnić kompleksowe szyfrowanie i usuwanie wiadomości? <a href="#jak-mogę-zapewnić-kompleksowe-szyfrowanie-i-usuwanie-wiadomości" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Najlepszym sposobem, aby mieć pewność, że każda wiadomość jest kompleksowo zaszyfrowana, a metadane usunięte tak szybko, jak to możliwe, jest <a href="#howtoe2ee">korzystanie z czatów z gwarantowanym szyfrowaniem end-to-end</a> i włączonymi <a href="#ephemeralmsgs">znikającymi wiadomościami</a>.</p>
|
||||
|
||||
<p>Gwarantowane szyfrowane metodą end-to-end czaty chronią przed atakami <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM attacks</a>, a włączenie znikających wiadomości powoduje usunięcie wiadomości z serwera po upływie czasu skonfigurowanego przez użytkownika.</p>
|
||||
|
||||
<p>Jeśli nie potrzebujesz dłuższej kopii wiadomości na serwerze, możesz także włączyć opcję <a href="#delold">„automatycznie usuń wiadomości z serwera”</a>.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
|
||||
@@ -870,23 +836,35 @@ nadal będziesz mógł pisać, ale nie będziesz już powiadamiany o żadnych no
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Nie, Delta Chat nie obsługuje funkcji Perfect Forward Secrecy (PFS). Oznacza to, że jeśli twój prywatny klucz deszyfrujący Delta Chat wycieknie i ktoś zdobędzie twoje wcześniejsze wiadomości w trakcie przesyłania, będzie mógł je odszyfrować i odczytać przy użyciu ujawnionego klucza deszyfrowania.</p>
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>Należy jednak pamiętać, że jeśli ktoś zdobędzie twoje klucze deszyfrujące, zazwyczaj będzie mógł również uzyskać twoje wiadomości, niezależnie od tego, czy obowiązuje zasada Perfect Forward Secrecy, czy nie. Typową sytuacją w świecie rzeczywistym w przypadku wycieku kluczy deszyfrujących jest przejęcie urządzenia, które omawiamy w naszej odpowiedzi na temat <a href="#device-seizure">przejęcia metadanych i urządzenia</a>.</p>
|
||||
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
|
||||
This means that if your Delta Chat private decryption key is leaked,
|
||||
and someone has collected your prior in-transit messages,
|
||||
they will be able to decrypt and read them using the leaked decryption key.</p>
|
||||
|
||||
<p>Możliwe, że Delta Chat ewoluuje, aby wspierać Perfect Forward Secrecy, ponieważ OpenPGP to tylko kontener na zaszyfrowane wiadomości, ale zarządzanie kluczami szyfrowania (a tym samym rotacja kluczy lub „zapadanie kluczy”) mogłoby być zorganizowane w elastyczny sposób. Zobacz <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">prototyp PFS firmy Seqouia</a>, aby zapoznać się z istniejącymi eksperymentami w społeczności implementatorów OpenPGP.</p>
|
||||
<p>Note however, that Forward Secrecy only increases your security
|
||||
if you delete messages or use ephemeral deletion timers.
|
||||
Otherwise, if anyone obtains your decryption keys,
|
||||
they are typically also able to get all your non-deleted messages
|
||||
and don’t need to decrypt any previously collected messages.</p>
|
||||
|
||||
<p>The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we also discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
|
||||
<h3 id="czy-szyfrowanie-end-to-end-delta-chat-jest-tak-samo-bezpieczne-jak-signal">
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
|
||||
|
||||
Czy szyfrowanie end-to-end Delta Chat jest tak samo bezpieczne jak Signal? <a href="#czy-szyfrowanie-end-to-end-delta-chat-jest-tak-samo-bezpieczne-jak-signal" class="anchor"></a>
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>To zależy od tego, co jest dla ciebie ważne. Delta Chat <a href="#pfs">nie obsługuje PFS</a> tak jak Signal, ale zapewnia <a href="#e2eeguarantee">gwarantowane szyfrowane end-to-end czatów</a>, które jest zabezpieczeniem przed zaatakowanymi serwerami lub uszkodzonymi sieciami. Signal i większość innych komunikatorów obsługujących PFS nie zapewniają praktycznego schematu ochrony czatów grupowych przed atakami sieciowymi, które są prawdopodobnie bardziej niepokojące niż potencjalny atakujący, który przejmuje twój telefon i prywatne ustawienia szyfrowania i w ten sposób nie twoje wiadomości i mimo to ma pełny zapis wszystkich poprzednio zaszyfrowanych wiadomości.</p>
|
||||
<p>Tak.</p>
|
||||
|
||||
<p>W każdym razie szyfrowanie end-to-end Delta Chat wykorzystuje <a href="#openpgp-secure">bezpieczny podzbiór OpenPGP</a>, który został poddany <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">niezależnemu audytowi bezpieczeństwa</a>.</p>
|
||||
<p>We devised a forward secrecy scheme that withstood initial scrutiny from cryptographers and usable security experts.
|
||||
Our tentative scheme is designed to reliably work in federated messaging networks and with multi-device usage.
|
||||
However, an implementation has not been scheduled yet (as of Mid 2025).</p>
|
||||
|
||||
<h3 id="importkey">
|
||||
|
||||
@@ -1208,6 +1186,11 @@ Listy rozgłoszeniowe są nadal wysoce eksperymentalne i bardzo prawdopodobne,
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Note:
|
||||
Changing email addresses is temporarily disabled
|
||||
because of ongoing changes to the DeltaChat core.
|
||||
It should be available again in a few months.</p>
|
||||
|
||||
<ol>
|
||||
<li>
|
||||
<p>Zmień swój adres w „Ustawienia → Zaawansowane → Hasło i konto” i wprowadź hasło do swojego nowego konta (i jeśli to konieczne, ustawienia serwera). Otrzymasz informację o przeniesieniu na nowy adres. Dodatkowe powiadomienie pojawi się również na czacie „Komunikaty urządzenia”.</p>
|
||||
@@ -1281,19 +1264,17 @@ Oto, co robi Delta Chat z tymi uprawnieniami:</p>
|
||||
Jednak niektórzy dostawcy potrzebują specjalnych opcji, aby działać poprawnie, zobacz <a href="https://providers.delta.chat">Przegląd dostawców</a></li>
|
||||
</ul>
|
||||
|
||||
<h3 id="i-want-to-manage-my-own-server-for-delta-chat-what-do-you-recommend">
|
||||
<h3 id="chcę-zarządzać-własnym-serwerem-dla-delta-chat-co-polecacie">
|
||||
|
||||
|
||||
I want to manage my own server for Delta Chat. What do you recommend? <a href="#i-want-to-manage-my-own-server-for-delta-chat-what-do-you-recommend" class="anchor"></a>
|
||||
Chcę zarządzać własnym serwerem dla Delta Chat. Co polecacie? <a href="#chcę-zarządzać-własnym-serwerem-dla-delta-chat-co-polecacie" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<ul>
|
||||
<li>Most mail servers will work well. But what we personally recommend is a
|
||||
chatmail relay server, as described <a href="https://delta.chat/en/2023-12-13-chatmail">in this
|
||||
blogpost</a>.</li>
|
||||
<li>You can find an <a href="https://github.com/chatmail/relay">installation guide on GitHub</a>.</li>
|
||||
<li>Większość serwerów pocztowych będzie działać dobrze. Ale my osobiście polecamy serwer przekaźnikowy chatmail, jak opisano <a href="https://delta.chat/en/2023-12-13-chatmail">w tym wpisie na blogu</a>.</li>
|
||||
<li>Możesz znaleźć <a href="https://github.com/chatmail/relay">przewodnik instalacji na GitHub</a>.</li>
|
||||
</ul>
|
||||
|
||||
<h3 id="dlaczego-muszę-wpisać-moje-hasło-e-mail-do-delta-chat-czy-to-jest-bezpieczne">
|
||||
|
||||
@@ -36,27 +36,23 @@
|
||||
<li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#encryption-and-security">Encryption and Security</a>
|
||||
<li><a href="#e2ee">Encryption and Security</a>
|
||||
<ul>
|
||||
<li><a href="#which-standards-are-used-for-end-to-end-encryption">Which standards are used for end-to-end encryption?</a></li>
|
||||
<li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I get guaranteed end-to-end encryption and green checkmarks?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark and “guaranteed end-to-end encryption” mean?</a></li>
|
||||
<li><a href="#nocryptanymore">A contact “sent a message from another device”, what can i do?</a></li>
|
||||
<li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
|
||||
<li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li>
|
||||
<li><a href="#openpgp-secure">Is OpenPGP secure?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end -encryption?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
|
||||
<li><a href="#is-delta-chat-vulnerable-to-efail">Is Delta Chat vulnerable to EFAIL?</a></li>
|
||||
<li><a href="#tls">Is a message exposed in cleartext if end-to-end encryption is not available?</a></li>
|
||||
<li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
|
||||
<li><a href="#message-metadata">How does Delta Chat protect metadata in messages?</a></li>
|
||||
<li><a href="#device-seizure">How to protect metadata and contacts when a device is seized?</a></li>
|
||||
<li><a href="#how-can-i-check-encryption-information">How can i check encryption information?</a></li>
|
||||
<li><a href="#how-can-i-check-the-encryption-status-of-messages">How can I check the encryption status of messages?</a></li>
|
||||
<li><a href="#why-do-i-see-unencrypted-messages">Why do I see unencrypted messages?</a></li>
|
||||
<li><a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app?</a></li>
|
||||
<li><a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion">How can I ensure message end-to-end encryption and deletion?</a></li>
|
||||
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
|
||||
<li><a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">Is end-to-end encryption of Delta Chat as safe as Signal?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#importkey">Posso reutilizar minha chave privada existente?</a></li>
|
||||
<li><a href="#security-audits">Was Delta Chat independently audited for security vulnerabilities?</a></li>
|
||||
</ul>
|
||||
@@ -720,10 +716,10 @@ that achieves “instant delivery” of messages for all chatmail servers
|
||||
including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>.
|
||||
Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p>
|
||||
|
||||
<h2 id="encryption-and-security">
|
||||
<h2 id="e2ee">
|
||||
|
||||
|
||||
Encryption and Security <a href="#encryption-and-security" class="anchor"></a>
|
||||
Encryption and Security <a href="#e2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h2>
|
||||
@@ -736,18 +732,26 @@ Welcome to the power of the interoperable and massive chatmail and e-mail system
|
||||
|
||||
</h3>
|
||||
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption with contacts and group chats.
|
||||
Autocrypt uses a limited and <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>.
|
||||
End-to-End encrypted messages are marked with a padlock
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
|
||||
<p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
|
||||
to provide automatic end-to-end encryption using these protocols:</p>
|
||||
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
|
||||
are used for establishing chats with guaranteed end-to-end encryption
|
||||
which protects against network attacks and compromised servers.
|
||||
Chats marked with a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
guarantee end-to-end encrypted messages.</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
|
||||
to exchange encryption setup information through QR-code scanning or “invite links”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption between contacts and all members of a group chat.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
|
||||
chat</a>
|
||||
enables receivers to use end-to-end encryption with the contact.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
|
||||
|
||||
<h3 id="whene2e">
|
||||
|
||||
@@ -757,28 +761,37 @@ guarantee end-to-end encrypted messages.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>All end-to-end encrypted messages carry a padlock:</p>
|
||||
|
||||
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p>
|
||||
|
||||
<p>End-to-end encryption is guaranteed if there is a green checkmark next to the chat title:</p>
|
||||
|
||||
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
|
||||
<p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
|
||||
Since the Delta Chat Version 2 release series (July 2025)
|
||||
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
<h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
|
||||
|
||||
|
||||
How can I get guaranteed end-to-end encryption and green checkmarks? <a href="#howtoe2ee" class="anchor"></a>
|
||||
Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If you have a second communication channel with your chat partner,
|
||||
like a video chat or a different messenger,
|
||||
you can generate an invite link.</p>
|
||||
<p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
|
||||
it is impossible to receive or send messages without end-to-end encryption.</p>
|
||||
|
||||
<p>If you are together in person,
|
||||
you can show a QR code to your chat partner.</p>
|
||||
<p>If you instead create a profile using a classic e-mail server,
|
||||
you can send and receive messages without end-to-end encryption.
|
||||
Such messages lacking end-to-end encryption are marked with an e-mail icon
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
|
||||
|
||||
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You can send an invite link through another private chat,
|
||||
show an invitation QR code when next to each other or in a video call,
|
||||
or click on a “contact” that was shared in a chat.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
@@ -787,141 +800,60 @@ tap the chat group title to see its member list,
|
||||
and select “QR Invite code”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
tap the QR Code icon <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
|
||||
on the Delta Chat app main screen.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Let your chat partner scan the QR image
|
||||
<p>Ask your chat partner to scan the QR image
|
||||
with their Delta Chat app,
|
||||
or click “Copy” or “Share” to create an invite link
|
||||
and share it with your chat partner.</p>
|
||||
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">Secure-Join network messages are exchanged</a> between both devices.</p>
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>If both devices are online,
|
||||
both sides will eventually see a (group or direct) chat with a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
next to the title.</p>
|
||||
<p>If both sides are online, they will soon see a (group or direct) chat
|
||||
and can start messaging securely.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>If one of the devices is offline, the green checkmarks will only
|
||||
appear later when the device is internet-connected again
|
||||
and the Secure-Join network protocol completed.</p>
|
||||
<p>If one side is offline or in bad network,
|
||||
the ability to chat is delayed until connectivity is restored.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Congratulations!
|
||||
You now will automatically use guaranteed end-to-end encryption
|
||||
with this contact and both of you can add each other to green-checkmarked groups
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />,
|
||||
thereby automatically spreading guaranteed end-to-end encryption among its members.</p>
|
||||
You now will automatically use end-to-end encryption
|
||||
with this contact.
|
||||
If you add each other to chat groups,
|
||||
end-to-end encryption will be established among all members.</p>
|
||||
|
||||
<h3 id="e2eeguarantee">
|
||||
|
||||
|
||||
What does the green checkmark and “guaranteed end-to-end encryption” mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Chat titles with green checkmarks
|
||||
<p>A contact profile might show a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
mean that all messages in the chat will be end-to-end encrypted
|
||||
and can not be read or altered by compromised e-mail servers or Internet providers.
|
||||
Joining green-checkmarked group chats
|
||||
safely spreads everybody’s encryption information (and green checkmarks)
|
||||
in a manner that guarantees end-to-end encryption in the group and among members.</p>
|
||||
|
||||
<p>Contact profiles with green checkmarks
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
mean that messaging a contact is currently guaranteed to be end-to-end encrypted.
|
||||
and an “Introduced by” line.
|
||||
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
|
||||
or was introduced by a another green-checkmarked contact.
|
||||
Introductions happen automatically when adding members to groups.
|
||||
Whoever adds a contact to a green-checkmarked group becomes an introducer
|
||||
to those members who didn’t yet know about the added contact.
|
||||
Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
|
||||
becomes an introducer.
|
||||
In a contact profile you can tap on the “Introduced by …” text repeatedly
|
||||
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
|
||||
|
||||
<p>Note that in a contact profile you may see and tap introducers
|
||||
but there is no green checkmark in the profile title.
|
||||
This usually means that the contact <a href="#nocryptanymore">“sent a message from another device”</a>.</p>
|
||||
|
||||
<p>For more in-depth discussion of “guaranteed end-to-end encryption”
|
||||
please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
|
||||
and specifically read about “Verified Groups”, the technical term
|
||||
of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p>
|
||||
|
||||
<h3 id="nocryptanymore">
|
||||
|
||||
|
||||
A contact “sent a message from another device”, what can i do? <a href="#nocryptanymore" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Your chat with a contact lost guaranteed end-to-end encryption.
|
||||
The green checkmark was removed for this chat and contact when you see this warning.
|
||||
<strong>If you find the sudden drop of guaranteed end-to-end encryption
|
||||
surprising for this contact then don’t accept the warning!</strong>
|
||||
Instead check with your contact through a second channel
|
||||
like a video call, other messenger or a phone call,
|
||||
to find out what happened.</p>
|
||||
|
||||
<p>If your contact actually caused the drop of guaranteed end-to-end encryption
|
||||
please see the next paragraphs for common reasons and their mitigations.
|
||||
Regardless, all other green-checkmarked chats remain guaranteed end-to-end encrypted
|
||||
even if the contact is a member there.</p>
|
||||
|
||||
<p><strong>Your contact is using Delta Chat on a second device (phone or laptop)</strong></p>
|
||||
|
||||
<p>If they have another device with a Delta Chat app running,
|
||||
they should remove the profile from the new device
|
||||
and add it <a href="#multiclient">as a second device as described here</a>.
|
||||
As soon as they message you afterwards, the warning will be gone
|
||||
and guaranteed encryption is established with both devices of your contact.</p>
|
||||
|
||||
<p><strong>Your contact reinstalled Delta Chat using their old account login</strong></p>
|
||||
|
||||
<p>If they have <a href="#backup">a backup file</a>,
|
||||
they should remove the profile from the new device
|
||||
and rather import the backup file to re-create their profile.
|
||||
As soon as they message you afterwards, the warning will be gone
|
||||
and guaranteed encryption is re-established for this contact.</p>
|
||||
|
||||
<p>If they don’t have a backup file, it’s best to perform a <a href="#howtoe2ee">QR scan</a>
|
||||
with your chat partner to re-establish guaranteed end-to-end encryption.</p>
|
||||
|
||||
<p><strong>Your contact sent a mail through a webmail interface or another e-mail app
|
||||
and will get back to using Delta Chat soon again.</strong></p>
|
||||
|
||||
<p>If you are sure that the contact sometimes uses webmail,
|
||||
or another mail app lacking end-to-end encryption,
|
||||
then you may accept the warning.
|
||||
As soon as your contact uses Delta Chat again,
|
||||
guaranteed end-to-end encryption will be automatically re-established.</p>
|
||||
|
||||
<p><strong>Your contact stopped using Delta Chat entirely</strong></p>
|
||||
|
||||
<p>Sometimes remaining in contact is more important than end-to-end encryption.
|
||||
<a href="#tls">“Transport Layer Encryption” (TLS)</a> may still meaningfully protect
|
||||
the confidentiality of your messages between your device and the e-mail server.
|
||||
But without end-to-end encryption you and your contact are trusting your e-mail server
|
||||
to not read or manipulate your messages, and to not hand them to third parties.</p>
|
||||
|
||||
<p>In any case, you can not do much else than accept the warning.
|
||||
Please also remove the contact from any active green-checkmarked group
|
||||
which you can find in “Chats in Common” in the Contact profile.
|
||||
This spares your contact from getting “unreadable” messages.</p>
|
||||
|
||||
<p>If the contact removed Delta Chat because of buggy or undesirable behaviour,
|
||||
please consider posting to our <a href="https://support.delta.chat">support forum</a>
|
||||
to help us identify and address common problems. Thanks!</p>
|
||||
|
||||
<h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted">
|
||||
|
||||
|
||||
@@ -946,8 +878,7 @@ and attachment metadata such as filenames.</p>
|
||||
</h3>
|
||||
|
||||
<p>Yes, Delta Chat uses a secure subset of OpenPGP
|
||||
and only displays a padlock security indicator on a message
|
||||
if the whole message is properly encrypted and signed.
|
||||
requiring the whole message to be properly encrypted and signed.
|
||||
For example, “Detached signatures” are not treated as secure.</p>
|
||||
|
||||
<p>OpenPGP is not insecure by itself.
|
||||
@@ -968,7 +899,7 @@ which was thankfully adopted in summer 2023.</p>
|
||||
<h3 id="openpgp-alternatives">
|
||||
|
||||
|
||||
Did you consider using alternatives to OpenPGP for end-to-end -encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -1011,17 +942,15 @@ as defined by the Autocrypt Level 1 specification.</p>
|
||||
<h3 id="tls">
|
||||
|
||||
|
||||
Is a message exposed in cleartext if end-to-end encryption is not available? <a href="#tls" class="anchor"></a>
|
||||
Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Even if your messages are not guaranteed to be end-to-end encrypted,
|
||||
they are still protected from Internet providers like cell or cable companies.
|
||||
However, your and your recipient’s e-mail providers
|
||||
may read, analyze or even modify your messages,
|
||||
including any attachments,
|
||||
if they are not end-to-end encrypted.</p>
|
||||
<p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
|
||||
they are still protected from cell or cable companies who can not read or modify your e-mail messages.
|
||||
But both your and your recipient’s e-mail providers
|
||||
may read, analyze or modify your messages, including any attachments.</p>
|
||||
|
||||
<p>Delta Chat by default uses strict
|
||||
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a>
|
||||
@@ -1033,10 +962,6 @@ If the involved e-mail servers support <a href="https://datatracker.ietf.org/doc
|
||||
then transport encryption will be enforced between e-mail providers
|
||||
in which case Delta Chat communications will never be exposed in cleartext to the Internet
|
||||
even if the message was not end-to-end encrypted.</p>
|
||||
|
||||
<p>Note that <a href="#howtoe2ee">maintaining guaranteed end-to-end encryption</a> on top of TLS encryption
|
||||
provides pervasive safety between your and the recipient’s devices.
|
||||
Not even your e-mail or Internet provider will be able to read or modify your messages.</p>
|
||||
|
||||
<h3 id="message-metadata">
|
||||
|
||||
@@ -1099,74 +1024,6 @@ Delta Chat shows two fingerprints there.
|
||||
If the same fingerprints appear on your own and your contact’s device,
|
||||
the connection is safe.</p>
|
||||
|
||||
<h3 id="how-can-i-check-the-encryption-status-of-messages">
|
||||
|
||||
|
||||
How can I check the encryption status of messages? <a href="#how-can-i-check-the-encryption-status-of-messages" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>A little <strong>padlock</strong> in a message bubble denotes
|
||||
that the message was properly end-to-end encrypted from the given sender.
|
||||
If there is <strong>no padlock</strong>, the message was not properly end-to-end encrypted
|
||||
most likely because the sender uses an app or webmail interface
|
||||
without support for end-to-end–encryption.</p>
|
||||
|
||||
<h3 id="why-do-i-see-unencrypted-messages">
|
||||
|
||||
|
||||
Why do I see unencrypted messages? <a href="#why-do-i-see-unencrypted-messages" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If a contact uses a non-Autocrypt e-mail app,
|
||||
all messages involving this contact (in a group or 1:1 chat)
|
||||
will not be end-to-end encrypted, and thus not show a “padlock” with messages.
|
||||
Note that even if your contacts use Delta Chat on their account,
|
||||
they might also use a non-Autocrypt e-mail app on that account
|
||||
which then may cause intermittently unencrypted messages.
|
||||
Replying unencrypted to unencrypted messages is mandated by Autocrypt
|
||||
to prevent unreadable messages on the side of your contacts
|
||||
and their non-Autocrypt e-mail app.</p>
|
||||
|
||||
<h3 id="how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">
|
||||
|
||||
|
||||
How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app? <a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If you need a safely end-to-end encrypted chat with a contact
|
||||
who is using their e-mail account both with Delta Chat and non-Autocrypt apps (e.g. webmail),
|
||||
it’s best to setup <a href="#howtoe2ee">guaranteed end-to-end encryption with them</a>
|
||||
and then create a guaranteed end-to-end encrypted group chat with you two as members.
|
||||
In this group chat all messages will be end-to-end encrypted
|
||||
even if the direct chat between you two has a
|
||||
<a href="#nocryptanymore">“… sent a message from another device”</a> warning.</p>
|
||||
|
||||
<h3 id="how-can-i-ensure-message-end-to-end-encryption-and-deletion">
|
||||
|
||||
|
||||
How can I ensure message end-to-end encryption and deletion? <a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>The best way to ensure every message is end-to-end encrypted,
|
||||
and metadata deleted as quickly as possible
|
||||
is <a href="#howtoe2ee">using chats with guaranteed end-to-end encryption</a>
|
||||
and turning on <a href="#ephemeralmsgs">disappearing messages</a>.</p>
|
||||
|
||||
<p>Guaranteed end-to-end encrypted chats protect against <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM attacks</a>
|
||||
and turning on disappearing messages deletes the messages
|
||||
on the server after a user-configured time.</p>
|
||||
|
||||
<p>If you don’t need a longer-lived copy of your messages on the server,
|
||||
you can also turn on <a href="#delold">“delete messages from server automatically”</a>.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
|
||||
@@ -1175,45 +1032,35 @@ you can also turn on <a href="#delold">“delete messages from server automatica
|
||||
|
||||
</h3>
|
||||
|
||||
<p>No, Delta Chat doesn’t support Perfect Forward Secrecy (PFS).
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
|
||||
This means that if your Delta Chat private decryption key is leaked,
|
||||
and someone has collected your prior in-transit messages,
|
||||
they will be able to decrypt and read them using the leaked decryption key.</p>
|
||||
|
||||
<p>Note, however, that if anyone obtains to your decryption keys,
|
||||
they will typically also be able to obtain your messages,
|
||||
irrespective if Perfect Forward Secrecy is in place or not.
|
||||
The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
<p>Note however, that Forward Secrecy only increases your security
|
||||
if you delete messages or use ephemeral deletion timers.
|
||||
Otherwise, if anyone obtains your decryption keys,
|
||||
they are typically also able to get all your non-deleted messages
|
||||
and don’t need to decrypt any previously collected messages.</p>
|
||||
|
||||
<p>It is possible that Delta Chat evolves to support Perfect Forward Secrecy,
|
||||
because OpenPGP is just a container for encrypted messages
|
||||
but encryption key management (and thus key rotation or key “ratcheting”)
|
||||
could be organized in flexible ways.
|
||||
See <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouia’s PFS prototype</a>
|
||||
for existing experiments in the OpenPGP implementor community.</p>
|
||||
<p>The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we also discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
|
||||
<h3 id="is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
|
||||
|
||||
Is end-to-end encryption of Delta Chat as safe as Signal? <a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal" class="anchor"></a>
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>It depends on what is important to you.
|
||||
Delta Chat <a href="#pfs">does not support PFS</a> like Signal does
|
||||
but it provides <a href="#e2eeguarantee">guaranteed end-to-end encrypted chats</a>
|
||||
that are safe against compromised servers or corrupted networks.
|
||||
Signal and most other PFS-supporting messengers do not provide
|
||||
a practical scheme for protecting chat groups from network attacks
|
||||
which are arguably more worrisome
|
||||
than a potential attacker who seizes your phone and private encryption setup
|
||||
but somehow not your messages, yet has a full record of all
|
||||
past encrypted messages.</p>
|
||||
<p>Sim.</p>
|
||||
|
||||
<p>In any case, Delta Chat’s end-to-end encryption uses a <a href="#openpgp-secure">secure subset of OpenPGP</a>
|
||||
which has been <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">independently security-audited</a>.</p>
|
||||
<p>We devised a forward secrecy scheme that withstood initial scrutiny from cryptographers and usable security experts.
|
||||
Our tentative scheme is designed to reliably work in federated messaging networks and with multi-device usage.
|
||||
However, an implementation has not been scheduled yet (as of Mid 2025).</p>
|
||||
|
||||
<h3 id="importkey">
|
||||
|
||||
@@ -1248,7 +1095,7 @@ from most recent to older:</p>
|
||||
<li>
|
||||
<p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of
|
||||
rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place.
|
||||
rPGP serves as the end-to-end encyption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
|
||||
rPGP serves as the end-to-end encryption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
|
||||
Two advisories were released related to the findings of this audit:</p>
|
||||
|
||||
<ul>
|
||||
@@ -1642,6 +1489,11 @@ seria feito pelo aplicativo Delta Chat.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Note:
|
||||
Changing email addresses is temporarily disabled
|
||||
because of ongoing changes to the DeltaChat core.
|
||||
It should be available again in a few months.</p>
|
||||
|
||||
<ol>
|
||||
<li>
|
||||
<p>Change your address in “Settings → Advanced → Password and Account” and
|
||||
|
||||
+112
-259
@@ -36,27 +36,23 @@
|
||||
<li><a href="#почему-delta-chat-интегрируется-с-централизованными-проприетарными-push-сервисами-applegoogle">Почему Delta Chat интегрируется с централизованными проприетарными Push-сервисами Apple/Google?</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#шифрование-и-безопасность">Шифрование и безопасность</a>
|
||||
<li><a href="#e2ee">Шифрование и безопасность</a>
|
||||
<ul>
|
||||
<li><a href="#какие-стандарты-используются-для-сквозного-шифрования">Какие стандарты используются для сквозного шифрования?</a></li>
|
||||
<li><a href="#whene2e">Как узнать зашифрованы ли сообщения сквозным шифрованием?</a></li>
|
||||
<li><a href="#howtoe2ee">Как получить гарантированное сквозное шифрование и зелёные галочки?</a></li>
|
||||
<li><a href="#e2eeguarantee">Что означает зелёная галочка и “гарантированное сквозное шифрование”?</a></li>
|
||||
<li><a href="#nocryptanymore">Контакт “отправил сообщение с другого устройства”, что делать?</a></li>
|
||||
<li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
|
||||
<li><a href="#зашифрованы-ли-вложения-изображения-файлы-аудио-и-т-д-сквозным-шифрованием">Зашифрованы ли вложения (изображения, файлы, аудио и т. д.) сквозным шифрованием?</a></li>
|
||||
<li><a href="#openpgp-secure">OpenPGP безопасен?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Рассматривали ли вы альтернативы OpenPGP для сквозного шифрования?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
|
||||
<li><a href="#подвержен-ли-delta-chat-уязвимости-efail">Подвержен ли Delta Chat уязвимости EFAIL?</a></li>
|
||||
<li><a href="#tls">Будет ли сообщение передано в открытом виде, если сквозное шифрование недоступно?</a></li>
|
||||
<li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
|
||||
<li><a href="#message-metadata">Как Delta Chat защищает метаданные в сообщениях?</a></li>
|
||||
<li><a href="#device-seizure">Как защитить метаданные и контакты при изъятии устройства?</a></li>
|
||||
<li><a href="#как-я-могу-проверить-информацию-о-шифровании">Как я могу проверить информацию о шифровании?</a></li>
|
||||
<li><a href="#как-я-могу-проверить-статус-шифрования-сообщений">Как я могу проверить статус шифрования сообщений?</a></li>
|
||||
<li><a href="#почему-я-вижу-незашифрованные-сообщения">Почему я вижу незашифрованные сообщения?</a></li>
|
||||
<li><a href="#как-я-могу-получить-зашифрованный-сквозным-шифрованием-чат-с-контактом-delta-chat-который-иногда-использует-веб-почту-или-другое-приложение-электронной-почты-не-поддерживающее-autocrypt">Как я могу получить зашифрованный сквозным шифрованием чат с контактом Delta Chat, который иногда использует веб-почту или другое приложение электронной почты, не поддерживающее Autocrypt?</a></li>
|
||||
<li><a href="#как-я-могу-обеспечить-сквозное-шифрование-и-удаление-сообщений">Как я могу обеспечить сквозное шифрование и удаление сообщений?</a></li>
|
||||
<li><a href="#pfs">Поддерживает ли Delta Chat совершенную прямую секретность (Perfect forward secrecy, PFS)?</a></li>
|
||||
<li><a href="#является-ли-сквозное-шифрование-delta-chat-таким-же-безопасным-как-signal">Является ли сквозное шифрование Delta Chat таким же безопасным как Signal?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#importkey">Можно ли повторно использовать существующий секретный ключ?</a></li>
|
||||
<li><a href="#security-audits">Проходил ли Delta Chat независимую проверку на наличие уязвимостей безопасности?</a></li>
|
||||
</ul>
|
||||
@@ -719,10 +715,10 @@ Push-уведомления недоступны.</p>
|
||||
включая потенциальный сервер, который <a href="https://delta.chat/chatmail#selfhosted">вы можете настроить самостоятельно без нашего разрешения.</a>.
|
||||
Добро пожаловать в мир мощной и совместимой системы chatmail и электронной почты :)</p>
|
||||
|
||||
<h2 id="шифрование-и-безопасность">
|
||||
<h2 id="e2ee">
|
||||
|
||||
|
||||
Шифрование и безопасность <a href="#шифрование-и-безопасность" class="anchor"></a>
|
||||
Шифрование и безопасность <a href="#e2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h2>
|
||||
@@ -735,18 +731,26 @@ Push-уведомления недоступны.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> используется для автоматической
|
||||
установки сквозного шифрования при работе с контактами и групповыми чатами.
|
||||
Autocrypt использует ограниченное и <a href="#openpgp-secure">безопасное подмножество стандарта OpenPGP</a>.
|
||||
Сообщения, зашифрованные сквозным шифрованием, помечаются замком
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
|
||||
<p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
|
||||
to provide automatic end-to-end encryption using these protocols:</p>
|
||||
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Протоколы Secure-Join</a>
|
||||
используются для создания чатов с гарантированным сквозным шифрованием,
|
||||
которое защищает от сетевых атак и скомпрометированных серверов.
|
||||
Чаты, отмеченные зелёной галочкой
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
гарантируют сквозное шифрование сообщений.</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
|
||||
to exchange encryption setup information through QR-code scanning or “invite links”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption between contacts and all members of a group chat.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
|
||||
chat</a>
|
||||
enables receivers to use end-to-end encryption with the contact.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
|
||||
|
||||
<h3 id="whene2e">
|
||||
|
||||
@@ -756,28 +760,37 @@ Autocrypt использует ограниченное и <a href="#openpgp-sec
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Все сообщения, зашифрованные сквозным шифрованием, имеют значок замка:</p>
|
||||
|
||||
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="Значок замка в пузырьке" /></p>
|
||||
|
||||
<p>Сквозное шифрование гарантировано, если рядом с заголовком чата стоит зелёная галочка:</p>
|
||||
|
||||
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="Зелёная галочка в заголовке" /></p>
|
||||
<p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
|
||||
Since the Delta Chat Version 2 release series (July 2025)
|
||||
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
<h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
|
||||
|
||||
|
||||
Как получить гарантированное сквозное шифрование и зелёные галочки? <a href="#howtoe2ee" class="anchor"></a>
|
||||
Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Если у вас есть второй канал связи с вашим собеседником,
|
||||
например, видеочат или другой мессенджер,
|
||||
вы можете создать ссылку-приглашение.</p>
|
||||
<p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
|
||||
it is impossible to receive or send messages without end-to-end encryption.</p>
|
||||
|
||||
<p>Если вы встретились лично с собеседником,
|
||||
вы можете показать ему свой QR-код.</p>
|
||||
<p>If you instead create a profile using a classic e-mail server,
|
||||
you can send and receive messages without end-to-end encryption.
|
||||
Such messages lacking end-to-end encryption are marked with an e-mail icon
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
|
||||
|
||||
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You can send an invite link through another private chat,
|
||||
show an invitation QR code when next to each other or in a video call,
|
||||
or click on a “contact” that was shared in a chat.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
@@ -786,141 +799,60 @@ Autocrypt использует ограниченное и <a href="#openpgp-sec
|
||||
и выберите “QR-код приглашения”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Для <strong>приглашений в прямой чат 1:1</strong>,
|
||||
коснитесь значка QR-кода <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
|
||||
на главном экране приложения Delta Chat.</p>
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
tap the QR Code icon <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
|
||||
on the Delta Chat app main screen.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Позвольте вашему собеседнику отсканировать QR-код
|
||||
с помощью приложения Delta Chat,
|
||||
или нажмите “Копировать” или “Поделиться”, чтобы создать ссылку-приглашение
|
||||
и отправьте её вашему собеседнику.</p>
|
||||
<p>Ask your chat partner to scan the QR image
|
||||
with their Delta Chat app,
|
||||
or click “Copy” or “Share” to create an invite link
|
||||
and share it with your chat partner.</p>
|
||||
|
||||
<p>Теперь ожидайте, пока <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">сообщения Secure-Join</a> будут переданы между обоими устройствами.</p>
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>Если оба устройства находятся в сети,
|
||||
обе стороны в конечном итоге увидят (групповой или прямой) чат с зелёной галочкой
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="зелёная галочка" />
|
||||
рядом с названием.</p>
|
||||
<p>If both sides are online, they will soon see a (group or direct) chat
|
||||
and can start messaging securely.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Если одно из устройств не подключено к сети, зелёные галочки появятся только после того,
|
||||
как устройство снова подключится к Интернету
|
||||
и сетевой протокол Secure-Join будет завершён.</p>
|
||||
<p>If one side is offline or in bad network,
|
||||
the ability to chat is delayed until connectivity is restored.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Поздравляем!
|
||||
Теперь вы будете автоматически использовать гарантированное сквозное шифрование
|
||||
с этим контактом, и вы оба сможете добавлять друг друга в группы, отмеченные зелёной галочкой
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="зелёная галочка" />,
|
||||
тем самым автоматически распространяя гарантированное сквозное шифрование среди её участников.</p>
|
||||
<p>Congratulations!
|
||||
You now will automatically use end-to-end encryption
|
||||
with this contact.
|
||||
If you add each other to chat groups,
|
||||
end-to-end encryption will be established among all members.</p>
|
||||
|
||||
<h3 id="e2eeguarantee">
|
||||
|
||||
|
||||
Что означает зелёная галочка и “гарантированное сквозное шифрование”? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Чаты, помеченные зелёными галочками
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="зелёная галочка" />
|
||||
означают, что все сообщения в чате будут зашифрованы сквозным шифрованием
|
||||
и не могут быть прочитаны или изменены скомпрометированными серверами электронной почты или интернет-провайдерами.
|
||||
Присоединение к групповым чатам с зелёной галочкой
|
||||
безопасно распространяет информацию о шифровании всех участников (и зелёные галочки)
|
||||
таким образом, чтобы гарантировать сквозное шифрование в группе и между её участниками.</p>
|
||||
|
||||
<p>Профили контактов с зелёной галочкой
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="зелёная галочка" />
|
||||
означают, что отправка сообщений контакту в настоящее время гарантированно зашифрована сквозным шифрованием.
|
||||
Каждый контакт с зелёной галочкой либо совершил с вами прямое <a href="#howtoe2ee">QR-сканирование</a>,
|
||||
либо был представлен другим контактом с зелёной галочкой.
|
||||
Знакомство происходит автоматически при добавлении участников в группы.
|
||||
Тот, кто добавляет контакт в группу, отмеченную зелёной галочкой, становится представителем
|
||||
для тех участников, которые еще не знают о добавленном контакте.
|
||||
В профиле контакта можно несколько раз нажать на текст “Представлен …” несколько раз
|
||||
пока не дойдёте до того, с кем вы непосредственно провели <a href="#howtoe2ee">QR-сканирование</a>.</p>
|
||||
|
||||
<p>Обратите внимание, что в профиле контакта вы можете увидеть и присоединённых знакомых,
|
||||
но в заголовке профиля нет зелёной галочки.
|
||||
Обычно это означает, что контакт <a href="#nocryptanymore">“отправил сообщение с другого устройства”</a>.</p>
|
||||
<p>A contact profile might show a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
and an “Introduced by” line.
|
||||
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
|
||||
or was introduced by a another green-checkmarked contact.
|
||||
Introductions happen automatically when adding members to groups.
|
||||
Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
|
||||
becomes an introducer.
|
||||
In a contact profile you can tap on the “Introduced by …” text repeatedly
|
||||
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
|
||||
|
||||
<p>Для более подробного обсуждения “гарантированного сквозного шифрования”
|
||||
пожалуйста, обратитесь к <a href="https://securejoin.delta.chat/en/latest/new.html">протоколам Secure-Join</a>
|
||||
и прочитайте о “Проверенных группах”, техническом термине,
|
||||
который здесь называется “группами с зелёной галочкой” или чатами с “гарантированным сквозным шифрованием”.</p>
|
||||
|
||||
<h3 id="nocryptanymore">
|
||||
|
||||
|
||||
Контакт “отправил сообщение с другого устройства”, что делать? <a href="#nocryptanymore" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Ваш чат с контактом утратил гарантированное сквозное шифрование.
|
||||
Зелёная галочка была удалена для этого чата и контакта, и когда вы увидели предупреждение.
|
||||
<strong>Если вы обнаружили внезапное прекращение гарантированного сквозного шифрования
|
||||
для этого контакта, не принимайте предупреждение!</strong>
|
||||
Вместо этого свяжитесь со своим контактом по второму каналу,
|
||||
например, видеозвонок, другой мессенджер или телефонный звонок,
|
||||
чтобы узнать, что произошло.</p>
|
||||
|
||||
<p>Если ваш контакт стал причиной потери гарантированного сквозного шифрования,
|
||||
пожалуйста, ознакомьтесь с распространёнными причинами и способами их устранения в следующих параграфах.
|
||||
Независимо от этого, все остальные чаты, отмеченные зелёной галочкой, остаются гарантированно зашифрованными сквозным шифрованием,
|
||||
даже если этот контакт является его участником.</p>
|
||||
|
||||
<p><strong>Ваш контакт использует Delta Chat на втором устройстве (телефоне или ноутбуке)</strong></p>
|
||||
|
||||
<p>Если у него есть другое устройство с запущенным приложением Delta Chat,
|
||||
ему следует удалить учётную запись с нового устройства
|
||||
и добавить его <a href="#multiclient">как второе устройство, как описано здесь</a>.
|
||||
После того, как он отправит вам сообщение, предупреждение исчезнет
|
||||
и гарантированное шифрование будет установлено на обоих устройствах вашего собеседника.</p>
|
||||
|
||||
<p><strong>Ваш контакт переустановил Delta Chat, используя старые учетные данные для входа</strong></p>
|
||||
|
||||
<p>Если у него есть <a href="#backup">файл резервной копии</a>,
|
||||
ему следует удалить профиль с нового устройства
|
||||
и вместо этого импортировать резервную копию для восстановления своего профиля.
|
||||
После того, как он отправит вам сообщение, предупреждение исчезнет,
|
||||
и гарантированное шифрование будет восстановлено для этого контакта.</p>
|
||||
|
||||
<p>Если у него нет файла резервной копии, лучше всего выполнить <a href="#howtoe2ee">сканирование QR-кода</a>
|
||||
с вашим собеседником, чтобы восстановить гарантированное сквозное шифрование.</p>
|
||||
|
||||
<p><strong>Ваш контакт отправил письмо через интерфейс веб-почты или другое приложение электронной почты
|
||||
и снова вернулся к использованию Delta Chat.</strong></p>
|
||||
|
||||
<p>Если вы уверены, что ваш контакт иногда использует веб-почту
|
||||
или другое приложение электронной почты, в котором отсутствует сквозное шифрование,
|
||||
то вы можете принять предупреждение.
|
||||
Как только контакт снова начнёт использовать Delta Chat,
|
||||
гарантированное сквозное шифрование будет автоматически восстановлено.</p>
|
||||
|
||||
<p><strong>Ваш контакт полностью прекратил использование Delta Chat</strong></p>
|
||||
|
||||
<p>Иногда оставаться на связи важнее, чем сквозное шифрование.
|
||||
<a href="#tls">“Протокол защиты транспортного уровня” (TLS)</a> всё ещё может существенно защитить
|
||||
конфиденциальность ваших сообщений между вашим устройством и сервером электронной почты.
|
||||
Но без сквозного шифрования вы и ваш контакт должны доверять серверу электронной почты,
|
||||
который не должен читать и манипулировать вашими сообщениями, и не передавать их третьим лицам.</p>
|
||||
|
||||
<p>В любом случае, вы ничего не можете сделать, кроме как принять предупреждение.
|
||||
Также удалите этот контакт из всех активных групп, отмеченных зелёной галочкой,
|
||||
которые можно найти в разделе “Общие чаты” в профиле контакта.
|
||||
Это избавит ваш контакт от получения “нечитаемых” сообщений.</p>
|
||||
|
||||
<p>Если контакт удалил Delta Chat из-за ошибок или нежелательного поведения,
|
||||
пожалуйста, подумайте о том, чтобы поделиться этой информацией на нашем <a href="https://support.delta.chat">форуме поддержки</a>,
|
||||
чтобы помочь нам выявить и устранить общие проблемы. Спасибо!</p>
|
||||
|
||||
<h3 id="зашифрованы-ли-вложения-изображения-файлы-аудио-и-т-д-сквозным-шифрованием">
|
||||
|
||||
|
||||
@@ -944,10 +876,9 @@ Autocrypt использует ограниченное и <a href="#openpgp-sec
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Да, Delta Chat использует безопасное подмножество OpenPGP
|
||||
и отображает индикатор безопасности в виде замка только,
|
||||
если всё сообщение правильно зашифровано и подписано.
|
||||
Например, “Отдельные подписи” не считаются безопасными.</p>
|
||||
<p>Yes, Delta Chat uses a secure subset of OpenPGP
|
||||
requiring the whole message to be properly encrypted and signed.
|
||||
For example, “Detached signatures” are not treated as secure.</p>
|
||||
|
||||
<p>OpenPGP сам по себе не является небезопасным.
|
||||
Большинство обсуждаемых в публичной сфере проблем безопасности OpenPGP
|
||||
@@ -967,7 +898,7 @@ Delta Chat вместо этого использует реализацию Ope
|
||||
<h3 id="openpgp-alternatives">
|
||||
|
||||
|
||||
Рассматривали ли вы альтернативы OpenPGP для сквозного шифрования? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -1010,17 +941,15 @@ Delta Chat вместо этого использует реализацию Ope
|
||||
<h3 id="tls">
|
||||
|
||||
|
||||
Будет ли сообщение передано в открытом виде, если сквозное шифрование недоступно? <a href="#tls" class="anchor"></a>
|
||||
Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Даже если не гарантируется сквозное шифрование ваших сообщений,
|
||||
они все равно защищены от интернет-провайдеров, сотовых операторов или кабельных компаний.
|
||||
Однако провайдеры электронной почты, ваш и ваших получателей
|
||||
могут читать, анализировать или даже изменять ваши сообщения,
|
||||
включая любые вложения,
|
||||
если они не зашифрованы сквозным шифрованием.</p>
|
||||
<p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
|
||||
they are still protected from cell or cable companies who can not read or modify your e-mail messages.
|
||||
But both your and your recipient’s e-mail providers
|
||||
may read, analyze or modify your messages, including any attachments.</p>
|
||||
|
||||
<p>Delta Chat по умолчанию использует строгое
|
||||
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS-шифрование</a>,
|
||||
@@ -1032,10 +961,6 @@ Delta Chat вместо этого использует реализацию Ope
|
||||
то между провайдерами электронной почты будет применяться протокол защиты транспортного уровня.
|
||||
В этом случае сообщения Delta Chat никогда не будут переданы в открытом виде через Интернет,
|
||||
даже если сообщение не было зашифровано сквозным шифрованием.</p>
|
||||
|
||||
<p>Обратите внимание, что <a href="#howtoe2ee">поддержание гарантированного сквозного шифрования</a> поверх шифрования TLS
|
||||
обеспечивает полную безопасность между вашими устройствами и устройствами получателя.
|
||||
Ни ваш провайдер электронной почты, ни провайдер Интернета не смогут прочитать или изменить ваши сообщения.</p>
|
||||
|
||||
<h3 id="message-metadata">
|
||||
|
||||
@@ -1099,74 +1024,6 @@ Delta Chat показывает там два отпечатка.
|
||||
Если на вашем устройстве и на устройстве вашего контакта показаны одинаковые отпечатки,
|
||||
соединение безопасно.</p>
|
||||
|
||||
<h3 id="как-я-могу-проверить-статус-шифрования-сообщений">
|
||||
|
||||
|
||||
Как я могу проверить статус шифрования сообщений? <a href="#как-я-могу-проверить-статус-шифрования-сообщений" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Маленький <strong>значок замка</strong> в сообщении означает,
|
||||
что сообщение было правильно зашифровано сквозным шифрованием от данного отправителя.
|
||||
Если <strong>замка нет</strong>, сообщение не было правильно зашифровано,
|
||||
возможно, потому что отправитель использует приложение или веб-интерфейс электронной почты
|
||||
без поддержки сквозного шифрования.</p>
|
||||
|
||||
<h3 id="почему-я-вижу-незашифрованные-сообщения">
|
||||
|
||||
|
||||
Почему я вижу незашифрованные сообщения? <a href="#почему-я-вижу-незашифрованные-сообщения" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Если контакт использует приложение электронной почты, не поддерживающее Autocrypt,
|
||||
все сообщения, включающие этого контакта (в групповом или личном 1:1 чате),
|
||||
не будут зашифрованы сквозным шифрованием, и поэтому не будут иметь “значок замка” в сообщениях.
|
||||
Обратите внимание, что даже если ваши контакты используют Delta Chat на своем аккаунте,
|
||||
они также могут использовать приложение электронной почты, не поддерживающее Autocrypt,
|
||||
на том же аккаунте, что может привести к периодически незашифрованным сообщениям.
|
||||
Ответ на незашифрованные сообщения незашифрованным сообщением является обязательным в Autocrypt,
|
||||
чтобы предотвратить появление нечитаемых сообщений на стороне ваших контактов
|
||||
и их приложении электронной почты, которое не поддерживает Autocrypt.</p>
|
||||
|
||||
<h3 id="как-я-могу-получить-зашифрованный-сквозным-шифрованием-чат-с-контактом-delta-chat-который-иногда-использует-веб-почту-или-другое-приложение-электронной-почты-не-поддерживающее-autocrypt">
|
||||
|
||||
|
||||
Как я могу получить зашифрованный сквозным шифрованием чат с контактом Delta Chat, который иногда использует веб-почту или другое приложение электронной почты, не поддерживающее Autocrypt? <a href="#как-я-могу-получить-зашифрованный-сквозным-шифрованием-чат-с-контактом-delta-chat-который-иногда-использует-веб-почту-или-другое-приложение-электронной-почты-не-поддерживающее-autocrypt" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Если вам нужен зашифрованный сквозным шифрованием чат с контактом,
|
||||
который использует свой адрес электронной почты как с Delta Chat, так и с приложениями, не поддерживающими Autocrypt (например, веб-почтой),
|
||||
лучше всего настроить с ним <a href="#howtoe2ee">гарантированное сквозное шифрование</a>
|
||||
и затем создать гарантированно зашифрованный сквозным шифрованием групповой чат с вами двумя как участниками.
|
||||
В этом групповом чате все сообщения будут зашифрованы сквозным шифрованием,
|
||||
даже если прямой чат между вами двумя имеет предупреждение
|
||||
<a href="#nocryptanymore">“… отправил сообщение с другого устройства”</a>.</p>
|
||||
|
||||
<h3 id="как-я-могу-обеспечить-сквозное-шифрование-и-удаление-сообщений">
|
||||
|
||||
|
||||
Как я могу обеспечить сквозное шифрование и удаление сообщений? <a href="#как-я-могу-обеспечить-сквозное-шифрование-и-удаление-сообщений" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Лучший способ обеспечить сквозное шифрование каждого сообщения,
|
||||
где метаданные удаляются как можно быстрее,
|
||||
это <a href="#howtoe2ee">использовать чаты с гарантированным сквозным шифрованием</a>
|
||||
и включить <a href="#ephemeralmsgs">исчезающие сообщения</a>.</p>
|
||||
|
||||
<p>Чаты с гарантированным сквозным шифрованием защищают от <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">атак “человек посередине”</a>,
|
||||
а включение исчезающих сообщений удаляет сообщения
|
||||
на сервере через заданное пользователем время.</p>
|
||||
|
||||
<p>Если вам не нужна долгоживущая копия ваших сообщений на сервере,
|
||||
вы также можете включить <a href="#delold">“удалять сообщения с сервера автоматически”</a>.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
|
||||
@@ -1175,44 +1032,35 @@ Delta Chat показывает там два отпечатка.
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Нет, Delta Chat не поддерживает совершенную прямую секретность (PFS).
|
||||
Это означает, что если ваш личный ключ дешифрования Delta Chat будет скомпрометирован,
|
||||
и кто-то собрал ваши предыдущие сообщения, переданные по сети,
|
||||
то они смогут расшифровать и прочитать их с помощью скомпрометированного ключа дешифрования.</p>
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>Обратите внимание, если кто-то получит доступ к вашим ключам дешифрования,
|
||||
они, как правило, также смогут получить доступ к вашим сообщениям,
|
||||
независимо от того, используется ли совершенная прямая секретность или нет.
|
||||
Типичная реальная ситуация для утечки ключей дешифрования - это изъятие устройства,
|
||||
о чём мы говорим в нашем ответе <a href="#device-seizure">о метаданных и изъятии устройства</a>.</p>
|
||||
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
|
||||
This means that if your Delta Chat private decryption key is leaked,
|
||||
and someone has collected your prior in-transit messages,
|
||||
they will be able to decrypt and read them using the leaked decryption key.</p>
|
||||
|
||||
<p>Возможно, Delta Chat будет развиваться в направлении поддержки совершенной прямой секретности (PFS),
|
||||
поскольку OpenPGP является всего лишь контейнером для зашифрованных сообщений,
|
||||
но управление ключами шифрования (и, следовательно, ротация ключей или “переключение” ключей)
|
||||
могут быть организованы гибкими способами.
|
||||
См. <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">прототип PFS Seqouia</a>
|
||||
для существующих экспериментов в сообществе разработчиков OpenPGP.</p>
|
||||
<p>Note however, that Forward Secrecy only increases your security
|
||||
if you delete messages or use ephemeral deletion timers.
|
||||
Otherwise, if anyone obtains your decryption keys,
|
||||
they are typically also able to get all your non-deleted messages
|
||||
and don’t need to decrypt any previously collected messages.</p>
|
||||
|
||||
<p>The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we also discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
|
||||
<h3 id="является-ли-сквозное-шифрование-delta-chat-таким-же-безопасным-как-signal">
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
|
||||
|
||||
Является ли сквозное шифрование Delta Chat таким же безопасным как Signal? <a href="#является-ли-сквозное-шифрование-delta-chat-таким-же-безопасным-как-signal" class="anchor"></a>
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Это зависит от того, что для вас важно.
|
||||
Delta Chat <a href="#pfs">не поддерживает PFS</a>, как Signal,
|
||||
но обеспечивает <a href="#e2eeguarantee">гарантированно зашифрованные сквозным шифрованием чаты</a>
|
||||
защищенные от скомпрометированных серверов или поврежденных сетей.
|
||||
Signal и большинство других мессенджеров, поддерживающих PFS,
|
||||
не предоставляют практической схемы защиты групповых чатов от сетевых атак,
|
||||
которые, возможно, вызывают большее беспокойство,
|
||||
чем потенциальный злоумышленник, который захватывает ваш телефон и настройки персонального шифрования,
|
||||
но почему-то не ваши сообщения, но при этом имеет полный отчет обо всех прошлых зашифрованных сообщениях.</p>
|
||||
<p>Да.</p>
|
||||
|
||||
<p>В любом случае, сквозное шифрование Delta Chat использует <a href="#openpgp-secure">безопасное подмножество OpenPGP</a>
|
||||
которое прошло <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">независимую проверку безопасности</a>.</p>
|
||||
<p>We devised a forward secrecy scheme that withstood initial scrutiny from cryptographers and usable security experts.
|
||||
Our tentative scheme is designed to reliably work in federated messaging networks and with multi-device usage.
|
||||
However, an implementation has not been scheduled yet (as of Mid 2025).</p>
|
||||
|
||||
<h3 id="importkey">
|
||||
|
||||
@@ -1640,6 +1488,11 @@ Delta Chat</a>.</li>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Note:
|
||||
Changing email addresses is temporarily disabled
|
||||
because of ongoing changes to the DeltaChat core.
|
||||
It should be available again in a few months.</p>
|
||||
|
||||
<ol>
|
||||
<li>
|
||||
<p>Измените свой адрес в разделе “Настройки → Дополнительные параметры → Пароль и аккаунт” и
|
||||
|
||||
@@ -36,27 +36,23 @@
|
||||
<li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#encryption-and-security">Encryption and Security</a>
|
||||
<li><a href="#e2ee">Encryption and Security</a>
|
||||
<ul>
|
||||
<li><a href="#which-standards-are-used-for-end-to-end-encryption">Which standards are used for end-to-end encryption?</a></li>
|
||||
<li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I get guaranteed end-to-end encryption and green checkmarks?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark and “guaranteed end-to-end encryption” mean?</a></li>
|
||||
<li><a href="#nocryptanymore">A contact “sent a message from another device”, what can i do?</a></li>
|
||||
<li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
|
||||
<li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li>
|
||||
<li><a href="#openpgp-secure">Is OpenPGP secure?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end -encryption?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
|
||||
<li><a href="#is-delta-chat-vulnerable-to-efail">Is Delta Chat vulnerable to EFAIL?</a></li>
|
||||
<li><a href="#tls">Is a message exposed in cleartext if end-to-end encryption is not available?</a></li>
|
||||
<li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
|
||||
<li><a href="#message-metadata">How does Delta Chat protect metadata in messages?</a></li>
|
||||
<li><a href="#device-seizure">How to protect metadata and contacts when a device is seized?</a></li>
|
||||
<li><a href="#how-can-i-check-encryption-information">How can i check encryption information?</a></li>
|
||||
<li><a href="#how-can-i-check-the-encryption-status-of-messages">How can I check the encryption status of messages?</a></li>
|
||||
<li><a href="#why-do-i-see-unencrypted-messages">Why do I see unencrypted messages?</a></li>
|
||||
<li><a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app?</a></li>
|
||||
<li><a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion">How can I ensure message end-to-end encryption and deletion?</a></li>
|
||||
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
|
||||
<li><a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">Is end-to-end encryption of Delta Chat as safe as Signal?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#importkey">Môžem znova použiť svoj existujúci súkromný kľúč?</a></li>
|
||||
<li><a href="#security-audits">Was Delta Chat independently audited for security vulnerabilities?</a></li>
|
||||
</ul>
|
||||
@@ -723,10 +719,10 @@ that achieves “instant delivery” of messages for all chatmail servers
|
||||
including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>.
|
||||
Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p>
|
||||
|
||||
<h2 id="encryption-and-security">
|
||||
<h2 id="e2ee">
|
||||
|
||||
|
||||
Encryption and Security <a href="#encryption-and-security" class="anchor"></a>
|
||||
Encryption and Security <a href="#e2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h2>
|
||||
@@ -739,18 +735,26 @@ Welcome to the power of the interoperable and massive chatmail and e-mail system
|
||||
|
||||
</h3>
|
||||
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption with contacts and group chats.
|
||||
Autocrypt uses a limited and <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>.
|
||||
End-to-End encrypted messages are marked with a padlock
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
|
||||
<p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
|
||||
to provide automatic end-to-end encryption using these protocols:</p>
|
||||
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
|
||||
are used for establishing chats with guaranteed end-to-end encryption
|
||||
which protects against network attacks and compromised servers.
|
||||
Chats marked with a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
guarantee end-to-end encrypted messages.</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
|
||||
to exchange encryption setup information through QR-code scanning or “invite links”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption between contacts and all members of a group chat.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
|
||||
chat</a>
|
||||
enables receivers to use end-to-end encryption with the contact.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
|
||||
|
||||
<h3 id="whene2e">
|
||||
|
||||
@@ -760,28 +764,37 @@ guarantee end-to-end encrypted messages.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>All end-to-end encrypted messages carry a padlock:</p>
|
||||
|
||||
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p>
|
||||
|
||||
<p>End-to-end encryption is guaranteed if there is a green checkmark next to the chat title:</p>
|
||||
|
||||
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
|
||||
<p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
|
||||
Since the Delta Chat Version 2 release series (July 2025)
|
||||
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
<h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
|
||||
|
||||
|
||||
How can I get guaranteed end-to-end encryption and green checkmarks? <a href="#howtoe2ee" class="anchor"></a>
|
||||
Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If you have a second communication channel with your chat partner,
|
||||
like a video chat or a different messenger,
|
||||
you can generate an invite link.</p>
|
||||
<p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
|
||||
it is impossible to receive or send messages without end-to-end encryption.</p>
|
||||
|
||||
<p>If you are together in person,
|
||||
you can show a QR code to your chat partner.</p>
|
||||
<p>If you instead create a profile using a classic e-mail server,
|
||||
you can send and receive messages without end-to-end encryption.
|
||||
Such messages lacking end-to-end encryption are marked with an e-mail icon
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
|
||||
|
||||
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You can send an invite link through another private chat,
|
||||
show an invitation QR code when next to each other or in a video call,
|
||||
or click on a “contact” that was shared in a chat.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
@@ -790,141 +803,60 @@ tap the chat group title to see its member list,
|
||||
and select “QR Invite code”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
tap the QR Code icon <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
|
||||
on the Delta Chat app main screen.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Let your chat partner scan the QR image
|
||||
<p>Ask your chat partner to scan the QR image
|
||||
with their Delta Chat app,
|
||||
or click “Copy” or “Share” to create an invite link
|
||||
and share it with your chat partner.</p>
|
||||
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">Secure-Join network messages are exchanged</a> between both devices.</p>
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>If both devices are online,
|
||||
both sides will eventually see a (group or direct) chat with a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
next to the title.</p>
|
||||
<p>If both sides are online, they will soon see a (group or direct) chat
|
||||
and can start messaging securely.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>If one of the devices is offline, the green checkmarks will only
|
||||
appear later when the device is internet-connected again
|
||||
and the Secure-Join network protocol completed.</p>
|
||||
<p>If one side is offline or in bad network,
|
||||
the ability to chat is delayed until connectivity is restored.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Congratulations!
|
||||
You now will automatically use guaranteed end-to-end encryption
|
||||
with this contact and both of you can add each other to green-checkmarked groups
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />,
|
||||
thereby automatically spreading guaranteed end-to-end encryption among its members.</p>
|
||||
You now will automatically use end-to-end encryption
|
||||
with this contact.
|
||||
If you add each other to chat groups,
|
||||
end-to-end encryption will be established among all members.</p>
|
||||
|
||||
<h3 id="e2eeguarantee">
|
||||
|
||||
|
||||
What does the green checkmark and “guaranteed end-to-end encryption” mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Chat titles with green checkmarks
|
||||
<p>A contact profile might show a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
mean that all messages in the chat will be end-to-end encrypted
|
||||
and can not be read or altered by compromised e-mail servers or Internet providers.
|
||||
Joining green-checkmarked group chats
|
||||
safely spreads everybody’s encryption information (and green checkmarks)
|
||||
in a manner that guarantees end-to-end encryption in the group and among members.</p>
|
||||
|
||||
<p>Contact profiles with green checkmarks
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
mean that messaging a contact is currently guaranteed to be end-to-end encrypted.
|
||||
and an “Introduced by” line.
|
||||
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
|
||||
or was introduced by a another green-checkmarked contact.
|
||||
Introductions happen automatically when adding members to groups.
|
||||
Whoever adds a contact to a green-checkmarked group becomes an introducer
|
||||
to those members who didn’t yet know about the added contact.
|
||||
Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
|
||||
becomes an introducer.
|
||||
In a contact profile you can tap on the “Introduced by …” text repeatedly
|
||||
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
|
||||
|
||||
<p>Note that in a contact profile you may see and tap introducers
|
||||
but there is no green checkmark in the profile title.
|
||||
This usually means that the contact <a href="#nocryptanymore">“sent a message from another device”</a>.</p>
|
||||
|
||||
<p>For more in-depth discussion of “guaranteed end-to-end encryption”
|
||||
please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
|
||||
and specifically read about “Verified Groups”, the technical term
|
||||
of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p>
|
||||
|
||||
<h3 id="nocryptanymore">
|
||||
|
||||
|
||||
A contact “sent a message from another device”, what can i do? <a href="#nocryptanymore" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Your chat with a contact lost guaranteed end-to-end encryption.
|
||||
The green checkmark was removed for this chat and contact when you see this warning.
|
||||
<strong>If you find the sudden drop of guaranteed end-to-end encryption
|
||||
surprising for this contact then don’t accept the warning!</strong>
|
||||
Instead check with your contact through a second channel
|
||||
like a video call, other messenger or a phone call,
|
||||
to find out what happened.</p>
|
||||
|
||||
<p>If your contact actually caused the drop of guaranteed end-to-end encryption
|
||||
please see the next paragraphs for common reasons and their mitigations.
|
||||
Regardless, all other green-checkmarked chats remain guaranteed end-to-end encrypted
|
||||
even if the contact is a member there.</p>
|
||||
|
||||
<p><strong>Your contact is using Delta Chat on a second device (phone or laptop)</strong></p>
|
||||
|
||||
<p>If they have another device with a Delta Chat app running,
|
||||
they should remove the profile from the new device
|
||||
and add it <a href="#multiclient">as a second device as described here</a>.
|
||||
As soon as they message you afterwards, the warning will be gone
|
||||
and guaranteed encryption is established with both devices of your contact.</p>
|
||||
|
||||
<p><strong>Your contact reinstalled Delta Chat using their old account login</strong></p>
|
||||
|
||||
<p>If they have <a href="#backup">a backup file</a>,
|
||||
they should remove the profile from the new device
|
||||
and rather import the backup file to re-create their profile.
|
||||
As soon as they message you afterwards, the warning will be gone
|
||||
and guaranteed encryption is re-established for this contact.</p>
|
||||
|
||||
<p>If they don’t have a backup file, it’s best to perform a <a href="#howtoe2ee">QR scan</a>
|
||||
with your chat partner to re-establish guaranteed end-to-end encryption.</p>
|
||||
|
||||
<p><strong>Your contact sent a mail through a webmail interface or another e-mail app
|
||||
and will get back to using Delta Chat soon again.</strong></p>
|
||||
|
||||
<p>If you are sure that the contact sometimes uses webmail,
|
||||
or another mail app lacking end-to-end encryption,
|
||||
then you may accept the warning.
|
||||
As soon as your contact uses Delta Chat again,
|
||||
guaranteed end-to-end encryption will be automatically re-established.</p>
|
||||
|
||||
<p><strong>Your contact stopped using Delta Chat entirely</strong></p>
|
||||
|
||||
<p>Sometimes remaining in contact is more important than end-to-end encryption.
|
||||
<a href="#tls">“Transport Layer Encryption” (TLS)</a> may still meaningfully protect
|
||||
the confidentiality of your messages between your device and the e-mail server.
|
||||
But without end-to-end encryption you and your contact are trusting your e-mail server
|
||||
to not read or manipulate your messages, and to not hand them to third parties.</p>
|
||||
|
||||
<p>In any case, you can not do much else than accept the warning.
|
||||
Please also remove the contact from any active green-checkmarked group
|
||||
which you can find in “Chats in Common” in the Contact profile.
|
||||
This spares your contact from getting “unreadable” messages.</p>
|
||||
|
||||
<p>If the contact removed Delta Chat because of buggy or undesirable behaviour,
|
||||
please consider posting to our <a href="https://support.delta.chat">support forum</a>
|
||||
to help us identify and address common problems. Thanks!</p>
|
||||
|
||||
<h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted">
|
||||
|
||||
|
||||
@@ -949,8 +881,7 @@ and attachment metadata such as filenames.</p>
|
||||
</h3>
|
||||
|
||||
<p>Yes, Delta Chat uses a secure subset of OpenPGP
|
||||
and only displays a padlock security indicator on a message
|
||||
if the whole message is properly encrypted and signed.
|
||||
requiring the whole message to be properly encrypted and signed.
|
||||
For example, “Detached signatures” are not treated as secure.</p>
|
||||
|
||||
<p>OpenPGP is not insecure by itself.
|
||||
@@ -971,7 +902,7 @@ which was thankfully adopted in summer 2023.</p>
|
||||
<h3 id="openpgp-alternatives">
|
||||
|
||||
|
||||
Did you consider using alternatives to OpenPGP for end-to-end -encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -1014,17 +945,15 @@ as defined by the Autocrypt Level 1 specification.</p>
|
||||
<h3 id="tls">
|
||||
|
||||
|
||||
Is a message exposed in cleartext if end-to-end encryption is not available? <a href="#tls" class="anchor"></a>
|
||||
Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Even if your messages are not guaranteed to be end-to-end encrypted,
|
||||
they are still protected from Internet providers like cell or cable companies.
|
||||
However, your and your recipient’s e-mail providers
|
||||
may read, analyze or even modify your messages,
|
||||
including any attachments,
|
||||
if they are not end-to-end encrypted.</p>
|
||||
<p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
|
||||
they are still protected from cell or cable companies who can not read or modify your e-mail messages.
|
||||
But both your and your recipient’s e-mail providers
|
||||
may read, analyze or modify your messages, including any attachments.</p>
|
||||
|
||||
<p>Delta Chat by default uses strict
|
||||
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a>
|
||||
@@ -1036,10 +965,6 @@ If the involved e-mail servers support <a href="https://datatracker.ietf.org/doc
|
||||
then transport encryption will be enforced between e-mail providers
|
||||
in which case Delta Chat communications will never be exposed in cleartext to the Internet
|
||||
even if the message was not end-to-end encrypted.</p>
|
||||
|
||||
<p>Note that <a href="#howtoe2ee">maintaining guaranteed end-to-end encryption</a> on top of TLS encryption
|
||||
provides pervasive safety between your and the recipient’s devices.
|
||||
Not even your e-mail or Internet provider will be able to read or modify your messages.</p>
|
||||
|
||||
<h3 id="message-metadata">
|
||||
|
||||
@@ -1102,74 +1027,6 @@ Delta Chat shows two fingerprints there.
|
||||
If the same fingerprints appear on your own and your contact’s device,
|
||||
the connection is safe.</p>
|
||||
|
||||
<h3 id="how-can-i-check-the-encryption-status-of-messages">
|
||||
|
||||
|
||||
How can I check the encryption status of messages? <a href="#how-can-i-check-the-encryption-status-of-messages" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>A little <strong>padlock</strong> in a message bubble denotes
|
||||
that the message was properly end-to-end encrypted from the given sender.
|
||||
If there is <strong>no padlock</strong>, the message was not properly end-to-end encrypted
|
||||
most likely because the sender uses an app or webmail interface
|
||||
without support for end-to-end–encryption.</p>
|
||||
|
||||
<h3 id="why-do-i-see-unencrypted-messages">
|
||||
|
||||
|
||||
Why do I see unencrypted messages? <a href="#why-do-i-see-unencrypted-messages" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If a contact uses a non-Autocrypt e-mail app,
|
||||
all messages involving this contact (in a group or 1:1 chat)
|
||||
will not be end-to-end encrypted, and thus not show a “padlock” with messages.
|
||||
Note that even if your contacts use Delta Chat on their account,
|
||||
they might also use a non-Autocrypt e-mail app on that account
|
||||
which then may cause intermittently unencrypted messages.
|
||||
Replying unencrypted to unencrypted messages is mandated by Autocrypt
|
||||
to prevent unreadable messages on the side of your contacts
|
||||
and their non-Autocrypt e-mail app.</p>
|
||||
|
||||
<h3 id="how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">
|
||||
|
||||
|
||||
How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app? <a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If you need a safely end-to-end encrypted chat with a contact
|
||||
who is using their e-mail account both with Delta Chat and non-Autocrypt apps (e.g. webmail),
|
||||
it’s best to setup <a href="#howtoe2ee">guaranteed end-to-end encryption with them</a>
|
||||
and then create a guaranteed end-to-end encrypted group chat with you two as members.
|
||||
In this group chat all messages will be end-to-end encrypted
|
||||
even if the direct chat between you two has a
|
||||
<a href="#nocryptanymore">“… sent a message from another device”</a> warning.</p>
|
||||
|
||||
<h3 id="how-can-i-ensure-message-end-to-end-encryption-and-deletion">
|
||||
|
||||
|
||||
How can I ensure message end-to-end encryption and deletion? <a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>The best way to ensure every message is end-to-end encrypted,
|
||||
and metadata deleted as quickly as possible
|
||||
is <a href="#howtoe2ee">using chats with guaranteed end-to-end encryption</a>
|
||||
and turning on <a href="#ephemeralmsgs">disappearing messages</a>.</p>
|
||||
|
||||
<p>Guaranteed end-to-end encrypted chats protect against <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM attacks</a>
|
||||
and turning on disappearing messages deletes the messages
|
||||
on the server after a user-configured time.</p>
|
||||
|
||||
<p>If you don’t need a longer-lived copy of your messages on the server,
|
||||
you can also turn on <a href="#delold">“delete messages from server automatically”</a>.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
|
||||
@@ -1178,45 +1035,35 @@ you can also turn on <a href="#delold">“delete messages from server automatica
|
||||
|
||||
</h3>
|
||||
|
||||
<p>No, Delta Chat doesn’t support Perfect Forward Secrecy (PFS).
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
|
||||
This means that if your Delta Chat private decryption key is leaked,
|
||||
and someone has collected your prior in-transit messages,
|
||||
they will be able to decrypt and read them using the leaked decryption key.</p>
|
||||
|
||||
<p>Note, however, that if anyone obtains to your decryption keys,
|
||||
they will typically also be able to obtain your messages,
|
||||
irrespective if Perfect Forward Secrecy is in place or not.
|
||||
The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
<p>Note however, that Forward Secrecy only increases your security
|
||||
if you delete messages or use ephemeral deletion timers.
|
||||
Otherwise, if anyone obtains your decryption keys,
|
||||
they are typically also able to get all your non-deleted messages
|
||||
and don’t need to decrypt any previously collected messages.</p>
|
||||
|
||||
<p>It is possible that Delta Chat evolves to support Perfect Forward Secrecy,
|
||||
because OpenPGP is just a container for encrypted messages
|
||||
but encryption key management (and thus key rotation or key “ratcheting”)
|
||||
could be organized in flexible ways.
|
||||
See <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouia’s PFS prototype</a>
|
||||
for existing experiments in the OpenPGP implementor community.</p>
|
||||
<p>The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we also discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
|
||||
<h3 id="is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
|
||||
|
||||
Is end-to-end encryption of Delta Chat as safe as Signal? <a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal" class="anchor"></a>
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>It depends on what is important to you.
|
||||
Delta Chat <a href="#pfs">does not support PFS</a> like Signal does
|
||||
but it provides <a href="#e2eeguarantee">guaranteed end-to-end encrypted chats</a>
|
||||
that are safe against compromised servers or corrupted networks.
|
||||
Signal and most other PFS-supporting messengers do not provide
|
||||
a practical scheme for protecting chat groups from network attacks
|
||||
which are arguably more worrisome
|
||||
than a potential attacker who seizes your phone and private encryption setup
|
||||
but somehow not your messages, yet has a full record of all
|
||||
past encrypted messages.</p>
|
||||
<p>Yes.</p>
|
||||
|
||||
<p>In any case, Delta Chat’s end-to-end encryption uses a <a href="#openpgp-secure">secure subset of OpenPGP</a>
|
||||
which has been <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">independently security-audited</a>.</p>
|
||||
<p>We devised a forward secrecy scheme that withstood initial scrutiny from cryptographers and usable security experts.
|
||||
Our tentative scheme is designed to reliably work in federated messaging networks and with multi-device usage.
|
||||
However, an implementation has not been scheduled yet (as of Mid 2025).</p>
|
||||
|
||||
<h3 id="importkey">
|
||||
|
||||
@@ -1251,7 +1098,7 @@ from most recent to older:</p>
|
||||
<li>
|
||||
<p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of
|
||||
rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place.
|
||||
rPGP serves as the end-to-end encyption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
|
||||
rPGP serves as the end-to-end encryption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
|
||||
Two advisories were released related to the findings of this audit:</p>
|
||||
|
||||
<ul>
|
||||
@@ -1645,6 +1492,11 @@ vykonáva aplikácia Delta Chat.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Note:
|
||||
Changing email addresses is temporarily disabled
|
||||
because of ongoing changes to the DeltaChat core.
|
||||
It should be available again in a few months.</p>
|
||||
|
||||
<ol>
|
||||
<li>
|
||||
<p>Change your address in “Settings → Advanced → Password and Account” and
|
||||
|
||||
@@ -36,27 +36,23 @@
|
||||
<li><a href="#why-does-delta-chat-integrate-with-centralized-proprietary-applegoogle-push-services">Why does Delta Chat integrate with centralized proprietary Apple/Google push services?</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#fshehtëzim-dhe-siguri">Fshehtëzim dhe Siguri</a>
|
||||
<li><a href="#e2ee">Fshehtëzim dhe Siguri</a>
|
||||
<ul>
|
||||
<li><a href="#cilët-standarde-përdoren-për-fshehtëzim-skaj-më-skaj">Cilët standarde përdoren për fshehtëzim skaj-më-skaj?</a></li>
|
||||
<li><a href="#whene2e">How can i know if messages are end-to-end encrypted?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I get guaranteed end-to-end encryption and green checkmarks?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark and “guaranteed end-to-end encryption” mean?</a></li>
|
||||
<li><a href="#nocryptanymore">A contact “sent a message from another device”, what can i do?</a></li>
|
||||
<li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
|
||||
<li><a href="#are-attachments-pictures-files-audio-etc-end-to-end-encrypted">Are attachments (pictures, files, audio etc.) end-to-end encrypted?</a></li>
|
||||
<li><a href="#openpgp-secure">A është i siguruar OpenPGP?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end -encryption?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
|
||||
<li><a href="#a-mund-të-preket-delta-chat-i-nga-efail">A mund të preket Delta Chat-i nga EFAIL?</a></li>
|
||||
<li><a href="#tls">Is a message exposed in cleartext if end-to-end encryption is not available?</a></li>
|
||||
<li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
|
||||
<li><a href="#message-metadata">Si i mbron Delta Chat-i tejtëdhënat në mesazhe?</a></li>
|
||||
<li><a href="#device-seizure">Si të mbrohen tejtëdhënat dhe kontaktet, kur shtien në dorë një pajisje?</a></li>
|
||||
<li><a href="#how-can-i-check-encryption-information">How can i check encryption information?</a></li>
|
||||
<li><a href="#si-mund-ta-kontrolloj-gjendjen-e-fshehtëzimit-të-mesazheve">Si mund ta kontrolloj gjendjen e fshehtëzimit të mesazheve?</a></li>
|
||||
<li><a href="#pse-shoh-mesazhe-të-pafshehtëzuar">Pse shoh mesazhe të pafshehtëzuar?</a></li>
|
||||
<li><a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app?</a></li>
|
||||
<li><a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion">How can I ensure message end-to-end encryption and deletion?</a></li>
|
||||
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
|
||||
<li><a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">Is end-to-end encryption of Delta Chat as safe as Signal?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#importkey">A mund të ripërdor kyçin tim ekzistues privat?</a></li>
|
||||
<li><a href="#security-audits">A është bërë auditim i pavarur i Delta Chat-it për cenueshmëri sigurie?</a></li>
|
||||
</ul>
|
||||
@@ -724,10 +720,10 @@ that achieves “instant delivery” of messages for all chatmail servers
|
||||
including a potential one <a href="https://delta.chat/chatmail#selfhosted">you might setup yourself without our permission</a>.
|
||||
Welcome to the power of the interoperable and massive chatmail and e-mail system :)</p>
|
||||
|
||||
<h2 id="fshehtëzim-dhe-siguri">
|
||||
<h2 id="e2ee">
|
||||
|
||||
|
||||
Fshehtëzim dhe Siguri <a href="#fshehtëzim-dhe-siguri" class="anchor"></a>
|
||||
Fshehtëzim dhe Siguri <a href="#e2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h2>
|
||||
@@ -740,18 +736,26 @@ Welcome to the power of the interoperable and massive chatmail and e-mail system
|
||||
|
||||
</h3>
|
||||
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption with contacts and group chats.
|
||||
Autocrypt uses a limited and <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>.
|
||||
End-to-End encrypted messages are marked with a padlock
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
|
||||
<p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
|
||||
to provide automatic end-to-end encryption using these protocols:</p>
|
||||
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
|
||||
are used for establishing chats with guaranteed end-to-end encryption
|
||||
which protects against network attacks and compromised servers.
|
||||
Chats marked with a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
guarantee end-to-end encrypted messages.</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
|
||||
to exchange encryption setup information through QR-code scanning or “invite links”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption between contacts and all members of a group chat.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
|
||||
chat</a>
|
||||
enables receivers to use end-to-end encryption with the contact.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
|
||||
|
||||
<h3 id="whene2e">
|
||||
|
||||
@@ -761,28 +765,37 @@ guarantee end-to-end encrypted messages.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>All end-to-end encrypted messages carry a padlock:</p>
|
||||
|
||||
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p>
|
||||
|
||||
<p>End-to-end encryption is guaranteed if there is a green checkmark next to the chat title:</p>
|
||||
|
||||
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
|
||||
<p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
|
||||
Since the Delta Chat Version 2 release series (July 2025)
|
||||
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
<h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
|
||||
|
||||
|
||||
How can I get guaranteed end-to-end encryption and green checkmarks? <a href="#howtoe2ee" class="anchor"></a>
|
||||
Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If you have a second communication channel with your chat partner,
|
||||
like a video chat or a different messenger,
|
||||
you can generate an invite link.</p>
|
||||
<p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
|
||||
it is impossible to receive or send messages without end-to-end encryption.</p>
|
||||
|
||||
<p>If you are together in person,
|
||||
you can show a QR code to your chat partner.</p>
|
||||
<p>If you instead create a profile using a classic e-mail server,
|
||||
you can send and receive messages without end-to-end encryption.
|
||||
Such messages lacking end-to-end encryption are marked with an e-mail icon
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
|
||||
|
||||
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You can send an invite link through another private chat,
|
||||
show an invitation QR code when next to each other or in a video call,
|
||||
or click on a “contact” that was shared in a chat.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
@@ -791,141 +804,60 @@ tap the chat group title to see its member list,
|
||||
and select “QR Invite code”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
tap the QR Code icon <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
|
||||
on the Delta Chat app main screen.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Let your chat partner scan the QR image
|
||||
<p>Ask your chat partner to scan the QR image
|
||||
with their Delta Chat app,
|
||||
or click “Copy” or “Share” to create an invite link
|
||||
and share it with your chat partner.</p>
|
||||
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">Secure-Join network messages are exchanged</a> between both devices.</p>
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>If both devices are online,
|
||||
both sides will eventually see a (group or direct) chat with a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
next to the title.</p>
|
||||
<p>If both sides are online, they will soon see a (group or direct) chat
|
||||
and can start messaging securely.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>If one of the devices is offline, the green checkmarks will only
|
||||
appear later when the device is internet-connected again
|
||||
and the Secure-Join network protocol completed.</p>
|
||||
<p>If one side is offline or in bad network,
|
||||
the ability to chat is delayed until connectivity is restored.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Congratulations!
|
||||
You now will automatically use guaranteed end-to-end encryption
|
||||
with this contact and both of you can add each other to green-checkmarked groups
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />,
|
||||
thereby automatically spreading guaranteed end-to-end encryption among its members.</p>
|
||||
You now will automatically use end-to-end encryption
|
||||
with this contact.
|
||||
If you add each other to chat groups,
|
||||
end-to-end encryption will be established among all members.</p>
|
||||
|
||||
<h3 id="e2eeguarantee">
|
||||
|
||||
|
||||
What does the green checkmark and “guaranteed end-to-end encryption” mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Chat titles with green checkmarks
|
||||
<p>A contact profile might show a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
mean that all messages in the chat will be end-to-end encrypted
|
||||
and can not be read or altered by compromised e-mail servers or Internet providers.
|
||||
Joining green-checkmarked group chats
|
||||
safely spreads everybody’s encryption information (and green checkmarks)
|
||||
in a manner that guarantees end-to-end encryption in the group and among members.</p>
|
||||
|
||||
<p>Contact profiles with green checkmarks
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
mean that messaging a contact is currently guaranteed to be end-to-end encrypted.
|
||||
and an “Introduced by” line.
|
||||
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
|
||||
or was introduced by a another green-checkmarked contact.
|
||||
Introductions happen automatically when adding members to groups.
|
||||
Whoever adds a contact to a green-checkmarked group becomes an introducer
|
||||
to those members who didn’t yet know about the added contact.
|
||||
Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
|
||||
becomes an introducer.
|
||||
In a contact profile you can tap on the “Introduced by …” text repeatedly
|
||||
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
|
||||
|
||||
<p>Note that in a contact profile you may see and tap introducers
|
||||
but there is no green checkmark in the profile title.
|
||||
This usually means that the contact <a href="#nocryptanymore">“sent a message from another device”</a>.</p>
|
||||
|
||||
<p>For more in-depth discussion of “guaranteed end-to-end encryption”
|
||||
please see <a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join protocols</a>
|
||||
and specifically read about “Verified Groups”, the technical term
|
||||
of what is called here “green-checkmarked” or “guaranteed end-to-end encrypted” chats.</p>
|
||||
|
||||
<h3 id="nocryptanymore">
|
||||
|
||||
|
||||
A contact “sent a message from another device”, what can i do? <a href="#nocryptanymore" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Your chat with a contact lost guaranteed end-to-end encryption.
|
||||
The green checkmark was removed for this chat and contact when you see this warning.
|
||||
<strong>If you find the sudden drop of guaranteed end-to-end encryption
|
||||
surprising for this contact then don’t accept the warning!</strong>
|
||||
Instead check with your contact through a second channel
|
||||
like a video call, other messenger or a phone call,
|
||||
to find out what happened.</p>
|
||||
|
||||
<p>If your contact actually caused the drop of guaranteed end-to-end encryption
|
||||
please see the next paragraphs for common reasons and their mitigations.
|
||||
Regardless, all other green-checkmarked chats remain guaranteed end-to-end encrypted
|
||||
even if the contact is a member there.</p>
|
||||
|
||||
<p><strong>Your contact is using Delta Chat on a second device (phone or laptop)</strong></p>
|
||||
|
||||
<p>If they have another device with a Delta Chat app running,
|
||||
they should remove the profile from the new device
|
||||
and add it <a href="#multiclient">as a second device as described here</a>.
|
||||
As soon as they message you afterwards, the warning will be gone
|
||||
and guaranteed encryption is established with both devices of your contact.</p>
|
||||
|
||||
<p><strong>Your contact reinstalled Delta Chat using their old account login</strong></p>
|
||||
|
||||
<p>If they have <a href="#backup">a backup file</a>,
|
||||
they should remove the profile from the new device
|
||||
and rather import the backup file to re-create their profile.
|
||||
As soon as they message you afterwards, the warning will be gone
|
||||
and guaranteed encryption is re-established for this contact.</p>
|
||||
|
||||
<p>If they don’t have a backup file, it’s best to perform a <a href="#howtoe2ee">QR scan</a>
|
||||
with your chat partner to re-establish guaranteed end-to-end encryption.</p>
|
||||
|
||||
<p><strong>Your contact sent a mail through a webmail interface or another e-mail app
|
||||
and will get back to using Delta Chat soon again.</strong></p>
|
||||
|
||||
<p>If you are sure that the contact sometimes uses webmail,
|
||||
or another mail app lacking end-to-end encryption,
|
||||
then you may accept the warning.
|
||||
As soon as your contact uses Delta Chat again,
|
||||
guaranteed end-to-end encryption will be automatically re-established.</p>
|
||||
|
||||
<p><strong>Your contact stopped using Delta Chat entirely</strong></p>
|
||||
|
||||
<p>Sometimes remaining in contact is more important than end-to-end encryption.
|
||||
<a href="#tls">“Transport Layer Encryption” (TLS)</a> may still meaningfully protect
|
||||
the confidentiality of your messages between your device and the e-mail server.
|
||||
But without end-to-end encryption you and your contact are trusting your e-mail server
|
||||
to not read or manipulate your messages, and to not hand them to third parties.</p>
|
||||
|
||||
<p>In any case, you can not do much else than accept the warning.
|
||||
Please also remove the contact from any active green-checkmarked group
|
||||
which you can find in “Chats in Common” in the Contact profile.
|
||||
This spares your contact from getting “unreadable” messages.</p>
|
||||
|
||||
<p>If the contact removed Delta Chat because of buggy or undesirable behaviour,
|
||||
please consider posting to our <a href="https://support.delta.chat">support forum</a>
|
||||
to help us identify and address common problems. Thanks!</p>
|
||||
|
||||
<h3 id="are-attachments-pictures-files-audio-etc-end-to-end-encrypted">
|
||||
|
||||
|
||||
@@ -950,8 +882,7 @@ and attachment metadata such as filenames.</p>
|
||||
</h3>
|
||||
|
||||
<p>Yes, Delta Chat uses a secure subset of OpenPGP
|
||||
and only displays a padlock security indicator on a message
|
||||
if the whole message is properly encrypted and signed.
|
||||
requiring the whole message to be properly encrypted and signed.
|
||||
For example, “Detached signatures” are not treated as secure.</p>
|
||||
|
||||
<p>OpenPGP is not insecure by itself.
|
||||
@@ -972,7 +903,7 @@ which was thankfully adopted in summer 2023.</p>
|
||||
<h3 id="openpgp-alternatives">
|
||||
|
||||
|
||||
Did you consider using alternatives to OpenPGP for end-to-end -encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -1015,17 +946,15 @@ as defined by the Autocrypt Level 1 specification.</p>
|
||||
<h3 id="tls">
|
||||
|
||||
|
||||
Is a message exposed in cleartext if end-to-end encryption is not available? <a href="#tls" class="anchor"></a>
|
||||
Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Even if your messages are not guaranteed to be end-to-end encrypted,
|
||||
they are still protected from Internet providers like cell or cable companies.
|
||||
However, your and your recipient’s e-mail providers
|
||||
may read, analyze or even modify your messages,
|
||||
including any attachments,
|
||||
if they are not end-to-end encrypted.</p>
|
||||
<p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
|
||||
they are still protected from cell or cable companies who can not read or modify your e-mail messages.
|
||||
But both your and your recipient’s e-mail providers
|
||||
may read, analyze or modify your messages, including any attachments.</p>
|
||||
|
||||
<p>Delta Chat by default uses strict
|
||||
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS encryption</a>
|
||||
@@ -1037,10 +966,6 @@ If the involved e-mail servers support <a href="https://datatracker.ietf.org/doc
|
||||
then transport encryption will be enforced between e-mail providers
|
||||
in which case Delta Chat communications will never be exposed in cleartext to the Internet
|
||||
even if the message was not end-to-end encrypted.</p>
|
||||
|
||||
<p>Note that <a href="#howtoe2ee">maintaining guaranteed end-to-end encryption</a> on top of TLS encryption
|
||||
provides pervasive safety between your and the recipient’s devices.
|
||||
Not even your e-mail or Internet provider will be able to read or modify your messages.</p>
|
||||
|
||||
<h3 id="message-metadata">
|
||||
|
||||
@@ -1103,74 +1028,6 @@ Delta Chat shows two fingerprints there.
|
||||
If the same fingerprints appear on your own and your contact’s device,
|
||||
the connection is safe.</p>
|
||||
|
||||
<h3 id="si-mund-ta-kontrolloj-gjendjen-e-fshehtëzimit-të-mesazheve">
|
||||
|
||||
|
||||
Si mund ta kontrolloj gjendjen e fshehtëzimit të mesazheve? <a href="#si-mund-ta-kontrolloj-gjendjen-e-fshehtëzimit-të-mesazheve" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>A little <strong>padlock</strong> in a message bubble denotes
|
||||
that the message was properly end-to-end encrypted from the given sender.
|
||||
If there is <strong>no padlock</strong>, the message was not properly end-to-end encrypted
|
||||
most likely because the sender uses an app or webmail interface
|
||||
without support for end-to-end–encryption.</p>
|
||||
|
||||
<h3 id="pse-shoh-mesazhe-të-pafshehtëzuar">
|
||||
|
||||
|
||||
Pse shoh mesazhe të pafshehtëzuar? <a href="#pse-shoh-mesazhe-të-pafshehtëzuar" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If a contact uses a non-Autocrypt e-mail app,
|
||||
all messages involving this contact (in a group or 1:1 chat)
|
||||
will not be end-to-end encrypted, and thus not show a “padlock” with messages.
|
||||
Note that even if your contacts use Delta Chat on their account,
|
||||
they might also use a non-Autocrypt e-mail app on that account
|
||||
which then may cause intermittently unencrypted messages.
|
||||
Replying unencrypted to unencrypted messages is mandated by Autocrypt
|
||||
to prevent unreadable messages on the side of your contacts
|
||||
and their non-Autocrypt e-mail app.</p>
|
||||
|
||||
<h3 id="how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app">
|
||||
|
||||
|
||||
How can i get an end-to-end encrypted chat with a Delta Chat contact who sometimes uses webmail or another non-Autocrypt e-mail app? <a href="#how-can-i-get-an-end-to-end-encrypted-chat-with-a-delta-chat-contact-who-sometimes-uses-webmail-or-another-non-autocrypt-e-mail-app" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>If you need a safely end-to-end encrypted chat with a contact
|
||||
who is using their e-mail account both with Delta Chat and non-Autocrypt apps (e.g. webmail),
|
||||
it’s best to setup <a href="#howtoe2ee">guaranteed end-to-end encryption with them</a>
|
||||
and then create a guaranteed end-to-end encrypted group chat with you two as members.
|
||||
In this group chat all messages will be end-to-end encrypted
|
||||
even if the direct chat between you two has a
|
||||
<a href="#nocryptanymore">“… sent a message from another device”</a> warning.</p>
|
||||
|
||||
<h3 id="how-can-i-ensure-message-end-to-end-encryption-and-deletion">
|
||||
|
||||
|
||||
How can I ensure message end-to-end encryption and deletion? <a href="#how-can-i-ensure-message-end-to-end-encryption-and-deletion" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>The best way to ensure every message is end-to-end encrypted,
|
||||
and metadata deleted as quickly as possible
|
||||
is <a href="#howtoe2ee">using chats with guaranteed end-to-end encryption</a>
|
||||
and turning on <a href="#ephemeralmsgs">disappearing messages</a>.</p>
|
||||
|
||||
<p>Guaranteed end-to-end encrypted chats protect against <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM attacks</a>
|
||||
and turning on disappearing messages deletes the messages
|
||||
on the server after a user-configured time.</p>
|
||||
|
||||
<p>Nëse s’ju duhet te shërbyesi një kopje jetëgjatë e mesazheve tuaj,
|
||||
mund edhe të aktivizoni <a href="#delold">“fshiji automatikisht nga shërbyesi mesazhe”</a>.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
|
||||
@@ -1179,45 +1036,35 @@ mund edhe të aktivizoni <a href="#delold">“fshiji automatikisht nga shërbyes
|
||||
|
||||
</h3>
|
||||
|
||||
<p>No, Delta Chat doesn’t support Perfect Forward Secrecy (PFS).
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
|
||||
This means that if your Delta Chat private decryption key is leaked,
|
||||
and someone has collected your prior in-transit messages,
|
||||
they will be able to decrypt and read them using the leaked decryption key.</p>
|
||||
|
||||
<p>Note, however, that if anyone obtains to your decryption keys,
|
||||
they will typically also be able to obtain your messages,
|
||||
irrespective if Perfect Forward Secrecy is in place or not.
|
||||
The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
<p>Note however, that Forward Secrecy only increases your security
|
||||
if you delete messages or use ephemeral deletion timers.
|
||||
Otherwise, if anyone obtains your decryption keys,
|
||||
they are typically also able to get all your non-deleted messages
|
||||
and don’t need to decrypt any previously collected messages.</p>
|
||||
|
||||
<p>It is possible that Delta Chat evolves to support Perfect Forward Secrecy,
|
||||
because OpenPGP is just a container for encrypted messages
|
||||
but encryption key management (and thus key rotation or key “ratcheting”)
|
||||
could be organized in flexible ways.
|
||||
See <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouia’s PFS prototype</a>
|
||||
for existing experiments in the OpenPGP implementor community.</p>
|
||||
<p>The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we also discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
|
||||
<h3 id="is-end-to-end-encryption-of-delta-chat-as-safe-as-signal">
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
|
||||
|
||||
Is end-to-end encryption of Delta Chat as safe as Signal? <a href="#is-end-to-end-encryption-of-delta-chat-as-safe-as-signal" class="anchor"></a>
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>It depends on what is important to you.
|
||||
Delta Chat <a href="#pfs">does not support PFS</a> like Signal does
|
||||
but it provides <a href="#e2eeguarantee">guaranteed end-to-end encrypted chats</a>
|
||||
that are safe against compromised servers or corrupted networks.
|
||||
Signal and most other PFS-supporting messengers do not provide
|
||||
a practical scheme for protecting chat groups from network attacks
|
||||
which are arguably more worrisome
|
||||
than a potential attacker who seizes your phone and private encryption setup
|
||||
but somehow not your messages, yet has a full record of all
|
||||
past encrypted messages.</p>
|
||||
<p>Po</p>
|
||||
|
||||
<p>In any case, Delta Chat’s end-to-end encryption uses a <a href="#openpgp-secure">secure subset of OpenPGP</a>
|
||||
which has been <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">independently security-audited</a>.</p>
|
||||
<p>We devised a forward secrecy scheme that withstood initial scrutiny from cryptographers and usable security experts.
|
||||
Our tentative scheme is designed to reliably work in federated messaging networks and with multi-device usage.
|
||||
However, an implementation has not been scheduled yet (as of Mid 2025).</p>
|
||||
|
||||
<h3 id="importkey">
|
||||
|
||||
@@ -1252,7 +1099,7 @@ from most recent to older:</p>
|
||||
<li>
|
||||
<p>2024 December, an <a href="https://github.com/rpgp/docs/blob/main/audits/NGI%20Core%20rPGP%20penetration%20test%20report%202024%201.0.pdf">NLNET-commissioned Evaluation of
|
||||
rPGP</a> by <a href="https://www.radicallyopensecurity.com/">Radically Open Security</a> took place.
|
||||
rPGP serves as the end-to-end encyption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
|
||||
rPGP serves as the end-to-end encryption <a href="https://openpgp.org">OpenPGP</a> engine of Delta Chat.
|
||||
Two advisories were released related to the findings of this audit:</p>
|
||||
|
||||
<ul>
|
||||
@@ -1645,6 +1492,11 @@ DeltaChat. Zakonisht kjo do të bëhej nga aplikacioni Delta Chat.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Note:
|
||||
Changing email addresses is temporarily disabled
|
||||
because of ongoing changes to the DeltaChat core.
|
||||
It should be available again in a few months.</p>
|
||||
|
||||
<ol>
|
||||
<li>
|
||||
<p>Change your address in “Settings → Advanced → Password and Account” and
|
||||
|
||||
+112
-133
@@ -36,27 +36,23 @@
|
||||
<li><a href="#чому-delta-chat-інтегрується-з-централізованими-пропрієтарними-push-сервісами-applegoogle">Чому Delta Chat інтегрується з централізованими пропрієтарними push-сервісами Apple/Google?</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#шифрування-та-безпека">Шифрування та безпека</a>
|
||||
<li><a href="#e2ee">Шифрування та безпека</a>
|
||||
<ul>
|
||||
<li><a href="#які-стандарти-використовуються-для-наскрізного-шифрування">Які стандарти використовуються для наскрізного шифрування?</a></li>
|
||||
<li><a href="#whene2e">Як дізнатися, чи повідомлення зашифровано наскрізним шифруванням?</a></li>
|
||||
<li><a href="#howtoe2ee">Як отримати гарантоване наскрізне шифрування та зелені галочки?</a></li>
|
||||
<li><a href="#e2eeguarantee">Що означає зелена галочка і “гарантоване наскрізне шифрування”?</a></li>
|
||||
<li><a href="#nocryptanymore">Контакт “надіслав повідомлення з іншого пристрою”, що робити?</a></li>
|
||||
<li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
|
||||
<li><a href="#чи-зашифровані-наскрізно-вкладення-зображення-файли-аудіо-тощо">Чи зашифровані наскрізно вкладення (зображення, файли, аудіо тощо)?</a></li>
|
||||
<li><a href="#openpgp-secure">Чи безпечний OpenPGP?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Чи розглядали ви можливість використання альтернатив OpenPGP для наскрізного шифрування?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
|
||||
<li><a href="#чи-вразливий-delta-chat-до-efail">Чи вразливий Delta Chat до EFAIL?</a></li>
|
||||
<li><a href="#tls">Чи буде показано повідомлення відкритим текстом, якщо наскрізне шифрування недоступне?</a></li>
|
||||
<li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
|
||||
<li><a href="#message-metadata">Як Delta Chat захищає метадані у повідомленнях?</a></li>
|
||||
<li><a href="#device-seizure">Як захистити метадані та контакти якщо пристрій вилучено?</a></li>
|
||||
<li><a href="#як-перевірити-інформацію-про-шифрування">Як перевірити інформацію про шифрування?</a></li>
|
||||
<li><a href="#як-перевірити-стан-шифрування-повідомлень">Як перевірити стан шифрування повідомлень?</a></li>
|
||||
<li><a href="#чому-я-бачу-незашифровані-повідомлення">Чому я бачу незашифровані повідомлення?</a></li>
|
||||
<li><a href="#як-я-можу-отримати-наскрізно-зашифрований-чат-з-контактом-delta-chat-який-іноді-користується-веб-поштою-або-іншим-додатком-електронної-пошти-що-не-підтримує-autocrypt">Як я можу отримати наскрізно зашифрований чат з контактом Delta Chat, який іноді користується веб-поштою або іншим додатком електронної пошти, що не підтримує Autocrypt?</a></li>
|
||||
<li><a href="#як-забезпечити-наскрізне-шифрування-та-видалення-повідомлень">Як забезпечити наскрізне шифрування та видалення повідомлень?</a></li>
|
||||
<li><a href="#pfs">Чи підтримує Delta Chat цілковиту пряму секретність (Perfect Forward Secrecy)?</a></li>
|
||||
<li><a href="#чи-є-наскрізне-шифрування-delta-chat-таким-же-безпечним-як-signal">Чи є наскрізне шифрування Delta Chat таким же безпечним, як Signal?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#importkey">Чи можна повторно використовувати існуючий закритий ключ?</a></li>
|
||||
<li><a href="#security-audits">Чи проходив Delta Chat незалежний аудит на наявність вразливостей у безпеці?</a></li>
|
||||
</ul>
|
||||
@@ -593,10 +589,10 @@ Push-сповіщення автоматично активуються для
|
||||
|
||||
<p>Зверніть увагу, що Delta Chat має <a href="#privacy-notifications">невелику систему push-повідомлень, що зберігає конфіденційність</a> яка забезпечує “миттєву доставку” повідомлень на всі chatmail-сервери включаючи потенційний <a href="https://delta.chat/chatmail#selfhosted">який ви можете налаштувати самостійно без нашого дозволу</a>. Ласкаво просимо до потужності сумісної та масової системи чат-пошти та електронної пошти :)</p>
|
||||
|
||||
<h2 id="шифрування-та-безпека">
|
||||
<h2 id="e2ee">
|
||||
|
||||
|
||||
Шифрування та безпека <a href="#шифрування-та-безпека" class="anchor"></a>
|
||||
Шифрування та безпека <a href="#e2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h2>
|
||||
@@ -609,10 +605,26 @@ Push-сповіщення автоматично активуються для
|
||||
|
||||
</h3>
|
||||
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> використовується для автоматичного встановлення наскрізного шифрування з контактами та груповими чатами.
|
||||
Autocrypt використовує обмежену і <a href="#openpgp-secure">безпечну підмножину стандарту OpenPGP</a>. Зашифровані наскрізним шифруванням повідомлення позначаються замком <img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />.</p>
|
||||
<p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
|
||||
to provide automatic end-to-end encryption using these protocols:</p>
|
||||
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Протоколи Secure-Join</a> використовуються для створення чатів з гарантованим наскрізним шифруванням що захищає від мережевих атак і скомпрометованих серверів. Чати, відмічені зеленою галочкою <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> гарантують наскрізне шифрування повідомлень.</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
|
||||
to exchange encryption setup information through QR-code scanning or “invite links”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption between contacts and all members of a group chat.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
|
||||
chat</a>
|
||||
enables receivers to use end-to-end encryption with the contact.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
|
||||
|
||||
<h3 id="whene2e">
|
||||
|
||||
@@ -622,102 +634,94 @@ Autocrypt використовує обмежену і <a href="#openpgp-secure"
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Всі наскрізні зашифровані повідомлення мають навісний замок:</p>
|
||||
|
||||
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p>
|
||||
|
||||
<p>Наскрізне шифрування гарантується, якщо поруч із заголовком чату стоїть зелена галочка:</p>
|
||||
|
||||
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
|
||||
<p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
|
||||
Since the Delta Chat Version 2 release series (July 2025)
|
||||
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
<h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
|
||||
|
||||
|
||||
Як отримати гарантоване наскрізне шифрування та зелені галочки? <a href="#howtoe2ee" class="anchor"></a>
|
||||
Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Якщо у вас є другий канал зв’язку з вашим партнером по чату, наприклад, відеочат або інший месенджер, ви можете згенерувати посилання-запрошення.</p>
|
||||
<p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
|
||||
it is impossible to receive or send messages without end-to-end encryption.</p>
|
||||
|
||||
<p>Якщо ви разом особисто, ви можете показати QR-код своєму співрозмовнику.</p>
|
||||
<p>If you instead create a profile using a classic e-mail server,
|
||||
you can send and receive messages without end-to-end encryption.
|
||||
Such messages lacking end-to-end encryption are marked with an e-mail icon
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
|
||||
|
||||
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You can send an invite link through another private chat,
|
||||
show an invitation QR code when next to each other or in a video call,
|
||||
or click on a “contact” that was shared in a chat.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>Для <strong>Запрошення до групи</strong>, торкніться назви групи чату, щоб побачити список її учасників, і виберіть “QR-код запрошення”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Для <strong>прямих запрошень у чат 1:1</strong>, торкніться іконки QR-коду <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" /> на головному екрані програми Delta Chat.</p>
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
tap the QR Code icon <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
|
||||
on the Delta Chat app main screen.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Дозвольте вашому партнеру по чату відсканувати QR-зображення
|
||||
у своєму додатку Delta Chat, або натисніть “Копіювати” чи “Поділитися”, щоб створити посилання-запрошення і поділитися ним з вашим співрозмовником.</p>
|
||||
<p>Ask your chat partner to scan the QR image
|
||||
with their Delta Chat app,
|
||||
or click “Copy” or “Share” to create an invite link
|
||||
and share it with your chat partner.</p>
|
||||
|
||||
<p>Тепер зачекайте, поки між обома пристроями <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">відбудеться обмін мережевими повідомленнями Secure-Join</a>.</p>
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>Якщо обидва пристрої онлайн, обидві сторони зрештою побачать (груповий або прямий) чат із зеленою галочкою <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> поруч із заголовком.</p>
|
||||
<p>If both sides are online, they will soon see a (group or direct) chat
|
||||
and can start messaging securely.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Якщо один з пристроїв не в мережі, зелені галочки з’являться пізніше, коли пристрій знову буде підключено до Інтернету а мережевий протокол Secure-Join буде завершено.</p>
|
||||
<p>If one side is offline or in bad network,
|
||||
the ability to chat is delayed until connectivity is restored.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Вітаємо! Тепер ви автоматично використовуватимете гарантоване наскрізне шифрування з цим контактом, і ви обидва можете додавати один одного в групи, позначені зеленою галочкою <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />, таким чином автоматично поширюючи гарантоване наскрізне шифрування серед її членів.</p>
|
||||
<p>Congratulations!
|
||||
You now will automatically use end-to-end encryption
|
||||
with this contact.
|
||||
If you add each other to chat groups,
|
||||
end-to-end encryption will be established among all members.</p>
|
||||
|
||||
<h3 id="e2eeguarantee">
|
||||
|
||||
|
||||
Що означає зелена галочка і “гарантоване наскрізне шифрування”? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Назви чатів із зеленими галочками <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> означають, що всі повідомлення в чаті будуть наскрізно зашифровані і не можуть бути прочитані або змінені скомпрометованими поштовими серверами або інтернет-провайдерами.
|
||||
Приєднання до групових чатів із зеленими галочками безпечно поширює інформацію про шифрування (і зелені галочки) всіх учасників таким чином, що гарантує наскрізне шифрування в групі та між її учасниками.</p>
|
||||
|
||||
<p>Профілі контактів із зеленими галочками <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> означають, що повідомлення контакту наразі гарантовано зашифровані наскрізним шифруванням. Кожен контакт із зеленою галочкою або зробив пряме <a href="#howtoe2ee">QR-сканування</a> з вами або був представлений іншим контактом, позначеним зеленою галочкою. Знайомство відбувається автоматично під час додавання учасників до груп. Той, хто додає контакт до групи, позначеної зеленою галочкою, стає представником для тих учасників, які ще не знали про доданий контакт. У профілі контакту ви можете кілька разів натиснути на текст “Представлений …” поки не потрапите до того, з ким ви безпосередньо зробили <a href="#howtoe2ee">QR-сканування</a>.</p>
|
||||
|
||||
<p>Зверніть увагу, що в профілі контакту ви можете бачити і натискати рекомендувачів але в заголовку профілю немає зеленої галочки. Зазвичай це означає, що контакт <a href="#nocryptanymore">“надіслав повідомлення з іншого пристрою”</a>.</p>
|
||||
<p>A contact profile might show a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
and an “Introduced by” line.
|
||||
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
|
||||
or was introduced by a another green-checkmarked contact.
|
||||
Introductions happen automatically when adding members to groups.
|
||||
Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
|
||||
becomes an introducer.
|
||||
In a contact profile you can tap on the “Introduced by …” text repeatedly
|
||||
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
|
||||
|
||||
<p>Для більш детального обговорення “гарантованого наскрізного шифрування” будь ласка, перегляньте <a href="https://securejoin.delta.chat/en/latest/new.html">Протоколи безпечного приєднання</a> і, зокрема, прочитайте про “Перевірені групи”, технічний термін того, що тут називається чатами з “зеленою галочкою” або “гарантованим наскрізним шифруванням”.</p>
|
||||
|
||||
<h3 id="nocryptanymore">
|
||||
|
||||
|
||||
Контакт “надіслав повідомлення з іншого пристрою”, що робити? <a href="#nocryptanymore" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Ваш чат з контактом втратив гарантоване наскрізне шифрування. Зелену галочку було знято для цього чату та контакту, коли ви побачили це попередження. **Якщо ви вважаєте раптове зникнення гарантованого наскрізного шифрування несподіваним для цього контакту, не приймайте попередження! Замість цього зв’яжіться з контактом через другий канал наприклад, відеодзвінок, інший месенджер або телефонний дзвінок, щоб з’ясувати, що сталося.</p>
|
||||
|
||||
<p>Якщо ваш контакт дійсно спричинив втрату гарантованого наскрізного шифрування будь ласка, зверніться до наступних параграфів, щоб дізнатися про типові причини та способи їх усунення. Незважаючи на це, всі інші чати, позначені зеленою галочкою, залишаються гарантовано зашифрованими з кінця в кінець навіть якщо контакт є їхнім учасником.</p>
|
||||
|
||||
<p><strong>Ваш контакт використовує Delta Chat на другому пристрої (телефоні або ноутбуці)</strong>.</p>
|
||||
|
||||
<p>Якщо у них є інший пристрій із запущеним додатком Delta Chat, вони повинні видалити профіль з нового пристрою і додати його <a href="#multiclient">як другий пристрій, як описано тут</a>. Як тільки вони напишуть вам повідомлення, попередження зникне і гарантоване шифрування буде встановлено на обох пристроях вашого контакту.</p>
|
||||
|
||||
<p><strong>Ваш контакт перевстановив Delta Chat, використовуючи свій старий логін</strong></p>
|
||||
|
||||
<p>Якщо у них є <a href="#backup">файл резервної копії</a>, вони повинні видалити профіль з нового пристрою і, замість цього, імпортувати файл резервної копії для відновлення свого профілю. Як тільки вони напишуть вам повідомлення, попередження зникне і гарантоване шифрування буде відновлено для цього контакту.</p>
|
||||
|
||||
<p>Якщо у них немає резервної копії файлу, найкраще виконати <a href="#howtoe2ee">QR-сканування</a> з вашим співрозмовником, щоб відновити гарантоване кінцеве шифрування.</p>
|
||||
|
||||
<p><strong>Ваш контакт надіслав листа через веб-інтерфейс або іншу поштову програму і незабаром повернеться до використання Delta Chat.</strong></p>
|
||||
|
||||
<p>Якщо ви впевнені, що контакт іноді користується веб-поштою, або іншу поштову програму без наскрізного шифрування, ви можете прийняти попередження. Як тільки ваш контакт знову скористається Delta Chat, гарантоване наскрізне шифрування буде автоматично відновлено.</p>
|
||||
|
||||
<p><strong>Ваш контакт повністю припинив користуватися Delta Chat</strong>.</p>
|
||||
|
||||
<p>Іноді залишатися на зв’язку важливіше, ніж наскрізне шифрування. <a href="#tls">“Шифрування на транспортному рівні” (TLS)</a> все ще може ефективно захищати конфіденційність ваших повідомлень між вашим пристроєм і сервером електронної пошти. Але без наскрізного шифрування ви та ваш контакт довіряєте серверу електронної пошти не читати і не маніпулювати вашими повідомленнями, а також не передавати їх третім особам.</p>
|
||||
|
||||
<p>У будь-якому випадку, ви не можете зробити нічого іншого, окрім як прийняти попередження. Будь ласка, також видаліть контакт з будь-якої активної групи, позначеної зеленою галочкою які ви можете знайти в розділі “Загальні чати” в профілі контакту. Це позбавить ваш контакт від отримання “нечитабельних” повідомлень.</p>
|
||||
|
||||
<p>Якщо контакт видалив Delta Chat через помилки або небажану поведінку, будь ласка, розгляньте можливість написати повідомлення на нашому <a href="https://support.delta.chat">форумі підтримки</a> щоб допомогти нам виявити та вирішити загальні проблеми. Дякуємо!</p>
|
||||
|
||||
<h3 id="чи-зашифровані-наскрізно-вкладення-зображення-файли-аудіо-тощо">
|
||||
|
||||
|
||||
@@ -738,7 +742,9 @@ Autocrypt використовує обмежену і <a href="#openpgp-secure"
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Так, Delta Chat використовує безпечну підмножину OpenPGP і відображає індикатор безпеки у вигляді замка в повідомленні лише тоді, коли все повідомлення належним чином зашифровано і підписано. Наприклад, “Відокремлені підписи” не вважаються безпечними.</p>
|
||||
<p>Yes, Delta Chat uses a secure subset of OpenPGP
|
||||
requiring the whole message to be properly encrypted and signed.
|
||||
For example, “Detached signatures” are not treated as secure.</p>
|
||||
|
||||
<p>OpenPGP сам по собі не є небезпечним. Більшість публічно обговорюваних проблем безпеки OpenPGP насправді виникають через недостатню зручність використання або погану реалізацію інструментів чи програм (або обох).
|
||||
Особливо важливо розрізняти OpenPGP, стандарт шифрування IETF, і GnuPG (GPG), інструмент командного рядка, що реалізує OpenPGP.
|
||||
@@ -750,7 +756,7 @@ Delta Chat скоріше використовує реалізацію OpenPGP
|
||||
<h3 id="openpgp-alternatives">
|
||||
|
||||
|
||||
Чи розглядали ви можливість використання альтернатив OpenPGP для наскрізного шифрування? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -774,16 +780,17 @@ Delta Chat скоріше використовує реалізацію OpenPGP
|
||||
<h3 id="tls">
|
||||
|
||||
|
||||
Чи буде показано повідомлення відкритим текстом, якщо наскрізне шифрування недоступне? <a href="#tls" class="anchor"></a>
|
||||
Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Навіть якщо ваші повідомлення не гарантовано зашифровані наскрізним шифруванням, вони все одно захищені від інтернет-провайдерів, таких як мобільні або кабельні компанії. Однак, ваші провайдери та провайдери електронної пошти одержувача можуть читати, аналізувати або навіть змінювати ваші повідомлення, включаючи будь-які вкладення, якщо вони не зашифровані наскрізним шифруванням.</p>
|
||||
<p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
|
||||
they are still protected from cell or cable companies who can not read or modify your e-mail messages.
|
||||
But both your and your recipient’s e-mail providers
|
||||
may read, analyze or modify your messages, including any attachments.</p>
|
||||
|
||||
<p>За замовчуванням Delta Chat використовує суворе <a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS-шифрування</a> яке захищає з’єднання між вашим пристроєм і провайдером електронної пошти. Вся робота з TLS-шифруванням Delta Chat пройшла незалежний <a href="#security-audits">аудит безпеки</a>. Крім того, з’єднання між вашим провайдером та провайдером електронної пошти одержувача зазвичай також шифрується при передачі даних. Якщо задіяні поштові сервери підтримують <a href="https://datatracker.ietf.org/doc/html/rfc8461">MTA-STS</a> то між провайдерами електронної пошти буде застосовуватися транспортне шифрування в цьому випадку повідомлення Delta Chat ніколи не будуть доступні в Інтернеті у вигляді відкритого тексту навіть якщо повідомлення не було наскрізь зашифровано.</p>
|
||||
|
||||
<p>Зверніть увагу, що <a href="#howtoe2ee">підтримка гарантованого наскрізного шифрування</a>, на додаток до шифрування TLS, забезпечує повну безпеку між вашим пристроєм і пристроєм одержувача. Навіть ваш провайдер електронної пошти або інтернет-провайдер не зможуть прочитати або змінити ваші повідомлення.</p>
|
||||
|
||||
<h3 id="message-metadata">
|
||||
|
||||
@@ -828,51 +835,6 @@ Delta Chat скоріше використовує реалізацію OpenPGP
|
||||
|
||||
<p>Ви можете перевірити стан наскрізного шифрування вручну в діалоговому вікні “Шифрування” (профіль користувача на Android/iOS або клацніть правою кнопкою миші на елементі списку чату користувача на робочому столі). Delta Chat показує там два відбитки. Якщо на вашому пристрої та пристрої вашого співрозмовника з’являються однакові відбитки, з’єднання безпечне.</p>
|
||||
|
||||
<h3 id="як-перевірити-стан-шифрування-повідомлень">
|
||||
|
||||
|
||||
Як перевірити стан шифрування повідомлень? <a href="#як-перевірити-стан-шифрування-повідомлень" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Маленький <strong>замок</strong> в бульбашці повідомлення позначає, що повідомлення було належним чином наскрізно зашифроване від відправника. Якщо <strong>немає замка</strong>, повідомлення не було належним чином наскрізно зашифровано, найімовірніше, тому що відправник використовує додаток або інтерфейс веб-пошти без підтримки кінцевого шифрування.</p>
|
||||
|
||||
<h3 id="чому-я-бачу-незашифровані-повідомлення">
|
||||
|
||||
|
||||
Чому я бачу незашифровані повідомлення? <a href="#чому-я-бачу-незашифровані-повідомлення" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Якщо контакт використовує поштову програму, яка не підтримує Autocrypt всі повідомлення за участю цього контакту (в групі або чаті 1:1) не будуть наскрізно зашифровані, а отже, не показуватимуть “висячого замка” з повідомленнями. Зверніть увагу, що навіть якщо ваші контакти використовують Delta Chat у своєму акаунті, вони також можуть використовувати програму електронної пошти без функції шифрування, що може спричинити періодичні незашифровані повідомлення. Відповідати незашифрованими на незашифровані повідомлення вимагає Autocrypt щоб запобігти отриманню нечитабельних повідомлень на стороні ваших контактів та їхніх поштових програм, які не підтримують Autocrypt.</p>
|
||||
|
||||
<h3 id="як-я-можу-отримати-наскрізно-зашифрований-чат-з-контактом-delta-chat-який-іноді-користується-веб-поштою-або-іншим-додатком-електронної-пошти-що-не-підтримує-autocrypt">
|
||||
|
||||
|
||||
Як я можу отримати наскрізно зашифрований чат з контактом Delta Chat, який іноді користується веб-поштою або іншим додатком електронної пошти, що не підтримує Autocrypt? <a href="#як-я-можу-отримати-наскрізно-зашифрований-чат-з-контактом-delta-chat-який-іноді-користується-веб-поштою-або-іншим-додатком-електронної-пошти-що-не-підтримує-autocrypt" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Якщо вам потрібен безпечний наскрізно зашифрований чат з контактом який використовує свій акаунт як у Delta Chat, так і в інших додатках (наприклад, веб-пошті), що не підтримують автошифрування, найкраще налаштувати <a href="#howtoe2ee">гарантоване наскрізне шифрування з ними</a>, а потім створити груповий чат з гарантованим наскрізним шифруванням, учасниками якого будете ви двоє. У цьому груповому чаті всі повідомлення будуть наскрізно зашифровані навіть якщо в прямому чаті між вами буде <a href="#nocryptanymore">“… надіслано повідомлення з іншого пристрою”</a>.</p>
|
||||
|
||||
<h3 id="як-забезпечити-наскрізне-шифрування-та-видалення-повідомлень">
|
||||
|
||||
|
||||
Як забезпечити наскрізне шифрування та видалення повідомлень? <a href="#як-забезпечити-наскрізне-шифрування-та-видалення-повідомлень" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Найкращий спосіб забезпечити наскрізне шифрування кожного повідомлення, а метадані видалялися якнайшвидше, це <a href="#howtoe2ee">використання чатів з гарантованим наскрізним шифруванням</a>
|
||||
та увімкнення <a href="#ephemeralmsgs">зникаючих повідомлень</a>.</p>
|
||||
|
||||
<p>Гарантований наскрізно шифрований чат захищає від <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM-атак</a>, а увімкнення функції зникнення повідомлень видаляє повідомлення на сервері через певний час, налаштований користувачем.</p>
|
||||
|
||||
<p>Якщо вам не потрібне більш довготривале зберігання копій ваших повідомлень на сервері, ви також можете увімкнути <a href="#delold">“автоматично видаляти повідомлення з сервера”</a>.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
|
||||
@@ -881,23 +843,35 @@ Delta Chat скоріше використовує реалізацію OpenPGP
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Ні, Delta Chat не підтримує ідеальну пряму секретність (PFS). Це означає, що якщо ваш приватний ключ дешифрування Delta Chat витік, і хтось зібрав ваші попередні транзитні повідомлення, він зможе розшифрувати і прочитати їх за допомогою витоку ключа розшифрування.</p>
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>Зауважте, однак, що якщо хтось отримає ваші ключі розшифрування, вони, як правило, також зможуть отримати ваші повідомлення, незалежно від того, чи працює Perfect Forward Secrecy чи ні. Типовою реальною ситуацією для витоку ключів дешифрування є вилучення пристрою яку ми обговорюємо в нашій відповіді <a href="#device-seizure">про метадані та вилучення пристрою</a>.</p>
|
||||
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
|
||||
This means that if your Delta Chat private decryption key is leaked,
|
||||
and someone has collected your prior in-transit messages,
|
||||
they will be able to decrypt and read them using the leaked decryption key.</p>
|
||||
|
||||
<p>Можливо, що Delta Chat розвивається для підтримки Perfect Forward Secrecy, тому що OpenPGP - це лише контейнер для зашифрованих повідомлень, але керування ключами шифрування (і, відповідно, ротація ключів або “храповик” ключів) може бути організоване у гнучкий спосіб. Дивіться <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Прототип PFS від Seqouia</a> щодо існуючих експериментів у спільноті реалізаторів OpenPGP.</p>
|
||||
<p>Note however, that Forward Secrecy only increases your security
|
||||
if you delete messages or use ephemeral deletion timers.
|
||||
Otherwise, if anyone obtains your decryption keys,
|
||||
they are typically also able to get all your non-deleted messages
|
||||
and don’t need to decrypt any previously collected messages.</p>
|
||||
|
||||
<p>The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we also discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
|
||||
<h3 id="чи-є-наскрізне-шифрування-delta-chat-таким-же-безпечним-як-signal">
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
|
||||
|
||||
Чи є наскрізне шифрування Delta Chat таким же безпечним, як Signal? <a href="#чи-є-наскрізне-шифрування-delta-chat-таким-же-безпечним-як-signal" class="anchor"></a>
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Це залежить від того, що для вас важливо. Delta Chat <a href="#pfs">не підтримує PFS</a>, як Signal але він забезпечує <a href="#e2eeguarantee">гарантовано наскрізні зашифровані чати</a> які захищені від скомпрометованих серверів або пошкоджених мереж. Signal та більшість інших месенджерів, що підтримують PFS, не надають практичної схеми захисту чат-груп від мережевих атак які, можливо, викликають більше занепокоєння ніж потенційний зловмисник, який заволодіє вашим телефоном і приватними налаштуваннями шифрування, але чомусь не ваші повідомлення, але має повний запис усіх минулих зашифрованих повідомлень.</p>
|
||||
<p>Так.</p>
|
||||
|
||||
<p>У будь-якому випадку, наскрізне шифрування Delta Chat використовує <a href="#openpgp-secure">безпечну підмножину OpenPGP</a> який пройшов <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">незалежний аудит безпеки</a>.</p>
|
||||
<p>We devised a forward secrecy scheme that withstood initial scrutiny from cryptographers and usable security experts.
|
||||
Our tentative scheme is designed to reliably work in federated messaging networks and with multi-device usage.
|
||||
However, an implementation has not been scheduled yet (as of Mid 2025).</p>
|
||||
|
||||
<h3 id="importkey">
|
||||
|
||||
@@ -1223,6 +1197,11 @@ and will very probably be replaced by something else, stay tuned :)</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Note:
|
||||
Changing email addresses is temporarily disabled
|
||||
because of ongoing changes to the DeltaChat core.
|
||||
It should be available again in a few months.</p>
|
||||
|
||||
<ol>
|
||||
<li>
|
||||
<p>Змініть свою адресу в розділі “Налаштування → Додатково → Пароль та обліковий запис” та введіть пароль вашого нового поштового акаунта (і, за необхідності, налаштування сервера). Ви отримаєте інформаційне повідомлення про те, що ви переїжджаєте на нову адресу. Додаткове повідомлення також з’явиться у вашому чаті “Повідомлення пристрою”.</p>
|
||||
|
||||
@@ -36,27 +36,23 @@
|
||||
<li><a href="#为什么-delta-chat-与集中式专有的-applegoogle-推送服务集成">为什么 Delta Chat 与集中式专有的 Apple/Google 推送服务集成?</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><a href="#加密和安全">加密和安全</a>
|
||||
<li><a href="#e2ee">加密和安全</a>
|
||||
<ul>
|
||||
<li><a href="#端到端加密使用了哪些标准-">端到端加密使用了哪些标准 ?</a></li>
|
||||
<li><a href="#whene2e">我如何知道信息是否经过端到端加密?</a></li>
|
||||
<li><a href="#howtoe2ee">如何获得保证的端到端加密和绿色复选标记?</a></li>
|
||||
<li><a href="#e2eeguarantee">绿色复选标记和“保证的端到端加密”是什么意思?</a></li>
|
||||
<li><a href="#nocryptanymore">联系人“从另一台设备发送了消息”,我该怎么办?</a></li>
|
||||
<li><a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption">Can i still receive or send mails without end-to-end encryption?</a></li>
|
||||
<li><a href="#howtoe2ee">How can I establish a chat with a new contact?</a></li>
|
||||
<li><a href="#e2eeguarantee">What does the green checkmark in a contact profile mean?</a></li>
|
||||
<li><a href="#附件图片文件音频等是否已端到端加密">附件(图片、文件、音频等)是否已端到端加密?</a></li>
|
||||
<li><a href="#openpgp-secure">OpenPGP 安全吗?</a></li>
|
||||
<li><a href="#openpgp-alternatives">你们是否考虑过使用 OpenPGP 的替代方案进行端到端加密?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
|
||||
<li><a href="#delta-chat-是否容易受到-efail-攻击">Delta Chat 是否容易受到 EFAIL 攻击?</a></li>
|
||||
<li><a href="#tls">如果端到端加密不可用,消息是否会以明文形式暴露?</a></li>
|
||||
<li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
|
||||
<li><a href="#message-metadata">Delta Chat 如何保护消息中的元数据?</a></li>
|
||||
<li><a href="#device-seizure">当设备被查封时,如何保护元数据和联系人?</a></li>
|
||||
<li><a href="#如何检查加密信息">如何检查加密信息?</a></li>
|
||||
<li><a href="#如何检查消息的加密状态">如何检查消息的加密状态?</a></li>
|
||||
<li><a href="#为什么我会看到未加密的消息">为什么我会看到未加密的消息?</a></li>
|
||||
<li><a href="#如何与有时使用-webmail-或其他非-autocrypt-电子邮件应用的-delta-chat-联系人获得端到端加密的聊天">如何与有时使用 Webmail 或其他非 Autocrypt 电子邮件应用的 Delta Chat 联系人获得端到端加密的聊天?</a></li>
|
||||
<li><a href="#如何确保消息端到端加密和删除">如何确保消息端到端加密和删除?</a></li>
|
||||
<li><a href="#pfs">Delta Chat 是否支持完美前向保密?</a></li>
|
||||
<li><a href="#delta-chat-的端到端加密是否与-signal-一样安全">Delta Chat 的端到端加密是否与 Signal 一样安全?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#importkey">我可以重复使用现有的私钥吗?</a></li>
|
||||
<li><a href="#security-audits">Delta Chat 是否已进行独立的安全漏洞审计?</a></li>
|
||||
</ul>
|
||||
@@ -686,10 +682,10 @@ Delta Chat 收到的所有电子邮件都将在此期限后从服务器中删除
|
||||
包括<a href="https://delta.chat/chatmail#selfhosted">你可能在未经我们许可的情况下自行设置的服务器</a>。
|
||||
欢迎来到可互操作且庞大的 Chatmail 和电子邮件系统的力量 :)</p>
|
||||
|
||||
<h2 id="加密和安全">
|
||||
<h2 id="e2ee">
|
||||
|
||||
|
||||
加密和安全 <a href="#加密和安全" class="anchor"></a>
|
||||
加密和安全 <a href="#e2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h2>
|
||||
@@ -702,18 +698,26 @@ Delta Chat 收到的所有电子邮件都将在此期限后从服务器中删除
|
||||
|
||||
</h3>
|
||||
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> 用于自动
|
||||
与联系人和群组聊天建立端到端加密。
|
||||
Autocrypt 使用 OpenPGP 标准的有限且<a href="#openpgp-secure">安全子集</a>。
|
||||
端到端加密消息标有挂锁
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../lock-icon.png" alt="padlock" />。</p>
|
||||
<p>Delta Chat uses a <a href="#openpgp-secure">secure subset of the OpenPGP standard</a>
|
||||
to provide automatic end-to-end encryption using these protocols:</p>
|
||||
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">安全加入协议</a>
|
||||
用于建立具有保证的端到端加密的聊天,
|
||||
从而防止网络攻击和受损服务器。
|
||||
标有绿色复选标记的聊天
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
保证端到端加密消息。</p>
|
||||
<ul>
|
||||
<li>
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a>
|
||||
to exchange encryption setup information through QR-code scanning or “invite links”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> is used for automatically
|
||||
establishing end-to-end encryption between contacts and all members of a group chat.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Sharing a contact to a
|
||||
chat</a>
|
||||
enables receivers to use end-to-end encryption with the contact.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
|
||||
|
||||
<h3 id="whene2e">
|
||||
|
||||
@@ -723,28 +727,37 @@ Autocrypt 使用 OpenPGP 标准的有限且<a href="#openpgp-secure">安全子
|
||||
|
||||
</h3>
|
||||
|
||||
<p>所有端到端加密的消息都带有挂锁:</p>
|
||||
|
||||
<p><img style="width:160px; margin:1px" src="../lock-screenshot.png" alt="padlock in bubble" /></p>
|
||||
|
||||
<p>如果聊天标题旁边有绿色复选标记,则保证端到端加密:</p>
|
||||
|
||||
<p><img style="width:211px; margin:1px" src="../green-checkmark-screenshot.png" alt="green checkmark in title" /></p>
|
||||
<p>All messages in Delta Chat are <strong>end-to-end encrypted by default</strong>.
|
||||
Since the Delta Chat Version 2 release series (July 2025)
|
||||
there are no lock or similar markers on end-to-end encrypted messages, anymore.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
<h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
|
||||
|
||||
|
||||
如何获得保证的端到端加密和绿色复选标记? <a href="#howtoe2ee" class="anchor"></a>
|
||||
Can i still receive or send mails without end-to-end encryption? <a href="#can-i-still-receive-or-send-mails-without-end-to-end-encryption" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>如果你与你的聊天伙伴有第二个通信渠道,
|
||||
例如视频聊天或不同的即时通讯应用,
|
||||
你可以生成邀请链接。</p>
|
||||
<p>If you use default <a href="https://chatmail.at/relays">chatmail relays</a>,
|
||||
it is impossible to receive or send messages without end-to-end encryption.</p>
|
||||
|
||||
<p>如果你们面对面在一起,
|
||||
你可以向你的聊天伙伴展示二维码。</p>
|
||||
<p>If you instead create a profile using a classic e-mail server,
|
||||
you can send and receive messages without end-to-end encryption.
|
||||
Such messages lacking end-to-end encryption are marked with an e-mail icon
|
||||
<img style="vertical-align:middle; width:1.2em; margin:1px" src="../email-icon.png" alt="email" />.</p>
|
||||
|
||||
<h3 id="howtoe2ee">
|
||||
|
||||
|
||||
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You can send an invite link through another private chat,
|
||||
show an invitation QR code when next to each other or in a video call,
|
||||
or click on a “contact” that was shared in a chat.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
@@ -753,132 +766,60 @@ Autocrypt 使用 OpenPGP 标准的有限且<a href="#openpgp-secure">安全子
|
||||
然后选择“QR 邀请码”。</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>对于<strong>直接 1:1 聊天邀请</strong>,
|
||||
点击 Delta Chat 应用主屏幕上的二维码图标 <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />。</p>
|
||||
<p>For <strong>direct 1:1 chat invitations</strong>,
|
||||
tap the QR Code icon <img style="vertical-align:middle; width:1.8em; margin:1px" src="../qr-icon.png" />
|
||||
on the Delta Chat app main screen.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>让你的聊天伙伴用他们的 Delta Chat 应用扫描二维码图像,
|
||||
或点击“复制”或“分享”以创建邀请链接
|
||||
并与你的聊天伙伴分享。</p>
|
||||
<p>Ask your chat partner to scan the QR image
|
||||
with their Delta Chat app,
|
||||
or click “Copy” or “Share” to create an invite link
|
||||
and share it with your chat partner.</p>
|
||||
|
||||
<p>现在等待 <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">安全加入网络消息在两个设备之间交换</a>。</p>
|
||||
<p>Now wait while <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">end-to-end encryption is getting established</a>.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>如果两个设备都处于在线状态,
|
||||
双方最终都会看到一个(群组或直接)聊天,标题旁边带有绿色复选标记
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />。</p>
|
||||
<p>If both sides are online, they will soon see a (group or direct) chat
|
||||
and can start messaging securely.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>如果其中一个设备处于离线状态,则只有当设备再次连接互联网且安全加入网络协议完成时,绿色复选标记才会出现。</p>
|
||||
<p>If one side is offline or in bad network,
|
||||
the ability to chat is delayed until connectivity is restored.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>恭喜!
|
||||
从现在开始您将会自动使用安全的端到端加密与此联系人联系,并且双方都可以将对方添加到绿色复选标记的群组
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />,从而自动在其成员之间传播有保障的端到端加密。</p>
|
||||
<p>Congratulations!
|
||||
You now will automatically use end-to-end encryption
|
||||
with this contact.
|
||||
If you add each other to chat groups,
|
||||
end-to-end encryption will be established among all members.</p>
|
||||
|
||||
<h3 id="e2eeguarantee">
|
||||
|
||||
|
||||
绿色复选标记和“保证的端到端加密”是什么意思? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>带有绿色复选标记的聊天标题
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="绿色复选标记" />
|
||||
表示聊天中的所有消息都将进行端到端加密,
|
||||
并且不会被受损的电子邮件服务器或互联网提供商读取或更改。
|
||||
加入带有绿色复选标记的群组聊天
|
||||
可以安全地传播每个人的加密信息(和绿色复选标记),
|
||||
从而保证群组和成员之间的端到端加密。</p>
|
||||
|
||||
<p>带有绿色复选标记的联系人配置文件
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="绿色复选标记" />
|
||||
表示当前保证与联系人的消息传递是端到端加密的。
|
||||
每个带有绿色复选标记的联系人要么直接与你进行了 <a href="#howtoe2ee">二维码扫描</a>,
|
||||
要么由另一个带有绿色复选标记的联系人介绍。
|
||||
当向群组添加成员时,介绍会自动发生。
|
||||
任何将联系人添加到带有绿色复选标记的群组的人都成为
|
||||
那些还不认识添加的联系人的成员的介绍人。
|
||||
在联系人配置文件中,你可以反复点击“由…介绍”文本
|
||||
,直到你到达直接与你进行 <a href="#howtoe2ee">二维码扫描</a> 的那个人。</p>
|
||||
|
||||
<p>请注意,在联系人配置文件中,你可能会看到并点击介绍人,<br />但在配置文件标题中没有绿色复选标记。<br />这通常意味着联系人“<a href="#nocryptanymore">从另一台设备发送了消息</a>”。</p>
|
||||
<p>A contact profile might show a green checkmark
|
||||
<img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" />
|
||||
and an “Introduced by” line.
|
||||
Every green-checkmarked contact either did a direct <a href="#howtoe2ee">QR-scan</a> with you
|
||||
or was introduced by a another green-checkmarked contact.
|
||||
Introductions happen automatically when adding members to groups.
|
||||
Whoever adds a green-checkmarked contact to a group with only green-checkmarked members
|
||||
becomes an introducer.
|
||||
In a contact profile you can tap on the “Introduced by …” text repeatedly
|
||||
until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-scan</a>.</p>
|
||||
|
||||
<p>有关“保证的端到端加密”的更深入讨论,
|
||||
请参阅 <a href="https://securejoin.delta.chat/en/latest/new.html">安全加入协议</a>,
|
||||
并专门阅读有关“已验证群组”的内容,这是
|
||||
此处所谓的“带有绿色复选标记”或“保证的端到端加密”聊天的技术术语。</p>
|
||||
|
||||
<h3 id="nocryptanymore">
|
||||
|
||||
|
||||
联系人“从另一台设备发送了消息”,我该怎么办? <a href="#nocryptanymore" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>你与联系人的聊天失去了保证的端到端加密。
|
||||
当你看到此警告时,此聊天的绿色复选标记和联系人已被删除。
|
||||
<strong>如果你发现保证的端到端加密突然下降
|
||||
对于此联系人来说很意外,请不要接受警告!</strong>
|
||||
相反,请通过第二个渠道(
|
||||
如视频通话、其他即时通讯应用或电话)与你的联系人核实
|
||||
,以找出发生了什么。</p>
|
||||
|
||||
<p>如果你的联系人实际上导致了保证的端到端加密下降,
|
||||
请参阅以下段落,了解常见原因及其缓解措施。
|
||||
无论如何,所有其他带有绿色复选标记的聊天都保持保证的端到端加密,
|
||||
即使该联系人是那里的成员。</p>
|
||||
|
||||
<p><strong>你的联系人在第二台设备(手机或笔记本电脑)上使用 Delta Chat</strong></p>
|
||||
|
||||
<p>如果他们有另一台运行 Delta Chat 应用的设备,
|
||||
他们应该从新设备中删除配置文件,
|
||||
并<a href="#multiclient">按照此处所述将其添加为第二台设备</a>。
|
||||
在他们之后给你发消息后,警告将消失,
|
||||
并且保证的加密将在你的联系人的两台设备之间建立。</p>
|
||||
|
||||
<p><strong>你的联系人使用他们的旧帐户登录名重新安装了 Delta Chat</strong></p>
|
||||
|
||||
<p>如果他们有<a href="#backup">备份文件</a>,
|
||||
他们应该从新设备中删除配置文件,
|
||||
而是导入备份文件以重新创建他们的配置文件。
|
||||
在他们之后给你发消息后,警告将消失,
|
||||
并且保证的加密将为此联系人重新建立。</p>
|
||||
|
||||
<p>如果他们没有备份文件,最好与你的聊天伙伴执行 <a href="#howtoe2ee">二维码扫描</a>,
|
||||
以重新建立保证的端到端加密。</p>
|
||||
|
||||
<p><strong>你的联系人通过 Webmail 界面或其他电子邮件应用发送了邮件,
|
||||
并且将很快恢复使用 Delta Chat。</strong></p>
|
||||
|
||||
<p>如果你确定联系人有时使用 Webmail,
|
||||
或其他缺少端到端加密的邮件应用,
|
||||
那么你可以接受警告。
|
||||
一旦你的联系人再次使用 Delta Chat,
|
||||
保证的端到端加密将自动重新建立。</p>
|
||||
|
||||
<p><strong>你的联系人完全停止使用 Delta Chat</strong></p>
|
||||
|
||||
<p>有时保持联系比端到端加密更重要。
|
||||
<a href="#tls">“传输层加密” (TLS)</a> 可能仍然有意义地保护
|
||||
你的设备和电子邮件服务器之间消息的机密性。
|
||||
但是,如果没有端到端加密,你和你的联系人将信任你的电子邮件服务器
|
||||
不会读取或操纵你的消息,也不会将其交给第三方。</p>
|
||||
|
||||
<p>在任何情况下,你都无法做太多其他事情,只能接受警告。
|
||||
另请从任何活动的带有绿色复选标记的群组中删除该联系人,
|
||||
你可以在联系人配置文件中的“共享聊天”中找到这些群组。
|
||||
这可以避免你的联系人收到“无法读取”的消息。</p>
|
||||
|
||||
<p>如果联系人因为错误或不良行为而删除了 Delta Chat,
|
||||
请考虑发布到我们的 <a href="https://support.delta.chat">支持论坛</a>,
|
||||
以帮助我们识别和解决常见问题。 谢谢!</p>
|
||||
|
||||
<h3 id="附件图片文件音频等是否已端到端加密">
|
||||
|
||||
|
||||
@@ -901,10 +842,9 @@ Autocrypt 使用 OpenPGP 标准的有限且<a href="#openpgp-secure">安全子
|
||||
|
||||
</h3>
|
||||
|
||||
<p>是的,Delta Chat 使用 OpenPGP 的安全子集,
|
||||
并且仅在消息上显示挂锁安全指示器
|
||||
,前提是整个消息都已正确加密和签名。
|
||||
例如,“分离签名”不被视为安全。</p>
|
||||
<p>Yes, Delta Chat uses a secure subset of OpenPGP
|
||||
requiring the whole message to be properly encrypted and signed.
|
||||
For example, “Detached signatures” are not treated as secure.</p>
|
||||
|
||||
<p>OpenPGP 加密标准本身不存在安全隐患。
|
||||
目前公众讨论中涉及的 OpenPGP 安全问题,
|
||||
@@ -923,7 +863,7 @@ Delta Chat 实际使用的是 Rust 语言编写的 OpenPGP 实现库 <a href="ht
|
||||
<h3 id="openpgp-alternatives">
|
||||
|
||||
|
||||
你们是否考虑过使用 OpenPGP 的替代方案进行端到端加密? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -965,17 +905,15 @@ Delta Chat 实际使用的是 Rust 语言编写的 OpenPGP 实现库 <a href="ht
|
||||
<h3 id="tls">
|
||||
|
||||
|
||||
如果端到端加密不可用,消息是否会以明文形式暴露? <a href="#tls" class="anchor"></a>
|
||||
Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>即使你的消息未保证端到端加密,
|
||||
它们仍然受到互联网提供商(如手机或有线电视公司)的保护。
|
||||
但是,你的和你的接收者的电子邮件提供商
|
||||
可能会读取、分析甚至修改你的消息,
|
||||
包括任何附件,
|
||||
如果它们未进行端到端加密。</p>
|
||||
<p>If you are sending or receiving e-mail messages without end-to-end encryption (using a classic e-mail server),
|
||||
they are still protected from cell or cable companies who can not read or modify your e-mail messages.
|
||||
But both your and your recipient’s e-mail providers
|
||||
may read, analyze or modify your messages, including any attachments.</p>
|
||||
|
||||
<p>Delta Chat 默认使用严格的
|
||||
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">TLS 加密</a>,
|
||||
@@ -986,10 +924,6 @@ Delta Chat 的所有 TLS 处理都经过了独立的 <a href="#security-audits">
|
||||
如果所涉及的电子邮件服务器支持 <a href="https://datatracker.ietf.org/doc/html/rfc8461">MTA-STS</a>,
|
||||
则将在电子邮件提供商之间强制执行传输加密,
|
||||
在这种情况下,即使消息未进行端到端加密,Delta Chat 通信也永远不会以明文形式暴露给互联网。</p>
|
||||
|
||||
<p>请注意,<a href="#howtoe2ee">在 TLS 加密之上保持保证的端到端加密</a>
|
||||
可在你的和接收者的设备之间提供普遍的安全性。
|
||||
即使你的电子邮件或互联网提供商也无法读取或修改你的消息。</p>
|
||||
|
||||
<h3 id="message-metadata">
|
||||
|
||||
@@ -1051,72 +985,6 @@ Delta Chat 在此处显示两个指纹。
|
||||
如果相同的指纹出现在你自己的设备和你联系人的设备上,
|
||||
则连接是安全的。</p>
|
||||
|
||||
<h3 id="如何检查消息的加密状态">
|
||||
|
||||
|
||||
如何检查消息的加密状态? <a href="#如何检查消息的加密状态" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>消息气泡中的小<strong>挂锁</strong>表示
|
||||
消息已从给定的发件人正确进行端到端加密。
|
||||
如果<strong>没有挂锁</strong>,则消息未正确进行端到端加密,
|
||||
最可能是因为发件人使用的应用或 Webmail 界面
|
||||
不支持端到端加密。</p>
|
||||
|
||||
<h3 id="为什么我会看到未加密的消息">
|
||||
|
||||
|
||||
为什么我会看到未加密的消息? <a href="#为什么我会看到未加密的消息" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>如果联系人使用非 Autocrypt 电子邮件应用,
|
||||
则涉及此联系人(在群组或 1:1 聊天中)的所有消息
|
||||
将不会进行端到端加密,因此消息中不会显示“挂锁”。
|
||||
请注意,即使你的联系人在其帐户上使用 Delta Chat,
|
||||
他们也可能在该帐户上使用非 Autocrypt 电子邮件应用,
|
||||
这可能会导致间歇性未加密的消息。
|
||||
回复未加密的消息是 Autocrypt 强制执行的
|
||||
,以防止你的联系人及其非 Autocrypt 电子邮件应用端出现无法读取的消息。</p>
|
||||
|
||||
<h3 id="如何与有时使用-webmail-或其他非-autocrypt-电子邮件应用的-delta-chat-联系人获得端到端加密的聊天">
|
||||
|
||||
|
||||
如何与有时使用 Webmail 或其他非 Autocrypt 电子邮件应用的 Delta Chat 联系人获得端到端加密的聊天? <a href="#如何与有时使用-webmail-或其他非-autocrypt-电子邮件应用的-delta-chat-联系人获得端到端加密的聊天" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>如果你需要与
|
||||
同时使用 Delta Chat 和非 Autocrypt 应用(例如 Webmail)的电子邮件帐户的联系人进行安全端到端加密的聊天,
|
||||
最好与他们设置 <a href="#howtoe2ee">保证的端到端加密</a>,
|
||||
然后创建一个由你二人作为成员的保证的端到端加密的群组聊天。
|
||||
在此群组聊天中,所有消息都将进行端到端加密,
|
||||
即使你二人之间的直接聊天有
|
||||
<a href="#nocryptanymore">“…从另一台设备发送了消息”</a> 警告</p>
|
||||
|
||||
<h3 id="如何确保消息端到端加密和删除">
|
||||
|
||||
|
||||
如何确保消息端到端加密和删除? <a href="#如何确保消息端到端加密和删除" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>确保每条消息都进行端到端加密,
|
||||
并尽快删除元数据的最佳方法是
|
||||
<a href="#howtoe2ee">使用具有保证的端到端加密的聊天</a>
|
||||
并开启 <a href="#ephemeralmsgs">阅后即焚消息</a>。</p>
|
||||
|
||||
<p>保证的端到端加密聊天可防止 <a href="https://en.wikipedia.org/wiki/Man-in-the-middle_attack">MITM 攻击</a>,
|
||||
而开启阅后即焚消息会在用户配置的时间后删除服务器上的消息。</p>
|
||||
|
||||
<p>如果你不需要在服务器上保留消息的长期副本,
|
||||
你还可以开启 <a href="#delold">“自动从服务器删除消息”</a>。</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
|
||||
@@ -1125,45 +993,35 @@ Delta Chat 在此处显示两个指纹。
|
||||
|
||||
</h3>
|
||||
|
||||
<p>不,Delta Chat 不支持完美前向保密 (PFS)。
|
||||
这意味着,如果您的 Delta Chat 私人解密密钥泄露,
|
||||
并且有人收集了您之前传输的消息,
|
||||
他们将能够使用泄露的解密密钥解密并阅读这些消息。</p>
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>但请注意,如果有人获得您的解密密钥,
|
||||
他们通常也能够获得您的消息,
|
||||
无论是否实施了完全前向保密。
|
||||
泄露解密密钥的典型现实情况是设备扣押,
|
||||
我们在<a href="#device-seizure">关于元数据和设备扣押</a>的回答中讨论了这一点。</p>
|
||||
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
|
||||
This means that if your Delta Chat private decryption key is leaked,
|
||||
and someone has collected your prior in-transit messages,
|
||||
they will be able to decrypt and read them using the leaked decryption key.</p>
|
||||
|
||||
<p>Delta Chat 可能会发展为支持完美前向保密,
|
||||
因为 OpenPGP 只是加密消息的容器,
|
||||
但密钥管理(以及密钥轮换或密钥“棘轮”)
|
||||
可以以灵活的方式组织。
|
||||
请参阅 <a href="https://gitlab.com/sequoia-pgp/openpgp-dr">Seqouia 的 PFS 原型</a>,
|
||||
了解 OpenPGP 实现者社区中现有的实验。</p>
|
||||
<p>Note however, that Forward Secrecy only increases your security
|
||||
if you delete messages or use ephemeral deletion timers.
|
||||
Otherwise, if anyone obtains your decryption keys,
|
||||
they are typically also able to get all your non-deleted messages
|
||||
and don’t need to decrypt any previously collected messages.</p>
|
||||
|
||||
<p>The typical real-world situation for leaked decryption keys is device seizure
|
||||
which we also discuss in our answer <a href="#device-seizure">on metadata and device seizure</a>.</p>
|
||||
|
||||
<h3 id="delta-chat-的端到端加密是否与-signal-一样安全">
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
|
||||
|
||||
Delta Chat 的端到端加密是否与 Signal 一样安全? <a href="#delta-chat-的端到端加密是否与-signal-一样安全" class="anchor"></a>
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>这取决于对你而言重要的是什么。
|
||||
Delta Chat <a href="#pfs">不支持像 Signal 那样的 PFS</a>,
|
||||
但它提供了 <a href="#e2eeguarantee">保证的端到端加密聊天</a>,
|
||||
可以安全地抵御受损的服务器或损坏的网络。
|
||||
Signal 和大多数其他支持 PFS 的即时通讯应用
|
||||
没有提供实用的方案来保护聊天群组免受网络攻击,
|
||||
而网络攻击可以说比
|
||||
潜在的攻击者查封你的手机和私有加密设置
|
||||
但不知何故没有你的消息,却完整记录了所有
|
||||
过去的加密消息更令人担忧。</p>
|
||||
<p>是的。</p>
|
||||
|
||||
<p>在任何情况下,Delta Chat 的端到端加密都使用 <a href="#openpgp-secure">OpenPGP 的安全子集</a>,
|
||||
该子集已 <a href="https://delta.chat/assets/blog/2019-first-security-review.pdf">通过独立的安全审计</a>。</p>
|
||||
<p>We devised a forward secrecy scheme that withstood initial scrutiny from cryptographers and usable security experts.
|
||||
Our tentative scheme is designed to reliably work in federated messaging networks and with multi-device usage.
|
||||
However, an implementation has not been scheduled yet (as of Mid 2025).</p>
|
||||
|
||||
<h3 id="importkey">
|
||||
|
||||
@@ -1571,6 +1429,11 @@ and will very probably be replaced by something else, stay tuned :)</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Note:
|
||||
Changing email addresses is temporarily disabled
|
||||
because of ongoing changes to the DeltaChat core.
|
||||
It should be available again in a few months.</p>
|
||||
|
||||
<ol>
|
||||
<li>
|
||||
<p>在“设置 → 高级 → 密码和帐户”中更改你的地址,
|
||||
|
||||
Reference in New Issue
Block a user