mirror of
https://github.com/ArcaneChat/android.git
synced 2026-07-03 14:05:24 +02:00
Compare commits
8 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
 adbenitez
|
e6f4a616fb | ||
|
adb
|
68f270eea3 | ||
|
adbenitez
|
52aeec8d17 | ||
|
adb
|
bdcaffde3d | ||
|
adbenitez
|
d19dcb41ec | ||
|
adbenitez
|
5525cfa5a9 | ||
|
adbenitez
|
8715e9eba2 | ||
|
adbenitez
|
3cc58c2a0f |
@@ -1,6 +1,6 @@
|
||||
# Delta Chat Android Changelog
|
||||
|
||||
## v2.6.0
|
||||
## v2.8.0
|
||||
|
||||
* Profiles focus on recognizing contacts
|
||||
* See the number of media directly in the profile, no need to tap around
|
||||
@@ -19,7 +19,7 @@
|
||||
* Allow to sort profiles up in the profile switcher
|
||||
* Add new option to create unencrypted email thread
|
||||
* Green checkmarks are removed where they mostly refer to guaranteed encryption, which is the default now. They are still used for profile's "Introduced by"
|
||||
* Update to core 2.6.0
|
||||
* Update to core 2.8.0
|
||||
|
||||
## v1.58.4
|
||||
2025-05
|
||||
|
||||
@@ -30,4 +30,4 @@ This app has some extended support for WebXDC apps:
|
||||
|
||||
This app is based on the [official Delta Chat client](https://github.com/deltachat/deltachat-android) with several improvements.
|
||||
|
||||
This app uses a [modified](https://github.com/ArcaneChat/core) version of the [Delta Chat Core Library](https://github.com/deltachat/deltachat-core-rust).
|
||||
This app uses a [modified](https://github.com/ArcaneChat/core) version of the [Chatmail Core Library](https://github.com/chatmail/core).
|
||||
|
||||
+2
-2
@@ -33,8 +33,8 @@ android {
|
||||
useLibrary 'org.apache.http.legacy'
|
||||
|
||||
defaultConfig {
|
||||
versionCode 30000725
|
||||
versionName "2.6.0"
|
||||
versionCode 30000726
|
||||
versionName "2.8.0"
|
||||
|
||||
applicationId "chat.delta.lite"
|
||||
multiDexEnabled true
|
||||
|
||||
+1
-1
Submodule jni/deltachat-core-rust updated: aa5d7b704c...9c68a91f41
@@ -50,9 +50,10 @@
|
||||
<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="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
|
||||
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
|
||||
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</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>
|
||||
@@ -973,25 +974,25 @@ even if the message was not end-to-end encrypted.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Delta Chat protects most message metadata by putting the following information
|
||||
into the end-to-end encrypted part of messages:</p>
|
||||
<p>Unlike most other messengers,
|
||||
Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
|
||||
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
|
||||
|
||||
<p>E-mail Servers can therefore only see</p>
|
||||
|
||||
<ul>
|
||||
<li>Subject line</li>
|
||||
<li>Group avatar and name</li>
|
||||
<li>MDN (read receipt) requests (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li>
|
||||
<li>Disappearing message timer (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li>
|
||||
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li>
|
||||
<li><code class="language-plaintext highlighter-rouge">Secure-Join</code> header containing secure join commands</li>
|
||||
<li>Notification about enabling location streaming</li>
|
||||
<li>WebRTC room URL</li>
|
||||
<li>
|
||||
<p>the message date,</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>sender and receiver addresses</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>and message size.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>E-Mail servers do not get access to this protected metadata
|
||||
but they do see the message date as well as the message size,
|
||||
and, more importantly, the sender and receiver addresses.
|
||||
E-mail servers need receiver addresses to route and
|
||||
deliver messages to recipient’s devices.</p>
|
||||
<p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
|
||||
|
||||
<h3 id="device-seizure">
|
||||
|
||||
@@ -1003,28 +1004,34 @@ deliver messages to recipient’s devices.</p>
|
||||
|
||||
<p>Both for protecting against metadata-collecting e-mail servers
|
||||
as well as against the threat of device seizure
|
||||
we recommend to use a <a href="https://delta.chat/chatmail">chatmail server</a>
|
||||
to create pseudonymous temporary profiles through QR-code scans.
|
||||
we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
|
||||
to create chat profiles using random e-mail addresses for transport.
|
||||
Note that Delta Chat apps on all platforms support multiple profiles
|
||||
so you can easily use situation-specific profiles next to your “main” profile
|
||||
with the knowledge that all their data, along with all metadata, will be deleted.
|
||||
Moreover, if a device is seized then contacts using temporary profiles
|
||||
can not be identified easily, as compared to messengers which reveal
|
||||
phone numbers in chat groups which in turn are often associated with legal identities.</p>
|
||||
Moreover, if a device is seized then chat contacts using short-lived profiles
|
||||
can not be identified easily.</p>
|
||||
|
||||
<h3 id="how-can-i-check-encryption-information">
|
||||
<h3 id="sealedsender">
|
||||
|
||||
|
||||
How can i check encryption information? <a href="#how-can-i-check-encryption-information" class="anchor"></a>
|
||||
Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
|
||||
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
|
||||
Delta Chat shows two fingerprints there.
|
||||
If the same fingerprints appear on your own and your contact’s device,
|
||||
the connection is safe.</p>
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
|
||||
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
|
||||
It is particularly important because the Signal server knows the mobile number of each account,
|
||||
which is usually associated with a passport identity.</p>
|
||||
|
||||
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
|
||||
do not ask for any private data (including no phone numbers),
|
||||
it might still be worthwhile to protect relational metadata between addresses.
|
||||
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
|
||||
but an implementation has not been agreed as a priority yet.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
@@ -1037,32 +1044,49 @@ the connection is safe.</p>
|
||||
<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,
|
||||
This means that if your 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>
|
||||
they will be able to decrypt and read them using the leaked decryption key.
|
||||
Note that Forward Secrecy only increases security if you delete messages.
|
||||
Otherwise, someone obtaining your decryption keys
|
||||
is typically also able to get all your non-deleted messages
|
||||
and doesn’t even need to decrypt any previously collected messages.</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>
|
||||
<p>We designed a Forward Secrecy approach that withstood
|
||||
initial examination from some cryptographers and implementation experts
|
||||
but is pending a more formal write up
|
||||
to ascertain it reliably works in federated messaging and with multi-device usage,
|
||||
before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
|
||||
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
|
||||
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
<h3 id="pqc">
|
||||
|
||||
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Yes.</p>
|
||||
<p>No, not yet.</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>
|
||||
<p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
|
||||
which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
|
||||
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
|
||||
in collaboration with other OpenPGP implementers.</p>
|
||||
|
||||
<h3 id="how-can-i-manually-check-encryption-information">
|
||||
|
||||
|
||||
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
|
||||
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
|
||||
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="importkey">
|
||||
|
||||
|
||||
@@ -40,19 +40,20 @@
|
||||
<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="#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="#kann-ich-e-mails-ohne-ende-zu-ende-verschlüsselung-empfangen-oder-senden">Kann ich E-Mails ohne Ende-zu-Ende-Verschlüsselung empfangen oder senden?</a></li>
|
||||
<li><a href="#howtoe2ee">Wie kann ich einen Chat mit einem neuen Kontakt erstellen?</a></li>
|
||||
<li><a href="#e2eeguarantee">Was bedeutet das grüne Häkchen in einem Kontaktprofil?</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">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</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="#ist-delta-chat-anfällig-für-efail">Ist Delta Chat anfällig für EFAIL?</a></li>
|
||||
<li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
|
||||
<li><a href="#tls">Sind mit dem Mail-Symbol markierte Nachrichten im Internet sichtbar?</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="#sealedsender">Unterstützt Delta Chat „Sealed Sender“?</a></li>
|
||||
<li><a href="#pfs">Unterstützt Delta Chat “Perfect Forward Secrecy”?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#pqc">Unterstützt Delta Chat Post-Quantum-Verschlüsselung?</a></li>
|
||||
<li><a href="#wie-kann-ich-die-verschlüsselung-manuell-überprüfen">Wie kann ich die Verschlüsselung manuell überprüfen?</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>
|
||||
@@ -86,7 +87,7 @@
|
||||
<ul>
|
||||
<li><a href="#welche-app-berechtigungen-benötigt-delta-chat">Welche App-Berechtigungen benötigt Delta Chat?</a></li>
|
||||
<li><a href="#funktioniert-delta-chat-mit-meinem-e-mail-anbieter">Funktioniert Delta Chat mit <em>meinem</em> E-Mail-Anbieter?</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="#ich-möchte-meinen-eigenen-server-für-delta-chat-verwalten-gibt-es-empfehlungen">Ich möchte meinen eigenen Server für Delta Chat verwalten. Gibt es Empfehlungen?</a></li>
|
||||
<li><a href="#weshalb-muss-ich-mein-e-mail-kennwort-in-delta-chat-eingeben-ist-das-sicher">Weshalb muss ich mein E-Mail-Kennwort in Delta Chat eingeben? Ist das sicher?</a></li>
|
||||
<li><a href="#welche-nachrichten-erscheinen-in-delta-chat">Welche Nachrichten erscheinen in Delta Chat?</a></li>
|
||||
<li><a href="#unterstützt-delta-chat-html-e-mails">Unterstützt Delta Chat HTML-E-Mails?</a></li>
|
||||
@@ -726,26 +727,25 @@ enables receivers to use end-to-end encryption with the contact.</p>
|
||||
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="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
|
||||
<h3 id="kann-ich-e-mails-ohne-ende-zu-ende-verschlüsselung-empfangen-oder-senden">
|
||||
|
||||
|
||||
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>
|
||||
Kann ich E-Mails ohne Ende-zu-Ende-Verschlüsselung empfangen oder senden? <a href="#kann-ich-e-mails-ohne-ende-zu-ende-verschlüsselung-empfangen-oder-senden" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<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 die Standard-<a href="https://chatmail.at/relays">Chatmail-Relays</a> verwenden, ist es unmöglich, Nachrichten ohne End-to-End-Verschlüsselung zu empfangen oder zu senden.</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
|
||||
<p>Wenn Sie stattdessen ein Profil mit einem klassischen E-Mail-Server erstellen,
|
||||
können Sie Nachrichten ohne End-to-End-Verschlüsselung senden und empfangen.
|
||||
Solche Nachrichten werden mit einem E-Mail-Symbol gekennzeichnet
|
||||
<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>
|
||||
Wie kann ich einen Chat mit einem neuen Kontakt erstellen? <a href="#howtoe2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -794,7 +794,7 @@ end-to-end encryption will be established among all members.</p>
|
||||
<h3 id="e2eeguarantee">
|
||||
|
||||
|
||||
What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
Was bedeutet das grüne Häkchen in einem Kontaktprofil? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -858,7 +858,7 @@ die Sicherheitseigenschaften durch das im Sommer 2023 angenommene
|
||||
<h3 id="openpgp-alternatives">
|
||||
|
||||
|
||||
Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
Wurden Alternativen zu OpenPGP für die Ende-zu-Ende-Verschlüsselung in Betracht gezogen? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -901,7 +901,7 @@ so wie in der Autocrypt-Level-1-Spezifikation definiert.</p>
|
||||
<h3 id="tls">
|
||||
|
||||
|
||||
Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
|
||||
Sind mit dem Mail-Symbol markierte Nachrichten im Internet sichtbar? <a href="#tls" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -930,24 +930,25 @@ selbst wenn die Nachricht nicht Ende-zu-Ende-verschlüsselt war.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Delta Chat schützt die meisten Metadaten von Nachrichten, indem es die folgenden Informationen
|
||||
in den Ende-zu-Ende-verschlüsselten Teil der Nachrichten verschiebt:</p>
|
||||
<p>Anders als die meisten anderen Messenger
|
||||
speichern Delta-Chat-Apps keine Metadaten über Kontakte oder Gruppen auf Servern. Auch nicht in verschlüsselter Form.
|
||||
Stattdessen werden alle Gruppen-Metadaten durchgängig verschlüsselt und ausschließlich auf den Endgeräten der Nutzer gespeichert.</p>
|
||||
|
||||
<p>E-Mail-Server können deshalb nur das Folgende sehen:</p>
|
||||
|
||||
<ul>
|
||||
<li>Betreffzeile</li>
|
||||
<li>Avatar und Name der Gruppe</li>
|
||||
<li>Lesebestätigungen (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li>
|
||||
<li>Timer für verschwindende Nachrichten (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li>
|
||||
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li>
|
||||
<li><code class="language-plaintext highlighter-rouge">Secure-Join</code>-Header</li>
|
||||
<li>Aktivierung des Standort-Streamings</li>
|
||||
<li>WebRTC-Raum-URL</li>
|
||||
<li>
|
||||
<p>Uhrzeit und Datum der Nachricht</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Absende- und Empfangsadresse</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Größe der Nachricht</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>E-Mail-Server erhalten keinen Zugriff auf diese geschützten Metadaten,
|
||||
sehen aber Datum und Größe der Nachricht sowie die Absender- und Empfängeradressen.
|
||||
E-Mail-Server benötigen Empfängeradressen, um Nachrichten
|
||||
Nachrichten an die Geräte der Empfänger weiterzuleiten und zuzustellen.</p>
|
||||
<p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
|
||||
|
||||
<h3 id="device-seizure">
|
||||
|
||||
@@ -957,29 +958,36 @@ Nachrichten an die Geräte der Empfänger weiterzuleiten und zuzustellen.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Sowohl zum Schutz vor E-Mail-Servern, die Metadaten sammeln,
|
||||
als auch gegen die Gefahr der Beschlagnahmung von Geräten
|
||||
empfehlen wir die Verwendung einer für Delta Chat optimierten <a href="https://delta.chat/serverguide">E-Mail-Server-Instanz</a>, um pseudonym-temporäre Konten durch Scannen von QR-Codes zu erstellen.
|
||||
Beachten Sie, dass Delta-Chat-Apps auf allen Plattformen mehrere Konten unterstützen.
|
||||
Sie können also problemlos aktionsspezifische “1-Wochen-“ oder “1-Monats-Konten” neben Ihrem “Hauptkonto” verwenden,
|
||||
mit dem Wissen, dass alle temporären Kontodaten zusammen mit allen Metadaten gelöscht werden.
|
||||
Wenn ein Gerät beschlagnahmt wird, können Kontakte mit temporären E-Mail-Konten
|
||||
Konten nicht so leicht identifiziert werden, wie dies bei Messengern der Fall ist, die die
|
||||
Telefonnummern in Chatgruppen preisgeben, die wiederum oft mit legalen Identitäten verbunden sind.</p>
|
||||
<p>Both for protecting against metadata-collecting e-mail servers
|
||||
as well as against the threat of device seizure
|
||||
we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
|
||||
to create chat profiles using random e-mail addresses for transport.
|
||||
Note that Delta Chat apps on all platforms support multiple profiles
|
||||
so you can easily use situation-specific profiles next to your “main” profile
|
||||
with the knowledge that all their data, along with all metadata, will be deleted.
|
||||
Moreover, if a device is seized then chat contacts using short-lived profiles
|
||||
can not be identified easily.</p>
|
||||
|
||||
<h3 id="wie-kann-ich-die-verschlüsselungsinformationen-überprüfen">
|
||||
<h3 id="sealedsender">
|
||||
|
||||
|
||||
Wie kann ich die Verschlüsselungsinformationen überprüfen? <a href="#wie-kann-ich-die-verschlüsselungsinformationen-überprüfen" class="anchor"></a>
|
||||
Unterstützt Delta Chat „Sealed Sender“? <a href="#sealedsender" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Sie können den Status der Ende-zu-Ende-Verschlüsselung manuell im Dialog “Verschlüsselung”
|
||||
(Android/iOS: Benutzerprofil, Desktop: Rechtsklick auf den Chat eines Benutzers) überprüfen.
|
||||
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>
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
|
||||
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
|
||||
It is particularly important because the Signal server knows the mobile number of each account,
|
||||
which is usually associated with a passport identity.</p>
|
||||
|
||||
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
|
||||
do not ask for any private data (including no phone numbers),
|
||||
it might still be worthwhile to protect relational metadata between addresses.
|
||||
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
|
||||
but an implementation has not been agreed as a priority yet.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
@@ -992,32 +1000,49 @@ ist die Verbindung sicher.</p>
|
||||
<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,
|
||||
This means that if your 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>
|
||||
they will be able to decrypt and read them using the leaked decryption key.
|
||||
Note that Forward Secrecy only increases security if you delete messages.
|
||||
Otherwise, someone obtaining your decryption keys
|
||||
is typically also able to get all your non-deleted messages
|
||||
and doesn’t even need to decrypt any previously collected messages.</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>
|
||||
<p>We designed a Forward Secrecy approach that withstood
|
||||
initial examination from some cryptographers and implementation experts
|
||||
but is pending a more formal write up
|
||||
to ascertain it reliably works in federated messaging and with multi-device usage,
|
||||
before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
|
||||
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
|
||||
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
<h3 id="pqc">
|
||||
|
||||
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
Unterstützt Delta Chat Post-Quantum-Verschlüsselung? <a href="#pqc" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Ja.</p>
|
||||
<p>No, not yet.</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>
|
||||
<p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
|
||||
which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
|
||||
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
|
||||
in collaboration with other OpenPGP implementers.</p>
|
||||
|
||||
<h3 id="wie-kann-ich-die-verschlüsselung-manuell-überprüfen">
|
||||
|
||||
|
||||
Wie kann ich die Verschlüsselung manuell überprüfen? <a href="#wie-kann-ich-die-verschlüsselung-manuell-überprüfen" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Sie können den Status der Ende-zu-Ende-Verschlüsselung manuell im Dialog “Verschlüsselung”
|
||||
(Android/iOS: Benutzerprofil, Desktop: Rechtsklick auf den Chat eines Benutzers) überprüfen.
|
||||
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="importkey">
|
||||
|
||||
@@ -1457,10 +1482,10 @@ gesendet haben, Nachrichten an Ihre neue Adresse senden.</p>
|
||||
Allerdings benötigen einige Anbieter besondere Einstellungen, um ordnungsgemäß zu funktionieren; eine von NutzerInnen erstellte Sammlung zu einigen Optionen findet sich unter <a href="https://providers.delta.chat">Provider Overview</a>.</li>
|
||||
</ul>
|
||||
|
||||
<h3 id="i-want-to-manage-my-own-server-for-delta-chat-what-do-you-recommend">
|
||||
<h3 id="ich-möchte-meinen-eigenen-server-für-delta-chat-verwalten-gibt-es-empfehlungen">
|
||||
|
||||
|
||||
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>
|
||||
Ich möchte meinen eigenen Server für Delta Chat verwalten. Gibt es Empfehlungen? <a href="#ich-möchte-meinen-eigenen-server-für-delta-chat-verwalten-gibt-es-empfehlungen" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
@@ -50,9 +50,10 @@
|
||||
<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="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
|
||||
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
|
||||
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</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>
|
||||
@@ -977,25 +978,25 @@ even if the message was not end-to-end encrypted.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Delta Chat protects most message metadata by putting the following information
|
||||
into the end-to-end encrypted part of messages:</p>
|
||||
<p>Unlike most other messengers,
|
||||
Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
|
||||
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
|
||||
|
||||
<p>E-mail Servers can therefore only see</p>
|
||||
|
||||
<ul>
|
||||
<li>Subject line</li>
|
||||
<li>Group avatar and name</li>
|
||||
<li>MDN (read receipt) requests (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li>
|
||||
<li>Disappearing message timer (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li>
|
||||
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li>
|
||||
<li><code class="language-plaintext highlighter-rouge">Secure-Join</code> header containing secure join commands</li>
|
||||
<li>Notification about enabling location streaming</li>
|
||||
<li>WebRTC room URL</li>
|
||||
<li>
|
||||
<p>the message date,</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>sender and receiver addresses</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>and message size.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>E-Mail servers do not get access to this protected metadata
|
||||
but they do see the message date as well as the message size,
|
||||
and, more importantly, the sender and receiver addresses.
|
||||
E-mail servers need receiver addresses to route and
|
||||
deliver messages to recipient’s devices.</p>
|
||||
<p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
|
||||
|
||||
<h3 id="device-seizure">
|
||||
|
||||
@@ -1007,28 +1008,34 @@ deliver messages to recipient’s devices.</p>
|
||||
|
||||
<p>Both for protecting against metadata-collecting e-mail servers
|
||||
as well as against the threat of device seizure
|
||||
we recommend to use a <a href="https://delta.chat/chatmail">chatmail server</a>
|
||||
to create pseudonymous temporary profiles through QR-code scans.
|
||||
we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
|
||||
to create chat profiles using random e-mail addresses for transport.
|
||||
Note that Delta Chat apps on all platforms support multiple profiles
|
||||
so you can easily use situation-specific profiles next to your “main” profile
|
||||
with the knowledge that all their data, along with all metadata, will be deleted.
|
||||
Moreover, if a device is seized then contacts using temporary profiles
|
||||
can not be identified easily, as compared to messengers which reveal
|
||||
phone numbers in chat groups which in turn are often associated with legal identities.</p>
|
||||
Moreover, if a device is seized then chat contacts using short-lived profiles
|
||||
can not be identified easily.</p>
|
||||
|
||||
<h3 id="how-can-i-check-encryption-information">
|
||||
<h3 id="sealedsender">
|
||||
|
||||
|
||||
How can i check encryption information? <a href="#how-can-i-check-encryption-information" class="anchor"></a>
|
||||
Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
|
||||
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
|
||||
Delta Chat shows two fingerprints there.
|
||||
If the same fingerprints appear on your own and your contact’s device,
|
||||
the connection is safe.</p>
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
|
||||
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
|
||||
It is particularly important because the Signal server knows the mobile number of each account,
|
||||
which is usually associated with a passport identity.</p>
|
||||
|
||||
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
|
||||
do not ask for any private data (including no phone numbers),
|
||||
it might still be worthwhile to protect relational metadata between addresses.
|
||||
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
|
||||
but an implementation has not been agreed as a priority yet.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
@@ -1041,32 +1048,49 @@ the connection is safe.</p>
|
||||
<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,
|
||||
This means that if your 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>
|
||||
they will be able to decrypt and read them using the leaked decryption key.
|
||||
Note that Forward Secrecy only increases security if you delete messages.
|
||||
Otherwise, someone obtaining your decryption keys
|
||||
is typically also able to get all your non-deleted messages
|
||||
and doesn’t even need to decrypt any previously collected messages.</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>
|
||||
<p>We designed a Forward Secrecy approach that withstood
|
||||
initial examination from some cryptographers and implementation experts
|
||||
but is pending a more formal write up
|
||||
to ascertain it reliably works in federated messaging and with multi-device usage,
|
||||
before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
|
||||
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
|
||||
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
<h3 id="pqc">
|
||||
|
||||
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Yes.</p>
|
||||
<p>No, not yet.</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>
|
||||
<p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
|
||||
which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
|
||||
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
|
||||
in collaboration with other OpenPGP implementers.</p>
|
||||
|
||||
<h3 id="how-can-i-manually-check-encryption-information">
|
||||
|
||||
|
||||
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
|
||||
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
|
||||
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="importkey">
|
||||
|
||||
|
||||
@@ -50,9 +50,10 @@
|
||||
<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="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
|
||||
<li><a href="#pfs">¿Soporta Delta Chat Perfect Forward Secrecy?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
|
||||
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</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>
|
||||
@@ -966,24 +967,25 @@ even if the message was not end-to-end encrypted.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Delta Chat protege la mayoría de los metadatos de los mensajes al colocar la siguiente información en la parte cifrada de extremo a extremo de los mensajes:</p>
|
||||
<p>Unlike most other messengers,
|
||||
Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
|
||||
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
|
||||
|
||||
<p>E-mail Servers can therefore only see</p>
|
||||
|
||||
<ul>
|
||||
<li>Subject line</li>
|
||||
<li>Group avatar and name</li>
|
||||
<li>MDN (read receipt) requests (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li>
|
||||
<li>Disappearing message timer (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li>
|
||||
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li>
|
||||
<li><code class="language-plaintext highlighter-rouge">Secure-Join</code> header containing secure join commands</li>
|
||||
<li>Notification about enabling location streaming</li>
|
||||
<li>WebRTC room URL</li>
|
||||
<li>
|
||||
<p>the message date,</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>sender and receiver addresses</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>and message size.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Los servidores de correo electrónico no obtienen acceso a estos metadatos protegidos
|
||||
pero sí ven la fecha del mensaje así como el tamaño del mensaje,
|
||||
y, lo que es más importante, las direcciones del remitente y del destinatario.
|
||||
Los servidores de correo electrónico necesitan direcciones de destinatarios para enrutar y
|
||||
entregar mensajes a los dispositivos del destinatario.</p>
|
||||
<p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
|
||||
|
||||
<h3 id="device-seizure">
|
||||
|
||||
@@ -995,24 +997,34 @@ entregar mensajes a los dispositivos del destinatario.</p>
|
||||
|
||||
<p>Both for protecting against metadata-collecting e-mail servers
|
||||
as well as against the threat of device seizure
|
||||
we recommend to use a <a href="https://delta.chat/chatmail">chatmail server</a>
|
||||
to create pseudonymous temporary profiles through QR-code scans.
|
||||
we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
|
||||
to create chat profiles using random e-mail addresses for transport.
|
||||
Note that Delta Chat apps on all platforms support multiple profiles
|
||||
so you can easily use situation-specific profiles next to your “main” profile
|
||||
with the knowledge that all their data, along with all metadata, will be deleted.
|
||||
Moreover, if a device is seized then contacts using temporary profiles
|
||||
can not be identified easily, as compared to messengers which reveal
|
||||
phone numbers in chat groups which in turn are often associated with legal identities.</p>
|
||||
Moreover, if a device is seized then chat contacts using short-lived profiles
|
||||
can not be identified easily.</p>
|
||||
|
||||
<h3 id="cómo-puedo-verificar-la-información-de-cifrado">
|
||||
<h3 id="sealedsender">
|
||||
|
||||
|
||||
¿Cómo puedo verificar la información de cifrado? <a href="#cómo-puedo-verificar-la-información-de-cifrado" class="anchor"></a>
|
||||
Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<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>
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
|
||||
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
|
||||
It is particularly important because the Signal server knows the mobile number of each account,
|
||||
which is usually associated with a passport identity.</p>
|
||||
|
||||
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
|
||||
do not ask for any private data (including no phone numbers),
|
||||
it might still be worthwhile to protect relational metadata between addresses.
|
||||
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
|
||||
but an implementation has not been agreed as a priority yet.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
@@ -1025,32 +1037,45 @@ phone numbers in chat groups which in turn are often associated with legal ident
|
||||
<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,
|
||||
This means that if your 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>
|
||||
they will be able to decrypt and read them using the leaked decryption key.
|
||||
Note that Forward Secrecy only increases security if you delete messages.
|
||||
Otherwise, someone obtaining your decryption keys
|
||||
is typically also able to get all your non-deleted messages
|
||||
and doesn’t even need to decrypt any previously collected messages.</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>
|
||||
<p>We designed a Forward Secrecy approach that withstood
|
||||
initial examination from some cryptographers and implementation experts
|
||||
but is pending a more formal write up
|
||||
to ascertain it reliably works in federated messaging and with multi-device usage,
|
||||
before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
|
||||
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
|
||||
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
<h3 id="pqc">
|
||||
|
||||
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Yes.</p>
|
||||
<p>No, not yet.</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>
|
||||
<p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
|
||||
which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
|
||||
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
|
||||
in collaboration with other OpenPGP implementers.</p>
|
||||
|
||||
<h3 id="how-can-i-manually-check-encryption-information">
|
||||
|
||||
|
||||
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<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="importkey">
|
||||
|
||||
|
||||
@@ -50,9 +50,10 @@
|
||||
<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="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
|
||||
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
|
||||
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</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>
|
||||
@@ -951,25 +952,25 @@ even if the message was not end-to-end encrypted.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Delta Chat protects most message metadata by putting the following information
|
||||
into the end-to-end encrypted part of messages:</p>
|
||||
<p>Unlike most other messengers,
|
||||
Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
|
||||
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
|
||||
|
||||
<p>E-mail Servers can therefore only see</p>
|
||||
|
||||
<ul>
|
||||
<li>Subject line</li>
|
||||
<li>Group avatar and name</li>
|
||||
<li>MDN (read receipt) requests (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li>
|
||||
<li>Disappearing message timer (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li>
|
||||
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li>
|
||||
<li><code class="language-plaintext highlighter-rouge">Secure-Join</code> header containing secure join commands</li>
|
||||
<li>Notification about enabling location streaming</li>
|
||||
<li>WebRTC room URL</li>
|
||||
<li>
|
||||
<p>the message date,</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>sender and receiver addresses</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>and message size.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>E-Mail servers do not get access to this protected metadata
|
||||
but they do see the message date as well as the message size,
|
||||
and, more importantly, the sender and receiver addresses.
|
||||
E-mail servers need receiver addresses to route and
|
||||
deliver messages to recipient’s devices.</p>
|
||||
<p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
|
||||
|
||||
<h3 id="device-seizure">
|
||||
|
||||
@@ -981,28 +982,34 @@ deliver messages to recipient’s devices.</p>
|
||||
|
||||
<p>Both for protecting against metadata-collecting e-mail servers
|
||||
as well as against the threat of device seizure
|
||||
we recommend to use a <a href="https://delta.chat/chatmail">chatmail server</a>
|
||||
to create pseudonymous temporary profiles through QR-code scans.
|
||||
we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
|
||||
to create chat profiles using random e-mail addresses for transport.
|
||||
Note that Delta Chat apps on all platforms support multiple profiles
|
||||
so you can easily use situation-specific profiles next to your “main” profile
|
||||
with the knowledge that all their data, along with all metadata, will be deleted.
|
||||
Moreover, if a device is seized then contacts using temporary profiles
|
||||
can not be identified easily, as compared to messengers which reveal
|
||||
phone numbers in chat groups which in turn are often associated with legal identities.</p>
|
||||
Moreover, if a device is seized then chat contacts using short-lived profiles
|
||||
can not be identified easily.</p>
|
||||
|
||||
<h3 id="how-can-i-check-encryption-information">
|
||||
<h3 id="sealedsender">
|
||||
|
||||
|
||||
How can i check encryption information? <a href="#how-can-i-check-encryption-information" class="anchor"></a>
|
||||
Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
|
||||
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
|
||||
Delta Chat shows two fingerprints there.
|
||||
If the same fingerprints appear on your own and your contact’s device,
|
||||
the connection is safe.</p>
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
|
||||
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
|
||||
It is particularly important because the Signal server knows the mobile number of each account,
|
||||
which is usually associated with a passport identity.</p>
|
||||
|
||||
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
|
||||
do not ask for any private data (including no phone numbers),
|
||||
it might still be worthwhile to protect relational metadata between addresses.
|
||||
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
|
||||
but an implementation has not been agreed as a priority yet.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
@@ -1015,32 +1022,49 @@ the connection is safe.</p>
|
||||
<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,
|
||||
This means that if your 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>
|
||||
they will be able to decrypt and read them using the leaked decryption key.
|
||||
Note that Forward Secrecy only increases security if you delete messages.
|
||||
Otherwise, someone obtaining your decryption keys
|
||||
is typically also able to get all your non-deleted messages
|
||||
and doesn’t even need to decrypt any previously collected messages.</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>
|
||||
<p>We designed a Forward Secrecy approach that withstood
|
||||
initial examination from some cryptographers and implementation experts
|
||||
but is pending a more formal write up
|
||||
to ascertain it reliably works in federated messaging and with multi-device usage,
|
||||
before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
|
||||
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
|
||||
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
<h3 id="pqc">
|
||||
|
||||
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Oui.</p>
|
||||
<p>No, not yet.</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>
|
||||
<p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
|
||||
which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
|
||||
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
|
||||
in collaboration with other OpenPGP implementers.</p>
|
||||
|
||||
<h3 id="how-can-i-manually-check-encryption-information">
|
||||
|
||||
|
||||
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
|
||||
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
|
||||
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="importkey">
|
||||
|
||||
|
||||
@@ -50,9 +50,10 @@
|
||||
<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="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
|
||||
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
|
||||
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</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>
|
||||
@@ -977,25 +978,25 @@ even if the message was not end-to-end encrypted.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Delta Chat protects most message metadata by putting the following information
|
||||
into the end-to-end encrypted part of messages:</p>
|
||||
<p>Unlike most other messengers,
|
||||
Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
|
||||
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
|
||||
|
||||
<p>E-mail Servers can therefore only see</p>
|
||||
|
||||
<ul>
|
||||
<li>Subject line</li>
|
||||
<li>Group avatar and name</li>
|
||||
<li>MDN (read receipt) requests (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li>
|
||||
<li>Disappearing message timer (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li>
|
||||
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li>
|
||||
<li><code class="language-plaintext highlighter-rouge">Secure-Join</code> header containing secure join commands</li>
|
||||
<li>Notification about enabling location streaming</li>
|
||||
<li>WebRTC room URL</li>
|
||||
<li>
|
||||
<p>the message date,</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>sender and receiver addresses</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>and message size.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>E-Mail servers do not get access to this protected metadata
|
||||
but they do see the message date as well as the message size,
|
||||
and, more importantly, the sender and receiver addresses.
|
||||
E-mail servers need receiver addresses to route and
|
||||
deliver messages to recipient’s devices.</p>
|
||||
<p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
|
||||
|
||||
<h3 id="device-seizure">
|
||||
|
||||
@@ -1007,28 +1008,34 @@ deliver messages to recipient’s devices.</p>
|
||||
|
||||
<p>Both for protecting against metadata-collecting e-mail servers
|
||||
as well as against the threat of device seizure
|
||||
we recommend to use a <a href="https://delta.chat/chatmail">chatmail server</a>
|
||||
to create pseudonymous temporary profiles through QR-code scans.
|
||||
we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
|
||||
to create chat profiles using random e-mail addresses for transport.
|
||||
Note that Delta Chat apps on all platforms support multiple profiles
|
||||
so you can easily use situation-specific profiles next to your “main” profile
|
||||
with the knowledge that all their data, along with all metadata, will be deleted.
|
||||
Moreover, if a device is seized then contacts using temporary profiles
|
||||
can not be identified easily, as compared to messengers which reveal
|
||||
phone numbers in chat groups which in turn are often associated with legal identities.</p>
|
||||
Moreover, if a device is seized then chat contacts using short-lived profiles
|
||||
can not be identified easily.</p>
|
||||
|
||||
<h3 id="how-can-i-check-encryption-information">
|
||||
<h3 id="sealedsender">
|
||||
|
||||
|
||||
How can i check encryption information? <a href="#how-can-i-check-encryption-information" class="anchor"></a>
|
||||
Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
|
||||
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
|
||||
Delta Chat shows two fingerprints there.
|
||||
If the same fingerprints appear on your own and your contact’s device,
|
||||
the connection is safe.</p>
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
|
||||
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
|
||||
It is particularly important because the Signal server knows the mobile number of each account,
|
||||
which is usually associated with a passport identity.</p>
|
||||
|
||||
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
|
||||
do not ask for any private data (including no phone numbers),
|
||||
it might still be worthwhile to protect relational metadata between addresses.
|
||||
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
|
||||
but an implementation has not been agreed as a priority yet.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
@@ -1041,32 +1048,49 @@ the connection is safe.</p>
|
||||
<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,
|
||||
This means that if your 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>
|
||||
they will be able to decrypt and read them using the leaked decryption key.
|
||||
Note that Forward Secrecy only increases security if you delete messages.
|
||||
Otherwise, someone obtaining your decryption keys
|
||||
is typically also able to get all your non-deleted messages
|
||||
and doesn’t even need to decrypt any previously collected messages.</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>
|
||||
<p>We designed a Forward Secrecy approach that withstood
|
||||
initial examination from some cryptographers and implementation experts
|
||||
but is pending a more formal write up
|
||||
to ascertain it reliably works in federated messaging and with multi-device usage,
|
||||
before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
|
||||
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
|
||||
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
<h3 id="pqc">
|
||||
|
||||
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Yes.</p>
|
||||
<p>No, not yet.</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>
|
||||
<p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
|
||||
which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
|
||||
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
|
||||
in collaboration with other OpenPGP implementers.</p>
|
||||
|
||||
<h3 id="how-can-i-manually-check-encryption-information">
|
||||
|
||||
|
||||
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
|
||||
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
|
||||
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="importkey">
|
||||
|
||||
|
||||
+133
-109
@@ -40,19 +40,20 @@
|
||||
<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="#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="#posso-ancora-ricevere-o-inviare-mails-senza-la-crittografia-end-to-end">Posso ancora ricevere o inviare mails senza la crittografia end-to-end?</a></li>
|
||||
<li><a href="#howtoe2ee">Come posso stabilire una chat con un nuovo contatto?</a></li>
|
||||
<li><a href="#e2eeguarantee">Cosa significa il segno di spunta verde nel profilo di un contatto?</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-alternatives">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</a></li>
|
||||
<li><a href="#openpgp-alternatives">Avete considerato l’utilizzo di alternative a OpenPGP per la crittografia end-to-end?</a></li>
|
||||
<li><a href="#delta-chat-è-vulnerabile-agli-efail">Delta Chat è vulnerabile agli EFAIL?</a></li>
|
||||
<li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
|
||||
<li><a href="#tls">I messaggi contrassegnati dall’icona della posta sono esposti su 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="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
|
||||
<li><a href="#pfs">Delta Chat supporta Perfect Forward Secrecy?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
|
||||
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</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>
|
||||
@@ -731,26 +732,26 @@ Benvenuti nella potenza del sistema interoperabile e massiccio di chatmail ed e-
|
||||
|
||||
</h3>
|
||||
|
||||
<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>Delta Chat utilizza un <a href="#openpgp-secure">sottoinsieme sicuro dello standard OpenPGP</a>
|
||||
per fornire la crittografia end-to-end automatica utilizzando questi protocolli:</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>
|
||||
per scambiare informazioni sulla configurazione della crittografia tramite la scansione del codice QR o i “link di invito”.</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>
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> viene utilizzato per stabilire
|
||||
automaticamente la crittografia end-to-end tra i contatti e tutti i membri di una chat di gruppo.</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
|
||||
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Condivisione di un contatto con una
|
||||
chat</a>
|
||||
enables receivers to use end-to-end encryption with the contact.</p>
|
||||
consente ai destinatari di utilizzare la crittografia end-to-end con il contatto.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
|
||||
<p>Delta Chat non esegue query, pubblica o interagisce con alcun server di chiavi OpenPGP.</p>
|
||||
|
||||
<h3 id="whene2e">
|
||||
|
||||
@@ -760,37 +761,37 @@ enables receivers to use end-to-end encryption with the contact.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<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>
|
||||
<p>Tutti i messaggi in Delta Chat sono <strong>crittografati end-to-end per impostazione predefinita</strong>.
|
||||
Dalla serie di rilasci della Versione 2 di Delta Chat (Luglio 2025)
|
||||
non ci sono più lucchetti o marcatori simili, sui messaggi crittografati end-to-end.</p>
|
||||
|
||||
<h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
|
||||
<h3 id="posso-ancora-ricevere-o-inviare-mails-senza-la-crittografia-end-to-end">
|
||||
|
||||
|
||||
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>
|
||||
Posso ancora ricevere o inviare mails senza la crittografia end-to-end? <a href="#posso-ancora-ricevere-o-inviare-mails-senza-la-crittografia-end-to-end" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<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 si utilizzano i <a href="https://chatmail.at/relays">relays di chatmail</a>,
|
||||
è impossibile ricevere o inviare messaggi senza la crittografia end-to-end.</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
|
||||
<p>Se invece si crea un profilo utilizzando un server di posta elettronica classico,
|
||||
è possibile inviare e ricevere messaggi senza crittografia end-to-end.
|
||||
I messaggi privi di crittografia end-to-end sono contrassegnati da un’icona e-mail<br />
|
||||
<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>
|
||||
Come posso stabilire una chat con un nuovo contatto? <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>
|
||||
<p>È possibile inviare un link di invito attraverso un’altra chat privata,
|
||||
mostrare un codice QR di invito quando si è vicini o in una videochiamata,
|
||||
o fare clic su un “contatto” condiviso in una chat.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
@@ -799,40 +800,40 @@ tocca il titolo del gruppo di chat per vedere l’elenco dei membri,
|
||||
e seleziona “Codice QR di Invito”.</p>
|
||||
</li>
|
||||
<li>
|
||||
<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>
|
||||
<p>Per <strong>inviti diretti alla chat 1:1</strong>,<br />
|
||||
toccare 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>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<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>Chiedere al partner di chat di scansionare l’immagine QR
|
||||
con la propria app Delta Chat,
|
||||
oppure cliccare su “Copia” o “Condividi” per creare un link di invito
|
||||
e condividerlo con il partner di chat.</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>
|
||||
<p>Ora aspettate che <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">la crittografia end-to-end venga stabilita</a>.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>If both sides are online, they will soon see a (group or direct) chat
|
||||
and can start messaging securely.</p>
|
||||
<p>Se entrambe le parti sono online, vedranno presto una chat (di gruppo o diretta)
|
||||
e potranno iniziare a messaggiare in modo sicuro.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>If one side is offline or in bad network,
|
||||
the ability to chat is delayed until connectivity is restored.</p>
|
||||
<p>Se una delle due parti è offline o con rete scadente,
|
||||
la possibilità di chattare viene ritardata fino al ripristino della connettività.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<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>
|
||||
<p>Congratulazioni!
|
||||
Ora utilizzerai automaticamente la crittografia end-to-end
|
||||
con questo contatto.
|
||||
Se vi aggiungete a gruppi di chat,
|
||||
la crittografia end-to-end sarà stabilita tra tutti i membri.</p>
|
||||
|
||||
<h3 id="e2eeguarantee">
|
||||
|
||||
|
||||
What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
Cosa significa il segno di spunta verde nel profilo di un contatto? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -876,9 +877,9 @@ e metadati degli allegati come i nomi dei file.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<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>Sì, Delta Chat utilizza un sottoinsieme sicuro di OpenPGP
|
||||
che richiede che l’intero messaggio sia correttamente crittografato e firmato.
|
||||
Ad esempio, le “Firme staccate” non sono considerate sicure.</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).
|
||||
@@ -896,7 +897,7 @@ per migliorare ulteriormente le caratteristiche di sicurezza implementando il
|
||||
<h3 id="openpgp-alternatives">
|
||||
|
||||
|
||||
Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
Avete considerato l’utilizzo di alternative a OpenPGP per la crittografia end-to-end? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -939,15 +940,15 @@ come definito dalla specifica Autocrypt Level 1.</p>
|
||||
<h3 id="tls">
|
||||
|
||||
|
||||
Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
|
||||
I messaggi contrassegnati dall’icona della posta sono esposti su Internet? <a href="#tls" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<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>Se inviate o ricevete messaggi e-mail senza crittografia end-to-end (utilizzando un server e-mail classico),
|
||||
sono comunque protetti dalle compagnie telefoniche o via cavo che non possono leggere o modificare i vostri messaggi e-mail.
|
||||
Ma sia il vostro provider e-mail che quello del destinatario
|
||||
possono leggere, analizzare o modificare i vostri messaggi, compresi gli allegati.</p>
|
||||
|
||||
<p>Delta Chat per impostazione predefinita utilizza
|
||||
<a href="https://en.wikipedia.org/wiki/Transport_Layer_Security">Crittografia TLS</a> rigorosa
|
||||
@@ -968,25 +969,25 @@ anche se il messaggio non sarà crittografato end-to-end.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Delta Chat protegge la maggior parte dei metadati dei messaggi inserendo le seguenti informazioni
|
||||
nella parte crittografata end-to-end dei messaggi:</p>
|
||||
<p>Unlike most other messengers,
|
||||
Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
|
||||
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
|
||||
|
||||
<p>E-mail Servers can therefore only see</p>
|
||||
|
||||
<ul>
|
||||
<li>Linea oggetto</li>
|
||||
<li>Avatar e nome del gruppo</li>
|
||||
<li>Richieste MDN (conferma di lettura) (“Chat-Disposition-Notification-To”)</li>
|
||||
<li>Temporizzatore dei messaggi che scompaiono (“Ephemeral-Timer”)</li>
|
||||
<li>“Membro del gruppo chat rimosso”, “Membro del gruppo chat aggiunto”.</li>
|
||||
<li>Intestazione “Secure-Join” contenente comandi di join sicuri</li>
|
||||
<li>Notifica sull’attivazione dello streaming della posizione</li>
|
||||
<li>URL della stanza WebRTC</li>
|
||||
<li>
|
||||
<p>the message date,</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>sender and receiver addresses</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>and message size.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>I server E-Mail non hanno accesso a questi metadati protetti
|
||||
ma vedono la data del messaggio e la dimensione del messaggio,
|
||||
e, cosa ancora più importante, gli indirizzi del mittente e del destinatario.
|
||||
I server E-Mail necessitano di indirizzi di destinatari per instradare e
|
||||
consegnare messaggi ai dispositivi del destinatario.</p>
|
||||
<p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
|
||||
|
||||
<h3 id="device-seizure">
|
||||
|
||||
@@ -996,30 +997,36 @@ consegnare messaggi ai dispositivi del destinatario.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Entrambi per la protezione dai server e-mail che raccolgono metadati
|
||||
nonché contro il pericolo di sequestro del dispositivo
|
||||
consigliamo di utilizzare un’<a href="https://delta.chat/serverguide">istanza del server e-mail</a> ottimizzata per Delta Chat
|
||||
per creare profili temporanei pseudonimi tramite scansioni di codici QR.
|
||||
Tieni presente che le app Delta Chat su tutte le piattaforme supportano più profili
|
||||
in questo modo puoi utilizzare facilmente profili “1 settimana” o “1 mese” specifici per azioni accanto al tuo profilo “principale”.
|
||||
con la consapevolezza che tutti i dati temporanei del profilo, insieme a tutti i metadati, verranno cancellati.
|
||||
Inoltre, se un dispositivo viene sequestrato, i contatti utilizzano profili e-mail temporanei
|
||||
non possono essere identificati facilmente, rispetto ai messaggeri che rivelano
|
||||
numeri di telefono nei gruppi di chat che a loro volta sono spesso associati a identità legali.</p>
|
||||
<p>Both for protecting against metadata-collecting e-mail servers
|
||||
as well as against the threat of device seizure
|
||||
we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
|
||||
to create chat profiles using random e-mail addresses for transport.
|
||||
Note that Delta Chat apps on all platforms support multiple profiles
|
||||
so you can easily use situation-specific profiles next to your “main” profile
|
||||
with the knowledge that all their data, along with all metadata, will be deleted.
|
||||
Moreover, if a device is seized then chat contacts using short-lived profiles
|
||||
can not be identified easily.</p>
|
||||
|
||||
<h3 id="come-posso-verificare-le-informazioni-di-crittografia">
|
||||
<h3 id="sealedsender">
|
||||
|
||||
|
||||
Come posso verificare le informazioni di crittografia? <a href="#come-posso-verificare-le-informazioni-di-crittografia" class="anchor"></a>
|
||||
Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>È possibile verificare manualmente lo stato della crittografia end-to-end nella finestra di dialogo “Crittografia”.
|
||||
(profilo utente su Android/iOS o clic con il pulsante destro del mouse sull’elemento dell’elenco chat di un utente sul desktop).
|
||||
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>
|
||||
<p>No, non ancora.</p>
|
||||
|
||||
<p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
|
||||
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
|
||||
It is particularly important because the Signal server knows the mobile number of each account,
|
||||
which is usually associated with a passport identity.</p>
|
||||
|
||||
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
|
||||
do not ask for any private data (including no phone numbers),
|
||||
it might still be worthwhile to protect relational metadata between addresses.
|
||||
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
|
||||
but an implementation has not been agreed as a priority yet.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
@@ -1029,35 +1036,52 @@ la connessione è sicura.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>No, not yet.</p>
|
||||
<p>No, non ancora.</p>
|
||||
|
||||
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
|
||||
This means that if your Delta Chat private decryption key is leaked,
|
||||
This means that if your 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>
|
||||
they will be able to decrypt and read them using the leaked decryption key.
|
||||
Note that Forward Secrecy only increases security if you delete messages.
|
||||
Otherwise, someone obtaining your decryption keys
|
||||
is typically also able to get all your non-deleted messages
|
||||
and doesn’t even need to decrypt any previously collected messages.</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>
|
||||
<p>We designed a Forward Secrecy approach that withstood
|
||||
initial examination from some cryptographers and implementation experts
|
||||
but is pending a more formal write up
|
||||
to ascertain it reliably works in federated messaging and with multi-device usage,
|
||||
before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
|
||||
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
|
||||
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
<h3 id="pqc">
|
||||
|
||||
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Sì.</p>
|
||||
<p>No, non ancora.</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>
|
||||
<p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
|
||||
which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
|
||||
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
|
||||
in collaboration with other OpenPGP implementers.</p>
|
||||
|
||||
<h3 id="how-can-i-manually-check-encryption-information">
|
||||
|
||||
|
||||
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>È possibile verificare manualmente lo stato della crittografia end-to-end nella finestra di dialogo “Crittografia”.
|
||||
(profilo utente su Android/iOS o clic con il pulsante destro del mouse sull’elemento dell’elenco chat di un utente sul desktop).
|
||||
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="importkey">
|
||||
|
||||
@@ -1483,10 +1507,10 @@ 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>
|
||||
<p>Nota:
|
||||
La modifica degli indirizzi e-mail è temporaneamente disabilitata
|
||||
a causa delle modifiche in corso al nucleo di DeltaChat.
|
||||
Dovrebbe essere nuovamente disponibile tra qualche mese.</p>
|
||||
|
||||
<ol>
|
||||
<li>
|
||||
|
||||
@@ -50,9 +50,10 @@
|
||||
<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="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
|
||||
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
|
||||
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</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>
|
||||
@@ -970,25 +971,25 @@ even if the message was not end-to-end encrypted.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Delta Chat protects most message metadata by putting the following information
|
||||
into the end-to-end encrypted part of messages:</p>
|
||||
<p>Unlike most other messengers,
|
||||
Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
|
||||
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
|
||||
|
||||
<p>E-mail Servers can therefore only see</p>
|
||||
|
||||
<ul>
|
||||
<li>Subject line</li>
|
||||
<li>Group avatar and name</li>
|
||||
<li>MDN (read receipt) requests (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li>
|
||||
<li>Disappearing message timer (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li>
|
||||
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li>
|
||||
<li><code class="language-plaintext highlighter-rouge">Secure-Join</code> header containing secure join commands</li>
|
||||
<li>Notification about enabling location streaming</li>
|
||||
<li>WebRTC room URL</li>
|
||||
<li>
|
||||
<p>the message date,</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>sender and receiver addresses</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>and message size.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>E-Mail servers do not get access to this protected metadata
|
||||
but they do see the message date as well as the message size,
|
||||
and, more importantly, the sender and receiver addresses.
|
||||
E-mail servers need receiver addresses to route and
|
||||
deliver messages to recipient’s devices.</p>
|
||||
<p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
|
||||
|
||||
<h3 id="device-seizure">
|
||||
|
||||
@@ -1000,28 +1001,34 @@ deliver messages to recipient’s devices.</p>
|
||||
|
||||
<p>Both for protecting against metadata-collecting e-mail servers
|
||||
as well as against the threat of device seizure
|
||||
we recommend to use a <a href="https://delta.chat/chatmail">chatmail server</a>
|
||||
to create pseudonymous temporary profiles through QR-code scans.
|
||||
we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
|
||||
to create chat profiles using random e-mail addresses for transport.
|
||||
Note that Delta Chat apps on all platforms support multiple profiles
|
||||
so you can easily use situation-specific profiles next to your “main” profile
|
||||
with the knowledge that all their data, along with all metadata, will be deleted.
|
||||
Moreover, if a device is seized then contacts using temporary profiles
|
||||
can not be identified easily, as compared to messengers which reveal
|
||||
phone numbers in chat groups which in turn are often associated with legal identities.</p>
|
||||
Moreover, if a device is seized then chat contacts using short-lived profiles
|
||||
can not be identified easily.</p>
|
||||
|
||||
<h3 id="how-can-i-check-encryption-information">
|
||||
<h3 id="sealedsender">
|
||||
|
||||
|
||||
How can i check encryption information? <a href="#how-can-i-check-encryption-information" class="anchor"></a>
|
||||
Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
|
||||
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
|
||||
Delta Chat shows two fingerprints there.
|
||||
If the same fingerprints appear on your own and your contact’s device,
|
||||
the connection is safe.</p>
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
|
||||
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
|
||||
It is particularly important because the Signal server knows the mobile number of each account,
|
||||
which is usually associated with a passport identity.</p>
|
||||
|
||||
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
|
||||
do not ask for any private data (including no phone numbers),
|
||||
it might still be worthwhile to protect relational metadata between addresses.
|
||||
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
|
||||
but an implementation has not been agreed as a priority yet.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
@@ -1034,32 +1041,49 @@ the connection is safe.</p>
|
||||
<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,
|
||||
This means that if your 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>
|
||||
they will be able to decrypt and read them using the leaked decryption key.
|
||||
Note that Forward Secrecy only increases security if you delete messages.
|
||||
Otherwise, someone obtaining your decryption keys
|
||||
is typically also able to get all your non-deleted messages
|
||||
and doesn’t even need to decrypt any previously collected messages.</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>
|
||||
<p>We designed a Forward Secrecy approach that withstood
|
||||
initial examination from some cryptographers and implementation experts
|
||||
but is pending a more formal write up
|
||||
to ascertain it reliably works in federated messaging and with multi-device usage,
|
||||
before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
|
||||
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
|
||||
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
<h3 id="pqc">
|
||||
|
||||
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Yes.</p>
|
||||
<p>No, not yet.</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>
|
||||
<p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
|
||||
which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
|
||||
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
|
||||
in collaboration with other OpenPGP implementers.</p>
|
||||
|
||||
<h3 id="how-can-i-manually-check-encryption-information">
|
||||
|
||||
|
||||
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
|
||||
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
|
||||
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="importkey">
|
||||
|
||||
|
||||
@@ -40,19 +40,20 @@
|
||||
<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="#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-nadal-mogę-odbierać-lub-wysyłać-wiadomości-bez-szyfrowania-end-to-end">Czy nadal mogę odbierać lub wysyłać wiadomości bez szyfrowania end-to-end?</a></li>
|
||||
<li><a href="#howtoe2ee">Jak mogę nawiązać czat z nowym kontaktem?</a></li>
|
||||
<li><a href="#e2eeguarantee">Co oznacza zielony znacznik wyboru w profilu kontaktu?</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">Did you consider using alternatives to OpenPGP for end-to-end-encryption?</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="#czy-delta-chat-jest-podatny-na-efail">Czy Delta Chat jest podatny na EFAIL?</a></li>
|
||||
<li><a href="#tls">Are messages marked with the mail icon exposed on the Internet?</a></li>
|
||||
<li><a href="#tls">Czy wiadomości oznaczone ikoną poczty są widoczne w internecie?</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="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
|
||||
<li><a href="#pfs">Czy Delta Chat obsługuje funkcję Perfect Forward Secrecy?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
|
||||
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</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>
|
||||
@@ -601,26 +602,21 @@ nadal będziesz mógł pisać, ale nie będziesz już powiadamiany o żadnych no
|
||||
|
||||
</h3>
|
||||
|
||||
<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>Delta Chat wykorzystuje <a href="#openpgp-secure">bezpieczny podzbiór standardu OpenPGP</a> do automatycznego szyfrowania typu end-to-end za pomocą następujących protokołów:</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>
|
||||
<p><a href="https://securejoin.delta.chat/en/latest/new.html">Secure-Join</a> do wymiany informacji o konfiguracji szyfrowania poprzez skanowanie kodów QR lub „linki zaproszeń”.</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>
|
||||
<p><a href="https://autocrypt.org">Autocrypt</a> służy do automatycznego ustanawiania szyfrowania typu end-to-end między kontaktami a wszystkimi członkami czatu grupowego.</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>
|
||||
<p><a href="https://github.com/chatmail/core/blob/main/spec.md#attaching-a-contact-to-a-message">Udostępnienie kontaktu na czacie</a> umożliwia odbiorcom korzystanie z szyfrowania typu end-to-end z tym kontaktem.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Delta Chat does not query, publish or interact with any OpenPGP key servers.</p>
|
||||
<p>Delta Chat nie wysyła zapytań, nie publikuje ani nie wchodzi w interakcję z żadnymi serwerami kluczy OpenPGP.</p>
|
||||
|
||||
<h3 id="whene2e">
|
||||
|
||||
@@ -630,91 +626,63 @@ enables receivers to use end-to-end encryption with the contact.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<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>
|
||||
<p>Wszystkie wiadomości w Delta Chat są <strong>domyślnie szyfrowane metodą end-to-end</strong>. Od wydania Delta Chat w wersji 2 (lipiec 2025 r.) nie ma już blokad ani podobnych znaczników na wiadomościach szyfrowanych metodą end-to-end.</p>
|
||||
|
||||
<h3 id="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
|
||||
<h3 id="czy-nadal-mogę-odbierać-lub-wysyłać-wiadomości-bez-szyfrowania-end-to-end">
|
||||
|
||||
|
||||
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>
|
||||
Czy nadal mogę odbierać lub wysyłać wiadomości bez szyfrowania end-to-end? <a href="#czy-nadal-mogę-odbierać-lub-wysyłać-wiadomości-bez-szyfrowania-end-to-end" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<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 korzystasz z domyślnych <a href="https://chatmail.at/relays">przekaźników chatmail</a>, odbieranie ani wysyłanie wiadomości bez szyfrowania end-to-end jest niemożliwe.</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>
|
||||
<p>Jeśli zamiast tego utworzysz profil przy użyciu klasycznego serwera poczty e-mail, możesz wysyłać i odbierać wiadomości bez szyfrowania end-to-end. Takie wiadomości bez szyfrowania end-to-end są oznaczone ikoną e-mail <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>
|
||||
Jak mogę nawiązać czat z nowym kontaktem? <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>
|
||||
<p>Możesz wysłać link z zaproszeniem za pośrednictwem innego prywatnego czatu, wyświetlić kod QR zaproszenia, gdy kontakty znajdują się obok siebie lub w rozmowie wideo, albo dotknąć „kontakt”, który został udostępniony na czacie.</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>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>
|
||||
<p>Aby <strong>wysłać zaproszenie do czatu 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>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<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>Poproś rozmówcę o zeskanowanie obrazu QR za pomocą aplikacji Delta Chat lub dotknij „Kopiuj” lub „Udostępnij”, aby utworzyć link zaproszenia i udostępnić go rozmówcy.</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>
|
||||
<p>Poczekaj, aż <a href="https://securejoin.delta.chat/en/latest/new.html#setup-contact-protocol">szyfrowanie typu end-to-end zostanie nawiązane</a>.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<p>If both sides are online, they will soon see a (group or direct) chat
|
||||
and can start messaging securely.</p>
|
||||
<p>Jeśli obie strony są online, wkrótce zobaczą czat (grupowy lub bezpośredni) i będą mogły bezpiecznie wysyłać wiadomości.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>If one side is offline or in bad network,
|
||||
the ability to chat is delayed until connectivity is restored.</p>
|
||||
<p>Jeśli jedna ze stron jest offline lub ma słaby zasięg, możliwość czatowania zostanie wstrzymana do czasu przywrócenia połączenia.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<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>
|
||||
<p>Gratulacje! Teraz będziesz automatycznie korzystać z szyfrowania typu end-to-end dla tego kontaktu. Jeśli dodacie się nawzajem do czatów grupowych, szyfrowanie typu end-to-end zostanie nawiązane między wszystkimi członkami.</p>
|
||||
|
||||
<h3 id="e2eeguarantee">
|
||||
|
||||
|
||||
What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
Co oznacza zielony znacznik wyboru w profilu kontaktu? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<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>Profil kontaktu może wyświetlać zielony znacznik wyboru <img style="vertical-align:middle; width:1.5em; margin:1px" src="../green-checkmark.png" alt="green checkmark" /> i wiersz „Zweryfikowano przez…”. 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. Osoba, która doda kontakt oznaczony zielonym znacznikiem wyboru do grupy zawierającej wyłącznie członków oznaczonych zielonym znacznikiem wyboru, staje się osobą weryfikującą. 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>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>
|
||||
|
||||
@@ -738,9 +706,7 @@ until you get to the one with whom you directly did a <a href="#howtoe2ee">QR-sc
|
||||
|
||||
</h3>
|
||||
|
||||
<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>Tak, Delta Chat korzysta z bezpiecznego podzbioru OpenPGP, który wymaga prawidłowego zaszyfrowania i podpisania całej wiadomości. Na przykład „Odłączone podpisy” nie są traktowane jako bezpieczne.</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>
|
||||
|
||||
@@ -749,7 +715,7 @@ For example, “Detached signatures” are not treated as secure.</p>
|
||||
<h3 id="openpgp-alternatives">
|
||||
|
||||
|
||||
Did you consider using alternatives to OpenPGP for end-to-end-encryption? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
Czy rozważałeś użycie alternatyw dla OpenPGP do szyfrowania typu end-to-end? <a href="#openpgp-alternatives" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -773,15 +739,12 @@ For example, “Detached signatures” are not treated as secure.</p>
|
||||
<h3 id="tls">
|
||||
|
||||
|
||||
Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
|
||||
Czy wiadomości oznaczone ikoną poczty są widoczne w internecie? <a href="#tls" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<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>Jeśli wysyłasz lub odbierasz wiadomości e-mail bez szyfrowania end-to-end (korzystając z klasycznego serwera poczty), są one nadal chronione przed operatorami komórkowymi lub kablowymi, którzy nie mogą ich czytać ani modyfikować. Jednak zarówno twoi dostawcy poczty e-mail, jak i dostawcy poczty e-mail odbiorcy mogą czytać, analizować lub modyfikować twoje wiadomości, w tym wszelkie załączniki.</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>
|
||||
|
||||
@@ -793,20 +756,23 @@ may read, analyze or modify your messages, including any attachments.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Delta Chat chroni większość metadanych wiadomości, umieszczając następujące informacje w całkowicie zaszyfrowanej części wiadomości:</p>
|
||||
<p>W przeciwieństwie do większości innych komunikatorów, aplikacje Delta Chat nie przechowują żadnych metadanych dotyczących kontaktów ani grup na serwerach, również w formie zaszyfrowanej. Zamiast tego wszystkie metadane grup są szyfrowane metodą end-to-end i przechowywane wyłącznie na urządzeniach użytkowników końcowych.</p>
|
||||
|
||||
<p>Serwery poczty e-mail widzą zatem tylko:</p>
|
||||
|
||||
<ul>
|
||||
<li>Wiersz tematu</li>
|
||||
<li>Awatar i nazwa grupy</li>
|
||||
<li>Żądania MDN (potwierdzenie odczytu) (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li>
|
||||
<li>Licznik czasu znikania wiadomości (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li>
|
||||
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li>
|
||||
<li>Nagłówek <code class="language-plaintext highlighter-rouge">Secure-Join</code> zawierający polecenia bezpiecznego łączenia</li>
|
||||
<li>Powiadomienie o włączeniu przesyłania strumieniowego lokalizacji</li>
|
||||
<li>Adres URL pokoju WebRTC</li>
|
||||
<li>
|
||||
<p>datę wysłania wiadomości,</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>adresy nadawcy i odbiorcy,</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>oraz rozmiar wiadomości.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Serwery poczty e-mail nie mają dostępu do chronionych metadanych, ale widzą datę wiadomości, jej rozmiar oraz, co ważniejsze, adresy nadawcy i odbiorcy. Serwery poczty e-mail potrzebują adresów odbiorców, aby kierować i dostarczać wiadomości do urządzeń odbiorców.</p>
|
||||
<p>Wszystkie pozostałe metadane dotyczące wiadomości, kontaktów i grup znajdują się w zaszyfrowanej metodą end-to-end części wiadomości.</p>
|
||||
|
||||
<h3 id="device-seizure">
|
||||
|
||||
@@ -816,17 +782,36 @@ may read, analyze or modify your messages, including any attachments.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Zarówno w celu ochrony przed serwerami poczty e-mail gromadzącymi metadane, jak i przed zagrożeniem przejęcia urządzenia, zalecamy użycie zoptymalizowanej <a href="https://delta.chat/pl/serverguide">instancji serwera poczty e-mail</a> Delta Chat w celu tworzenia pseudonimowych kont tymczasowych poprzez skanowanie kodów QR. Pamiętaj, że aplikacje Delta Chat na wszystkich platformach obsługują wiele kont, dzięki czemu możesz z łatwością korzystać z kont „1-tygodniowych” lub „1-miesięcznych” związanych z konkretnymi działaniami obok konta „głównego”, wiedząc, że wszystkie tymczasowe dane konta wraz ze wszystkimi metadanymi zostaną usunięte. Co więcej, jeśli urządzenie zostanie przejęte, nie będzie można łatwo zidentyfikować kontaktów korzystających z tymczasowych kont e-mail, w porównaniu z komunikatorami, które ujawniają numery telefonów w grupach czatów, które z kolei często są powiązane z tożsamością prawną.</p>
|
||||
<p>Both for protecting against metadata-collecting e-mail servers
|
||||
as well as against the threat of device seizure
|
||||
we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
|
||||
to create chat profiles using random e-mail addresses for transport.
|
||||
Note that Delta Chat apps on all platforms support multiple profiles
|
||||
so you can easily use situation-specific profiles next to your “main” profile
|
||||
with the knowledge that all their data, along with all metadata, will be deleted.
|
||||
Moreover, if a device is seized then chat contacts using short-lived profiles
|
||||
can not be identified easily.</p>
|
||||
|
||||
<h3 id="jak-mogę-sprawdzić-informacje-o-szyfrowaniu">
|
||||
<h3 id="sealedsender">
|
||||
|
||||
|
||||
Jak mogę sprawdzić informacje o szyfrowaniu? <a href="#jak-mogę-sprawdzić-informacje-o-szyfrowaniu" class="anchor"></a>
|
||||
Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<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>
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
|
||||
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
|
||||
It is particularly important because the Signal server knows the mobile number of each account,
|
||||
which is usually associated with a passport identity.</p>
|
||||
|
||||
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
|
||||
do not ask for any private data (including no phone numbers),
|
||||
it might still be worthwhile to protect relational metadata between addresses.
|
||||
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
|
||||
but an implementation has not been agreed as a priority yet.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
@@ -839,32 +824,45 @@ may read, analyze or modify your messages, including any attachments.</p>
|
||||
<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,
|
||||
This means that if your 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>
|
||||
they will be able to decrypt and read them using the leaked decryption key.
|
||||
Note that Forward Secrecy only increases security if you delete messages.
|
||||
Otherwise, someone obtaining your decryption keys
|
||||
is typically also able to get all your non-deleted messages
|
||||
and doesn’t even need to decrypt any previously collected messages.</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>
|
||||
<p>We designed a Forward Secrecy approach that withstood
|
||||
initial examination from some cryptographers and implementation experts
|
||||
but is pending a more formal write up
|
||||
to ascertain it reliably works in federated messaging and with multi-device usage,
|
||||
before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
|
||||
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
|
||||
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
<h3 id="pqc">
|
||||
|
||||
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Tak.</p>
|
||||
<p>No, not yet.</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>
|
||||
<p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
|
||||
which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
|
||||
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
|
||||
in collaboration with other OpenPGP implementers.</p>
|
||||
|
||||
<h3 id="how-can-i-manually-check-encryption-information">
|
||||
|
||||
|
||||
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<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="importkey">
|
||||
|
||||
|
||||
@@ -50,9 +50,10 @@
|
||||
<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="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
|
||||
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
|
||||
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</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>
|
||||
@@ -971,25 +972,25 @@ even if the message was not end-to-end encrypted.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Delta Chat protects most message metadata by putting the following information
|
||||
into the end-to-end encrypted part of messages:</p>
|
||||
<p>Unlike most other messengers,
|
||||
Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
|
||||
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
|
||||
|
||||
<p>E-mail Servers can therefore only see</p>
|
||||
|
||||
<ul>
|
||||
<li>Subject line</li>
|
||||
<li>Group avatar and name</li>
|
||||
<li>MDN (read receipt) requests (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li>
|
||||
<li>Disappearing message timer (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li>
|
||||
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li>
|
||||
<li><code class="language-plaintext highlighter-rouge">Secure-Join</code> header containing secure join commands</li>
|
||||
<li>Notification about enabling location streaming</li>
|
||||
<li>WebRTC room URL</li>
|
||||
<li>
|
||||
<p>the message date,</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>sender and receiver addresses</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>and message size.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>E-Mail servers do not get access to this protected metadata
|
||||
but they do see the message date as well as the message size,
|
||||
and, more importantly, the sender and receiver addresses.
|
||||
E-mail servers need receiver addresses to route and
|
||||
deliver messages to recipient’s devices.</p>
|
||||
<p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
|
||||
|
||||
<h3 id="device-seizure">
|
||||
|
||||
@@ -1001,28 +1002,34 @@ deliver messages to recipient’s devices.</p>
|
||||
|
||||
<p>Both for protecting against metadata-collecting e-mail servers
|
||||
as well as against the threat of device seizure
|
||||
we recommend to use a <a href="https://delta.chat/chatmail">chatmail server</a>
|
||||
to create pseudonymous temporary profiles through QR-code scans.
|
||||
we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
|
||||
to create chat profiles using random e-mail addresses for transport.
|
||||
Note that Delta Chat apps on all platforms support multiple profiles
|
||||
so you can easily use situation-specific profiles next to your “main” profile
|
||||
with the knowledge that all their data, along with all metadata, will be deleted.
|
||||
Moreover, if a device is seized then contacts using temporary profiles
|
||||
can not be identified easily, as compared to messengers which reveal
|
||||
phone numbers in chat groups which in turn are often associated with legal identities.</p>
|
||||
Moreover, if a device is seized then chat contacts using short-lived profiles
|
||||
can not be identified easily.</p>
|
||||
|
||||
<h3 id="how-can-i-check-encryption-information">
|
||||
<h3 id="sealedsender">
|
||||
|
||||
|
||||
How can i check encryption information? <a href="#how-can-i-check-encryption-information" class="anchor"></a>
|
||||
Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
|
||||
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
|
||||
Delta Chat shows two fingerprints there.
|
||||
If the same fingerprints appear on your own and your contact’s device,
|
||||
the connection is safe.</p>
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
|
||||
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
|
||||
It is particularly important because the Signal server knows the mobile number of each account,
|
||||
which is usually associated with a passport identity.</p>
|
||||
|
||||
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
|
||||
do not ask for any private data (including no phone numbers),
|
||||
it might still be worthwhile to protect relational metadata between addresses.
|
||||
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
|
||||
but an implementation has not been agreed as a priority yet.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
@@ -1035,32 +1042,49 @@ the connection is safe.</p>
|
||||
<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,
|
||||
This means that if your 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>
|
||||
they will be able to decrypt and read them using the leaked decryption key.
|
||||
Note that Forward Secrecy only increases security if you delete messages.
|
||||
Otherwise, someone obtaining your decryption keys
|
||||
is typically also able to get all your non-deleted messages
|
||||
and doesn’t even need to decrypt any previously collected messages.</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>
|
||||
<p>We designed a Forward Secrecy approach that withstood
|
||||
initial examination from some cryptographers and implementation experts
|
||||
but is pending a more formal write up
|
||||
to ascertain it reliably works in federated messaging and with multi-device usage,
|
||||
before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
|
||||
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
|
||||
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
<h3 id="pqc">
|
||||
|
||||
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Sim.</p>
|
||||
<p>No, not yet.</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>
|
||||
<p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
|
||||
which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
|
||||
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
|
||||
in collaboration with other OpenPGP implementers.</p>
|
||||
|
||||
<h3 id="how-can-i-manually-check-encryption-information">
|
||||
|
||||
|
||||
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
|
||||
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
|
||||
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="importkey">
|
||||
|
||||
|
||||
@@ -40,19 +40,20 @@
|
||||
<ul>
|
||||
<li><a href="#какие-стандарты-используются-для-сквозного-шифрования">Какие стандарты используются для сквозного шифрования?</a></li>
|
||||
<li><a href="#whene2e">Как узнать зашифрованы ли сообщения сквозным шифрованием?</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="#howtoe2ee">Как мне установить чат с новым контактом?</a></li>
|
||||
<li><a href="#e2eeguarantee">Что означает зеленая галочка в профиле контакта?</a></li>
|
||||
<li><a href="#зашифрованы-ли-вложения-изображения-файлы-аудио-и-т-д-сквозным-шифрованием">Зашифрованы ли вложения (изображения, файлы, аудио и т. д.) сквозным шифрованием?</a></li>
|
||||
<li><a href="#openpgp-secure">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">Are messages marked with the mail icon exposed on the Internet?</a></li>
|
||||
<li><a href="#tls">Видны ли в Интернете сообщения, отмеченные значком почты?</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="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
|
||||
<li><a href="#pfs">Поддерживает ли Delta Chat совершенную прямую секретность (Perfect forward secrecy, PFS)?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
|
||||
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</a></li>
|
||||
<li><a href="#importkey">Можно ли повторно использовать существующий секретный ключ?</a></li>
|
||||
<li><a href="#security-audits">Проходил ли Delta Chat независимую проверку на наличие уязвимостей безопасности?</a></li>
|
||||
</ul>
|
||||
@@ -750,7 +751,7 @@ 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>
|
||||
<p>Delta Chat не запрашивает, не публикует и не взаимодействует с какими-либо серверами ключей OpenPGP.</p>
|
||||
|
||||
<h3 id="whene2e">
|
||||
|
||||
@@ -764,10 +765,10 @@ enables receivers to use end-to-end encryption with the contact.</p>
|
||||
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="can-i-still-receive-or-send-mails-without-end-to-end-encryption">
|
||||
<h3 id="могу-ли-я-получать-или-отправлять-письма-без-сквозного-шифрования">
|
||||
|
||||
|
||||
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>
|
||||
Могу ли я получать или отправлять письма без сквозного шифрования? <a href="#могу-ли-я-получать-или-отправлять-письма-без-сквозного-шифрования" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -783,7 +784,7 @@ Such messages lacking end-to-end encryption are marked with an e-mail icon
|
||||
<h3 id="howtoe2ee">
|
||||
|
||||
|
||||
How can I establish a chat with a new contact? <a href="#howtoe2ee" class="anchor"></a>
|
||||
Как мне установить чат с новым контактом? <a href="#howtoe2ee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -832,7 +833,7 @@ end-to-end encryption will be established among all members.</p>
|
||||
<h3 id="e2eeguarantee">
|
||||
|
||||
|
||||
What does the green checkmark in a contact profile mean? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
Что означает зеленая галочка в профиле контакта? <a href="#e2eeguarantee" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -941,7 +942,7 @@ Delta Chat вместо этого использует реализацию Ope
|
||||
<h3 id="tls">
|
||||
|
||||
|
||||
Are messages marked with the mail icon exposed on the Internet? <a href="#tls" class="anchor"></a>
|
||||
Видны ли в Интернете сообщения, отмеченные значком почты? <a href="#tls" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
@@ -970,25 +971,25 @@ may read, analyze or modify your messages, including any attachments.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Delta Chat защищает большинство метаданных сообщений, помещая следующую информацию,
|
||||
в зашифрованную сквозным шифрованием часть сообщений:</p>
|
||||
<p>Unlike most other messengers,
|
||||
Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
|
||||
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
|
||||
|
||||
<p>E-mail Servers can therefore only see</p>
|
||||
|
||||
<ul>
|
||||
<li>Тема сообщения</li>
|
||||
<li>Аватар и название группы</li>
|
||||
<li>Запросы MDN (уведомление о прочтении) (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li>
|
||||
<li>Таймер исчезающих сообщений (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li>
|
||||
<li>Участник-группы-чата-удалён (<code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>); Участник-группы-чата-добавлен (<code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code>)</li>
|
||||
<li>Заголовок <code class="language-plaintext highlighter-rouge">Secure-Join</code>, содержащий команды безопасного соединения</li>
|
||||
<li>Уведомление о включении потоковой передачи местоположения</li>
|
||||
<li>URL-адрес комнаты WebRTC</li>
|
||||
<li>
|
||||
<p>the message date,</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>sender and receiver addresses</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>and message size.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Серверы электронной почты не получают доступ к этим защищённым метаданным,
|
||||
но они видят дату сообщения, а также его размер,
|
||||
и, что более важно, адреса отправителя и получателя.
|
||||
Серверам электронной почты нужны адреса получателей для маршрутизации и
|
||||
доставки сообщений на устройства получателей.</p>
|
||||
<p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
|
||||
|
||||
<h3 id="device-seizure">
|
||||
|
||||
@@ -998,31 +999,36 @@ may read, analyze or modify your messages, including any attachments.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Для защиты от серверов электронной почты, собирающих метаданные,
|
||||
а также от угрозы конфискации устройства,
|
||||
мы рекомендуем использовать <a href="https://delta.chat/chatmail">сервер chatmail</a>,
|
||||
для создания безымянных (псевдонимных), временных профилей через сканирование QR-кодов.
|
||||
Обратите внимание, что приложения Delta Chat на всех платформах поддерживают несколько профилей,
|
||||
так что вы можете легко использовать отдельные профили, для конкретной ситуации,
|
||||
помимо вашего “основного” профиля,
|
||||
зная, что все их данные, вместе с метаданными, будут удалены.
|
||||
Кроме того, если устройство будет конфисковано, контакты, использующие временные профили,
|
||||
не могут быть легко идентифицированы, в отличие от мессенджеров, которые раскрывают
|
||||
номера телефонов в групповых чатах, которые часто связаны с реальными личностями.</p>
|
||||
<p>Both for protecting against metadata-collecting e-mail servers
|
||||
as well as against the threat of device seizure
|
||||
we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
|
||||
to create chat profiles using random e-mail addresses for transport.
|
||||
Note that Delta Chat apps on all platforms support multiple profiles
|
||||
so you can easily use situation-specific profiles next to your “main” profile
|
||||
with the knowledge that all their data, along with all metadata, will be deleted.
|
||||
Moreover, if a device is seized then chat contacts using short-lived profiles
|
||||
can not be identified easily.</p>
|
||||
|
||||
<h3 id="как-я-могу-проверить-информацию-о-шифровании">
|
||||
<h3 id="sealedsender">
|
||||
|
||||
|
||||
Как я могу проверить информацию о шифровании? <a href="#как-я-могу-проверить-информацию-о-шифровании" class="anchor"></a>
|
||||
Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Вы можете проверить статус сквозного шифрования вручную в диалоговом окне “Шифрование”
|
||||
(профиль пользователя на Android/iOS или щелкните правой кнопкой мыши элемент списка чата пользователя в приложении для ПК).
|
||||
Delta Chat показывает там два отпечатка.
|
||||
Если на вашем устройстве и на устройстве вашего контакта показаны одинаковые отпечатки,
|
||||
соединение безопасно.</p>
|
||||
<p>Нет, пока нет.</p>
|
||||
|
||||
<p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
|
||||
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
|
||||
It is particularly important because the Signal server knows the mobile number of each account,
|
||||
which is usually associated with a passport identity.</p>
|
||||
|
||||
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
|
||||
do not ask for any private data (including no phone numbers),
|
||||
it might still be worthwhile to protect relational metadata between addresses.
|
||||
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
|
||||
but an implementation has not been agreed as a priority yet.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
@@ -1032,35 +1038,52 @@ Delta Chat показывает там два отпечатка.
|
||||
|
||||
</h3>
|
||||
|
||||
<p>No, not yet.</p>
|
||||
<p>Нет, пока нет.</p>
|
||||
|
||||
<p>Delta Chat today doesn’t support Perfect Forward Secrecy (PFS).
|
||||
This means that if your Delta Chat private decryption key is leaked,
|
||||
This means that if your 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>
|
||||
they will be able to decrypt and read them using the leaked decryption key.
|
||||
Note that Forward Secrecy only increases security if you delete messages.
|
||||
Otherwise, someone obtaining your decryption keys
|
||||
is typically also able to get all your non-deleted messages
|
||||
and doesn’t even need to decrypt any previously collected messages.</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>
|
||||
<p>We designed a Forward Secrecy approach that withstood
|
||||
initial examination from some cryptographers and implementation experts
|
||||
but is pending a more formal write up
|
||||
to ascertain it reliably works in federated messaging and with multi-device usage,
|
||||
before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
|
||||
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
|
||||
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
<h3 id="pqc">
|
||||
|
||||
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Да.</p>
|
||||
<p>Нет, пока нет.</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>
|
||||
<p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
|
||||
which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
|
||||
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
|
||||
in collaboration with other OpenPGP implementers.</p>
|
||||
|
||||
<h3 id="how-can-i-manually-check-encryption-information">
|
||||
|
||||
|
||||
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Вы можете проверить статус сквозного шифрования вручную в диалоговом окне “Шифрование”
|
||||
(профиль пользователя на Android/iOS или щелкните правой кнопкой мыши элемент списка чата пользователя в приложении для ПК).
|
||||
Delta Chat показывает там два отпечатка.
|
||||
Если на вашем устройстве и на устройстве вашего контакта показаны одинаковые отпечатки,
|
||||
соединение безопасно.</p>
|
||||
|
||||
<h3 id="importkey">
|
||||
|
||||
|
||||
@@ -50,9 +50,10 @@
|
||||
<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="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
|
||||
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
|
||||
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</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>
|
||||
@@ -974,25 +975,25 @@ even if the message was not end-to-end encrypted.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Delta Chat protects most message metadata by putting the following information
|
||||
into the end-to-end encrypted part of messages:</p>
|
||||
<p>Unlike most other messengers,
|
||||
Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
|
||||
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
|
||||
|
||||
<p>E-mail Servers can therefore only see</p>
|
||||
|
||||
<ul>
|
||||
<li>Subject line</li>
|
||||
<li>Group avatar and name</li>
|
||||
<li>MDN (read receipt) requests (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li>
|
||||
<li>Disappearing message timer (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li>
|
||||
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li>
|
||||
<li><code class="language-plaintext highlighter-rouge">Secure-Join</code> header containing secure join commands</li>
|
||||
<li>Notification about enabling location streaming</li>
|
||||
<li>WebRTC room URL</li>
|
||||
<li>
|
||||
<p>the message date,</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>sender and receiver addresses</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>and message size.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>E-Mail servers do not get access to this protected metadata
|
||||
but they do see the message date as well as the message size,
|
||||
and, more importantly, the sender and receiver addresses.
|
||||
E-mail servers need receiver addresses to route and
|
||||
deliver messages to recipient’s devices.</p>
|
||||
<p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
|
||||
|
||||
<h3 id="device-seizure">
|
||||
|
||||
@@ -1004,28 +1005,34 @@ deliver messages to recipient’s devices.</p>
|
||||
|
||||
<p>Both for protecting against metadata-collecting e-mail servers
|
||||
as well as against the threat of device seizure
|
||||
we recommend to use a <a href="https://delta.chat/chatmail">chatmail server</a>
|
||||
to create pseudonymous temporary profiles through QR-code scans.
|
||||
we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
|
||||
to create chat profiles using random e-mail addresses for transport.
|
||||
Note that Delta Chat apps on all platforms support multiple profiles
|
||||
so you can easily use situation-specific profiles next to your “main” profile
|
||||
with the knowledge that all their data, along with all metadata, will be deleted.
|
||||
Moreover, if a device is seized then contacts using temporary profiles
|
||||
can not be identified easily, as compared to messengers which reveal
|
||||
phone numbers in chat groups which in turn are often associated with legal identities.</p>
|
||||
Moreover, if a device is seized then chat contacts using short-lived profiles
|
||||
can not be identified easily.</p>
|
||||
|
||||
<h3 id="how-can-i-check-encryption-information">
|
||||
<h3 id="sealedsender">
|
||||
|
||||
|
||||
How can i check encryption information? <a href="#how-can-i-check-encryption-information" class="anchor"></a>
|
||||
Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
|
||||
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
|
||||
Delta Chat shows two fingerprints there.
|
||||
If the same fingerprints appear on your own and your contact’s device,
|
||||
the connection is safe.</p>
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
|
||||
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
|
||||
It is particularly important because the Signal server knows the mobile number of each account,
|
||||
which is usually associated with a passport identity.</p>
|
||||
|
||||
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
|
||||
do not ask for any private data (including no phone numbers),
|
||||
it might still be worthwhile to protect relational metadata between addresses.
|
||||
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
|
||||
but an implementation has not been agreed as a priority yet.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
@@ -1038,32 +1045,49 @@ the connection is safe.</p>
|
||||
<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,
|
||||
This means that if your 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>
|
||||
they will be able to decrypt and read them using the leaked decryption key.
|
||||
Note that Forward Secrecy only increases security if you delete messages.
|
||||
Otherwise, someone obtaining your decryption keys
|
||||
is typically also able to get all your non-deleted messages
|
||||
and doesn’t even need to decrypt any previously collected messages.</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>
|
||||
<p>We designed a Forward Secrecy approach that withstood
|
||||
initial examination from some cryptographers and implementation experts
|
||||
but is pending a more formal write up
|
||||
to ascertain it reliably works in federated messaging and with multi-device usage,
|
||||
before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
|
||||
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
|
||||
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
<h3 id="pqc">
|
||||
|
||||
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Yes.</p>
|
||||
<p>No, not yet.</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>
|
||||
<p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
|
||||
which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
|
||||
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
|
||||
in collaboration with other OpenPGP implementers.</p>
|
||||
|
||||
<h3 id="how-can-i-manually-check-encryption-information">
|
||||
|
||||
|
||||
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
|
||||
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
|
||||
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="importkey">
|
||||
|
||||
|
||||
@@ -50,9 +50,10 @@
|
||||
<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="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
|
||||
<li><a href="#pfs">Does Delta Chat support Perfect Forward Secrecy?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
|
||||
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</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>
|
||||
@@ -975,25 +976,25 @@ even if the message was not end-to-end encrypted.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Delta Chat protects most message metadata by putting the following information
|
||||
into the end-to-end encrypted part of messages:</p>
|
||||
<p>Unlike most other messengers,
|
||||
Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
|
||||
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
|
||||
|
||||
<p>E-mail Servers can therefore only see</p>
|
||||
|
||||
<ul>
|
||||
<li>Rresht subjekti</li>
|
||||
<li>Avatar dhe emër grupi</li>
|
||||
<li>Kërkesa MDN (dëftesë leximi) (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li>
|
||||
<li>Afatmatës mesazhesh që zhduken (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li>
|
||||
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li>
|
||||
<li>Krye <code class="language-plaintext highlighter-rouge">Secure-Join</code> që përmban urdhra për pjesëmarrje të siguruar</li>
|
||||
<li>Njoftim mbi aktivizim tregimi vendndodhjeje</li>
|
||||
<li>URL dhome WebRTC</li>
|
||||
<li>
|
||||
<p>the message date,</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>sender and receiver addresses</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>and message size.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>E-Mail servers do not get access to this protected metadata
|
||||
but they do see the message date as well as the message size,
|
||||
and, more importantly, the sender and receiver addresses.
|
||||
E-mail servers need receiver addresses to route and
|
||||
deliver messages to recipient’s devices.</p>
|
||||
<p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
|
||||
|
||||
<h3 id="device-seizure">
|
||||
|
||||
@@ -1005,28 +1006,34 @@ deliver messages to recipient’s devices.</p>
|
||||
|
||||
<p>Both for protecting against metadata-collecting e-mail servers
|
||||
as well as against the threat of device seizure
|
||||
we recommend to use a <a href="https://delta.chat/chatmail">chatmail server</a>
|
||||
to create pseudonymous temporary profiles through QR-code scans.
|
||||
we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
|
||||
to create chat profiles using random e-mail addresses for transport.
|
||||
Note that Delta Chat apps on all platforms support multiple profiles
|
||||
so you can easily use situation-specific profiles next to your “main” profile
|
||||
with the knowledge that all their data, along with all metadata, will be deleted.
|
||||
Moreover, if a device is seized then contacts using temporary profiles
|
||||
can not be identified easily, as compared to messengers which reveal
|
||||
phone numbers in chat groups which in turn are often associated with legal identities.</p>
|
||||
Moreover, if a device is seized then chat contacts using short-lived profiles
|
||||
can not be identified easily.</p>
|
||||
|
||||
<h3 id="how-can-i-check-encryption-information">
|
||||
<h3 id="sealedsender">
|
||||
|
||||
|
||||
How can i check encryption information? <a href="#how-can-i-check-encryption-information" class="anchor"></a>
|
||||
Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
|
||||
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
|
||||
Delta Chat shows two fingerprints there.
|
||||
If the same fingerprints appear on your own and your contact’s device,
|
||||
the connection is safe.</p>
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
|
||||
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
|
||||
It is particularly important because the Signal server knows the mobile number of each account,
|
||||
which is usually associated with a passport identity.</p>
|
||||
|
||||
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
|
||||
do not ask for any private data (including no phone numbers),
|
||||
it might still be worthwhile to protect relational metadata between addresses.
|
||||
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
|
||||
but an implementation has not been agreed as a priority yet.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
@@ -1039,32 +1046,49 @@ the connection is safe.</p>
|
||||
<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,
|
||||
This means that if your 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>
|
||||
they will be able to decrypt and read them using the leaked decryption key.
|
||||
Note that Forward Secrecy only increases security if you delete messages.
|
||||
Otherwise, someone obtaining your decryption keys
|
||||
is typically also able to get all your non-deleted messages
|
||||
and doesn’t even need to decrypt any previously collected messages.</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>
|
||||
<p>We designed a Forward Secrecy approach that withstood
|
||||
initial examination from some cryptographers and implementation experts
|
||||
but is pending a more formal write up
|
||||
to ascertain it reliably works in federated messaging and with multi-device usage,
|
||||
before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
|
||||
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
|
||||
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
<h3 id="pqc">
|
||||
|
||||
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Po</p>
|
||||
<p>No, not yet.</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>
|
||||
<p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
|
||||
which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
|
||||
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
|
||||
in collaboration with other OpenPGP implementers.</p>
|
||||
|
||||
<h3 id="how-can-i-manually-check-encryption-information">
|
||||
|
||||
|
||||
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>You may check the end-to-end encryption status manually in the “Encryption” dialog
|
||||
(user profile on Android/iOS or right-click a user’s chat-list item on desktop).
|
||||
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="importkey">
|
||||
|
||||
|
||||
@@ -50,9 +50,10 @@
|
||||
<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="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
|
||||
<li><a href="#pfs">Чи підтримує Delta Chat цілковиту пряму секретність (Perfect Forward Secrecy)?</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
|
||||
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</a></li>
|
||||
<li><a href="#importkey">Чи можна повторно використовувати існуючий закритий ключ?</a></li>
|
||||
<li><a href="#security-audits">Чи проходив Delta Chat незалежний аудит на наявність вразливостей у безпеці?</a></li>
|
||||
</ul>
|
||||
@@ -800,20 +801,25 @@ may read, analyze or modify your messages, including any attachments.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Delta Chat захищає більшість метаданих повідомлень, поміщаючи наступну інформацію в наскрізно зашифровану частину повідомлень:</p>
|
||||
<p>Unlike most other messengers,
|
||||
Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
|
||||
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
|
||||
|
||||
<p>E-mail Servers can therefore only see</p>
|
||||
|
||||
<ul>
|
||||
<li>Тема повідомлення</li>
|
||||
<li>Аватар та назва групи</li>
|
||||
<li>Запити MDN (підтвердження прочитання) (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li>
|
||||
<li>Таймер зникнення повідомлень (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li>
|
||||
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed-Member-Added</code>.</li>
|
||||
<li>Заголовок <code class="language-plaintext highlighter-rouge">Secure-Join</code>, що містить команди безпечного приєднання</li>
|
||||
<li>Сповіщення про увімкнення потокового передавання місцезнаходження</li>
|
||||
<li>URL-адреса кімнати WebRTC</li>
|
||||
<li>
|
||||
<p>the message date,</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>sender and receiver addresses</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>and message size.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>Поштові сервери не мають доступу до цих захищених метаданих але вони бачать дату і розмір повідомлення, і, що важливіше, адреси відправника та отримувача. Поштовим серверам потрібні адреси одержувачів, щоб маршрутизувати і доставляти повідомлення на пристрої одержувача.</p>
|
||||
<p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
|
||||
|
||||
<h3 id="device-seizure">
|
||||
|
||||
@@ -823,17 +829,36 @@ may read, analyze or modify your messages, including any attachments.</p>
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Як для захисту від поштових серверів, що збирають метадані а також для захисту від загрози вилучення пристрою ми рекомендуємо використовувати <a href="https://delta.chat/chatmail">chatmail-сервер</a> для створення псевдонімних тимчасових профілів за допомогою сканування QR-коду. Зверніть увагу, що додатки Delta Chat на всіх платформах підтримують кілька профілів тому ви можете легко використовувати ситуативні профілі поруч з вашим “основним” профілем знаючи, що всі їхні дані, разом з усіма метаданими, будуть видалені. Більше того, якщо пристрій вилучено, то контакти, які використовують тимчасові профілі не можна буде легко ідентифікувати, на відміну від месенджерів, які розкривають номери телефонів у групах чату, які, в свою чергу, часто пов’язані з юридичними особами.</p>
|
||||
<p>Both for protecting against metadata-collecting e-mail servers
|
||||
as well as against the threat of device seizure
|
||||
we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
|
||||
to create chat profiles using random e-mail addresses for transport.
|
||||
Note that Delta Chat apps on all platforms support multiple profiles
|
||||
so you can easily use situation-specific profiles next to your “main” profile
|
||||
with the knowledge that all their data, along with all metadata, will be deleted.
|
||||
Moreover, if a device is seized then chat contacts using short-lived profiles
|
||||
can not be identified easily.</p>
|
||||
|
||||
<h3 id="як-перевірити-інформацію-про-шифрування">
|
||||
<h3 id="sealedsender">
|
||||
|
||||
|
||||
Як перевірити інформацію про шифрування? <a href="#як-перевірити-інформацію-про-шифрування" class="anchor"></a>
|
||||
Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Ви можете перевірити стан наскрізного шифрування вручну в діалоговому вікні “Шифрування” (профіль користувача на Android/iOS або клацніть правою кнопкою миші на елементі списку чату користувача на робочому столі). Delta Chat показує там два відбитки. Якщо на вашому пристрої та пристрої вашого співрозмовника з’являються однакові відбитки, з’єднання безпечне.</p>
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
|
||||
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
|
||||
It is particularly important because the Signal server knows the mobile number of each account,
|
||||
which is usually associated with a passport identity.</p>
|
||||
|
||||
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
|
||||
do not ask for any private data (including no phone numbers),
|
||||
it might still be worthwhile to protect relational metadata between addresses.
|
||||
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
|
||||
but an implementation has not been agreed as a priority yet.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
@@ -846,32 +871,45 @@ may read, analyze or modify your messages, including any attachments.</p>
|
||||
<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,
|
||||
This means that if your 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>
|
||||
they will be able to decrypt and read them using the leaked decryption key.
|
||||
Note that Forward Secrecy only increases security if you delete messages.
|
||||
Otherwise, someone obtaining your decryption keys
|
||||
is typically also able to get all your non-deleted messages
|
||||
and doesn’t even need to decrypt any previously collected messages.</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>
|
||||
<p>We designed a Forward Secrecy approach that withstood
|
||||
initial examination from some cryptographers and implementation experts
|
||||
but is pending a more formal write up
|
||||
to ascertain it reliably works in federated messaging and with multi-device usage,
|
||||
before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
|
||||
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
|
||||
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
<h3 id="pqc">
|
||||
|
||||
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Так.</p>
|
||||
<p>No, not yet.</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>
|
||||
<p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
|
||||
which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
|
||||
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
|
||||
in collaboration with other OpenPGP implementers.</p>
|
||||
|
||||
<h3 id="how-can-i-manually-check-encryption-information">
|
||||
|
||||
|
||||
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Ви можете перевірити стан наскрізного шифрування вручну в діалоговому вікні “Шифрування” (профіль користувача на Android/iOS або клацніть правою кнопкою миші на елементі списку чату користувача на робочому столі). Delta Chat показує там два відбитки. Якщо на вашому пристрої та пристрої вашого співрозмовника з’являються однакові відбитки, з’єднання безпечне.</p>
|
||||
|
||||
<h3 id="importkey">
|
||||
|
||||
|
||||
@@ -50,9 +50,10 @@
|
||||
<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="#sealedsender">Does Delta Chat support “Sealed Sender”?</a></li>
|
||||
<li><a href="#pfs">Delta Chat 是否支持完美前向保密？</a></li>
|
||||
<li><a href="#will-delta-chat-support-forward-secrecy">Will Delta Chat support Forward Secrecy?</a></li>
|
||||
<li><a href="#pqc">Does Delta Chat support Post-Quantum-Cryptography?</a></li>
|
||||
<li><a href="#how-can-i-manually-check-encryption-information">How can I manually check encryption information?</a></li>
|
||||
<li><a href="#importkey">我可以重复使用现有的私钥吗？</a></li>
|
||||
<li><a href="#security-audits">Delta Chat 是否已进行独立的安全漏洞审计？</a></li>
|
||||
</ul>
|
||||
@@ -933,24 +934,25 @@ Delta Chat 的所有 TLS 处理都经过了独立的 <a href="#security-audits">
|
||||
|
||||
</h3>
|
||||
|
||||
<p>Delta Chat 通过将以下信息放入消息的端到端加密部分来保护大多数消息元数据：</p>
|
||||
<p>Unlike most other messengers,
|
||||
Delta Chat apps do not store any metadata about contacts or groups on servers, also not in encrypted form.
|
||||
Instead, all group metadata is end-to-end encrypted and stored on end-user devices, only.</p>
|
||||
|
||||
<p>E-mail Servers can therefore only see</p>
|
||||
|
||||
<ul>
|
||||
<li>主题行</li>
|
||||
<li>群组头像和名称</li>
|
||||
<li>MDN（已读回执）请求 (<code class="language-plaintext highlighter-rouge">Chat-Disposition-Notification-To</code>)</li>
|
||||
<li>阅后即焚消息计时器 (<code class="language-plaintext highlighter-rouge">Ephemeral-Timer</code>)</li>
|
||||
<li><code class="language-plaintext highlighter-rouge">Chat-Group-Member-Removed</code>, <code class="language-plaintext highlighter-rouge">Chat-Group-Member-Added</code></li>
|
||||
<li>包含安全加入命令的 <code class="language-plaintext highlighter-rouge">Secure-Join</code> 标头</li>
|
||||
<li>关于启用位置流式传输的通知</li>
|
||||
<li>WebRTC 房间 URL</li>
|
||||
<li>
|
||||
<p>the message date,</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>sender and receiver addresses</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>and message size.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>电子邮件服务器无法访问此受保护的元数据，
|
||||
但它们可以看到消息日期以及消息大小，
|
||||
更重要的是，可以看到发件人和收件人地址。
|
||||
电子邮件服务器需要收件人地址来路由和
|
||||
将消息传递到接收者的设备。</p>
|
||||
<p>All other message, contact and group metadata resides in the end-to-end encrypted part of messages.</p>
|
||||
|
||||
<h3 id="device-seizure">
|
||||
|
||||
@@ -960,30 +962,36 @@ Delta Chat 的所有 TLS 处理都经过了独立的 <a href="#security-audits">
|
||||
|
||||
</h3>
|
||||
|
||||
<p>为了防止收集元数据的电子邮件服务器
|
||||
以及设备查封的威胁，
|
||||
我们建议使用 <a href="https://delta.chat/chatmail">Chatmail 服务器</a>
|
||||
通过二维码扫描创建匿名临时配置文件。
|
||||
请注意，所有平台上的 Delta Chat 应用都支持多配置文件，
|
||||
因此你可以轻松地在你“主要”配置文件旁边使用特定于情况的配置文件，
|
||||
并且知道它们的所有数据以及所有元数据都将被删除。
|
||||
此外，如果设备被查封，则与使用临时配置文件的联系人
|
||||
相比，无法轻易识别，因为即时通讯应用会在聊天群组中显示
|
||||
电话号码，而电话号码通常与合法身份相关联。</p>
|
||||
<p>Both for protecting against metadata-collecting e-mail servers
|
||||
as well as against the threat of device seizure
|
||||
we recommend to use a <a href="https://chatmail.at/relays">chatmail relay</a>
|
||||
to create chat profiles using random e-mail addresses for transport.
|
||||
Note that Delta Chat apps on all platforms support multiple profiles
|
||||
so you can easily use situation-specific profiles next to your “main” profile
|
||||
with the knowledge that all their data, along with all metadata, will be deleted.
|
||||
Moreover, if a device is seized then chat contacts using short-lived profiles
|
||||
can not be identified easily.</p>
|
||||
|
||||
<h3 id="如何检查加密信息">
|
||||
<h3 id="sealedsender">
|
||||
|
||||
|
||||
如何检查加密信息？ <a href="#如何检查加密信息" class="anchor"></a>
|
||||
Does Delta Chat support “Sealed Sender”? <a href="#sealedsender" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>你可以在“加密”对话框中手动检查端到端加密状态
|
||||
（Android/iOS 上的用户配置文件或桌面上的用户聊天列表项上右键单击）。
|
||||
Delta Chat 在此处显示两个指纹。
|
||||
如果相同的指纹出现在你自己的设备和你联系人的设备上，
|
||||
则连接是安全的。</p>
|
||||
<p>No, not yet.</p>
|
||||
|
||||
<p>The Signal messenger introduced <a href="https://signal.org/blog/sealed-sender/">“Sealed Sender” in 2018</a>
|
||||
to keep their server infrastructure ignorant of who is sending a message to a set of recipients.
|
||||
It is particularly important because the Signal server knows the mobile number of each account,
|
||||
which is usually associated with a passport identity.</p>
|
||||
|
||||
<p>Even if <a href="https://chatmail.at/relays">chatmail relays</a>
|
||||
do not ask for any private data (including no phone numbers),
|
||||
it might still be worthwhile to protect relational metadata between addresses.
|
||||
We don’t foresee bigger problems in using random throw-away e-mail addresses for sealed sending
|
||||
but an implementation has not been agreed as a priority yet.</p>
|
||||
|
||||
<h3 id="pfs">
|
||||
|
||||
@@ -996,32 +1004,49 @@ Delta Chat 在此处显示两个指纹。
|
||||
<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,
|
||||
This means that if your 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>
|
||||
they will be able to decrypt and read them using the leaked decryption key.
|
||||
Note that Forward Secrecy only increases security if you delete messages.
|
||||
Otherwise, someone obtaining your decryption keys
|
||||
is typically also able to get all your non-deleted messages
|
||||
and doesn’t even need to decrypt any previously collected messages.</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>
|
||||
<p>We designed a Forward Secrecy approach that withstood
|
||||
initial examination from some cryptographers and implementation experts
|
||||
but is pending a more formal write up
|
||||
to ascertain it reliably works in federated messaging and with multi-device usage,
|
||||
before it could be implemented in <a href="https://github.com/chatmail/core">chatmail core</a>,
|
||||
which would make it available in all <a href="https://chatmail.at/clients">chatmail clients</a>.</p>
|
||||
|
||||
<h3 id="will-delta-chat-support-forward-secrecy">
|
||||
<h3 id="pqc">
|
||||
|
||||
|
||||
Will Delta Chat support Forward Secrecy? <a href="#will-delta-chat-support-forward-secrecy" class="anchor"></a>
|
||||
Does Delta Chat support Post-Quantum-Cryptography? <a href="#pqc" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>是的。</p>
|
||||
<p>No, not yet.</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>
|
||||
<p>Delta Chat uses the Rust OpenPGP library <a href="https://github.com/rpgp/rpgp">rPGP</a>
|
||||
which supports the latest <a href="https://datatracker.ietf.org/doc/draft-ietf-openpgp-pqc/">IETF Post-Quantum-Cryptography OpenPGP draft</a>.
|
||||
We aim to add PQC support in <a href="https://github.com/chatmail/core">chatmail core</a> after the draft is finalized at the IETF
|
||||
in collaboration with other OpenPGP implementers.</p>
|
||||
|
||||
<h3 id="how-can-i-manually-check-encryption-information">
|
||||
|
||||
|
||||
How can I manually check encryption information? <a href="#how-can-i-manually-check-encryption-information" class="anchor"></a>
|
||||
|
||||
|
||||
</h3>
|
||||
|
||||
<p>你可以在“加密”对话框中手动检查端到端加密状态
|
||||
（Android/iOS 上的用户配置文件或桌面上的用户聊天列表项上右键单击）。
|
||||
Delta Chat 在此处显示两个指纹。
|
||||
如果相同的指纹出现在你自己的设备和你联系人的设备上，
|
||||
则连接是安全的。</p>
|
||||
|
||||
<h3 id="importkey">
|
||||
|
||||
|
||||
@@ -1048,6 +1048,7 @@
|
||||
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
|
||||
<string name="verified_by">%1$s által bemutatva</string>
|
||||
<string name="verified_by_you">Ön által bemutatva</string>
|
||||
<string name="verified_by_unknown">Bemutatva</string>
|
||||
<!-- deprecated, was stock string -->
|
||||
<string name="contact_setup_changed">Megváltoztatta a beállításokat %1$s számára.</string>
|
||||
<string name="verified_contact_required_explain">A végpontok közötti titkosítás garantálása érdekében csak zöld jelöléssel rendelkező névjegyeket adhat hozzá ehhez a csoporthoz.\n\n Személyesen is találkozhat a partnereivel és beolvashatja a QR-kódjukat, hogy bemutassa őket.</string>
|
||||
@@ -1222,6 +1223,8 @@
|
||||
<string name="perm_enable_bg_reminder_title">Koppintson ide az üzenetek fogadásához, miközben a Delta Chat a háttérben fut.</string>
|
||||
<string name="perm_enable_bg_already_done">Már engedélyezve van a Delta Chat számára, hogy a háttérben üzeneteket fogadjon.\n\nHa az üzenetek még mindig nem érkeznek meg a háttérben, ellenőrizze a rendszerbeállításokat is.</string>
|
||||
|
||||
<!-- device messages for updates -->
|
||||
<string name="update_2_0">Újdonságok:\n\n💯 A végpontok közötti titkosítás most már megbízható és örökre megmarad. A lakatok 🔒 eltűntek!\n\n✉️ A végpontok közötti titkosítás nélküli klasszikus e-mailek betűszimbólummal vannak jelölve\n\n😻 Új, továbbfejlesztett profilképernyő az összes névjegyhez\n\n🔲 Új gomb a csevegésben használt alkalmazások gyors eléréséhez\n\n❤️ Ha teheti, adományozzon nekünk, hogy függetlenek maradhassunk és továbbra is fejlesztéseket tudjunk végrehajtani: %1$s</string>
|
||||
<!-- deprecated -->
|
||||
<string name="update_1_50_android">Mik az újdonságok?\n\n❤️🔥 Új emodzsi-választó még több emodzsival\n\n🎮 Továbbfejlesztett, a csevegésben használható alkalmazások: Értesítéseket kaphat és megnyithatja az azokat támogató alkalmazásokban, azaz közvetlenül megnyithat egy hozzáadott naptárbejegyzést\n\n👍 Értesítést kaphat az üzeneteire adott reakciókról\n\n… 🛠️ Egyéb javítások, tudjon meg többet itt: %1$s</string>
|
||||
<!-- deprecated -->
|
||||
|
||||
@@ -1065,6 +1065,7 @@
|
||||
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
|
||||
<string name="verified_by">Verificato da %1$s</string>
|
||||
<string name="verified_by_you">Verificato da me</string>
|
||||
<string name="verified_by_unknown">Presentato</string>
|
||||
<!-- deprecated, was stock string -->
|
||||
<string name="contact_setup_changed">Impostazioni modificate per %1$s</string>
|
||||
<string name="verified_contact_required_explain">Per garantire la crittografia end-to-end, puoi aggiungere a questo gruppo solo i contatti con un segno di spunta verde.\n\nPuoi incontrare i contatti di persona e scansionare il loro Codice QR per verificarli.</string>
|
||||
|
||||
@@ -1048,6 +1048,7 @@
|
||||
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
|
||||
<string name="verified_by">%1$s tarafından tanıtıldı</string>
|
||||
<string name="verified_by_you">Benim tarafımdan tanıtıldı</string>
|
||||
<string name="verified_by_unknown">Tanıtıldı</string>
|
||||
<!-- deprecated, was stock string -->
|
||||
<string name="contact_setup_changed">%1$s için ayarlama değiştirildi.</string>
|
||||
<string name="verified_contact_required_explain">Uçtan uca şifrelemeyi güvencelemek için bu öbeğe yalnızca yeşil bir onay imi olan kişileri ekleyebilirsiniz.\n\nDoğrulanmayan kişilerle kişisel olarak tanışabilir ve onları tanıtmak için onların QR kodunu tarayabilirsiniz.</string>
|
||||
|
||||
@@ -264,6 +264,12 @@
|
||||
<string name="broadcast_lists">Списки трансляцій</string>
|
||||
<!-- deprecated -->
|
||||
<string name="new_broadcast_list">Новий Список трансляцій</string>
|
||||
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
|
||||
<string name="channel">Канал</string>
|
||||
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
|
||||
<string name="channels">Канали</string>
|
||||
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
|
||||
<string name="new_channel">Новий Канал</string>
|
||||
<string name="add_recipients">Додати одержувачів</string>
|
||||
<!-- deprecated -->
|
||||
<string name="edit_broadcast_list">Редагувати список трансляцій</string>
|
||||
@@ -271,6 +277,13 @@
|
||||
<string name="broadcast_list_name">Назва списку трансляцій</string>
|
||||
<!-- deprecated -->
|
||||
<string name="please_enter_broadcast_list_name">Будь ласка, введіть назву для списку трансляцій.</string>
|
||||
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
|
||||
<string name="channel_name">Назва Каналу</string>
|
||||
<string name="email">E-Mail</string>
|
||||
<!-- "New" as in "Create New E-Mail"; shown together with "New Group" and "New Channel" -->
|
||||
<string name="new_email">Новий E-Mail</string>
|
||||
<!-- the "Subject" of an e-mail, use the term common in classic e-mail apps -->
|
||||
<string name="subject">Тема</string>
|
||||
<string name="menu_send">Послати</string>
|
||||
<string name="menu_toggle_keyboard">Увімкнути емодзі-клавіатуру</string>
|
||||
<string name="menu_edit_group">Редагувати групу</string>
|
||||
@@ -280,6 +293,7 @@
|
||||
<string name="menu_unarchive_chat">Розархівувати чат</string>
|
||||
<string name="menu_add_attachment">Додати вкладення</string>
|
||||
<string name="menu_leave_group">Залишити групу</string>
|
||||
<string name="menu_leave_channel">Покинути Канал</string>
|
||||
<string name="menu_delete_chat">Видалити чат</string>
|
||||
<!-- Command to delete all messages in a chat. The chat itself will not be deleted but will be empty afterwards, so make sure to be different from "Delete Chat" here. "Clear" is a verb here, "Empty Chat" would also be fine (eg. in German "Chat leeren") -->
|
||||
<string name="clear_chat">Очистити чат</string>
|
||||
@@ -364,6 +378,8 @@
|
||||
<!-- Menu item beside an app/chat that adds an icon to the system's home screen. If the user taps that icon, the app/chat is opened directly. -->
|
||||
<string name="add_to_home_screen">Додати на стартовий екран</string>
|
||||
<string name="donate">Задонатити</string>
|
||||
<string name="donate_device_msg">❤️ Здається, вам подобається Delta Chat!\n\nПодумайте про пожертвування, щоб допомогти забезпечити безкоштовність Delta Chat для всіх.\n\nХоча Delta Chat є безкоштовним у використанні та з відкритим вихідним кодом, розробка коштує грошей. Допоможіть нам зберегти незалежність Delta Chat і зробити його ще більш чудовим у майбутньому.\n\nhttps://delta.chat/donate</string>
|
||||
|
||||
<string name="mute_for_one_hour">Вимкнути сповіщення на годину</string>
|
||||
<string name="mute_for_eight_hours">Вимкнути сповіщення на 8 годин</string>
|
||||
<string name="mute_for_one_day">Вимкнути сповіщення на добу</string>
|
||||
@@ -400,6 +416,9 @@
|
||||
<string name="videochat_invitation">Запрошення до відео чату</string>
|
||||
<string name="videochat_invitation_body">Вас запрошено у відео-чат, клікніть %1$s аби приєднатися.</string>
|
||||
|
||||
<!-- get confirmations -->
|
||||
<!-- confirmation for leaving groups, channels, broadcasts or a mailinglists. If a subject is needed, "Are you sure you want to leave the chat?" would work as well -->
|
||||
<string name="ask_leave_group">Ви впевнені, що хочете піти?</string>
|
||||
<plurals name="ask_delete_chat">
|
||||
<item quantity="one">¿Видалити %d чат на всіх Ваших пристроях?</item>
|
||||
<item quantity="few">¿Видалити %d чати на всіх Ваших пристроях?</item>
|
||||
@@ -433,6 +452,8 @@
|
||||
<string name="ask_remove_members">Видалити %1$s із групи?</string>
|
||||
<!-- deprecated -->
|
||||
<string name="ask_remove_from_broadcast">Видалити %1$s зі списку трансляцій?</string>
|
||||
<!-- %1$s is replaced by a comma-separated list of names -->
|
||||
<string name="ask_remove_from_channel">Видалити %1$s з каналу?</string>
|
||||
<string name="open_url_confirmation">Ви впевнені, що хочете відкрити це посилання?</string>
|
||||
|
||||
|
||||
@@ -470,6 +491,8 @@
|
||||
<string name="chat_new_one_to_one_hint">Відправити повідомлення → %1$s.</string>
|
||||
<!-- deprecated -->
|
||||
<string name="chat_new_broadcast_hint">У списку трансляцій одержувачі будуть отримувати повідомлення в чаті з Вами в режимі тільки-для-читання.</string>
|
||||
<!-- consider keeping the term "channel" as in WhatsApp or Telegram -->
|
||||
<string name="chat_new_channel_hint">Канали - це інструмент \"один до багатьох\" для трансляції ваших повідомлень.</string>
|
||||
<string name="chat_new_group_hint">Інші побачать цю групу лише після того, як ви надішлете перше повідомлення.</string>
|
||||
<string name="chat_record_slide_to_cancel">Рухайте для скасування</string>
|
||||
<string name="chat_record_explain">Натиснувши втримуйте, щоби записати голосове повідомлення, а для відправки відпустіть</string>
|
||||
@@ -479,6 +502,7 @@
|
||||
<string name="chat_input_placeholder">Повідомлення</string>
|
||||
<string name="chat_archived_label">Заархівовано</string>
|
||||
<string name="chat_request_label">Запит</string>
|
||||
<string name="chat_request_label_explain">Включайте запити в лічильники та сповіщення</string>
|
||||
<string name="chat_no_messages">Немає повідомлень.</string>
|
||||
<string name="chat_self_talk_subtitle">Повідомлення, відправлені самому собі</string>
|
||||
<string name="archive_empty_hint">Заархівовані Вами чати будуть відображені тут.</string>
|
||||
@@ -935,6 +959,8 @@
|
||||
<string name="remove_member_by_you">Ви видалили учасника %1$s.</string>
|
||||
<!-- %1$s will be replaced by name and address of the contact removed from the group, %2$s will be replaced by name and address of the contact who did the action -->
|
||||
<string name="remove_member_by_other">%2$s видалив (-ла) учасника %1$s.</string>
|
||||
<!-- "left" in the meaning of "exited". This string is added to a chat after groups, channels, broadcasts or mailinglists are left. If a subject is needed, "You left the chat." would work as well. -->
|
||||
<string name="group_left_by_you">Ви пішли</string>
|
||||
<!-- "left" in the meaning of "exited"; %1$s will be replaced by name and address of the contact leaving the group -->
|
||||
<string name="group_left_by_other">%1$s залишив (-ла) групу.</string>
|
||||
<string name="group_image_deleted_by_you">Ви видалили емблему групи.</string>
|
||||
@@ -1054,6 +1080,7 @@
|
||||
<!-- Shown in contact profile. The placeholder will be replaced by the name of the contact that introduced the contact. -->
|
||||
<string name="verified_by">Представни·ця: %1$s</string>
|
||||
<string name="verified_by_you">Представлено мною</string>
|
||||
<string name="verified_by_unknown">Представлено</string>
|
||||
<!-- deprecated, was stock string -->
|
||||
<string name="contact_setup_changed">Змінені параметри для %1$s</string>
|
||||
<string name="verified_contact_required_explain">Аби наскрізне шифрування лишалося ґарантованим, у цю групу можна додавати лише контактних осіб із зеленою галочкою.\n\nМожна зустрітись із контактною особою та відсканувати баркод із її пристрою, щоби представити її.</string>
|
||||
@@ -1228,6 +1255,8 @@
|
||||
<string name="perm_enable_bg_reminder_title">Натисніть тут, щоб отримувати повідомлення, коли Delta Chat знаходиться у фоновому режимі.</string>
|
||||
<string name="perm_enable_bg_already_done">Ви вже дозволили Delta Chat отримувати повідомлення у фоновому режимі.\n\nЯкщо повідомлення досі не приходять у фоновому режимі, перевірте налаштування системи.</string>
|
||||
|
||||
<!-- device messages for updates -->
|
||||
<string name="update_2_0">Що нового?\n\n💯 Наскрізне шифрування тепер надійне і завжди. Навісні замки 🔒 зникли!\n\n✉️ Класична електронна пошта без наскрізного шифрування позначається символом листа\n\n😻 Новий покращений екран профілю для всіх ваших контактів\n\n🔲 Нова кнопка для швидкого доступу до додатків, що використовуються в чаті\n\n❤️ Будь ласка, пожертвуйте, щоб допомогти нам залишатися незалежними та продовжувати вдосконалюватися: %1$s</string>
|
||||
<!-- deprecated -->
|
||||
<string name="update_1_50_android">Що нового? \n\n❤️🔥 Новий вибірник емодзі з більшою кількістю смайликів \n\n🎮 Покращені програми в чаті: отримуйте сповіщення та відкривайте додатки безпосередньо в контексті, наприклад, доданий запис у календарі \n\n👍 Отримуйте сповіщення про реакції на ваші повідомлення \n\n... 🛠️ ВИПРАВЛЕННЯ та ЩЕ БІЛЬШЕ на %1$s</string>
|
||||
<!-- deprecated -->
|
||||
|
||||
Reference in New Issue
Block a user