From 0dd27603db9e1a5cb49cb9ebb3ab8ac8741090a8 Mon Sep 17 00:00:00 2001 From: Crowdin Bot Date: Thu, 29 Jun 2023 04:04:24 +0000 Subject: [PATCH] New Crowdin translations by GitHub Action --- i18n/ar/real-time-communication.md | 6 +- i18n/ar/vpn.md | 4 +- i18n/bn/real-time-communication.md | 6 +- i18n/bn/vpn.md | 4 +- i18n/cs/real-time-communication.md | 6 +- i18n/cs/vpn.md | 4 +- i18n/de/real-time-communication.md | 6 +- i18n/de/vpn.md | 4 +- i18n/el/real-time-communication.md | 6 +- i18n/el/vpn.md | 4 +- i18n/eo/real-time-communication.md | 6 +- i18n/eo/vpn.md | 4 +- i18n/es/real-time-communication.md | 6 +- i18n/es/vpn.md | 4 +- i18n/fa/real-time-communication.md | 6 +- i18n/fa/vpn.md | 4 +- i18n/fr/real-time-communication.md | 6 +- i18n/fr/vpn.md | 4 +- i18n/he/real-time-communication.md | 6 +- i18n/he/vpn.md | 4 +- i18n/hi/real-time-communication.md | 6 +- i18n/hi/vpn.md | 4 +- i18n/hu/real-time-communication.md | 6 +- i18n/hu/vpn.md | 4 +- i18n/id/real-time-communication.md | 6 +- i18n/id/vpn.md | 4 +- i18n/it/real-time-communication.md | 6 +- i18n/it/vpn.md | 4 +- i18n/ja/real-time-communication.md | 6 +- i18n/ja/vpn.md | 4 +- i18n/ko/real-time-communication.md | 6 +- i18n/ko/vpn.md | 4 +- i18n/ku-IQ/real-time-communication.md | 6 +- i18n/ku-IQ/vpn.md | 4 +- i18n/nl/real-time-communication.md | 6 +- i18n/nl/vpn.md | 4 +- i18n/pl/real-time-communication.md | 6 +- i18n/pl/vpn.md | 4 +- i18n/pt-BR/real-time-communication.md | 6 +- i18n/pt-BR/vpn.md | 4 +- i18n/pt/basics/account-deletion.md | 2 +- i18n/pt/basics/common-threats.md | 33 +++++----- i18n/pt/basics/threat-modeling.md | 80 +++++++++++------------ i18n/pt/basics/why-privacy-matters.md | 14 ++-- i18n/pt/real-time-communication.md | 6 +- i18n/pt/vpn.md | 4 +- i18n/ru/desktop.md | 36 +++++------ i18n/ru/email-clients.md | 85 +++++++++++++------------ i18n/ru/real-time-communication.md | 6 +- i18n/ru/vpn.md | 4 +- i18n/sv/real-time-communication.md | 6 +- i18n/sv/vpn.md | 4 +- i18n/tr/real-time-communication.md | 6 +- i18n/tr/vpn.md | 4 +- i18n/uk/real-time-communication.md | 6 +- i18n/uk/vpn.md | 4 +- i18n/vi/real-time-communication.md | 6 +- i18n/vi/vpn.md | 4 +- i18n/zh-Hant/about/criteria.md | 4 +- i18n/zh-Hant/productivity.md | 26 ++++---- i18n/zh-Hant/real-time-communication.md | 40 ++++++------ i18n/zh-Hant/router.md | 14 ++-- i18n/zh-Hant/search-engines.md | 24 +++---- i18n/zh-Hant/tools.md | 10 +-- i18n/zh-Hant/video-streaming.md | 20 +++--- i18n/zh-Hant/vpn.md | 4 +- i18n/zh/real-time-communication.md | 6 +- i18n/zh/vpn.md | 4 +- includes/abbreviations.ar.txt | 1 + includes/abbreviations.bn.txt | 1 + includes/abbreviations.cs.txt | 1 + includes/abbreviations.de.txt | 1 + includes/abbreviations.el.txt | 1 + includes/abbreviations.eo.txt | 1 + includes/abbreviations.es.txt | 1 + includes/abbreviations.fa.txt | 1 + includes/abbreviations.fr.txt | 1 + includes/abbreviations.he.txt | 1 + includes/abbreviations.hi.txt | 1 + includes/abbreviations.hu.txt | 1 + includes/abbreviations.id.txt | 1 + includes/abbreviations.it.txt | 1 + includes/abbreviations.ja.txt | 1 + includes/abbreviations.ko.txt | 1 + includes/abbreviations.ku-IQ.txt | 1 + includes/abbreviations.nl.txt | 1 + includes/abbreviations.pl.txt | 1 + includes/abbreviations.pt-BR.txt | 1 + includes/abbreviations.pt.txt | 1 + includes/abbreviations.ru.txt | 1 + includes/abbreviations.sv.txt | 1 + includes/abbreviations.tr.txt | 1 + includes/abbreviations.uk.txt | 1 + includes/abbreviations.vi.txt | 1 + includes/abbreviations.zh-Hant.txt | 1 + includes/abbreviations.zh.txt | 1 + 96 files changed, 361 insertions(+), 329 deletions(-) diff --git a/i18n/ar/real-time-communication.md b/i18n/ar/real-time-communication.md index 9fc46b69..efd3570b 100644 --- a/i18n/ar/real-time-communication.md +++ b/i18n/ar/real-time-communication.md @@ -99,13 +99,13 @@ The client software was independently [audited](https://briarproject.org/news/20 Briar has a fully [published specification](https://code.briarproject.org/briar/briar-spec). -Briar supports perfect forward secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## Additional Options !!! warning - These messengers do not have Perfect [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. ### Element @@ -189,7 +189,7 @@ Session has a [whitepaper](https://arxiv.org/pdf/2002.04609.pdf) describing the Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page. -- Should have Perfect Forward Secrecy. +- Should have Forward Secrecy. - Should have open-source servers. - Should be decentralized, i.e. federated or P2P. - Should use E2EE for all messages by default. diff --git a/i18n/ar/vpn.md b/i18n/ar/vpn.md index c2a24922..2dd5fabe 100644 --- a/i18n/ar/vpn.md +++ b/i18n/ar/vpn.md @@ -279,13 +279,13 @@ A VPN is pointless if it can't even provide adequate security. We require all ou **Minimum to Qualify:** - Strong Encryption Schemes: OpenVPN with SHA-256 authentication; RSA-2048 or better handshake; AES-256-GCM or AES-256-CBC data encryption. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Published security audits from a reputable third-party firm. **Best Case:** - Strongest Encryption: RSA-4096. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Comprehensive published security audits from a reputable third-party firm. - Bug-bounty programs and/or a coordinated vulnerability-disclosure process. diff --git a/i18n/bn/real-time-communication.md b/i18n/bn/real-time-communication.md index 9fc46b69..efd3570b 100644 --- a/i18n/bn/real-time-communication.md +++ b/i18n/bn/real-time-communication.md @@ -99,13 +99,13 @@ The client software was independently [audited](https://briarproject.org/news/20 Briar has a fully [published specification](https://code.briarproject.org/briar/briar-spec). -Briar supports perfect forward secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## Additional Options !!! warning - These messengers do not have Perfect [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. ### Element @@ -189,7 +189,7 @@ Session has a [whitepaper](https://arxiv.org/pdf/2002.04609.pdf) describing the Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page. -- Should have Perfect Forward Secrecy. +- Should have Forward Secrecy. - Should have open-source servers. - Should be decentralized, i.e. federated or P2P. - Should use E2EE for all messages by default. diff --git a/i18n/bn/vpn.md b/i18n/bn/vpn.md index 0a09044d..af4643aa 100644 --- a/i18n/bn/vpn.md +++ b/i18n/bn/vpn.md @@ -279,13 +279,13 @@ A VPN is pointless if it can't even provide adequate security. We require all ou **Minimum to Qualify:** - Strong Encryption Schemes: OpenVPN with SHA-256 authentication; RSA-2048 or better handshake; AES-256-GCM or AES-256-CBC data encryption. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Published security audits from a reputable third-party firm. **Best Case:** - Strongest Encryption: RSA-4096. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Comprehensive published security audits from a reputable third-party firm. - Bug-bounty programs and/or a coordinated vulnerability-disclosure process. diff --git a/i18n/cs/real-time-communication.md b/i18n/cs/real-time-communication.md index 9fc46b69..efd3570b 100644 --- a/i18n/cs/real-time-communication.md +++ b/i18n/cs/real-time-communication.md @@ -99,13 +99,13 @@ The client software was independently [audited](https://briarproject.org/news/20 Briar has a fully [published specification](https://code.briarproject.org/briar/briar-spec). -Briar supports perfect forward secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## Additional Options !!! warning - These messengers do not have Perfect [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. ### Element @@ -189,7 +189,7 @@ Session has a [whitepaper](https://arxiv.org/pdf/2002.04609.pdf) describing the Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page. -- Should have Perfect Forward Secrecy. +- Should have Forward Secrecy. - Should have open-source servers. - Should be decentralized, i.e. federated or P2P. - Should use E2EE for all messages by default. diff --git a/i18n/cs/vpn.md b/i18n/cs/vpn.md index 0a09044d..af4643aa 100644 --- a/i18n/cs/vpn.md +++ b/i18n/cs/vpn.md @@ -279,13 +279,13 @@ A VPN is pointless if it can't even provide adequate security. We require all ou **Minimum to Qualify:** - Strong Encryption Schemes: OpenVPN with SHA-256 authentication; RSA-2048 or better handshake; AES-256-GCM or AES-256-CBC data encryption. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Published security audits from a reputable third-party firm. **Best Case:** - Strongest Encryption: RSA-4096. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Comprehensive published security audits from a reputable third-party firm. - Bug-bounty programs and/or a coordinated vulnerability-disclosure process. diff --git a/i18n/de/real-time-communication.md b/i18n/de/real-time-communication.md index 9fc46b69..efd3570b 100644 --- a/i18n/de/real-time-communication.md +++ b/i18n/de/real-time-communication.md @@ -99,13 +99,13 @@ The client software was independently [audited](https://briarproject.org/news/20 Briar has a fully [published specification](https://code.briarproject.org/briar/briar-spec). -Briar supports perfect forward secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## Additional Options !!! warning - These messengers do not have Perfect [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. ### Element @@ -189,7 +189,7 @@ Session has a [whitepaper](https://arxiv.org/pdf/2002.04609.pdf) describing the Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page. -- Should have Perfect Forward Secrecy. +- Should have Forward Secrecy. - Should have open-source servers. - Should be decentralized, i.e. federated or P2P. - Should use E2EE for all messages by default. diff --git a/i18n/de/vpn.md b/i18n/de/vpn.md index 1d669e0b..15406ac6 100644 --- a/i18n/de/vpn.md +++ b/i18n/de/vpn.md @@ -279,13 +279,13 @@ A VPN is pointless if it can't even provide adequate security. We require all ou **Mindestvoraussetzung um zu qualifizieren:** - Strong Encryption Schemes: OpenVPN with SHA-256 authentication; RSA-2048 or better handshake; AES-256-GCM or AES-256-CBC data encryption. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Published security audits from a reputable third-party firm. **Best Case:** - Strongest Encryption: RSA-4096. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Comprehensive published security audits from a reputable third-party firm. - Bug-bounty programs and/or a coordinated vulnerability-disclosure process. diff --git a/i18n/el/real-time-communication.md b/i18n/el/real-time-communication.md index 9fc46b69..efd3570b 100644 --- a/i18n/el/real-time-communication.md +++ b/i18n/el/real-time-communication.md @@ -99,13 +99,13 @@ The client software was independently [audited](https://briarproject.org/news/20 Briar has a fully [published specification](https://code.briarproject.org/briar/briar-spec). -Briar supports perfect forward secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## Additional Options !!! warning - These messengers do not have Perfect [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. ### Element @@ -189,7 +189,7 @@ Session has a [whitepaper](https://arxiv.org/pdf/2002.04609.pdf) describing the Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page. -- Should have Perfect Forward Secrecy. +- Should have Forward Secrecy. - Should have open-source servers. - Should be decentralized, i.e. federated or P2P. - Should use E2EE for all messages by default. diff --git a/i18n/el/vpn.md b/i18n/el/vpn.md index d5160d51..8440fa2b 100644 --- a/i18n/el/vpn.md +++ b/i18n/el/vpn.md @@ -279,13 +279,13 @@ A VPN is pointless if it can't even provide adequate security. We require all ou **Minimum to Qualify:** - Strong Encryption Schemes: OpenVPN with SHA-256 authentication; RSA-2048 or better handshake; AES-256-GCM or AES-256-CBC data encryption. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Published security audits from a reputable third-party firm. **Best Case:** - Strongest Encryption: RSA-4096. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Comprehensive published security audits from a reputable third-party firm. - Bug-bounty programs and/or a coordinated vulnerability-disclosure process. diff --git a/i18n/eo/real-time-communication.md b/i18n/eo/real-time-communication.md index 9fc46b69..efd3570b 100644 --- a/i18n/eo/real-time-communication.md +++ b/i18n/eo/real-time-communication.md @@ -99,13 +99,13 @@ The client software was independently [audited](https://briarproject.org/news/20 Briar has a fully [published specification](https://code.briarproject.org/briar/briar-spec). -Briar supports perfect forward secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## Additional Options !!! warning - These messengers do not have Perfect [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. ### Element @@ -189,7 +189,7 @@ Session has a [whitepaper](https://arxiv.org/pdf/2002.04609.pdf) describing the Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page. -- Should have Perfect Forward Secrecy. +- Should have Forward Secrecy. - Should have open-source servers. - Should be decentralized, i.e. federated or P2P. - Should use E2EE for all messages by default. diff --git a/i18n/eo/vpn.md b/i18n/eo/vpn.md index 0a09044d..af4643aa 100644 --- a/i18n/eo/vpn.md +++ b/i18n/eo/vpn.md @@ -279,13 +279,13 @@ A VPN is pointless if it can't even provide adequate security. We require all ou **Minimum to Qualify:** - Strong Encryption Schemes: OpenVPN with SHA-256 authentication; RSA-2048 or better handshake; AES-256-GCM or AES-256-CBC data encryption. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Published security audits from a reputable third-party firm. **Best Case:** - Strongest Encryption: RSA-4096. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Comprehensive published security audits from a reputable third-party firm. - Bug-bounty programs and/or a coordinated vulnerability-disclosure process. diff --git a/i18n/es/real-time-communication.md b/i18n/es/real-time-communication.md index f493c985..1413c8ae 100644 --- a/i18n/es/real-time-communication.md +++ b/i18n/es/real-time-communication.md @@ -99,13 +99,13 @@ El software cliente fue [auditado](https://briarproject.org/news/2017-beta-relea Briar tiene una [especificación publicada](https://code.briarproject.org/briar/briar-spec) completamente. -Briar admite el secreto de reenvío perfecto utilizando el protocolo Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) y el protocolo [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md). +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## Opciones Adicionales !!! warning "Advertencia" - Estos servicios de mensajería no tienen Perfect [Forward Secrecy](https://es.wikipedia.org/wiki/Perfect_forward_secrecy) (PFS), y aunque satisfacen ciertas necesidades que nuestras recomendaciones anteriores no pueden satisfacer, no los recomendamos para comunicaciones a largo plazo o sensibles. Cualquier compromiso de claves entre los destinatarios de los mensajes afectaría a la confidencialidad de **todas** las comunicaciones anteriores. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Cualquier compromiso de claves entre los destinatarios de los mensajes afectaría a la confidencialidad de **todas** las comunicaciones anteriores. ### Element @@ -189,7 +189,7 @@ Session tiene un [informe oficial](https://arxiv.org/pdf/2002.04609.pdf) que des Nuestro criterio del mejor caso representa lo que nos gustaría ver del proyecto perfecto en esta categoría. Es posible que nuestras recomendaciones no incluyan todas o algunas de estas funciones, pero las que sí las incluyan pueden estar mejor clasificadas que otras en esta página. -- Debe tener Perfect Forward Secrecy. +- Should have Forward Secrecy. - Debe tener servidores de código abierto. - Debe ser descentralizado, es decir, federado o P2P. - Debe utilizar E2EE para todos los mensajes por defecto. diff --git a/i18n/es/vpn.md b/i18n/es/vpn.md index 39a59aa7..6e3fcc97 100644 --- a/i18n/es/vpn.md +++ b/i18n/es/vpn.md @@ -281,13 +281,13 @@ Una VPN no tiene sentido si ni siquiera puede proporcionar una seguridad adecuad **Mínimo para Calificar:** - Esquemas de cifrado fuertes: OpenVPN con autenticación SHA-256; RSA-2048 o mejor handshake; AES-256-CBC o cifrado de datos AES-256-GCM. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Auditorías de seguridad publicadas por una empresa externa de prestigio. **Mejor Caso:** - Cifrado más fuerte: RSA-4096. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Auditorías de seguridad exhaustivas publicadas por una empresa externa de prestigio. - Programas de recompensa de errores y/o un proceso coordinado de divulgación de vulnerabilidades. diff --git a/i18n/fa/real-time-communication.md b/i18n/fa/real-time-communication.md index 9fc46b69..efd3570b 100644 --- a/i18n/fa/real-time-communication.md +++ b/i18n/fa/real-time-communication.md @@ -99,13 +99,13 @@ The client software was independently [audited](https://briarproject.org/news/20 Briar has a fully [published specification](https://code.briarproject.org/briar/briar-spec). -Briar supports perfect forward secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## Additional Options !!! warning - These messengers do not have Perfect [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. ### Element @@ -189,7 +189,7 @@ Session has a [whitepaper](https://arxiv.org/pdf/2002.04609.pdf) describing the Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page. -- Should have Perfect Forward Secrecy. +- Should have Forward Secrecy. - Should have open-source servers. - Should be decentralized, i.e. federated or P2P. - Should use E2EE for all messages by default. diff --git a/i18n/fa/vpn.md b/i18n/fa/vpn.md index 0a09044d..af4643aa 100644 --- a/i18n/fa/vpn.md +++ b/i18n/fa/vpn.md @@ -279,13 +279,13 @@ A VPN is pointless if it can't even provide adequate security. We require all ou **Minimum to Qualify:** - Strong Encryption Schemes: OpenVPN with SHA-256 authentication; RSA-2048 or better handshake; AES-256-GCM or AES-256-CBC data encryption. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Published security audits from a reputable third-party firm. **Best Case:** - Strongest Encryption: RSA-4096. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Comprehensive published security audits from a reputable third-party firm. - Bug-bounty programs and/or a coordinated vulnerability-disclosure process. diff --git a/i18n/fr/real-time-communication.md b/i18n/fr/real-time-communication.md index db05fbd9..8c655403 100644 --- a/i18n/fr/real-time-communication.md +++ b/i18n/fr/real-time-communication.md @@ -99,13 +99,13 @@ Le logiciel client a été indépendamment [audité](https://briarproject.org/ne Briar a un [cahier des charges](https://code.briarproject.org/briar/briar-spec) entièrement publié. -Briar prend en charge la confidentialité persistante en utilisant le protocole de [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) et [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) Bramble. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## Autres options !!! warning "Avertissement" - Ces messagers ne disposent pas de la fonction Perfect [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS), et bien qu'ils répondent à certains besoins que nos recommandations précédentes ne peuvent pas satisfaire, nous ne les recommandons pas pour les communications sensibles ou à long terme. Toute compromission de la clé parmi les destinataires du message affecterait la confidentialité de **toutes** les communications passées. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Toute compromission de la clé parmi les destinataires du message affecterait la confidentialité de **toutes** les communications passées. ### Element @@ -189,7 +189,7 @@ Session a un [livre blanc](https://arxiv.org/pdf/2002.04609.pdf) décrivant les Nos critères de cas idéal représentent ce que nous aimerions voir d'un projet parfait dans cette catégorie. Nos recommandations peuvent ne pas inclure tout ou partie de cette fonctionnalité, mais celles qui l'inclus peuvent être mieux classées que les autres sur cette page. -- Devrait prendre en charge la Confidentialité Persistante. +- Should have Forward Secrecy. - Devrait avoir des serveurs open-source. - Devrait être décentralisé, c'est-à-dire fédéré ou P2P. - Devrait utiliser E2EE pour tous les messages par défaut. diff --git a/i18n/fr/vpn.md b/i18n/fr/vpn.md index 84dfa6af..5f75ac5b 100644 --- a/i18n/fr/vpn.md +++ b/i18n/fr/vpn.md @@ -279,13 +279,13 @@ Un VPN est inutile s'il ne peut même pas fournir une sécurité adéquate. Nous **Minimum pour se qualifier :** - Schémas de chiffrement forts : OpenVPN avec authentification SHA-256 ; poignée de main RSA-2048 ou mieux ; chiffrement des données AES-256-GCM ou AES-256-CBC. -- Confidentialité Persistante (PFS). +- Forward Secrecy. - Des audits de sécurité publiés par une société tierce réputée. **Dans le meilleur des cas :** - Chiffrement le plus fort : RSA-4096. -- Confidentialité Persistante (PFS). +- Forward Secrecy. - Des audits de sécurité complets publiés par une société tierce réputée. - Des programmes de primes aux bugs et/ou un processus coordonné de divulgation des vulnérabilités. diff --git a/i18n/he/real-time-communication.md b/i18n/he/real-time-communication.md index 89cd0a6a..98e1fcd8 100644 --- a/i18n/he/real-time-communication.md +++ b/i18n/he/real-time-communication.md @@ -99,13 +99,13 @@ SimpleX Chat [נבדק](https://simplex.chat/blog/20221108-simplex-chat-v4.2-sec ל Briar יש מפרט ש[פורסם במלואו](https://code.briarproject.org/briar/briar-spec). -Briar תומך בסודיות קדימה מושלמת על ידי שימוש ב-[Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) ו [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) פרוטוקול. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## אפשרויות נוספות !!! warning "אזהרה" - למסנג'רים האלה אין [סודיות קדימה](https://en.wikipedia.org/wiki/Forward_secrecy) מושלם (PFS), ולמרות שהם ממלאים צרכים מסוימים שהמלצות קודמות שלנו אולי לא, אנחנו לא ממליצים עליהם לאורך זמן- מונחים או תקשורת רגישה. כל פשרה מרכזית בין מקבלי ההודעות תשפיע על הסודיות של **כל** התקשורת העבר. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. כל פשרה מרכזית בין מקבלי ההודעות תשפיע על הסודיות של **כל** התקשורת העבר. ### Element @@ -189,7 +189,7 @@ Oxen ביקשה ביקורת בלתי תלויה למפגש במרץ 2020. הב הקריטריונים הטובים ביותר שלנו מייצגים את מה שהיינו רוצים לראות מהפרויקט המושלם בקטגוריה זו. ייתכן שההמלצות שלנו לא יכללו חלק מהפונקציונליות הזו או את כולה, אך אלו שכן כן עשויות לדרג גבוה יותר מאחרות בדף זה. -- צריך להיות סודיות קדימה מושלמת. +- Should have Forward Secrecy. - צריכים להיות שרתי קוד פתוח. - צריך להיות מבוזר, כלומר מאוחד או P2P. - אמור להשתמש ב- E2EE עבור כל ההודעות כברירת מחדל. diff --git a/i18n/he/vpn.md b/i18n/he/vpn.md index a77b26b4..79723390 100644 --- a/i18n/he/vpn.md +++ b/i18n/he/vpn.md @@ -279,13 +279,13 @@ VPN הוא חסר טעם אם הוא אפילו לא יכול לספק אבטח **מינימום כדי לעמוד בדרישות:** - ערכות הצפנה חזקות: OpenVPN עם אימות SHA -256; RSA -2048 או לחיצת יד טובה יותר; AES -256 - GCM או הצפנת נתונים AES -256 - CBC. -- סודיות קדימה מושלמת (PFS). +- Forward Secrecy. - פירסם ביקורות אבטחה מחברת צד שלישי מכובדת. **המקרה הטוב ביותר:** - הצפנה חזקה ביותר: RSA -4096. -- סודיות קדימה מושלמת (PFS). +- Forward Secrecy. - ביקורות אבטחה מקיפות שפורסמו מחברת צד שלישי בעלת מוניטין. - תוכניות לחיפוש באגים ו/או תהליך גילוי - פגיעות מתואם. diff --git a/i18n/hi/real-time-communication.md b/i18n/hi/real-time-communication.md index 9fc46b69..efd3570b 100644 --- a/i18n/hi/real-time-communication.md +++ b/i18n/hi/real-time-communication.md @@ -99,13 +99,13 @@ The client software was independently [audited](https://briarproject.org/news/20 Briar has a fully [published specification](https://code.briarproject.org/briar/briar-spec). -Briar supports perfect forward secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## Additional Options !!! warning - These messengers do not have Perfect [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. ### Element @@ -189,7 +189,7 @@ Session has a [whitepaper](https://arxiv.org/pdf/2002.04609.pdf) describing the Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page. -- Should have Perfect Forward Secrecy. +- Should have Forward Secrecy. - Should have open-source servers. - Should be decentralized, i.e. federated or P2P. - Should use E2EE for all messages by default. diff --git a/i18n/hi/vpn.md b/i18n/hi/vpn.md index 0a09044d..af4643aa 100644 --- a/i18n/hi/vpn.md +++ b/i18n/hi/vpn.md @@ -279,13 +279,13 @@ A VPN is pointless if it can't even provide adequate security. We require all ou **Minimum to Qualify:** - Strong Encryption Schemes: OpenVPN with SHA-256 authentication; RSA-2048 or better handshake; AES-256-GCM or AES-256-CBC data encryption. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Published security audits from a reputable third-party firm. **Best Case:** - Strongest Encryption: RSA-4096. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Comprehensive published security audits from a reputable third-party firm. - Bug-bounty programs and/or a coordinated vulnerability-disclosure process. diff --git a/i18n/hu/real-time-communication.md b/i18n/hu/real-time-communication.md index f4c2db81..827d3e10 100644 --- a/i18n/hu/real-time-communication.md +++ b/i18n/hu/real-time-communication.md @@ -99,13 +99,13 @@ The client software was independently [audited](https://briarproject.org/news/20 Briar has a fully [published specification](https://code.briarproject.org/briar/briar-spec). -Briar supports perfect forward secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## Additional Options !!! warning - These messengers do not have Perfect [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. ### Element @@ -189,7 +189,7 @@ Session has a [whitepaper](https://arxiv.org/pdf/2002.04609.pdf) describing the Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page. -- Should have Perfect Forward Secrecy. +- Should have Forward Secrecy. - Should have open-source servers. - Should be decentralized, i.e. federated or P2P. - Should use E2EE for all messages by default. diff --git a/i18n/hu/vpn.md b/i18n/hu/vpn.md index 550fbf97..390c9f30 100644 --- a/i18n/hu/vpn.md +++ b/i18n/hu/vpn.md @@ -279,13 +279,13 @@ Egy VPN értelmetlen, ha még megfelelő biztonságot sem tud nyújtani. Minden **Minimális Elvárások:** - Erős Titkosítási Rendszerek: OpenVPN SHA-256 hitelesítssel; RSA-2048 vagy jobb handshake; AES-256-GCM vagy AES-256-CBC adattitkosítás. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Közzétett biztonsági felülvizsgálatok egy megbízható harmadik feles cégtől. **Legjobb Esetben:** - Legerősebb Titkosítás: RSA-4096. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Széleskürű és közzétett biztonsági felülvizsgálatok egy megbízható harmadik feles cégtől. - Bug-bounty programok és/vagy összehangolt sebezhetőség-közzétételi folyamat. diff --git a/i18n/id/real-time-communication.md b/i18n/id/real-time-communication.md index 9fc46b69..efd3570b 100644 --- a/i18n/id/real-time-communication.md +++ b/i18n/id/real-time-communication.md @@ -99,13 +99,13 @@ The client software was independently [audited](https://briarproject.org/news/20 Briar has a fully [published specification](https://code.briarproject.org/briar/briar-spec). -Briar supports perfect forward secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## Additional Options !!! warning - These messengers do not have Perfect [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. ### Element @@ -189,7 +189,7 @@ Session has a [whitepaper](https://arxiv.org/pdf/2002.04609.pdf) describing the Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page. -- Should have Perfect Forward Secrecy. +- Should have Forward Secrecy. - Should have open-source servers. - Should be decentralized, i.e. federated or P2P. - Should use E2EE for all messages by default. diff --git a/i18n/id/vpn.md b/i18n/id/vpn.md index 5a5fdc43..703a0628 100644 --- a/i18n/id/vpn.md +++ b/i18n/id/vpn.md @@ -279,13 +279,13 @@ VPN tidak ada gunanya jika tidak bisa menyediakan keamanan yang memadai. Kami me **Minimum untuk Memenuhi Syarat:** - Skema enkripsi yang kuat: OpenVPN dengan autentikasi SHA-256; RSA-2048 atau jabat tangan yang lebih baik; enkripsi data AES-256-GCM atau AES-256-CBC. -- Kerahasiaan Maju Sempurna (PFS). +- Forward Secrecy. - Audit keamanan yang dipublikasikan dari perusahaan pihak ketiga yang memiliki reputasi baik. **Kasus Terbaik:** - Enkripsi terkuat: RSA-4096. -- Kerahasiaan Maju Sempurna (PFS). +- Forward Secrecy. - Audit keamanan yang dipublikasikan secara komprehensif dari perusahaan pihak ketiga yang memiliki reputasi baik. - Program bug-bounty dan/atau proses pengungkapan kerentanan yang terkoordinasi. diff --git a/i18n/it/real-time-communication.md b/i18n/it/real-time-communication.md index bf9032ee..726124a1 100644 --- a/i18n/it/real-time-communication.md +++ b/i18n/it/real-time-communication.md @@ -99,13 +99,13 @@ Il software per il client è stato [verificato](https://briarproject.org/news/20 Le specifiche di Briar sono [completamente pubbliche](https://code.briarproject.org/briar/briar-spec). -Briar supporta la Perfect Forward Secrecy usando l'[Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) Bramble e il protocollo [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md). +Briar supporta la Forward Secrecy usando l'[Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) Bramble e il protocollo [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md). ## Altre alternative !!! warning "Attenzione" - Questi messenger non hanno la Perfect [Forward Secrecy](https://it.wikipedia.org/wiki/Forward_secrecy) (PFS) e, pur soddisfacendo alcune esigenze che le nostre precedenti raccomandazioni potrebbero non fare, non li consigliamo per comunicazioni a lungo termine o sensibili. Qualsiasi compromissione di chiavi tra i destinatari del messaggio inciderebbe sulla riservatezza di **tutte** le comunicazioni passate. + Questi messenger non utilizzano la [Forward Secrecy](https://it.wikipedia.org/wiki/Forward_secrecy) e anche se soddisfano alcune esigenze che le nostre precedenti raccomandazioni non soddisfano, non le raccomandiamo per le comunicazioni a lungo termine o sensibili. Qualsiasi compromissione di chiavi tra i destinatari del messaggio inciderebbe sulla riservatezza di **tutte** le comunicazioni passate. ### Element @@ -189,7 +189,7 @@ Session ha un [libro bianco](https://arxiv.org/pdf/2002.04609.pdf) che descrive I nostri criteri ottimali rappresentano ciò che vorremmo vedere dal progetto perfetto in questa categoria. Le nostre raccomandazioni potrebbero non includere tutte o alcune di queste funzionalità, ma quelle che le includono potrebbero avere una posizione più alta rispetto ad altre in questa pagina. -- Deve avere la Perfect Forward Secrecy. +- Dovrebbe avere la Forward Secrecy. - Deve avere server open source. - Deve essere decentralizzato, cioè federato o P2P. - Deve usare E2EE per tutti i messaggi in modo predefinito. diff --git a/i18n/it/vpn.md b/i18n/it/vpn.md index c6d0aa27..78b9c00b 100644 --- a/i18n/it/vpn.md +++ b/i18n/it/vpn.md @@ -279,13 +279,13 @@ Una VPN è inutile se non è nemmeno in grado di fornire una sicurezza adeguata. **Requisiti minimi:** - Schemi di crittografia forti: OpenVPN con autenticazione SHA-256; handshake RSA-2048 o migliore; crittografia dei dati AES-256-GCM o AES-256-CBC. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Audit sulla sicurezza pubblicati da un'azienda terza affidabile. **Caso migliore:** - Crittografia più forte: RSA-4096. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Audit sulla sicurezza completi pubblicati da un'azienda terza affidabile. - Programmi di bug-bounty e/o un processo coordinato di divulgazione delle vulnerabilità. diff --git a/i18n/ja/real-time-communication.md b/i18n/ja/real-time-communication.md index a9ff7c8e..e20278b7 100644 --- a/i18n/ja/real-time-communication.md +++ b/i18n/ja/real-time-communication.md @@ -99,13 +99,13 @@ The client software was independently [audited](https://briarproject.org/news/20 Briar has a fully [published specification](https://code.briarproject.org/briar/briar-spec). -Briar supports perfect forward secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## 追加のオプション !!! warning - These messengers do not have Perfect [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. ### Element @@ -189,7 +189,7 @@ Session has a [whitepaper](https://arxiv.org/pdf/2002.04609.pdf) describing the Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page. -- Should have Perfect Forward Secrecy. +- Should have Forward Secrecy. - Should have open-source servers. - Should be decentralized, i.e. federated or P2P. - Should use E2EE for all messages by default. diff --git a/i18n/ja/vpn.md b/i18n/ja/vpn.md index 1f34e22b..d9aa4cf3 100644 --- a/i18n/ja/vpn.md +++ b/i18n/ja/vpn.md @@ -279,13 +279,13 @@ A VPN is pointless if it can't even provide adequate security. We require all ou **Minimum to Qualify:** - Strong Encryption Schemes: OpenVPN with SHA-256 authentication; RSA-2048 or better handshake; AES-256-GCM or AES-256-CBC data encryption. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Published security audits from a reputable third-party firm. **Best Case:** - Strongest Encryption: RSA-4096. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Comprehensive published security audits from a reputable third-party firm. - Bug-bounty programs and/or a coordinated vulnerability-disclosure process. diff --git a/i18n/ko/real-time-communication.md b/i18n/ko/real-time-communication.md index c72f8c9a..a6026dd4 100644 --- a/i18n/ko/real-time-communication.md +++ b/i18n/ko/real-time-communication.md @@ -99,13 +99,13 @@ Briar 연락처에 누군가를 등록하려면 서로가 모두 서로를 연 Briar [사양 문서](https://code.briarproject.org/briar/briar-spec)는 전체 공개되어 있습니다. -Briar는 Bramble [핸드셰이크](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) 및 [전송](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) 프로토콜을 사용해 완전 순방향 비밀성을 지원합니다. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## 추가 선택지 !!! warning "경고" - 이러한 메신저는 [완전 순방향 비밀성](https://en.wikipedia.org/wiki/Forward_secrecy)(PFS, Perfect Forward Secrecy)을 지원하지 않습니다. 이 중에는 앞서 권장드린 메신저가 지원하지 않는 요구 사항을 만족하는 것도 있지만, 장기적인 사용이나 민감한 대화를 나누는 용도로 사용하는 것은 권장드리지 않습니다. 대화 참여자 중 한 명만 키가 유출되더라도 이전에 주고받은 **모든** 메시지의 기밀성이 손상됩니다. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. 대화 참여자 중 한 명만 키가 유출되더라도 이전에 주고받은 **모든** 메시지의 기밀성이 손상됩니다. ### Element @@ -189,7 +189,7 @@ Session은 애플리케이션 및 프로토콜의 기술적인 설명을 담은 평가 기준에서 '우대 사항'은 해당 부문에서 완벽한 프로젝트에 기대하는 바를 나타냅니다. 다음의 우대 사항에 해당하지 않더라도 권장 목록에 포함될 수 있습니다. 단, 우대 사항에 해당할수록 이 페이지의 다른 항목보다 높은 순위를 갖습니다. -- 완전 순방향 비밀성(Perfect Forward Secrecy)을 보장해야 합니다. +- Should have Forward Secrecy. - 오픈 소스 서버가 있어야 합니다. - 탈중앙 방식(연합 방식/P2P 방식)이어야 합니다. - 모든 메시지에 E2EE가 기본 적용이어야 합니다. diff --git a/i18n/ko/vpn.md b/i18n/ko/vpn.md index 2e0129b7..24a55390 100644 --- a/i18n/ko/vpn.md +++ b/i18n/ko/vpn.md @@ -279,13 +279,13 @@ We prefer our recommended providers to collect as little data as possible. Not c **최소 요구 사항:** - 강력한 암호화 방식 사용: SHA-256 해시 기반 인증을 이용하는 OpenVPN, RSA-2048 또는 더 강력한 비대칭 암호 알고리즘을 이용하는 핸드셰이크, AES-256-GCM 또는 AES-256-CBC 를 이용하는 데이터 암호화 -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - 검증된 제 3자로부터 보안 감사 결과가 게시됨 **우대 사항:** - 가장 강력한 암호화 방식으로 RSA-4096을 지원 -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - 검증된 제 3자로부터 종합적인 보안 감사 결과가 게시됨 - 버그 바운티 프로그램 또는 체계적인 취약점 공개 프로세스가 있음 diff --git a/i18n/ku-IQ/real-time-communication.md b/i18n/ku-IQ/real-time-communication.md index 9fc46b69..efd3570b 100644 --- a/i18n/ku-IQ/real-time-communication.md +++ b/i18n/ku-IQ/real-time-communication.md @@ -99,13 +99,13 @@ The client software was independently [audited](https://briarproject.org/news/20 Briar has a fully [published specification](https://code.briarproject.org/briar/briar-spec). -Briar supports perfect forward secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## Additional Options !!! warning - These messengers do not have Perfect [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. ### Element @@ -189,7 +189,7 @@ Session has a [whitepaper](https://arxiv.org/pdf/2002.04609.pdf) describing the Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page. -- Should have Perfect Forward Secrecy. +- Should have Forward Secrecy. - Should have open-source servers. - Should be decentralized, i.e. federated or P2P. - Should use E2EE for all messages by default. diff --git a/i18n/ku-IQ/vpn.md b/i18n/ku-IQ/vpn.md index baaf986f..547b9b27 100644 --- a/i18n/ku-IQ/vpn.md +++ b/i18n/ku-IQ/vpn.md @@ -279,13 +279,13 @@ A VPN is pointless if it can't even provide adequate security. We require all ou **Minimum to Qualify:** - Strong Encryption Schemes: OpenVPN with SHA-256 authentication; RSA-2048 or better handshake; AES-256-GCM or AES-256-CBC data encryption. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Published security audits from a reputable third-party firm. **Best Case:** - Strongest Encryption: RSA-4096. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Comprehensive published security audits from a reputable third-party firm. - Bug-bounty programs and/or a coordinated vulnerability-disclosure process. diff --git a/i18n/nl/real-time-communication.md b/i18n/nl/real-time-communication.md index de77f7be..57678dce 100644 --- a/i18n/nl/real-time-communication.md +++ b/i18n/nl/real-time-communication.md @@ -99,13 +99,13 @@ De clientsoftware was onafhankelijk [gecontroleerd](https://briarproject.org/new Briar heeft een volledig [gepubliceerde specificatie](https://code.briarproject.org/briar/briar-spec). -Briar ondersteunt perfect forward secrecy door het gebruik van jet Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) en [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## Aanvullende opties !!! warning - Deze boodschappers hebben geen Perfect [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS), en hoewel zij in bepaalde behoeften voorzien die onze vorige aanbevelingen niet hebben, bevelen wij ze niet aan voor langdurige of gevoelige communicatie. Elke compromittering van sleutels tussen ontvangers van berichten zou de vertrouwelijkheid van **alle** eerdere communicaties aantasten. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Elke compromittering van sleutels tussen ontvangers van berichten zou de vertrouwelijkheid van **alle** eerdere communicaties aantasten. ### Element @@ -189,7 +189,7 @@ Session heeft een [whitepaper](https://arxiv.org/pdf/2002.04609.pdf) die de tech Onze best-case criteria geven aan wat wij zouden willen zien van het perfecte project in deze categorie. Het is mogelijk dat onze aanbevelingen geen of niet alle functies bevatten, maar degene die dat wel doen kunnen hoger gerangschikt worden dan andere op deze pagina. -- Moet Perfect Forward Secrecy hebben. +- Should have Forward Secrecy. - Moet open-source servers hebben. - Moet gedecentraliseerd zijn, d.w.z. gefedereerd of P2P. - Moet standaard E2EE gebruiken voor privé-berichten. diff --git a/i18n/nl/vpn.md b/i18n/nl/vpn.md index 1beca54c..e9933d52 100644 --- a/i18n/nl/vpn.md +++ b/i18n/nl/vpn.md @@ -279,13 +279,13 @@ Een VPN is zinloos als het niet eens voldoende beveiliging kan bieden. Wij eisen **Minimum om in aanmerking te komen:** - Sterke coderingsschema's: OpenVPN met SHA-256 authenticatie; RSA-2048 of betere handshake; AES-256-GCM of AES-256-CBC data-encryptie. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Gepubliceerde veiligheidscontroles van een gerenommeerde derde partij. **Beste geval:** - Sterkste encryptie: RSA-4096. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Uitgebreide gepubliceerde veiligheidscontroles door een gerenommeerde derde partij. - Programma's voor bug-bounty's en/of een gecoördineerd proces voor de openbaarmaking van kwetsbaarheden. diff --git a/i18n/pl/real-time-communication.md b/i18n/pl/real-time-communication.md index ccd86cb4..0dff66a0 100644 --- a/i18n/pl/real-time-communication.md +++ b/i18n/pl/real-time-communication.md @@ -99,13 +99,13 @@ The client software was independently [audited](https://briarproject.org/news/20 Briar has a fully [published specification](https://code.briarproject.org/briar/briar-spec). -Briar supports perfect forward secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## Additional Options !!! warning - These messengers do not have Perfect [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. ### Element @@ -189,7 +189,7 @@ Session has a [whitepaper](https://arxiv.org/pdf/2002.04609.pdf) describing the Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page. -- Should have Perfect Forward Secrecy. +- Should have Forward Secrecy. - Should have open-source servers. - Should be decentralized, i.e. federated or P2P. - Should use E2EE for all messages by default. diff --git a/i18n/pl/vpn.md b/i18n/pl/vpn.md index 89e158c7..261592f4 100644 --- a/i18n/pl/vpn.md +++ b/i18n/pl/vpn.md @@ -279,13 +279,13 @@ A VPN is pointless if it can't even provide adequate security. We require all ou **Minimum to Qualify:** - Strong Encryption Schemes: OpenVPN with SHA-256 authentication; RSA-2048 or better handshake; AES-256-GCM or AES-256-CBC data encryption. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Published security audits from a reputable third-party firm. **Best Case:** - Strongest Encryption: RSA-4096. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Comprehensive published security audits from a reputable third-party firm. - Bug-bounty programs and/or a coordinated vulnerability-disclosure process. diff --git a/i18n/pt-BR/real-time-communication.md b/i18n/pt-BR/real-time-communication.md index 9d725e0c..c3864f01 100644 --- a/i18n/pt-BR/real-time-communication.md +++ b/i18n/pt-BR/real-time-communication.md @@ -99,13 +99,13 @@ The client software was independently [audited](https://briarproject.org/news/20 Briar has a fully [published specification](https://code.briarproject.org/briar/briar-spec). -Briar supports perfect forward secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## Additional Options !!! warning - These messengers do not have Perfect [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. ### Element @@ -189,7 +189,7 @@ Session has a [whitepaper](https://arxiv.org/pdf/2002.04609.pdf) describing the Nosso critério de melhor caso representa o que gostaríamos de ver em um projeto perfeito nessa categoria. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page. -- Should have Perfect Forward Secrecy. +- Should have Forward Secrecy. - Should have open-source servers. - Should be decentralized, i.e. federated or P2P. - Should use E2EE for all messages by default. diff --git a/i18n/pt-BR/vpn.md b/i18n/pt-BR/vpn.md index 3b91414c..442f9fb7 100644 --- a/i18n/pt-BR/vpn.md +++ b/i18n/pt-BR/vpn.md @@ -279,13 +279,13 @@ Uma VPN é inútil se não puder fornecer nem mesmo a segurança adequada. Exigi **Mínimo Para Qualificação:** - Esquemas de Criptografia Fortes: OpenVPN com autenticação SHA-256; handshake RSA-2048 ou melhor; criptografia de dados AES-256-GCM ou AES-256-CBC. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Auditorias de segurança publicadas por uma empresa terceirizada de boa reputação. **Melhor Caso:** - Criptografia Mais Forte: RSA-4096. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Auditorias abrangentes de segurança publicadas por uma empresa terceirizada de boa reputação. - Programas de recompensa por bugs e/ou um processo coordenado de divulgação de vulnerabilidades. diff --git a/i18n/pt/basics/account-deletion.md b/i18n/pt/basics/account-deletion.md index 81b61988..18adb2af 100644 --- a/i18n/pt/basics/account-deletion.md +++ b/i18n/pt/basics/account-deletion.md @@ -23,7 +23,7 @@ Desktop platforms also often have a password manager which may help you recover - Windows [Credential Manager](https://support.microsoft.com/en-us/windows/accessing-credential-manager-1b5c916a-6a16-889f-8581-fc16e8165ac0) - macOS [Passwords](https://support.apple.com/en-us/HT211145) - iOS [Passwords](https://support.apple.com/en-us/HT211146) -- Linux, Gnome Keyring, which can be accessed through [Seahorse](https://wiki.gnome.org/Apps/Seahorse) or [KDE Wallet Manager](https://userbase.kde.org/KDE_Wallet_Manager) +- Linux, Gnome Keyring, que pode ser acedido através de [Seahorse](https://wiki.gnome.org/Apps/Seahorse) ou [KDE Wallet Manager](https://userbase.kde.org /KDE_Wallet_Manager) ### E-mail diff --git a/i18n/pt/basics/common-threats.md b/i18n/pt/basics/common-threats.md index 443e2023..b19c9f74 100644 --- a/i18n/pt/basics/common-threats.md +++ b/i18n/pt/basics/common-threats.md @@ -119,31 +119,30 @@ A melhor forma de manter os seus dados privados é simplesmente não os tornar p - [Veja o nosso guia sobre a eliminação de contas :material-arrow-right-drop-circle:](account-deletion.md) -On sites where you do share information, checking the privacy settings of your account to limit how widely that data is spread is very important. For example, enable "private mode" on your accounts if given the option: This ensures that your account isn't being indexed by search engines, and that it can't be viewed without your permission. +Nos sites onde partilha informações, é muito importante verificar as definições de privacidade da sua conta, de forma a limitar a divulgação desses dados. Por exemplo, ative o "modo privado" nas suas contas, se tiver essa opção: assim, garante que a sua conta não está a ser indexada pelos motores de busca e que não pode ser visualizada sem a sua autorização. -If you've already submitted your real information to sites which shouldn't have it, consider using disinformation tactics, like submitting fictitious information related to that online identity. This makes your real information indistinguishable from the false information. +Se já submeteu as suas informações reais a sites que não as deveriam ter, considere a possibilidade de utilizar táticas de desinformação, como submeter informações fictícias relacionadas com essa identidade online. Isso torna as suas informações reais indistinguíveis das falsas. -## Avoiding Censorship +## Evitar a Censura -:material-close-outline: Censorship +:material-close-outline: Censura -Censorship online can be carried out (to varying degrees) by actors including totalitarian governments, network administrators, and service providers. These efforts to control communication and restrict access to information will always be incompatible with the human right to Freedom of Expression.[^5] +A censura online pode ser realizada (em diferentes graus) por diversos atores, incluindo governos totalitários, administradores de redes e prestadores de serviços. Estes esforços para controlar a comunicação e restringir o acesso à informação serão sempre incompatíveis com o direito humano à liberdade de expressão.[^5] -Censorship on corporate platforms is increasingly common, as platforms like Twitter and Facebook give in to public demand, market pressures, and pressures from government agencies. Government pressures can be covert requests to businesses, such as the White House [requesting the takedown](https://www.nytimes.com/2012/09/17/technology/on-the-web-a-fine-line-on-free-speech-across-globe.html) of a provocative YouTube video, or overt, such as the Chinese government requiring companies to adhere to a strict regime of censorship. +A censura nas plataformas corporativas é cada vez mais comum, uma vez que plataformas como o Twitter e o Facebook cedem à procura pública, às pressões do mercado e às pressões das agências governamentais. As pressões do governo podem ser solicitações dissimuladas a empresas, como no caso em que a Casa Branca [solicitou a retirada](https://www.nytimes.com/2012/09/17/technology/on-the-web-a-fine-line-on-free-speech-across-globe.html) de um vídeo provocador do YouTube, ou, de forma evidente, quando o Governo chinês exige que as empresas respeitem um regime rigoroso de censura. -People concerned with the threat of censorship can use technologies like [Tor](../advanced/tor-overview.md) to circumvent it, and support censorship-resistant communication platforms like [Matrix](../real-time-communication.md#element), which doesn't have a centralized account authority that can close accounts arbitrarily. +As pessoas que se preocupam com a ameaça da censura podem usar tecnologias como o [Tor](../advanced/tor-overview.md) para contorná-la, e utilizar plataformas de comunicação resistentes à censura, como o [Matrix](../real-time-communication.md#element), que não tem uma autoridade de conta centralizada que pode fechar as contas arbitrariamente. -!!! aviso - Backup `BitLocker-Recovery-Key.txt` em um dispositivo de armazenamento separado. +!!! dica - While evading censorship itself can be easy, hiding the fact that you are doing it can be very problematic. + Enquanto evitar a censura em si pode ser fácil, esconder esse facto pode ser muito problemático. - You should consider which aspects of the network your adversary can observe, and whether you have plausible deniability for your actions. For example, using [encrypted DNS](../advanced/dns-overview.md#what-is-encrypted-dns) can help you bypass rudimentary, DNS-based censorship systems, but it can't truly hide what you are visiting from your ISP. A VPN or Tor can help hide what you are visiting from network administrators, but can't hide that you're using those networks in the first place. Pluggable transports (such as Obfs4proxy, Meek, or Shadowsocks) can help you evade firewalls that block common VPN protocols or Tor, but your circumvention attempts can still be detected by methods like probing or [deep packet inspection](https://en.wikipedia.org/wiki/Deep_packet_inspection). + Deve considerar quais os aspetos da rede que o seu adversário pode observar e se tem negação plausível das suas ações. Por exemplo, usar [DNS criptografado](../advanced/dns-overview.md#what-is-encrypted-dns) pode ajudá-lo a contornar sistemas rudimentares de censura baseados em DNS, mas não pode realmente esconder as suas atividades online do seu ISP. Uma VPN ou o Tor podem ajudar a esconder o que está a visitar dos administradores de rede, mas não pode esconder o facto de estar a usar essas redes. Transportes conectáveis (como Obfs4proxy, Meek ou Shadowsocks) podem ajudá-lo a evitar firewalls que bloqueiam protocolos VPN comuns ou Tor, mas as suas tentativas de contornar o problema podem ser detetadas através de métodos como sondagem ou [inspeção profunda de pacotes](https://en. wikipedia.org/wiki/Deep_packet_inspection). -You must always consider the risks of trying to bypass censorship, the potential consequences, and how sophisticated your adversary may be. You should be cautious with your software selection, and have a backup plan in case you are caught. +Deve sempre considerar os riscos de tentar contornar a censura, as possíveis consequências e o quão sofisticado o seu adversário pode ser. Deve ser cauteloso com a sua seleção de software e ter um plano de backup, caso seja apanhado. -[^1]: Wikipedia: [*Mass Surveillance*](https://en.wikipedia.org/wiki/Mass_surveillance) and [*Surveillance*](https://en.wikipedia.org/wiki/Surveillance). -[^2]: United States Privacy and Civil Liberties Oversight Board: [*Report on the Telephone Records Program Conducted under Section 215*](https://documents.pclob.gov/prod/Documents/OversightReport/ec542143-1079-424a-84b3-acc354698560/215-Report_on_the_Telephone_Records_Program.pdf) -[^3]: Wikipedia: [*Surveillance capitalism*](https://en.wikipedia.org/wiki/Surveillance_capitalism) -[^4]: "[Enumerating badness](https://www.ranum.com/security/computer_security/editorials/dumb/)" (or, "listing all the bad things that we know about"), as many adblockers and antivirus programs do, fails to adequately protect you from new and unknown threats because they have not yet been added to the filter list. You should also employ other mitigation techniques. -[^5]: United Nations: [*Universal Declaration of Human Rights*](https://www.un.org/en/about-us/universal-declaration-of-human-rights). +[^1]: Wikipedia: [*Vigilância em massa*](https://en.wikipedia.org/wiki/Mass_surveillance) e [*Vigilância*](https: //en.wikipedia.org/wiki/Surveillance). +[^2]: Conselho de Supervisão de Privacidade e Liberdades Civis dos Estados Unidos: [*Relatório sobre o Programa de Registos Telefónicos Conduzido ao abrigo da Secção 215*](https://documents.pclob.gov/prod/Documents/OversightReport/ec542143-1079-424a-84b3-acc354698560/215-Report_on_the_Telephone_Records_Program.pdf) +[^3]: Wikipedia: [*Capitalismo de vigilância<*](https://en.wikipedia.org/wiki/Surveillance_capitalism) +[^4]: "[Enumerar maldades](https://www.ranum.com/security/computer_security/editorials/dumb/)" (ou "listar todas as coisas más que conhecemos"), como muitos bloqueadores de anúncios e programas antivírus, não o protegem adequadamente contra novas ameaças ou ameaças desconhecidas, dado estas aindam não terem sido adicionadas à lista de filtros. Deve empregar outras técnicas de mitigação. +[^5]: Nações Unidas: [*Declaração Universal dos Direitos Humanos *](https://www.un.org/en/about-us/universal-declaration-of-human-rights). diff --git a/i18n/pt/basics/threat-modeling.md b/i18n/pt/basics/threat-modeling.md index 7b10a724..701291e2 100644 --- a/i18n/pt/basics/threat-modeling.md +++ b/i18n/pt/basics/threat-modeling.md @@ -1,23 +1,23 @@ --- -meta_title: "Threat Modeling: The First Step on Your Privacy Journey - Privacy Guides" -title: "evergreen" +meta_title: "Modelo de ameaças: o primeiro passo na sua jornada de privacidade - Privacy Guides" +title: "Modelo de ameaças" icon: 'O que são modelos de ameaça?' -description: Balancing security, privacy, and usability is one of the first and most difficult tasks you'll face on your privacy journey. +description: Equilibrar segurança, privacidade e usabilidade é uma das primeiras e mais difíceis tarefas que enfrentará na sua jornada de privacidade. --- -Balancing security, privacy, and usability is one of the first and most difficult tasks you'll face on your privacy journey. Everything is a trade-off: The more secure something is, the more restricting or inconvenient it generally is, etc. Often, people find that the problem with the tools they see recommended is that they're just too hard to start using! +Equilibrar segurança, privacidade e usabilidade é uma das primeiras e mais difíceis tarefas que enfrentará na sua jornada de privacidade. Tudo implica cedências: quanto mais seguro algo é, mais restritivo ou inconveniente é geralmente, etc. Muitas vezes, as pessoas descobrem que o problema com as ferramentas que consideram recomendadas é que são muito difíceis de começar a usar! -Se você quisesse usar o **mais** ferramentas seguras disponíveis, você teria que sacrificar *muito* de usabilidade. And, even then, ==nothing is ever fully secure.== There's **high** security, but never **full** security. É por isso que os modelos de ameaça são importantes. +Se quisesse usar as ferramentas **mais** seguras disponíveis, teria que sacrificar *muito* a usabilidade. E, mesmo assim, ==nada é totalmente seguro.== Há **alta** segurança, mas nunca **total** segurança. É por isso que os modelos de ameaça são importantes. -**So, what are these threat models, anyway?** +**Então, quais são esses modelos de ameaças, afinal?** -==A threat model is a list of the most probable threats to your security and privacy endeavors.== Since it's impossible to protect yourself against **every** attack(er), you should focus on the **most probable** threats. In computer security, a threat is an event that could undermine your efforts to stay private and secure. +==Um modelo de ameaças é uma lista das ameaças mais prováveis aos seus empreendimentos de segurança e privacidade.== Como é impossível proteger-se contra **cada** ataque (ou atacante), deve-se concentrar nas ameaças **mais prováveis**. Na segurança do computador, uma ameaça é um evento que pode minar os seus esforços para permanecer privado e seguro. -Focusing on the threats that matter to you narrows down your thinking about the protection you need, so you can choose the tools that are right for the job. +Concentrar-se nas ameaças que são importantes para si, reduz a quantidade de reflexão e pensamento destinados à proteção necessária, para que possa escolher as ferramentas certas para o trabalho que pretende realizar. -## Creating Your Threat Model +## Crie o seu modelo de ameaças -To identify what could happen to the things you value and determine from whom you need to protect them, you should answer these five questions: +Para identificar o que pode acontecer às coisas que valoriza e determinar de quem precisa de as proteger, responda a estas cinco perguntas: 1. O que é que eu quero proteger? 2. De quem eu quero protegê-lo? @@ -27,85 +27,85 @@ To identify what could happen to the things you value and determine from whom yo ### O que é que eu quero proteger? -Um "bem" é algo que você valoriza e quer proteger. In the context of digital security, ==an asset is usually some kind of information.== For example, your emails, contact lists, instant messages, location, and files are all possible assets. Os seus próprios dispositivos também podem ser bens. +Um "bem" é algo que você valoriza e quer proteger. No contexto da segurança digital, ==um ativo é geralmente algum tipo de informação.== Por exemplo, os seus e-mails, listas de contactos, mensagens instantâneas ou localização e arquivos são todos ativos possíveis. Os seus próprios dispositivos também podem ser bens. -*Faça uma lista dos seus bens: dados que você guarda, onde são guardados, quem tem acesso a eles e o que impede outros de acederem a eles.* +*Faça uma lista dos seus bens: dados que guarda, onde são guardados, quem tem acesso a eles e o que impede outros de lhes acederem.* ### De quem eu quero protegê-lo? -Para responder a esta pergunta, é importante identificar quem pode querer ter como alvo você ou suas informações. ==A person or entity that poses a threat to your assets is an “adversary”.== Examples of potential adversaries are your boss, your former partner, your business competition, your government, or a hacker on a public network. +Para responder a esta pergunta, é importante identificar quem pode querer ter como alvo você ou as suas informações. ==Uma pessoa ou entidade que representa uma ameaça aos seus ativos é um “adversário”.== Exemplos de potenciais adversários são o seu chefe, o seu ex-parceiro, o seu concorrente comercial, o seu governo ou um hacker numa rede pública. -*Make a list of your adversaries or those who might want to get ahold of your assets. A sua lista pode incluir indivíduos, uma agência governamental ou corporações.* +*Faça uma lista dos seus adversários ou daqueles que podem querer apropriar-se dos seus ativos. A sua lista pode incluir indivíduos, agências governamentais ou corporações.* -Depending on who your adversaries are, under some circumstances, this list might be something you want to destroy after you're done security planning. +Dependendo de quem são os seus adversários, em algumas circunstâncias, essa lista pode ser algo que vai querer destruir depois de concluir o planeamento de segurança. ### Qual é a probabilidade de eu precisar de o proteger? -==Risk is the likelihood that a particular threat against a particular asset will actually occur.== It goes hand-in-hand with capability. Embora a sua operadora de celular tenha a capacidade de acessar todos os seus dados, o risco de que eles coloquem seus dados particulares online para prejudicar sua reputação é baixo. +==Risco é a probabilidade de que uma ameaça específica contra um ativo específico realmente ocorra.== Ele anda de mãos dadas com a capacidade. Embora a sua operadora de telemóvel tenha a capacidade de aceder a todos os seus dados, o risco de que eles coloquem os seus dados particulares online para prejudicar a sua reputação é baixo. -É importante distinguir entre o que pode acontecer e a probabilidade de acontecer. Por exemplo, há uma ameaça de colapso do seu edifício, mas o risco de isso acontecer é muito maior em São Francisco (onde os terremotos são comuns) do que em Estocolmo (onde eles não são). +É importante distinguir entre o que pode acontecer e a probabilidade de acontecer. Por exemplo, há uma ameaça de colapso do seu edifício, mas o risco de isso acontecer é muito maior em São Francisco (onde os terramotos são comuns) do que em Estocolmo (onde são raros). -Assessing risks is both a personal and subjective process. Many people find certain threats unacceptable, no matter the likelihood they will occur, because the mere presence of the threat is not worth the cost. Em outros casos, as pessoas desconsideram os altos riscos porque não vêem a ameaça como um problema. +A avaliação de riscos é um processo pessoal e subjetivo. Muitas pessoas consideram certas ameaças inaceitáveis, independentemente da probabilidade de ocorrência, porque a mera presença da ameaça não vale o custo. Noutros casos, as pessoas desconsideram os altos riscos, porque não veem a ameaça como um problema. -*Escreva quais ameaças você vai levar a sério, e quais podem ser muito raras ou inofensivas (ou muito difíceis de combater) para se preocupar.* +*Escreva quais as ameaças que leva a sério, e quais as que podem ser muito raras ou inofensivas (ou muito difíceis de combater).* ### Quão más são as consequências se eu falhar? -Há muitas maneiras de um adversário poder ter acesso aos seus dados. Por exemplo, um adversário pode ler suas comunicações privadas enquanto elas passam pela rede, ou podem apagar ou corromper seus dados. +Há muitas formas de um adversário poder ter acesso aos seus dados. Por exemplo, um adversário pode ler as suas comunicações privadas no momento em que elas passam pela rede, e podem apagar ou corromper os seus dados. -==The motives of adversaries differ widely, as do their tactics.== A government trying to prevent the spread of a video showing police violence may be content to simply delete or reduce the availability of that video. Em contraste, um adversário político pode desejar ter acesso a conteúdo secreto e publicar esse conteúdo sem que você saiba. +==Os motivos dos adversários diferem amplamente, assim como as suas táticas.== Um governo que tenta impedir a disseminação de um vídeo que mostra violência policial, pode-se contentar em simplesmente apagá-lo ou reduzir a disponibilidade desse vídeo. Em contraste, um adversário político pode desejar ter acesso a conteúdo secreto e publicar esse conteúdo sem que disso dê conta. -O planejamento de segurança envolve compreender quão ruins podem ser as conseqüências se um adversário conseguir ter acesso a um de seus ativos. Para determinar isso, você deve considerar a capacidade do seu adversário. For example, your mobile phone provider has access to all of your phone records. Um hacker em uma rede Wi-Fi aberta pode acessar suas comunicações não criptografadas. O seu governo pode ter capacidades mais fortes. +O planeamento de segurança envolve compreender quão más podem ser as consequências se um adversário conseguir ter acesso a um dos seus ativos. Para determinar isso, deve considerar a capacidade do seu adversário. Por exemplo, a sua operadora de telemóvel tem acesso a todos os seus registos telefónicos. Um hacker numa rede Wi-Fi aberta pode aceder às suas comunicações não encriptadas. O seu governo pode ter capacidades mais fortes. *Escreva o que o seu adversário pode querer fazer com os seus dados privados.* ### Quantos problemas estou disposto a enfrentar para tentar evitar possíveis consequências? -==There is no perfect option for security.== Not everyone has the same priorities, concerns, or access to resources. Sua avaliação de risco lhe permitirá planejar a estratégia certa para você, equilibrando conveniência, custo e privacidade. +==Não há opção perfeita para a segurança.== Nem todos têm as mesmas prioridades, preocupações ou acesso aos recursos. A avaliação de risco permitir-lhe-á planear a estratégia certa, equilibrando conveniência, custo e privacidade. -Por exemplo, um advogado que representa um cliente em um caso de segurança nacional pode estar disposto a ir mais longe para proteger as comunicações sobre esse caso, como o uso de e-mail criptografado, do que uma mãe que envia regularmente e-mails com vídeos engraçados de gatos para sua filha. +Por exemplo, um advogado que representa um cliente num caso de segurança nacional pode estar disposto a ir mais longe para proteger as comunicações sobre esse caso, como o uso de e-mail encriptado, do que uma mãe que envia regularmente e-mails com vídeos engraçados de gatos para a sua filha. -*Escreva as opções que você tem disponíveis para ajudar a mitigar suas ameaças únicas. Observe se você tem alguma restrição financeira, técnica ou social.* +*Escreva as opções que você tem disponíveis para ajudar a mitigar as suas ameaças únicas. Verifique se tem alguma restrição financeira, técnica ou social.* -### Try it yourself: Protecting Your Belongings +### Experimente você mesmo: Proteger os seus bens -These questions can apply to a wide variety of situations, online and offline. As a generic demonstration of how these questions work, let's build a plan to keep your house and possessions safe. +Estas perguntas podem aplicar-se a uma ampla variedade de situações, online e offline. Numa demonstração genérica de como estas questões funcionam, vamos construir um plano para manter a sua casa e os seus bens seguros. -**O que você quer proteger? (Ou, *o que é que você tem que vale a pena proteger?*)** +**O que deseja proteger? (Ou, *o que é que tem que vale a pena proteger?*)** : -Seus bens podem incluir jóias, eletrônicos, documentos importantes ou fotos. +Os seus bens podem incluir joias, aparelhos eletrónicos, documentos importantes ou fotos. -**De quem você quer protegê-lo?** +**De quem quer protegê-los?** : Os seus adversários podem incluir assaltantes, companheiros de quarto ou convidados. -**Qual é a probabilidade de precisar de o proteger?** +**Qual é a probabilidade de precisar de os proteger?** : -O seu bairro tem um histórico de assaltos? How trustworthy are your roommates or guests? Quais são as capacidades dos seus adversários? Quais são os riscos que você deve considerar? +O seu bairro tem um histórico de assaltos? Quão confiáveis são os seus colegas de quarto ou convidados? Quais são as capacidades dos seus adversários? Quais são os riscos que deve considerar? **Quão más são as consequências se falhar?** : -Tem alguma coisa na sua casa que não possa substituir? Do you have the time or money to replace those things? Você tem um seguro que cobre bens roubados de sua casa? +Tem alguma coisa na sua casa que não possa substituir? Tem tempo ou dinheiro para substituir essas coisas? Tem um seguro de casa que cubra roubo de bens? -**Quantos problemas você está disposto a passar para evitar essas consequências?** +**Quantos problemas está disposto a passar para evitar essas consequências?** : -Você está disposto a comprar um cofre para documentos sensíveis? Tem dinheiro para comprar um cadeado de alta qualidade? Tem tempo para abrir uma caixa de segurança no seu banco local e guardar lá os seus valores? +Está disposto a comprar um cofre para documentos sensíveis? Tem dinheiro para comprar um aloquete de alta qualidade? Tem tempo para abrir uma caixa de segurança no seu banco e guardar lá os seus valores? -Só depois de se ter feito estas perguntas é que estará em condições de avaliar que medidas tomar. Se os seus bens são valiosos, mas a probabilidade de um arrombamento é baixa, então você pode não querer investir muito dinheiro numa fechadura. But, if the probability of a break-in is high, you'll want to get the best lock on the market and consider adding a security system. +Só depois de se ter feito estas perguntas é que estará em condições de avaliar que medidas tomar. Se os seus bens são valiosos, mas a probabilidade de um arrombamento é baixa, então poderá não querer investir muito dinheiro numa fechadura. Mas, se a probabilidade de arrombamento for alta, convém obter a melhor fechadura do mercado e considerar a instalação de um sistema de segurança. -Fazer um plano de segurança o ajudará a entender as ameaças que são únicas para você e a avaliar seus ativos, seus adversários e as capacidades de seus adversários, juntamente com a probabilidade de riscos que você enfrenta. +Fazer um plano de segurança ajudá-lo-á a entender as ameaças que são únicas e a avaliar os seus ativos, os seus adversários e as capacidades dos seus adversários, juntamente com a probabilidade de riscos que enfrenta. ## Leitura Adicional -For people looking to increase their privacy and security online, we've compiled a list of common threats our visitors face or goals our visitors have, to give you some inspiration and demonstrate the basis of our recommendations. +Para as pessoas que procuram aumentar a sua privacidade e segurança online, compilámos uma lista de ameaças comuns que os nossos visitantes enfrentam ou objetivos que nossos visitantes têm, para lhe dar alguma inspiração e demonstrar a base das nossas recomendações. -- [Common Goals and Threats :material-arrow-right-drop-circle:](common-threats.md) +- [Objetivos e ameaças comuns :material-arrow-right-drop-circle:](common-threats.md) ## Fontes -- [Autodefesa de Vigilância EFF: Seu Plano de Segurança](https://ssd.eff.org/en/module/your-security-plan) +- [Autodefesa de Vigilância EFF: O seu Plano de Segurança](https://ssd.eff.org/en/module/your-security-plan) diff --git a/i18n/pt/basics/why-privacy-matters.md b/i18n/pt/basics/why-privacy-matters.md index afe1e72d..7004e02a 100644 --- a/i18n/pt/basics/why-privacy-matters.md +++ b/i18n/pt/basics/why-privacy-matters.md @@ -1,20 +1,20 @@ --- -title: "Why Privacy Matters" +title: "Porque é que a privacidade é importante" icon: 'material/shield-account' --- -In the modern age of digital data exploitation, your privacy has never been more critical, and yet many believe it is already a lost cause. It is not. ==Your privacy is up for grabs==, and you need to care about it. Privacy is about power, and it is so important that this power ends up in the right hands. +Na era moderna da exploração dos dados digitais, a sua privacidade nunca foi tão crítica e, mesmo assim, muitos acreditam que já é uma causa perdida. Não é. ==A sua privacidade está em jogo==, e precisa de se preocupar com isso. A privacidade tem a ver com poder, e é muito importante que esse poder esteja nas mãos certas. -Privacy is ultimately about human information, and this is important because we know that human information confers power over human beings. If we care about our ability to be authentic, fulfilled, and free humans, we have to care about the rules that apply to information about us. So much of our modern society is structured around **information**. When you shop online, read the news, look something up, vote, seek directions, or really anything else, you are relying on information. If we live in an information society, our information matters, and therefore privacy matters. +Em última análise, a privacidade diz respeito à informação humana, e sabemos que a informação humana confere poder sobre os seres humanos. Se nos importamos com nossa capacidade de sermos humanos autênticos, plenos e livres, temos de nos preocupar com as regras que se aplicam à utilização da nossa informação. Grande parte da nossa sociedade moderna está estruturada em torno de **informações**. Quando faz compras online, lê as notícias, olha para cima, vota, procura orientações ou qualquer outra coisa, depende de informações. Se vivemos numa sociedade da informação, a informação é importante e, como consequência, também a privacidade. -## What is Privacy? +## O que é Privacidade? -Many people get the concepts of **privacy**, **security**, and **anonymity** confused. You'll see people criticize various products as "not private" when really they mean it doesn't provide anonymity, for example. On this website, we cover all three of these topics, but it is important you understand the difference between them, and when each one comes into play. +Muitas pessoas confundem os conceitos de **privacidade**, **segurança** e **anonimato**. Há pessoas que criticam vários produtos como "não oferecendo privacidade", quando na realidade não oferecem anonimato. Neste site, abordamos os três temas, mas é importante que se compreenda a diferença entre eles, e quando cada um entra em jogo. **Privacidade** : -==Privacy is the assurance that your data is only seen by the parties you intend to view it.== In the context of an instant messenger, for example, end-to-end encryption provides privacy by keeping your message visible only to yourself and the recipient. +==A privacidade é a garantia de que os seus dados só são vistos por quem autoriza.== No contexto de uma aplicação de mensagens instantâneas, por exemplo, a encriptação ponta a ponta garante privacidade, mantendo a sua mensagem visível apenas para si e para o destinatário. **Segurança** : @@ -24,7 +24,7 @@ A segurança é a capacidade de confiar nas aplicações que utiliza - que são Os certificados permitem a certeza de que está a falar diretamente com o site que está a visitar e impedem que os atacantes na sua rede leiam ou modifiquem os dados enviados para ou a partir do site. -**Anonymity** +**Anonimato** : O anonimato é a capacidade de agir sem um identificador persistente. Pode obter essa privacidade online com o browser [Tor](../tor.md), que lhe permite navegar na Internet com um endereço IP e uma ligação de rede aleatórios, que substituem os seus. diff --git a/i18n/pt/real-time-communication.md b/i18n/pt/real-time-communication.md index 87cc76bd..96b99e04 100644 --- a/i18n/pt/real-time-communication.md +++ b/i18n/pt/real-time-communication.md @@ -102,13 +102,13 @@ O software cliente foi [auditado de forma independente](https://briarproject.org O Briar publicou na íntegra a sua [especificação](https://code.briarproject.org/briar/briar-spec). -O Briar suporta encaminhamento totalmente sigiloso, através do Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) e [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md). +O Briar suporta Forward Secrecy, através do Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) e do [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md). ## Opções adicionais !!! aviso - Estas aplicações de mensagens instantâneas não têm Perfect [Forward Secrecy] (https://en.wikipedia.org/wiki/Forward_secrecy) (PFS) e, embora satisfaçam certas necessidades que as nossas recomendações anteriores não podem satisfazer, não os recomendamos para comunicações de longo prazo ou sensíveis. Qualquer comprometimento da chave entre os destinatários da mensagem afetará a confidencialidade de **todas** as comunicações anteriores. + Estas aplicações de mensagens instantâneas não têm [Forward Secrecy] (https://en.wikipedia.org/wiki/Forward_secrecy) e, embora satisfaçam certas necessidades que as nossas recomendações anteriores não podem satisfazer, não os recomendamos para comunicações de longo prazo ou sensíveis. Qualquer comprometimento da chave entre os destinatários da mensagem afetará a confidencialidade de **todas** as comunicações anteriores. ### Element @@ -194,7 +194,7 @@ O Session tem um [whitepaper](https://arxiv.org/pdf/2002.04609.pdf) que descreve Os nossos melhores critérios representam o que gostaríamos de ver num projeto perfeito desta categoria. As nossas recomendações podem não incluir todas as funcionalidades, mas incluem as que, na nossa opinião, têm um impacto mais elevado. -- Deve ter o Perfect Forward Secrecy. +- Deve ter o Forward Secrecy. - Deve ter servidores de código aberto. - Deve ser descentralizado, ou seja, federado ou P2P. - Deve utilizar o E2EE para todas as mensagens por defeito. diff --git a/i18n/pt/vpn.md b/i18n/pt/vpn.md index 22ca5fac..b204da14 100644 --- a/i18n/pt/vpn.md +++ b/i18n/pt/vpn.md @@ -281,13 +281,13 @@ Uma VPN é inútil se não proporcionar uma segurança adequada. Exigimos que to **Mínimos de qualificação:** - Esquemas de encriptação fortes: OpenVPN com autenticação SHA-256; handshake RSA-2048 ou superior; encriptação de dados AES-256-GCM ou AES-256-CBC. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Auditorias de segurança publicadas por uma empresa terceira de renome. **Melhor caso:** - Encriptação máxima: RSA-4096. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Auditorias de segurança exaustivas publicadas por uma empresa terceira de renome. - Programas de recompensa por deteção de erros e/ou processos coordenados de divulgação de vulnerabilidades. diff --git a/i18n/ru/desktop.md b/i18n/ru/desktop.md index 5fcc9234..228eb3b0 100644 --- a/i18n/ru/desktop.md +++ b/i18n/ru/desktop.md @@ -73,13 +73,13 @@ Arch Linux имеет плавающий цикл релиза. Не сущес [:octicons-info-16:](https://docs.fedoraproject.org/en-US/fedora-silverblue/){ .card-link title=Документация} [:octicons-heart-16:](https://whatcanidoforfedora.org/){ .card-link title=Поддержать } -Silverblue (and Kinoite) differ from Fedora Workstation as they replace the [DNF](https://fedoraproject.org/wiki/DNF) package manager with a much more advanced alternative called [`rpm-ostree`](https://docs.fedoraproject.org/en-US/fedora/rawhide/system-administrators-guide/package-management/rpm-ostree/). The `rpm-ostree` package manager works by downloading a base image for the system, then overlaying packages over it in a [git](https://en.wikipedia.org/wiki/Git)-like commit tree. When the system is updated, a new base image is downloaded and the overlays will be applied to that new image. +Silverblue (и Kinoite) отличаются от Fedora Workstation тем, что заменяют пакетный менеджер [DNF](https://fedoraproject.org/wiki/DNF) гораздо более продвинутой альтернативой под названием [`rpm-ostree`](https://docs.fedoraproject.org/en-US/fedora/rawhide/system-administrators-guide/package-management/rpm-ostree/). Менеджер пакетов `rpm-ostree` работает путем скачивания базового образа для системы, а затем наложения пакетов на него в [git](https://en.wikipedia.org/wiki/Git)-подобном дереве коммитов. Когда система обновляется, загружается новое базовое изображение, и наложения будут применены к этому новому изображению. -After the update is complete you will reboot the system into the new deployment. `rpm-ostree` keeps two deployments of the system so that you can easily rollback if something breaks in the new deployment. There is also the option to pin more deployments as needed. +После завершения обновления вы перезагрузите систему в новую установку. `rpm-ostree` сохраняет две версии системы, чтобы вы могли легко откатиться назад, если что-то сломается в новой версии. Также есть возможность подключить большее количество версий по мере необходимости. -[Flatpak](https://www.flatpak.org) is the primary package installation method on these distributions, as `rpm-ostree` is only meant to overlay packages that cannot stay inside of a container on top of the base image. +[Flatpak](https://www.flatpak.org) является основным методом установки пакетов в этих дистрибутивах, так как `rpm-ostree` предназначен только для наложения пакетов, которые не могут оставаться внутри контейнера, поверх базового образа. -As an alternative to Flatpaks, there is the option of [Toolbox](https://docs.fedoraproject.org/en-US/fedora-silverblue/toolbox/) to create [Podman](https://podman.io) containers with a shared home directory with the host operating system and mimic a traditional Fedora environment, which is a [useful feature](https://containertoolbx.org) for the discerning developer. +В качестве альтернативы для Flatpak существует возможность [Toolbox](https://docs.fedoraproject.org/en-US/fedora-silverblue/toolbox/) для создания [Podman](https://podman.io) контейнеров с общим домашним каталогом с операционной системой хоста и имитации традиционного окружения Fedora, что является [полезной функцией](https://containertoolbx.org) для взыскательных разработчиков. ### NixOS @@ -93,7 +93,7 @@ As an alternative to Flatpaks, there is the option of [Toolbox](https://docs.fed [:octicons-info-16:](https://nixos.org/learn.html){ .card-link title=Документация} [:octicons-heart-16:](https://nixos.org/donate.html){ .card-link title=Поддержать } -NixOS’s package manager keeps every version of every package in a different folder in the **Nix store**. Due to this you can have different versions of the same package installed on your system. After the package contents have been written to the folder, the folder is made read-only. +Менеджер пакетов NixOS хранит каждую версию каждого пакета в отдельной папке в **хранилище Nix**. Из-за этого в вашей системе могут быть установлены разные версии одного и того же пакета. После записи содержимого пакета в папку, папка становится доступной только для чтения. NixOS also provides atomic updates; first it downloads (or builds) the packages and files for the new system generation and then switches to it. There are different ways to switch to a new generation; you can tell NixOS to activate it after reboot or you can switch to it at runtime. You can also *test* the new generation by switching to it at runtime, but not setting it as the current system generation. If something in the update process breaks, you can just reboot and automatically and return to a working version of your system. @@ -118,13 +118,13 @@ Nix is a source-based package manager; if there’s no pre-built available in th [:octicons-info-16:](https://www.whonix.org/wiki/Documentation){ .card-link title=Документация} [:octicons-heart-16:](https://www.whonix.org/wiki/Donate){ .card-link title=Поддержать } -Whonix is meant to run as two virtual machines: a “Workstation” and a Tor “Gateway.” All communications from the Workstation must go through the Tor gateway. This means that even if the Workstation is compromised by malware of some kind, the true IP address remains hidden. +Whonix предназначен для запуска в виде двух виртуальных машин: "Рабочая" и "Шлюз Tor." Все соединения рабочей станции должны проходить через шлюз Tor. Это означает, даже если рабочая станция будет скомпрометирована каким-либо вредоносным ПО, настоящий IP-адрес останется скрытым. Some of its features include Tor Stream Isolation, [keystroke anonymization](https://www.whonix.org/wiki/Keystroke_Deanonymization#Kloak), [encrypted swap](https://github.com/Whonix/swap-file-creator), and a hardened memory allocator. Future versions of Whonix will likely include [full system AppArmor policies](https://github.com/Whonix/apparmor-profile-everything) and a [sandbox app launcher](https://www.whonix.org/wiki/Sandbox-app-launcher) to fully confine all processes on the system. -Whonix is best used [in conjunction with Qubes](https://www.whonix.org/wiki/Qubes/Why_use_Qubes_over_other_Virtualizers), Qubes-Whonix has various [disadvantages](https://forums.whonix.org/t/qubes-whonix-security-disadvantages-help-wanted/8581) when compared to other hypervisors. +Whonix лучше всего использовать [в сочетании с Qubes](https://www.whonix.org/wiki/Qubes/Why_use_Qubes_over_other_Virtualizers), Qubes-Whonix имеет различные [недостатки](https://forums.whonix.org/t/qubes-whonix-security-disadvantages-help-wanted/8581) по сравнению с другими гипервизорами. ### Tails @@ -138,11 +138,11 @@ Whonix is best used [in conjunction with Qubes](https://www.whonix.org/wiki/Qube [:octicons-info-16:](https://tails.boum.org/doc/index.en.html){ .card-link title=Документация} [:octicons-heart-16:](https://tails.boum.org/donate/){ .card-link title=Поддержать } -Tails is great for counter forensics due to amnesia (meaning nothing is written to the disk); however, it is not a hardened distribution like Whonix. It lacks many anonymity and security features that Whonix has and gets updated much less often (only once every six weeks). A Tails system that is compromised by malware may potentially bypass the transparent proxy allowing for the user to be deanonymized. +Tails отлично подходит для криминалистической экспертизы благодаря амнезии (то есть ничего не записывается на диск); однако это не такой защищенный дистрибутив, как Whonix. В нем нет многих функций анонимности и безопасности, которые есть в Whonix, и он обновляется гораздо реже (только раз в шесть недель). A Tails system that is compromised by malware may potentially bypass the transparent proxy allowing for the user to be deanonymized. Tails includes [uBlock Origin](desktop-browsers.md#ublock-origin) in Tor Browser by default, which may potentially make it easier for adversaries to fingerprint Tails users. [Whonix](desktop.md#whonix) virtual machines may be more leak-proof, however they are not amnesic, meaning data may be recovered from your storage device. -By design, Tails is meant to completely reset itself after each reboot. Encrypted [persistent storage](https://tails.boum.org/doc/persistent_storage/index.en.html) can be configured to store some data between reboots. +By design, Tails is meant to completely reset itself after each reboot. Зашифрованное [постоянное хранилище](https://tails.boum.org/doc/persistent_storage/index.en.html) может быть настроено для хранения некоторых данных между перезагрузками. ## Дистрибутивы для безопасности @@ -162,9 +162,9 @@ By design, Tails is meant to completely reset itself after each reboot. Encrypte [:octicons-code-16:](https://github.com/QubesOS/){ .card-link title="Исходный код" } [:octicons-heart-16:](https://www.qubes-os.org/donate/){ .card-link title=Поддержать } -Qubes OS is a Xen-based operating system meant to provide strong security for desktop computing through secure virtual machines (VMs), also known as *Qubes*. +Qubes OS - это операционная система на базе Xen, предназначенная для обеспечения надежной защиты настольных компьютеров с помощью защищенных виртуальных машин (ВМ), также известных как *Qubes*. -The Qubes OS operating system secures the computer by isolating subsystems (e.g., networking, USB, etc.) and applications in separate VMs. Should one part of the system be compromised, the extra isolation is likely to protect the rest of the system. For further details see the Qubes [FAQ](https://www.qubes-os.org/faq/). +Операционная система Qubes OS обеспечивает безопасность компьютера путем изоляции подсистем (например, сетевых, USB и т.д.) и приложений в отдельных виртуальных машинах. Should one part of the system be compromised, the extra isolation is likely to protect the rest of the system. For further details see the Qubes [FAQ](https://www.qubes-os.org/faq/). ## Критерии @@ -174,11 +174,11 @@ The Qubes OS operating system secures the computer by isolating subsystems (e.g. Мы всё еще работаем над установлением критериев для каждого раздела нашего сайта, поэтому они могут поменяться в будущем. Если у вас есть вопросы по поводу наших критериев, пожалуйста, [задавайте их на нашем форуме](https://discuss.privacyguides.net/latest). Если какой-то критерий здесь не указан, это не значит, что мы его не учли. Перед тем, как рекомендовать какой-либо проект мы учитываем и обсуждаем множество факторов. Документирование этих факторов ещё не завершено. -Our recommended operating systems: +Наши рекомендованные операционные системы: -- Must be open-source. -- Must receive regular software and Linux kernel updates. -- Linux distributions must support [Wayland](os/linux-overview.md#Wayland). -- Must support full-disk encryption during installation. -- Must not freeze regular releases for more than 1 year. We [do not recommend](os/linux-overview.md#release-cycle) "Long Term Support" or "stable" distro releases for desktop usage. -- Must support a wide variety of hardware. +- Должны иметь открытый исходный код. +- Должны получать регулярные обновления программного обеспечения и ядра Linux. +- Дистрибутивы Linux должны поддерживать [Wayland](os/linux-overview.md#Wayland). +- Должны предлагать шифрование всего диска во время установки. +- Не должны замораживать релизы более чем на 1 год. Мы [не рекомендуем](os/linux-overview.md#release-cycle) дистрибутивы с "Long Term Support" или "stable" релизами для персональных компьютеров. +- Должны поддерживать широкий спектр устройств. diff --git a/i18n/ru/email-clients.md b/i18n/ru/email-clients.md index f9a8a9dc..6e43e66d 100644 --- a/i18n/ru/email-clients.md +++ b/i18n/ru/email-clients.md @@ -5,15 +5,15 @@ description: Эти почтовые клиенты соблюдают конф cover: email-clients.png --- -Наш список рекомендаций содержит только почтовые клиенты, которые поддерживают [OpenPGP](/encryption/#openpgp) и безопасную аутентификацию (например, [OAuth](https://ru.wikipedia.org/wiki/OAuth)). OAuth позволяет использовать [многофакторную аутентификацию](/multi-factor-authentication) и предотвратить кражу учетных записей. +Наш список рекомендаций содержит только почтовые клиенты, которые поддерживают [OpenPGP](/encryption/#openpgp) и безопасную аутентификацию (например, [OAuth](https://ru.wikipedia.org/wiki/OAuth)). OAuth позволяет использовать [многофакторную аутентификацию](basics/multi-factor-authentication.md) и предотвратить кражу учетных записей. -??? warning "Email does not provide forward secrecy" +??? warning "Электронная почта не обеспечивает прямую секретность" - When using end-to-end encryption (E2EE) technology like OpenPGP, email will still have [some metadata](email.md#email-metadata-overview) that is not encrypted in the header of the email. + При использовании технологии сквозного шифрования (E2EE), например OpenPGP, электронная почта все равно будет содержать [некоторые метаданные](email.md#email-metadata-overview), которые не зашифрованы в заголовке письма. - OpenPGP also does not support [forward secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), which means if either your or the recipient's private key is ever stolen, all previous messages encrypted with it will be exposed: [How do I protect my private keys?](basics/email-security.md) Consider using a medium that provides forward secrecy: + OpenPGP также не поддерживает прямую секретность] (https://ru.wikipedia.org/wiki/Perfect_forward_secrecy), что означает: если ваш приватный ключ или приватный ключ получателя будет украден, то все предыдущие сообщения, зашифрованные с его помощью, будут раскрыты: [Как защитить мои приватные ключи?](basics/email-security.md) Рассмотрите возможность использования среды, обеспечивающей прямую секретность: - [Real-time Communication](real-time-communication.md){ .md-button } + [Связь в реальном времени](real-time-communication.md){ .md-button } ## Кросс-платформенные приложения @@ -100,31 +100,36 @@ Canary Mail имеет закрытый исходный код. Мы реком !!! recommendation - ![Логотип Mailvelope](assets/img/email-clients/mailvelope.svg){ align=right } + ![Логотип FairEmail](assets/img/email-clients/fairemail.svg){ align=right } - **Mailvelope** - браузерное расширение, позволяющее обмениваться зашифрованными письмами по стандарту OpenPGP. + **FairEmail** - это небольшое приложение электронной почты с открытым исходным кодом, использующее открытые стандарты (IMAP, SMTP, OpenPGP) с низким потреблением данных и заряда батареи. - [Перейти на mailvelope.com](https://www.mailvelope.com){ .md-button .md-button--primary } [Политика конфиденциальности](https://www.mailvelope.com/en/privacy-policy){ .md-button } + [:octicons-home-16: Домашняя страница](https://email.faircode.eu){ .md-button .md-button--primary } + [:octicons-eye-16:](https://github.com/M66B/FairEmail/blob/master/PRIVACY.md){ .card-link title="Политика конфиденциальности" } + [:octicons-info-16:](https://github.com/M66B/FairEmail/blob/master/FAQ.md){ .card-link title=Документация} + [:octicons-code-16:](https://github.com/M66B/FairEmail){ .card-link title="Исходный код" } + [:octicons-heart-16:](https://email.faircode.eu/donate/){ .card-link title=Поддержать } - **Скачать** - - [:fontawesome-brands-firefox: Firefox](https://addons.mozilla.org/firefox/addon/mailvelope) - - [:fontawesome-brands-chrome: Chrome](https://chrome.google.com/webstore/detail/mailvelope/kajibbejlbohfaggdiogboambcijhkke) - - [:fontawesome-brands-edge: Edge](https://microsoftedge.microsoft.com/addons/detail/mailvelope/dgcbddhdhjppfdfjpciagmmibadmoapc) - - [:fontawesome-brands-github: Исходный код](https://github.com/mailvelope/mailvelope) [Перейти на kontact.kde.org](https://kontact.kde.org){ .md-button .md-button--primary } [Политика конфиденциальности](https://kde.org/privacypolicy-apps){ .md-button } + ??? downloads "Скачать" + + - [:simple-googleplay: Google Play](https://play.google.com/store/apps/details?id=eu.faircode.email) + - [:simple-github: GitHub](https://github.com/M66B/FairEmail/releases) ### GNOME Evolution (GNOME) !!! recommendation - ![K-9 Mail logo](assets/img/email-clients/k9mail.svg){ align=right } + ![Логотип Evolution](assets/img/email-clients/evolution.svg){ align=right } - **K-9 Mail** - независимое почтовое приложение, которое поддерживает и POP3, и IMAP (только push). [Перейти на k9mail.app](https://k9mail.app){ .md-button .md-button--primary } [Политика конфиденциальности](https://k9mail.app/privacy){ .md-button } + **Evolution** — это приложение для управления персональной информацией, которое обеспечивает интегрированную почту, календарь и функциональность адресной книги. Evolution имеет подробную [документацию](https://help.gnome.org/users/evolution/stable/), чтобы помочь вам начать работу. - downloads - - [:fontawesome-brands-firefox: Firefox](https://addons.mozilla.org/firefox/addon/mailvelope) - - [:fontawesome-brands-chrome: Chrome](https://chrome.google.com/webstore/detail/mailvelope/kajibbejlbohfaggdiogboambcijhkke) - - [:fontawesome-brands-edge: Edge](https://microsoftedge.microsoft.com/addons/detail/mailvelope/dgcbddhdhjppfdfjpciagmmibadmoapc) - - [:fontawesome-brands-github: Исходный код](https://github.com/mailvelope/mailvelope) downloads + [:octicons-home-16: Домашняя страница](https://wiki.gnome.org/Apps/Evolution){ .md-button .md-button--primary } + [:octicons-eye-16:](https://wiki.gnome.org/Apps/Evolution/PrivacyPolicy){ .card-link title="Политика конфиденциальности" } + [:octicons-info-16:](https://help.gnome.org/users/evolution/stable/){ .card-link title=Документация} + [:octicons-code-16:](https://gitlab.gnome.org/GNOME/evolution/){ .card-link title="Исходный код" } + [:octicons-heart-16:](https://www.gnome.org/donate/){ .card-link title=Поддержать } + + ??? downloads "Скачать" - [:simple-flathub: Flathub](https://flathub.org/apps/details/org.gnome.Evolution) @@ -132,47 +137,47 @@ Canary Mail имеет закрытый исходный код. Мы реком !!! recommendation - ![FairEmail logo](assets/img/email-clients/fairemail.svg){ align=right } + ![логотип K-9 Mail](assets/img/email-clients/k9mail. vg){ align=right } - **FairEmail** — минимальное почтовое приложение с открытым исходным ходом, использующее открытые стандарты (IMAP, SMTP, OpenPGP) с малым потреблением памяти и заряда батареи. + **K-9 Mail** — это независимое почтовое приложение, которое поддерживает как POP3, так и IMAP, но поддерживает только push-почту для IMAP. - [Перейти на email.faircode.eu](https://email.faircode.eu){ .md-button .md-button--primary } [Политика конфиденциальности](https://github.com/M66B/FairEmail/blob/master/PRIVACY.md){ .md-button } + В будущем, K-9 Mail станет [официальным](https://k9mail.app/2022/06/13/K-9-Mail-and-Thunderbird.html) клиентом Thunderbird для Android. - downloads + [:octicons-home-16: Домашняя страница](https://k9mail.app){ .md-button .md-button--primary } + [:octicons-eye-16:](https://k9mail.app/privacy){ .card-link title="Политика конфиденциальности" } + [:octicons-info-16:](https://docs.k9mail.app/){ .card-link title=Документация} + [:octicons-code-16:](https://github.com/k9mail/k-9){ .card-link title="Исходный код" } + [:octicons-heart-16:](https://k9mail.app/contribute){ .card-link title=Поддержать } - - [:fontawesome-brands-google-play: Google Play](https://play.google.com/store/apps/details?id=com.fsck.k9) - - [:pg-f-droid: F-Droid](https://f-droid.org/packages/com.fsck.k9/) - - [:fontawesome-brands-github: Исходный код](https://github.com/k9mail) downloads + ??? downloads "Скачать" - [:simple-googleplay: Google Play](https://play.google.com/store/apps/details?id=com.fsck.k9) - [:simple-github: GitHub](https://github.com/k9mail/k-9/releases) !!! warning "Осторожно" - ![Canary Mail logo](assets/img/email-clients/canarymail.svg){ align=right } - - **Canary Mail** - платный почтовый клиент, разработанный для обеспечения сквозного шифрования с использованием таких функций, как биометрическая блокировка и т.д. [Перейти на canarymail.io](https://canarymail.io){ .md-button .md-button--primary } [Политика конфиденциальности](https://canarymail.io/privacy.html){ .md-button } + Когда вы отвечаете кому-то на письмо, отправленное сразу нескольким людям, поле с получателем может также содержать несколько адресов. Более подробную информацию можно найти тут [thundernest/k-9 #3738](https://github.com/thundernest/k-9/issues/3738). ### Kontact (KDE) !!! recommendation - ![Kontact logo](assets/img/email-clients/kontact.svg){ align=right } + ![Логотип Kontact](assets/img/email-clients/kontact.svg){ align=right } - **Kontact** is a personal information manager (PIM) application from the [KDE](https://kde.org) project. It provides a mail client, address book, organizer and RSS client. + **Kontact** - это менеджер персональной информации от проекта [KDE](https://kde.org). Он предоставляет почтовый клиент, адресную книгу, органайзер и клиент RSS. - [:octicons-home-16: Homepage](https://kontact.kde.org){ .md-button .md-button--primary } - [:octicons-eye-16:](https://kde.org/privacypolicy-apps){ .card-link title="Privacy Policy" } - [:octicons-info-16:](https://kontact.kde.org/users/){ .card-link title=Documentation} - [:octicons-code-16:](https://invent.kde.org/pim/kmail){ .card-link title="Source Code" } - [:octicons-heart-16:](https://kde.org/community/donations/){ .card-link title=Contribute } + [:octicons-home-16: Домашняя страница](https://kontact.kde.org){ .md-button .md-button--primary } + [:octicons-eye-16:](https://kde.org/privacypolicy-apps){ .card-link title="Политика конфиденциальности" } + [:octicons-info-16:](https://kontact.kde.org/users/){ .card-link title=Документация} + [:octicons-code-16:](https://invent.kde.org/pim/kmail){ .card-link title="Исходный код" } + [:octicons-heart-16:](https://kde.org/community/donations/){ .card-link title=Поддержать } - ??? downloads + ??? downloads "Скачать" - [:simple-linux: Linux](https://kontact.kde.org/download) - [:simple-flathub: Flathub](https://flathub.org/apps/details/org.kde.kontact) -### Mailvelope (Browser) +### Mailvelope (Браузер) !!! recommendation @@ -191,7 +196,7 @@ Canary Mail имеет закрытый исходный код. Мы реком - [:simple-googlechrome: Chrome](https://chrome.google.com/webstore/detail/mailvelope/kajibbejlbohfaggdiogboambcijhkke) - [:simple-microsoftedge: Edge](https://microsoftedge.microsoft.com/addons/detail/mailvelope/dgcbddhdhjppfdfjpciagmmibadmoapc) -### NeoMutt (CLI) +### NeoMutt (Командная строка) !!! recommendation diff --git a/i18n/ru/real-time-communication.md b/i18n/ru/real-time-communication.md index a8ee753c..9ea8441e 100644 --- a/i18n/ru/real-time-communication.md +++ b/i18n/ru/real-time-communication.md @@ -96,13 +96,13 @@ The client software was independently [audited](https://briarproject.org/news/20 Briar has a fully [published specification](https://code.briarproject.org/briar/briar-spec). -Briar supports perfect forward secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. +Briar поддерживает прямую секретность пересылки, используя протоколы Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) и [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md). ## Типы коммуникационных сетей !!! warning "Осторожно" - These messengers do not have Perfect [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. + Хотя эти мессенджеры и проходят по определённым критериям, они не поддерживают [прямую секретность](https://ru.wikipedia.org/wiki/Perfect_forward_secrecy), поэтому мы не рекомендуем их для длительных или конфиденциальных коммуникаций. Any key compromise among message recipients would affect the confidentiality of **all** past communications. ### Element @@ -186,7 +186,7 @@ Session has a [whitepaper](https://arxiv.org/pdf/2002.04609.pdf) describing the Эти критерии представляют собой то, что мы хотели бы видеть от идеального проекта в этой категории. Наши рекомендации могут не соответствовать всем или нескольким из этих критериев, но проекты, которые им соответствуют, расположены выше остальных. -- Should have Perfect Forward Secrecy. +- Должны поддерживать прямую секретность. - Should have open-source servers. - Should be decentralized, i.e. federated or P2P. - Should use E2EE for all messages by default. diff --git a/i18n/ru/vpn.md b/i18n/ru/vpn.md index 37823a1a..2cb4be33 100644 --- a/i18n/ru/vpn.md +++ b/i18n/ru/vpn.md @@ -279,13 +279,13 @@ VPN бессмысленен, если он даже не может обесп **Минимальные требования:** - Надежные схемы шифрования: OpenVPN с аутентификацией SHA-256; рукопожатие RSA-2048 или лучше; шифрование данных AES-256-GCM или AES-256-CBC. -- Совершенная прямая секретность (PFS). +- Прямая секретность. - Опубликованные аудиты безопасности от авторитетной сторонней фирмы. **В лучшем случае:** - Самое сильное шифрование: RSA-4096. -- Совершенная прямая секретность (PFS). +- Прямая секретность. - Опубликованные аудиты безопасности от авторитетной сторонней фирмы. - Программы "bug-bounty" и/или скоординированный процесс раскрытия информации об уязвимостях. diff --git a/i18n/sv/real-time-communication.md b/i18n/sv/real-time-communication.md index 622c8921..3e01eea1 100644 --- a/i18n/sv/real-time-communication.md +++ b/i18n/sv/real-time-communication.md @@ -99,13 +99,13 @@ The client software was independently [audited](https://briarproject.org/news/20 Briar has a fully [published specification](https://code.briarproject.org/briar/briar-spec). -Briar supports perfect forward secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## Additional Options !!! varning - These messengers do not have Perfect [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. ### Element @@ -189,7 +189,7 @@ Session has a [whitepaper](https://arxiv.org/pdf/2002.04609.pdf) describing the Våra kriterier för bästa fall representerar vad vi skulle vilja se av det perfekta projektet i denna kategori. Våra rekommendationer kanske inte innehåller alla eller några av dessa funktioner, men de som gör det kan vara högre rankade än andra på den här sidan. -- Should have Perfect Forward Secrecy. +- Should have Forward Secrecy. - Should have open-source servers. - Should be decentralized, i.e. federated or P2P. - Should use E2EE for all messages by default. diff --git a/i18n/sv/vpn.md b/i18n/sv/vpn.md index d020d333..756d4183 100644 --- a/i18n/sv/vpn.md +++ b/i18n/sv/vpn.md @@ -279,13 +279,13 @@ A VPN is pointless if it can't even provide adequate security. We require all ou **Minimum to Qualify:** - Strong Encryption Schemes: OpenVPN with SHA-256 authentication; RSA-2048 or better handshake; AES-256-GCM or AES-256-CBC data encryption. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Published security audits from a reputable third-party firm. **Best Case:** - Strongest Encryption: RSA-4096. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Comprehensive published security audits from a reputable third-party firm. - Bug-bounty programs and/or a coordinated vulnerability-disclosure process. diff --git a/i18n/tr/real-time-communication.md b/i18n/tr/real-time-communication.md index e5aa9411..8ca06445 100644 --- a/i18n/tr/real-time-communication.md +++ b/i18n/tr/real-time-communication.md @@ -99,13 +99,13 @@ The client software was independently [audited](https://briarproject.org/news/20 Briar has a fully [published specification](https://code.briarproject.org/briar/briar-spec). -Briar supports perfect forward secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## Additional Options !!! warning - These messengers do not have Perfect [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. ### Element @@ -189,7 +189,7 @@ Session has a [whitepaper](https://arxiv.org/pdf/2002.04609.pdf) describing the Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page. -- Should have Perfect Forward Secrecy. +- Should have Forward Secrecy. - Should have open-source servers. - Should be decentralized, i.e. federated or P2P. - Should use E2EE for all messages by default. diff --git a/i18n/tr/vpn.md b/i18n/tr/vpn.md index 94598782..7b0e3384 100644 --- a/i18n/tr/vpn.md +++ b/i18n/tr/vpn.md @@ -267,13 +267,13 @@ A VPN is pointless if it can't even provide adequate security. We require all ou **Minimum to Qualify:** - Strong Encryption Schemes: OpenVPN with SHA-256 authentication; RSA-2048 or better handshake; AES-256-GCM or AES-256-CBC data encryption. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Published security audits from a reputable third-party firm. **Best Case:** - Strongest Encryption: RSA-4096. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Comprehensive published security audits from a reputable third-party firm. - Bug-bounty programs and/or a coordinated vulnerability-disclosure process. diff --git a/i18n/uk/real-time-communication.md b/i18n/uk/real-time-communication.md index dd452e0c..49a85651 100644 --- a/i18n/uk/real-time-communication.md +++ b/i18n/uk/real-time-communication.md @@ -99,13 +99,13 @@ The client software was independently [audited](https://briarproject.org/news/20 Briar has a fully [published specification](https://code.briarproject.org/briar/briar-spec). -Briar supports perfect forward secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## Additional Options !!! warning - These messengers do not have Perfect [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. ### Element @@ -189,7 +189,7 @@ Session has a [whitepaper](https://arxiv.org/pdf/2002.04609.pdf) describing the Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page. -- Should have Perfect Forward Secrecy. +- Should have Forward Secrecy. - Should have open-source servers. - Should be decentralized, i.e. federated or P2P. - Should use E2EE for all messages by default. diff --git a/i18n/uk/vpn.md b/i18n/uk/vpn.md index 2f693774..93d53c1e 100644 --- a/i18n/uk/vpn.md +++ b/i18n/uk/vpn.md @@ -279,13 +279,13 @@ A VPN is pointless if it can't even provide adequate security. We require all ou **Minimum to Qualify:** - Strong Encryption Schemes: OpenVPN with SHA-256 authentication; RSA-2048 or better handshake; AES-256-GCM or AES-256-CBC data encryption. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Published security audits from a reputable third-party firm. **Best Case:** - Strongest Encryption: RSA-4096. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Comprehensive published security audits from a reputable third-party firm. - Bug-bounty programs and/or a coordinated vulnerability-disclosure process. diff --git a/i18n/vi/real-time-communication.md b/i18n/vi/real-time-communication.md index 0b0c363b..e591dd3e 100644 --- a/i18n/vi/real-time-communication.md +++ b/i18n/vi/real-time-communication.md @@ -97,13 +97,13 @@ The client software was independently [audited](https://briarproject.org/news/20 Briar has a fully [published specification](https://code.briarproject.org/briar/briar-spec). -Briar supports perfect forward secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## Additional Options !!! warning - These messengers do not have Perfect [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. ### Element @@ -193,7 +193,7 @@ Session has a [whitepaper](https://arxiv.org/pdf/2002.04609.pdf) describing the Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page. -- Should have Perfect Forward Secrecy. +- Should have Forward Secrecy. - Should have open-source servers. - Should be decentralized, i.e. federated or P2P. - Should use E2EE for all messages by default. diff --git a/i18n/vi/vpn.md b/i18n/vi/vpn.md index 7c6020c7..ee9358f2 100644 --- a/i18n/vi/vpn.md +++ b/i18n/vi/vpn.md @@ -279,13 +279,13 @@ A VPN is pointless if it can't even provide adequate security. We require all ou **Minimum to Qualify:** - Strong Encryption Schemes: OpenVPN with SHA-256 authentication; RSA-2048 or better handshake; AES-256-GCM or AES-256-CBC data encryption. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Published security audits from a reputable third-party firm. **Best Case:** - Strongest Encryption: RSA-4096. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Comprehensive published security audits from a reputable third-party firm. - Bug-bounty programs and/or a coordinated vulnerability-disclosure process. diff --git a/i18n/zh-Hant/about/criteria.md b/i18n/zh-Hant/about/criteria.md index 06443a6b..34533319 100644 --- a/i18n/zh-Hant/about/criteria.md +++ b/i18n/zh-Hant/about/criteria.md @@ -2,9 +2,9 @@ title: 通用標準 --- -!!! 示例“工作進行中” +!!! example "工作進行中" - 以下頁面是一項正在進行的工作，並未反映我們目前的建議的全部標準。 過去關於此主題的討論： [# 24] (https://github.com/privacyguides/privacyguides.org/ discussion/24) + 以下頁面是一項正在進行的工作，並未反映我們目前的建議的全部標準。 過去關於此主題的討論： [#24](https://github.com/privacyguides/privacyguides.org/discussion/24) 以下是一些必須適用於所有提交給 Privacy Guides 的內容。 每個類別都會有額外的加入要求。 diff --git a/i18n/zh-Hant/productivity.md b/i18n/zh-Hant/productivity.md index 6aba3991..a7451932 100644 --- a/i18n/zh-Hant/productivity.md +++ b/i18n/zh-Hant/productivity.md @@ -41,9 +41,9 @@ cover: productivity.png !!! recommendation - ! [CryptPad logo] (assets/img/productivity/cryptpad.svg) {align = right} + ![CryptPad logo](assets/img/productivity/cryptpad.svg){ align=right } - * * CryptPad * *隱私設計可替代流行的辦公工具。 網頁服務上的所有內容都是端到端加密，也可輕鬆與其他用戶共享。 + **CryptPad** 隱私設計可替代流行的辦公工具。 網頁服務上的所有內容都是端到端加密，也可輕鬆與其他用戶共享。 [:octicons-home-16: Homepage](https://cryptpad.fr){ .md-button .md-button--primary } [:octicons-eye-16:](https://cryptpad.fr/pad/#/2/pad/view/GcNjAWmK6YDB3EO2IipRZ0fUe89j43Ryqeb4fjkjehE/){ .card-link title="Privacy Policy" } @@ -55,7 +55,7 @@ cover: productivity.png **請注意，我們所推薦專案沒有任何瓜葛。 ** 除了 [標準準則](about/criteria.md)外，我們還發展出一套明確要求以提出客觀建議。 我們建議您在選擇使用項目之前先熟悉此列表，並進行自己的研究，以確保它是您的正確選擇。 -!!! !!! 例如 "本节是新的" +!!! example "此部分是新的" 我們正在努力為我們網站的每個部分建立定義的標準，這可能會有所變化。 如果您對我們的標準有任何疑問，請在 [論壇上提問](https://discuss.privacyguides.net/latest) ，如果沒有列出，請不要認為我們在提出建議時沒有考慮到某些事情。 當我們推薦一個項目時，有許多因素被考慮和討論，記錄每一個項目都是正在進行式。 @@ -81,9 +81,9 @@ cover: productivity.png !!! recommendation - ! [LibreOffice logo] (assets/img/productivity/libreoffice.svg) {align = right} + ![LibreOffice logo](assets/img/productivity/libreoffice.svg){ align= ight } - * * LibreOffice * *是一個免費且開源的辦公套件，具有廣泛的功能。 + **LibreOffice** 是一個免費且開源的辦公套件，具有廣泛的功能。 [:octicons-home-16: Homepage](https://www.libreoffice.org){ .md-button .md-button--primary } [:octicons-eye-16:](https://www.libreoffice.org/about-us/privacy/privacy-policy-en/){ .card-link title="Privacy Policy" } @@ -91,7 +91,7 @@ cover: productivity.png [:octicons-code-16:](https://www.libreoffice.org/about-us/source-code){ .card-link title="Source Code" } [:octicons-heart-16:](https://www.libreoffice.org/donate/){ .card-link title=Contribute } - ??? 下載 + ??? downloads "下載" - [:simple-googleplay: Google Play](https://www.libreoffice.org/download/android-and-ios/) - [:simple-appstore: App Store](https://www.libreoffice.org/download/android-and-ios/) @@ -105,16 +105,16 @@ cover: productivity.png !!! recommendation - ! [OnlyOffice logo] (assets/img/productivity/onlyoffice.svg) {align = right} + ![OnlyOffice logo](assets/img/productivity/onlyoffice.svg){ align=right } - * * OnlyOffice * *是一個基於雲的免費開源辦公套件，具有廣泛的功能，包括與Nextcloud的整合。 + **OnlyOffice** 是一個基於雲的免費開源辦公套件，具有廣泛的功能，包括與Nextcloud的整合。 [:octicons-home-16: Homepage](https://www.onlyoffice.com){ .md-button .md-button--primary } [:octicons-eye-16:](https://help.onlyoffice.com/products/files/doceditor.aspx?fileid=5048502&doc=SXhWMEVzSEYxNlVVaXJJeUVtS0kyYk14YWdXTEFUQmRWL250NllHNUFGbz0_IjUwNDg1MDIi0){ .card-link title="Privacy Policy" } [:octicons-info-16:](https://helpcenter.onlyoffice.com/userguides.aspx){ .card-link title=Documentation} [:octicons-code-16:](https://github.com/ONLYOFFICE){ .card-link title="Source Code" } - ??? 下載 + ??? downloads "下載" - [:simple-googleplay: Google Play](https://play.google.com/store/apps/details?id=com.onlyoffice.documents) - [:simple-appstore: App Store](https://apps.apple.com/app/id944896972) @@ -128,7 +128,7 @@ cover: productivity.png **請注意，我們所推薦專案沒有任何瓜葛。 ** 除了 [標準準則](about/criteria.md)外，我們還發展出一套明確要求以提出客觀建議。 我們建議您在選擇使用項目之前先熟悉此列表，並進行自己的研究，以確保它是您的正確選擇。 -!!! !!! 例如 "本节是新的" +!!! example "此部分是新的" 我們正在努力為我們網站的每個部分建立定義的標準，這可能會有所變化。 如果您對我們的標準有任何疑問，請在 [論壇上提問](https://discuss.privacyguides.net/latest) ，如果沒有列出，請不要認為我們在提出建議時沒有考慮到某些事情。 當我們推薦一個項目時，有許多因素被考慮和討論，記錄每一個項目都是正在進行式。 @@ -146,9 +146,9 @@ cover: productivity.png !!! recommendation - ! [PrivateBin logo] (assets/img/productivity/privatebin.svg) {align = right} + ![PrivateBin logo](assets/img/productivity/privatebin.svg){ align=right } - * * PrivateBin * *是一個極簡主義的開源網路剪貼板 ，伺服器對黏貼的資料一無所知。 資料在瀏覽器中使用 256位元AES 來加密/解密。 它是 ZeroBin 的改進版本。 有一個[實例列表] (https://privatebin.info/directory/)。 + **PrivateBin** 是一個極簡主義的開源網路剪貼板 ，伺服器對黏貼的資料一無所知。 資料在瀏覽器中使用 256位元AES 來加密/解密。 它是 ZeroBin 的改進版本。 有一個 [實例列表](https://privatebin.info/directory/)。 [:octicons-home-16: Homepage](https://privatebin.info){ .md-button .md-button--primary } [:octicons-server-16:](https://privatebin.info/directory/){ .card-link title="Public Instances"} @@ -159,7 +159,7 @@ cover: productivity.png **請注意，我們所推薦專案沒有任何瓜葛。 ** 除了 [標準準則](about/criteria.md)外，我們還發展出一套明確要求以提出客觀建議。 我們建議您在選擇使用項目之前先熟悉此列表，並進行自己的研究，以確保它是您的正確選擇。 -!!! !!! 例如 "本节是新的" +!!! example "此部分是新的" 我們正在努力為我們網站的每個部分建立定義的標準，這可能會有所變化。 如果您對我們的標準有任何疑問，請在 [論壇上提問](https://discuss.privacyguides.net/latest) ，如果沒有列出，請不要認為我們在提出建議時沒有考慮到某些事情。 當我們推薦一個項目時，有許多因素被考慮和討論，記錄每一個項目都是正在進行式。 diff --git a/i18n/zh-Hant/real-time-communication.md b/i18n/zh-Hant/real-time-communication.md index 8386bf41..fe5eb524 100644 --- a/i18n/zh-Hant/real-time-communication.md +++ b/i18n/zh-Hant/real-time-communication.md @@ -18,9 +18,9 @@ cover: real-time-communication.png !!! recommendation - ! [Signal logo] (assets/img/messengers/signal.svg) {align = right} + ![Signal logo](assets/img/messengers/signal.svg){ align=right } - * * Signal * *是由Signal Messenger LLC開發的行動應用程式。 該應用程式提供即時消息，以及語音和視頻通話。 + **Signal** 是由Signal Messenger LLC開發的行動應用程式。 該應用程式提供即時消息，以及語音和視頻通話。 所有通信都是E2EE。 連絡人清單會使用您的 Signal PIN 加密，而伺服器無法存取。 個人帳號也會加密，並僅與您聊天的聯絡人分享。 @@ -30,7 +30,7 @@ cover: real-time-communication.png [:octicons-code-16:](https://github.com/signalapp){ .card-link title="Source Code" } [:octicons-heart-16:](https://signal.org/donate/){ .card-link title=Contribute } - ??? 下載 + ??? downloads "下載" - [:simple-googleplay: Google Play](https://play.google.com/store/apps/details?id=org.thoughtcrime.securesms) - [:simple-appstore: App Store](https://apps.apple.com/app/id874139669) @@ -51,16 +51,16 @@ Signal支持 [私人羣組](https://signal.org/blog/signal-private-group-system/ !!! recommendation - ! [Simplex logo] (assets/img/messengers/simplex.svg) {align = right} + ![Simplex logo](assets/img/messengers/simplex.svg){ align=right } - * * SimpleX * * Chat 是一個分散的即時通訊工具，不依賴任何獨有識別碼，如電話號碼或用戶名。 SimpleX Chat 使用者可以掃描二維碼或點擊邀請連結以參與羣組對話。 + **SimpleX** Chat 是一個分散的即時通訊工具，不依賴任何獨有識別碼，如電話號碼或用戶名。 SimpleX Chat 使用者可以掃描二維碼或點擊邀請連結以參與羣組對話。 [:octicons-home-16: Homepage](https://simplex.chat){ .md-button .md-button--primary } [:octicons-eye-16:](https://github.com/simplex-chat/simplex-chat/blob/stable/PRIVACY.md){ .card-link title="Privacy Policy" } [:octicons-info-16:](https://github.com/simplex-chat/simplex-chat/tree/stable/docs){ .card-link title=Documentation} [:octicons-code-16:](https://github.com/simplex-chat){ .card-link title="Source Code" } - ??? 下載 + ??? downloads "下載" - [:simple-googleplay: Google Play](https://play.google.com/store/apps/details?id=chat.simplex.app) - [:simple-appstore: App Store](https://apps.apple.com/us/app/simplex-chat/id1605771084) @@ -76,9 +76,9 @@ SimpleX Chat 於2022年10月接受 Trail of Bits [審計](https://simplex.chat/b !!! recommendation - ! [Briar logo] (assets/img/messengers/briar.svg) {align = right} + ![Briar logo](assets/img/messengers/briar.svg){ align=right } - * * Briar * *是 [連接](https://briarproject.org/how-it-works/)其他使用 Tor網路客戶端的加密即時通訊工具。 Briar 還可以在本地附近通過 Wi-Fi 或藍牙連接。 當無法使用網際網路時， Briar 的本地網格(mesh)模式可能很有用。 + **Briar** 是 [連接](https://briarproject.org/how-it-works/)其他使用 Tor網路客戶端的加密即時通訊工具。 Briar 還可以在本地附近通過 Wi-Fi 或藍牙連接。 當無法使用網際網路時， Briar 的本地網格(mesh)模式可能很有用。 [:octicons-home-16: Homepage](https://briarproject.org/){ .md-button .md-button--primary } [:octicons-eye-16:](https://briarproject.org/privacy-policy/){ .card-link title="Privacy Policy" } @@ -86,7 +86,7 @@ SimpleX Chat 於2022年10月接受 Trail of Bits [審計](https://simplex.chat/b [:octicons-code-16:](https://code.briarproject.org/briar/briar){ .card-link title="Source Code" } [:octicons-heart-16:](https://briarproject.org/){ .card-link title="Donation options are listed on the bottom of the homepage" } - ??? 下載 + ??? downloads "下載" - [:simple-googleplay: Google Play](https://play.google.com/store/apps/details?id=org.briarproject.briar.android) - [:simple-windows11: Windows](https://briarproject.org/download-briar-desktop/) @@ -99,21 +99,21 @@ Briar 要新增聯絡人，必須先彼此互加。 您可以交換 `briar://` Briar有一個完整 [發布的規範](https://code.briarproject.org/briar/briar-spec)。 -Briar 使用 Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) 和 [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) 協議支持完美的前向保密。 +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## 額外選項 !!! warning "警告" - 這些通訊軟體沒有 Perfect [Forward Secrecy] (https://zh.wikipedia.org/wiki/Forward_secrecy) (PFS) ，雖然他們滿足了我們推薦產品所無法滿足的某些需求，但不建議長期使用或用在敏感通訊。 訊息收件人之間的任何密鑰洩露都會影響* *所有* *過去通信的機密性。 + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. 訊息收件人之間的任何密鑰洩露都會影響* *所有* *過去通信的機密性。 ### Element !!! recommendation - ! [Element logo] (assets/img/messengers/element.svg) {align = right} + ![Element logo](assets/img/messengers/element.svg){ align=right } - * * Element * *是 [Matrix](https://matrix.org/docs/guides/introduction)協議的參考用戶端，這是一個[開放標準] (https://matrix.org/docs/spec) 、安全去中心化實時通訊。 + **Element** 是 [Matrix](https://matrix.org/docs/guides/introduction) 協議的參考用戶端，這是一個 [開放標準](https://matrix.org/docs/spec) 、安全去中心化實時通訊。 在私人聊天室（需透過邀請加入）共享的訊息和文件預設為 E2EE ，一對一的語音和視訊通話也是如此。 @@ -122,7 +122,7 @@ Briar 使用 Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/ [:octicons-info-16:](https://element.io/help){ .card-link title=Documentation} [:octicons-code-16:](https://github.com/vector-im){ .card-link title="Source Code" } - ??? 下載 + ??? downloads "下載" - [:simple-googleplay: Google Play](https://play.google.com/store/apps/details?id=im.vector.app) - [:simple-appstore: App Store](https://apps.apple.com/app/vector/id1083446067) @@ -147,18 +147,18 @@ Matrix 協議本身 [理論上支援 PFS](https://gitlab.matrix.org/matrix-org/o !!! recommendation - ! [Session logo] (assets/img/messengers/session.svg) {align = right} + ![Session logo](assets/img/messengers/session.svg){ align=right } - * * Session * *是一款分散式通訊軟體，專注於私密、安全和匿名。 Session 支援直接訊息、羣組聊天和語音通話。 + **Session** 是一款分散式通訊軟體，專注於私密、安全和匿名。 Session 支援直接訊息、羣組聊天和語音通話。 - Session使用去中心化的[Oxen Service Node Network] (https://oxen.io/)來儲存和路由訊息。 每條加密訊息都通過 Oxen Service Node Network 中三個節點路由，使得節點幾乎不可能編譯有意義信息給此網路的使用者。 + Session使用去中心化的 [Oxen Service Node Network](https://oxen.io/) 來儲存和路由訊息。 每條加密訊息都通過 Oxen Service Node Network 中三個節點路由，使得節點幾乎不可能編譯有意義信息給此網路的使用者。 [:octicons-home-16: Homepage](https://getsession.org/){ .md-button .md-button--primary } [:octicons-eye-16:](https://getsession.org/privacy-policy){ .card-link title="Privacy Policy" } [:octicons-info-16:](https://getsession.org/faq){ .card-link title=Documentation} [:octicons-code-16:](https://github.com/oxen-io){ .card-link title="Source Code" } - ??? 下載 + ??? downloads "下載" - [:simple-googleplay: Google Play](https://play.google.com/store/apps/details?id=network.loki.messenger) - [:simple-appstore: App Store](https://apps.apple.com/app/id1470168868) @@ -182,7 +182,7 @@ Session [白皮書](https://arxiv.org/pdf/2002.04609.pdf) ，描述了應用程 **請注意，我們所推薦專案沒有任何瓜葛。 ** 除了 [標準準則](about/criteria.md)外，我們還發展出一套明確要求以提出客觀建議。 我們建議您在選擇使用項目之前先熟悉此列表，並進行自己的研究，以確保它是您的正確選擇。 -!!! !!! 例如 "本节是新的" +!!! example "此部分是新的" 我們正在努力為我們網站的每個部分建立定義的標準，這可能會有所變化。 如果您對我們的標準有任何疑問，請在 [論壇上提問](https://discuss.privacyguides.net/latest) ，如果沒有列出，請不要認為我們在提出建議時沒有考慮到某些事情。 當我們推薦一個項目時，有許多因素被考慮和討論，記錄每一個項目都是正在進行式。 @@ -198,7 +198,7 @@ Session [白皮書](https://arxiv.org/pdf/2002.04609.pdf) ，描述了應用程 最佳案例標準代表了我們希望從這個類別的完美項目應具備的功能。 推薦產品可能沒有此功能，但若有這些功能則會讓排名更為提高。 -- 要有完美的向前保密機制。 +- Should have Forward Secrecy. - 應該有開源伺服器。 - 應該是分散的，即聯邦式或 P2P。 - 預設情況下，所有訊息皆應使用 E2EE。 diff --git a/i18n/zh-Hant/router.md b/i18n/zh-Hant/router.md index 236cfacb..2edaeac1 100644 --- a/i18n/zh-Hant/router.md +++ b/i18n/zh-Hant/router.md @@ -11,10 +11,10 @@ cover: router.png !!! recommendation - ! [OpenWrt logo] (assets/img/router/openwrt.svg#only-light) {align = right} - ! [OpenWrt logo] (assets/img/router/openwrt-dark.svg#only-dark) {align = right} + ![OpenWrt logo](assets/img/router/openwrt.svg#only-light){ align=right } + ![OpenWrt logo](assets/img/router/openwrt-dark.svg#only-dark){ align=right } - * * OpenWrt * *是一個基於 Linux 的操作系統；它主要用於嵌入式設備以路由網路流量。 它包括util-linux ， uClibc和BusyBox。 所有組件都已為家庭路由器進行了優化。 + **OpenWrt** 是一個基於 Linux 的操作系統；它主要用於嵌入式設備以路由網路流量。 它包括util-linux ， uClibc和BusyBox。 所有組件都已為家庭路由器進行了優化。 [:octicons-home-16: Homepage](https://openwrt.org){ .md-button .md-button--primary } [:octicons-info-16:](https://openwrt.org/docs/start){ .card-link title=Documentation} @@ -27,9 +27,9 @@ cover: router.png !!! recommendation - ! [OPNsense logo] (assets/img/router/opnsense.svg) {align = right} + ![OPNsense logo](assets/img/router/opnsense.svg){ align=right } - * * OPNsense * *是開源的、基於FreeBSD 的防火牆和路由平臺，它包含許多進階功能，如流量整形、負載平衡和 VPN 功能，且有插件的形式提供更多功能。 OPNsense 通常部署作邊界防火牆、路由器、無線存取點、DHCP伺服器、DNS伺服器和 VPN 端點。 + **OPNsense** 是開源的、基於FreeBSD 的防火牆和路由平臺，它包含許多進階功能，如流量整形、負載平衡和 VPN 功能，且有插件的形式提供更多功能。 OPNsense 通常部署作邊界防火牆、路由器、無線存取點、DHCP伺服器、DNS伺服器和 VPN 端點。 [:octicons-home-16: Homepage](https://opnsense.org/){ .md-button .md-button--primary } [:octicons-info-16:](https://docs.opnsense.org/index.html){ .card-link title=Documentation} @@ -42,9 +42,9 @@ OPNsense 一開始是從 [pfSense](https://en.wikipedia.org/wiki/PfSense)分支 **請注意，我們所推薦專案沒有任何瓜葛。 ** 除了 [標準準則](about/criteria.md)外，我們還發展出一套明確要求以提出客觀建議。 我們建議您在選擇使用項目之前先熟悉此列表，並進行自己的研究，以確保它是您的正確選擇。 -!!! 示例“此部分是新的” +!!! example "此部分是新的" - 我們正在努力為這個網站的各個部分建立明確標準，它可能依情況變化。 如果您對我們的標準有任何疑問，請在[論壇上提問] (https://discuss.privacyguides.net/latest) ，如果沒有列出，請不要認為我們在提出建議時沒有考慮到某些事情。 當我們推薦一個項目時，有許多因素被考慮和討論，記錄每一個項目都是正在進行式。 + 我們正在努力為這個網站的各個部分建立明確標準，它可能依情況變化。 如果您對我們的標準有任何疑問，請 [論壇上提問](https://discuss.privacyguides.net/latest) ，如果沒有列出，請不要認為我們在提出建議時沒有考慮到某些事情。 當我們推薦一個項目時，有許多因素被考慮和討論，記錄每一個項目都是正在進行式。 - 它必須是開源的。 - 必須定期更新。 diff --git a/i18n/zh-Hant/search-engines.md b/i18n/zh-Hant/search-engines.md index 3f85fd45..1007be49 100644 --- a/i18n/zh-Hant/search-engines.md +++ b/i18n/zh-Hant/search-engines.md @@ -16,13 +16,13 @@ cover: search-engines.png !!! recommendation - ! [Brave Search logo] (assets/img/search-engines/brave-search.svg) {align = right} + ![Brave Search logo](assets/img/search-engines/brave-search.svg){ align=right } - * * Brave Search * *由 Brave 開發，主要提供自己獨立索引的結果。 該索引是針對 Google 搜索進行優化，因此與其他替代方案相比，可以提供更具上下文準確性的結果。 + **Brave Search** 由 Brave 開發，主要提供自己獨立索引的結果。 該索引是針對 Google 搜索進行優化，因此與其他替代方案相比，可以提供更具上下文準確性的結果。 Brave Search 包括獨特的功能，如討論，突出了對話為中心的結果，如論壇文章。 - 我們建議您停用[匿名使用指標] (https://search.brave.com/help/usage-metrics) ，因為它預設為啟用，可在設定中停用。 + 我們建議您停用 [匿名使用指標](https://search.brave.com/help/usage-metrics) ，因為它預設為啟用，可在設定中停用。 [:octicons-home-16: Homepage](https://search.brave.com/){ .md-button .md-button--primary } [:simple-torbrowser:](https://search.brave4u7jddbv7cyviptqjc7jusxh72uik7zt6adtckl5f4nwy2v72qd.onion){ .card-link title="Onion Service" } @@ -35,9 +35,9 @@ Brave Search 總部在美國。 他們的 [隱私政策](https://search.brave.co !!! recommendation - ! [DuckDuckGo logo] (assets/img/search-engines/duckduckgo.svg) {align = right} + ![DuckDuckGo logo](assets/img/search-engines/duckduckgo.svg){ align=right } - * * DuckDuckGo * *最主流的隱私搜尋引擎選項之一。 著名的 DuckDuckGo 搜索功能包括 [bangs]( https://duckduckgo.com/bang)和許多[即時答案] (https://help.duckduckgo.com/duckduckgo-help-pages/features/instant-answers-and-other-features/)。 搜尋引擎依賴商業 Bing API 來提供大多數結果，但它確實使用許多[其他來源](https://help.duckduckgo.com/results/sources/ )來獲取即時答案和其他非主要結果。 + **DuckDuckGo** 最主流的隱私搜尋引擎選項之一。 著名的 DuckDuckGo 搜索功能包括 [bangs]( https://duckduckgo.com/bang)和許多[即時答案] (https://help.duckduckgo.com/duckduckgo-help-pages/features/instant-answers-and-other-features/)。 搜尋引擎依賴商業 Bing API 來提供大多數結果，但它確實使用許多[其他來源](https://help.duckduckgo.com/results/sources/ )來獲取即時答案和其他非主要結果。 DuckDuckGo 是 Tor瀏覽器的預設搜尋引擎，也是 Apple Safari 瀏覽器上為數不多的可用選項之一。 @@ -54,9 +54,9 @@ DuckDuckGo 提供兩種 [其它版本](https://help.duckduckgo.com/features/non- !!! recommendation - ! [SearXNG logo] (assets/img/search-engines/searxng.svg) {align = right} + ![SearXNG logo](assets/img/search-engines/searxng.svg){ align=right } - * * SearXNG * *是一個開源、自我託管的中繼搜索引擎，聚合其他搜索引擎的結果，而自身不儲存任何資訊。 它是一個積極維護的 [SearX] (https://github.com/searx/searx)分支。 + **SearXNG** 是一個開源、自我託管的中繼搜索引擎，聚合其他搜索引擎的結果，而自身不儲存任何資訊。 它是一個積極維護的 [SearX](https://github.com/searx/searx) 分支。 [:octicons-home-16: Homepage](https://searxng.org){ .md-button .md-button--primary } [:octicons-server-16:](https://searx.space/){ .card-link title="Public Instances"} @@ -72,10 +72,10 @@ SearXNG 是您和它所聚合的搜尋引擎之間的代理。 您的搜尋查 !!! recommendation - ! [Startpage logo] (assets/img/search-engines/startpage.svg#only-light) {align = right} - ! [Startpage logo] (assets/img/search-engines/startpage-dark.svg#only-dark) {align = right} + ![Startpage logo](assets/img/search-engines/startpage.svg#only-light){ align=right } + ![Startpage logo](assets/img/search-engines/startpage-dark.svg#only-dark){ align=right } - * * Startpage * *是一個提供 Google 搜索結果而聞名的私密搜索引擎。 Startpage 的獨特功能之一是[匿名視圖] (https://www.startpage.com/en/anonymous-view/) ，它努力標準化用戶活動，使其更難被突出識別。 這個功能可用來隱藏 [某些](https://support.startpage.com/hc/en-us/articles/4455540212116-The-Anonymous-View-Proxy-technical-details) 網路與瀏覽器特徵。 不像名字所暗示的，該功能不應該依賴於匿名。 如果您正在尋找匿名性，請改用[Tor瀏覽器] (tor.md#tor-browser)。 + **Startpage** 是一個提供 Google 搜索結果而聞名的私密搜索引擎。 Startpage 的獨特功能之一是 [匿名視圖](https://www.startpage.com/en/anonymous-view/) ，它努力標準化用戶活動，使其更難被突出識別。 這個功能可用來隱藏 [某些](https://support.startpage.com/hc/en-us/articles/4455540212116-The-Anonymous-View-Proxy-technical-details) 網路與瀏覽器特徵。 不像名字所暗示的，該功能不應該依賴於匿名。 如果您正在尋找匿名性，請改用 [Tor瀏覽器](tor.md#tor-browser)。 [:octicons-home-16: Homepage](https://www.startpage.com){ .md-button .md-button--primary } [:octicons-eye-16:](https://www.startpage.com/en/privacy-policy){ .card-link title="Privacy Policy" } @@ -83,7 +83,7 @@ SearXNG 是您和它所聚合的搜尋引擎之間的代理。 您的搜尋查 !!! warning "警告" - Startpage 定期限制服務對某些 IP位址的存取，例如為 VPN 或Tor 保留的IP。 [DuckDuckGo](#duckduckgo)和[Brave Search] (#brave-search)是更友好的選項，如果您的威脅模型需要向搜索提供商隱藏您的IP位址。 + Startpage 定期限制服務對某些 IP位址的存取，例如為 VPN 或Tor 保留的IP。 [DuckDuckGo](#duckduckgo) 和 [Brave Search](#brave-search) 是更友好的選項，如果您的威脅模型需要向搜索提供商隱藏您的IP位址。 Startpage位於荷蘭。 根據他們的 [隱私政策](https://www.startpage.com/en/privacy-policy/)，他們記錄細節如：作業系統、瀏覽器類型和語言。 他們不會記錄您的IP位址、搜尋查詢或其他個人識別資訊。 @@ -96,7 +96,7 @@ Startpage 大股東是System1，它是一家廣告技術公司。 我們不認 **請注意，我們所推薦專案沒有任何瓜葛。 ** 除了 [標準準則](about/criteria.md)外，我們還發展出一套明確要求以提出客觀建議。 我們建議您在選擇使用項目之前先熟悉此列表，並進行自己的研究，以確保它是您的正確選擇。 -!!! !!! 例如 "本节是新的" +!!! example "此部分是新的" 我們正在努力為我們網站的每個部分建立定義的標準，這可能會有所變化。 如果您對我們的標準有任何疑問，請在 [論壇上提問](https://discuss.privacyguides.net/latest) ，如果沒有列出，請不要認為我們在提出建議時沒有考慮到某些事情。 當我們推薦一個項目時，有許多因素被考慮和討論，記錄每一個項目都是正在進行式。 diff --git a/i18n/zh-Hant/tools.md b/i18n/zh-Hant/tools.md index 8734ab35..24725580 100644 --- a/i18n/zh-Hant/tools.md +++ b/i18n/zh-Hant/tools.md @@ -187,11 +187,11 @@ description: Privacy Guides 是最透明和可靠的網站，用於尋找保護 ??? 注意 "VPN 不會讓您匿名" - 使用 VPN * *不會* *讓您的瀏覽習慣匿名，也不會為不安全（ HTTP ）流量增加額外的安全性。 + 使用 VPN **不會** 讓您的瀏覽習慣匿名，也不會為不安全（ HTTP ）流量增加額外的安全性。 - 如果追求的是**匿名性** ，應該使用 Tor 瀏覽器**取代** VPN。 + 如果追求的是 **匿名性** ，應該使用 Tor 瀏覽器**取代** VPN。 - 如果需要額外的**安全性** ，應該確保一直使用 HTTPS 連接到網站。 VPN不能取代良好的安全措施。 + 如果需要額外的 **安全性** ，應該確保一直使用 HTTPS 連接到網站。 VPN不能取代良好的安全措施。 [了解更多 :material-arrow-right-drop-circle:](vpn.md) @@ -262,9 +262,9 @@ description: Privacy Guides 是最透明和可靠的網站，用於尋找保護 ### 加密軟體 -??? 資訊 "作業系統磁碟加密" +??? info "作業系統磁碟加密" - 若要加密作業系統磁碟，通常建議使用作業系統提供的加密工具，無論是 Windows 的* * BitLocker * *、macOS * * FileVault * *或 Linux * * LUKS * *。 這些工具包含在作業系統中，通常使用硬體加密要素，例如 TPM ，而 VeraCrypt 等其他全磁碟加密軟體則不然。 VeraCrypt 仍然適用於非作業系統磁碟，例如外接磁碟，特別是可以從多重作業系統訪問的磁碟。 + 若要加密作業系統磁碟，通常建議使用作業系統提供的加密工具，無論是 Windows 的 **BitLocker**、macOS **FileVault** 或 Linux **LUKS**。 這些工具包含在作業系統中，通常使用硬體加密要素，例如 TPM ，而 VeraCrypt 等其他全磁碟加密軟體則不然。 VeraCrypt 仍然適用於非作業系統磁碟，例如外接磁碟，特別是可以從多重作業系統訪問的磁碟。 [了解更多 :material-arrow-right-drop-circle:](encryption.md##operating-system-included-full-disk-encryption-fde) diff --git a/i18n/zh-Hant/video-streaming.md b/i18n/zh-Hant/video-streaming.md index 8f887688..910f7424 100644 --- a/i18n/zh-Hant/video-streaming.md +++ b/i18n/zh-Hant/video-streaming.md @@ -11,30 +11,30 @@ cover: video-streaming.png !!! recommendation - ! [LBRY標誌] (assets/img/video-streaming/lbry.svg) {align = right} + ![LBRY標誌](assets/img/video-streaming/lbry.svg){ align=right } - * * LBRY 網路* *是一個分散式視頻共享網絡。 它透過類似 [BitTorrent](https://wikipedia.org/wiki/BitTorrent)-l網路來儲存影片內容，再利用 [區塊錬](https://wikipedia.org/wiki/Blockchain) 來存儲影片之索引。 這種設計的主要好處是抵抗審查。 + **LBRY 網路** 是一個分散式視頻共享網絡。 它透過類似 [BitTorrent](https://wikipedia.org/wiki/BitTorrent)-l網路來儲存影片內容，再利用 [區塊錬](https://wikipedia.org/wiki/Blockchain) 來存儲影片之索引。 這種設計的主要好處是抵抗審查。 - * * LBRY 桌面用戶端* *可協助串流來自 LBRY 網路的影片，並將訂閱清單儲存在自己的 LBRY 錢包。 + **LBRY 桌面用戶端** 可協助串流來自 LBRY 網路的影片，並將訂閱清單儲存在自己的 LBRY 錢包。 [:octicons-home-16: Homepage](https://lbry.com){ .md-button .md-button--primary } [:octicons-eye-16:](https://lbry.com/privacypolicy){ .card-link title="Privacy Policy" } [:octicons-info-16:](https://lbry.com/faq){ .card-link title=Documentation} [:octicons-code-16:](https://github.com/lbryio/lbry-desktop){ .card-link title="Source Code" } - ??? 下載 + ??? downloads "下載" - [:simple-windows11: Windows](https://lbry.com/windows) - [:simple-apple: macOS](https://lbry.com/osx) - [:simple-linux: Linux](https://lbry.com/linux) -!!! 備註 +!!! note "備註" - 建議僅使用* * LBRY桌面用戶端* * ，因為 F-Droid、Play Store 和App Store 中的 [Odysee](https://odysee.com)網站和 LBRY 用戶端具有強制同步和遙測功能。 + 建議僅使用 **LBRY桌面用戶端** ，因為 F-Droid、Play Store 和App Store 中的 [Odysee](https://odysee.com)網站和 LBRY 用戶端具有強制同步和遙測功能。 -!!! 警告 +!!! warning "警告" - 在觀看和託管影片時，LBRY 網路可看到您的 IP 位址。 如果您的[威脅模型] (basics/threat-modeling.md)需要隱藏您的IP 位址，請考慮使用 [VPN](vpn.md)或 [Tor](https://www.torproject.org)。 + 在觀看和託管影片時，LBRY 網路可看到您的 IP 位址。 如果您的 [威脅模型](basics/threat-modeling.md) 需要隱藏您的IP 位址，請考慮使用 [VPN](vpn.md)或 [Tor](https://www.torproject.org)。 建議**不要** 錢包與 LBRY Inc. 設為同步，因為尚不支援錢包同步的加密功能。 如果您將錢包與 LBRY Inc.同步，則必須信任他們不會查看您的訂閱列表， [LBC](https://lbry.com/faq/earn-credits) 資金或控制您的頻道。 @@ -44,9 +44,9 @@ cover: video-streaming.png **請注意，我們所推薦專案沒有任何瓜葛。 ** 除了 [標準準則](about/criteria.md)外，我們還發展出一套明確要求以提出客觀建議。 我們建議您在選擇使用項目之前先熟悉此列表，並進行自己的研究，以確保它是您的正確選擇。 -!!! 示例“此部分是新的” +!!! example "此部分是新的" - 我們正在努力為我們網站的每個部分建立定義的標準，這可能會有所變化。 如果您對我們的標準有任何疑問，請在[論壇上提問] (https://discuss.privacyguides.net/latest) ，如果沒有列出，請不要認為我們在提出建議時沒有考慮到某些事情。 當我們推薦一個項目時，有許多因素被考慮和討論，記錄每一個項目都是正在進行式。 + 我們正在努力為我們網站的每個部分建立定義的標準，這可能會有所變化。 如果您對我們的標準有任何疑問，請在 [論壇上提問](https://discuss.privacyguides.net/latest) ，如果沒有列出，請不要認為我們在提出建議時沒有考慮到某些事情。 當我們推薦一個項目時，有許多因素被考慮和討論，記錄每一個項目都是正在進行式。 - 無需集中式帳戶就可觀看影片。 - 分散式驗證，例如通過行動錢包的私鑰進行驗證是可以接受的。 diff --git a/i18n/zh-Hant/vpn.md b/i18n/zh-Hant/vpn.md index 51a75eec..284987ff 100644 --- a/i18n/zh-Hant/vpn.md +++ b/i18n/zh-Hant/vpn.md @@ -350,13 +350,13 @@ Intel 處理器的 Mac 電腦 若用 VPN killswitch 會發生 [系統崩潰](htt **最低合格要求：** - 強固加密方案：具有 SHA-256 驗證的 OpenVPN; RSA-2048 或更好的握手; AES-256-GCM 或 AES-256-CBC 數據加密。 -- 完全前向保密 (PFS) +- Forward Secrecy. - 公佈信譽良好第三方公司的安全審計。 **最佳案例：** - 最強加密： RSA-4096。 -- 完全前向保密 (PFS) +- Forward Secrecy. - 由信譽良好的第三方公司執行公佈的全面安全審計。 - 漏洞獎勵計劃和/或協調漏洞披露過程。 diff --git a/i18n/zh/real-time-communication.md b/i18n/zh/real-time-communication.md index c0aaa7f3..2eb5cc26 100644 --- a/i18n/zh/real-time-communication.md +++ b/i18n/zh/real-time-communication.md @@ -99,13 +99,13 @@ The client software was independently [audited](https://briarproject.org/news/20 Briar has a fully [published specification](https://code.briarproject.org/briar/briar-spec). -Briar supports perfect forward secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. +Briar supports Forward Secrecy by using the Bramble [Handshake](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BHP.md) and [Transport](https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BTP.md) protocol. ## Additional Options !!! 推荐 - These messengers do not have Perfect [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) (PFS), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. + These messengers do not have [Forward Secrecy](https://en.wikipedia.org/wiki/Forward_secrecy), and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of **all** past communications. ### Element @@ -189,7 +189,7 @@ Session has a [whitepaper](https://arxiv.org/pdf/2002.04609.pdf) describing the Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page. -- Should have Perfect Forward Secrecy. +- Should have Forward Secrecy. - Should have open-source servers. - Should be decentralized, i.e. federated or P2P. - Should use E2EE for all messages by default. diff --git a/i18n/zh/vpn.md b/i18n/zh/vpn.md index ce4cd38d..cb179fe0 100644 --- a/i18n/zh/vpn.md +++ b/i18n/zh/vpn.md @@ -268,13 +268,13 @@ A VPN is pointless if it can't even provide adequate security. We require all ou **符合条件的最低要求。** - Strong Encryption Schemes: OpenVPN with SHA-256 authentication; RSA-2048 or better handshake; AES-256-GCM or AES-256-CBC data encryption. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Published security audits from a reputable third-party firm. **Best Case:** - Strongest Encryption: RSA-4096. -- Perfect Forward Secrecy (PFS). +- Forward Secrecy. - Comprehensive published security audits from a reputable third-party firm. - Bug-bounty programs and/or a coordinated vulnerability-disclosure process. diff --git a/includes/abbreviations.ar.txt b/includes/abbreviations.ar.txt index 5926f4ed..f1806439 100644 --- a/includes/abbreviations.ar.txt +++ b/includes/abbreviations.ar.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase Cloud Messaging *[FDE]: Full Disk Encryption *[FIDO]: Fast IDentity Online +*[FS]: Forward Secrecy *[fork]: A new software project created by copying an existing project and adding to it independently *[GDPR]: General Data Protection Regulation *[GPG]: GNU Privacy Guard (PGP implementation) diff --git a/includes/abbreviations.bn.txt b/includes/abbreviations.bn.txt index db766c5e..b6e948d5 100644 --- a/includes/abbreviations.bn.txt +++ b/includes/abbreviations.bn.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase Cloud Messaging *[FDE]: Full Disk Encryption *[FIDO]: Fast IDentity Online +*[FS]: Forward Secrecy *[fork]: A new software project created by copying an existing project and adding to it independently *[GDPR]: General Data Protection Regulation *[GPG]: GNU Privacy Guard (PGP implementation) diff --git a/includes/abbreviations.cs.txt b/includes/abbreviations.cs.txt index 0367f357..85303cf7 100644 --- a/includes/abbreviations.cs.txt +++ b/includes/abbreviations.cs.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase Cloud Messaging *[FDE]: Full Disk Encryption *[FIDO]: Fast IDentity Online +*[FS]: Forward Secrecy *[fork]: A new software project created by copying an existing project and adding to it independently *[GDPR]: General Data Protection Regulation *[GPG]: GNU Privacy Guard (implementace PGP) diff --git a/includes/abbreviations.de.txt b/includes/abbreviations.de.txt index 771cbe2e..a3a98802 100644 --- a/includes/abbreviations.de.txt +++ b/includes/abbreviations.de.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase Cloud Messaging *[FDE]: vollständige Festplattenverschlüsselung *[FIDO]: Fast IDentity Online +*[FS]: Forward Secrecy *[fork]: Ein neues Softwareprojekt, das durch Kopieren eines bestehenden Projekts und das unabhängige Hinzufügen erstellt wird *[DSGVO]: Datenschutzverordnung *[GPG]: GNU Privacy Guard (PGP-Implementierung) diff --git a/includes/abbreviations.el.txt b/includes/abbreviations.el.txt index db766c5e..b6e948d5 100644 --- a/includes/abbreviations.el.txt +++ b/includes/abbreviations.el.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase Cloud Messaging *[FDE]: Full Disk Encryption *[FIDO]: Fast IDentity Online +*[FS]: Forward Secrecy *[fork]: A new software project created by copying an existing project and adding to it independently *[GDPR]: General Data Protection Regulation *[GPG]: GNU Privacy Guard (PGP implementation) diff --git a/includes/abbreviations.eo.txt b/includes/abbreviations.eo.txt index db766c5e..b6e948d5 100644 --- a/includes/abbreviations.eo.txt +++ b/includes/abbreviations.eo.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase Cloud Messaging *[FDE]: Full Disk Encryption *[FIDO]: Fast IDentity Online +*[FS]: Forward Secrecy *[fork]: A new software project created by copying an existing project and adding to it independently *[GDPR]: General Data Protection Regulation *[GPG]: GNU Privacy Guard (PGP implementation) diff --git a/includes/abbreviations.es.txt b/includes/abbreviations.es.txt index ddaec089..3351fa09 100644 --- a/includes/abbreviations.es.txt +++ b/includes/abbreviations.es.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase Cloud Messaging *[FDE]: Encriptación de Disco Completo *[FIDO]: Fast IDentity Online +*[FS]: Forward Secrecy *[fork]: Un nuevo proyecto de software creado copiando un proyecto existente y añadiéndole elementos de forma independiente *[GDPR]: Reglamento General de Protección de Datos *[GPG]: GNU Privacy Guard (implementación de PGP) diff --git a/includes/abbreviations.fa.txt b/includes/abbreviations.fa.txt index db766c5e..b6e948d5 100644 --- a/includes/abbreviations.fa.txt +++ b/includes/abbreviations.fa.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase Cloud Messaging *[FDE]: Full Disk Encryption *[FIDO]: Fast IDentity Online +*[FS]: Forward Secrecy *[fork]: A new software project created by copying an existing project and adding to it independently *[GDPR]: General Data Protection Regulation *[GPG]: GNU Privacy Guard (PGP implementation) diff --git a/includes/abbreviations.fr.txt b/includes/abbreviations.fr.txt index 4ad83900..bcf2c615 100644 --- a/includes/abbreviations.fr.txt +++ b/includes/abbreviations.fr.txt @@ -24,6 +24,7 @@ *[FCM]: Messagerie Cloud Firebase *[FDE]: Chiffrement complet du disque *[FIDO]: Identité rapide en ligne +*[FS]: Forward Secrecy *[fork]: Un nouveau projet de logiciel créé en copiant un projet existant et en le complétant de manière indépendante *[RGPD]: Règlement Général sur la Protection des Données *[GPG]: GNU Privacy Guard (implémentation de PGP) diff --git a/includes/abbreviations.he.txt b/includes/abbreviations.he.txt index f6253345..efe943f9 100644 --- a/includes/abbreviations.he.txt +++ b/includes/abbreviations.he.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase Cloud Messaging *[FDE]: הצפנת דיסק מלאה *[FIDO]: זיהוי מהיר באינטרנט +*[FS]: Forward Secrecy *[fork]: פרויקט תוכנה חדש שנוצר על ידי העתקת פרויקט קיים והוספה אליו באופן עצמאי *[GDPR]: תקנת הגנת מידע כללית *[GPG]: GNU Privacy Guard (יישום PGP) diff --git a/includes/abbreviations.hi.txt b/includes/abbreviations.hi.txt index db766c5e..b6e948d5 100644 --- a/includes/abbreviations.hi.txt +++ b/includes/abbreviations.hi.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase Cloud Messaging *[FDE]: Full Disk Encryption *[FIDO]: Fast IDentity Online +*[FS]: Forward Secrecy *[fork]: A new software project created by copying an existing project and adding to it independently *[GDPR]: General Data Protection Regulation *[GPG]: GNU Privacy Guard (PGP implementation) diff --git a/includes/abbreviations.hu.txt b/includes/abbreviations.hu.txt index e546ac56..fab280ae 100644 --- a/includes/abbreviations.hu.txt +++ b/includes/abbreviations.hu.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase Cloud Messaging *[FDE]: Full Disk Encryption - Teljes Lemez Titkosítás *[FIDO]: Fast IDentity Online +*[FS]: Forward Secrecy *[fork]: Egy meglévő projekt másolásával és független hozzájárulással létrehozott új szoftverprojekt *[GDPR]: General Data Protection Regulation - Általános Adatvédelmi Rendelet *[GPG]: GNU Privacy Guard (PGP implementáció) diff --git a/includes/abbreviations.id.txt b/includes/abbreviations.id.txt index a4218e75..1c9f86b6 100644 --- a/includes/abbreviations.id.txt +++ b/includes/abbreviations.id.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase Cloud Messaging *[FDE]: Enkripsi Diska Penuh *[FIDO]: Fast IDentity Online (Identitas Daring Cepat) +*[FS]: Forward Secrecy *[fork]: Proyek perangkat lunak baru yang dibuat dengan menyalin proyek yang sudah ada dan menambahkannya secara mandiri *[GDPR]: Peraturan Perlindungan Data Umum *[GPG]: GNU Privacy Guard (implementasi PGP) diff --git a/includes/abbreviations.it.txt b/includes/abbreviations.it.txt index 293b65fc..f776d4df 100644 --- a/includes/abbreviations.it.txt +++ b/includes/abbreviations.it.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase Cloud Messaging *[FDE]: Crittografia completa del disco *[FIDO]: Fast Identity Online +*[FS]: Forward Secrecy *[fork]: Un nuovo progetto basato su un altro progetto già esistente con l'aggiunta di elementi indipendenti *[GDPR]: Regolamento generale per la protezione dei dati personali *[GPG]: GNU Privacy Guard (implementazione PGP) diff --git a/includes/abbreviations.ja.txt b/includes/abbreviations.ja.txt index df9dbba0..1827a995 100644 --- a/includes/abbreviations.ja.txt +++ b/includes/abbreviations.ja.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase Cloud Messaging *[FDE]: Full Disk Encryption *[FIDO]: Fast IDentity Online +*[FS]: Forward Secrecy *[fork]: A new software project created by copying an existing project and adding to it independently *[GDPR]: EU一般データ保護規則（General Data Protection Regulation） *[GPG]: GNU Privacy Guard (PGP implementation) diff --git a/includes/abbreviations.ko.txt b/includes/abbreviations.ko.txt index 19e30847..011a8c8b 100644 --- a/includes/abbreviations.ko.txt +++ b/includes/abbreviations.ko.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase 클라우드 메시징 *[FDE]: 전체 디스크 암호화 *[FIDO]: Fast IDentity Online +*[FS]: Forward Secrecy *[포크]: 기존 프로젝트를 복사한 뒤 독립적으로 개발하여 만들어진 새로운 소프트웨어 프로젝트 *[GDPR]: 유럽 연합 일반 데이터 보호 규칙(General Data Protection Regulation) *[GPG]: GNU Privacy Guard (PGP 구현체) diff --git a/includes/abbreviations.ku-IQ.txt b/includes/abbreviations.ku-IQ.txt index db766c5e..b6e948d5 100644 --- a/includes/abbreviations.ku-IQ.txt +++ b/includes/abbreviations.ku-IQ.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase Cloud Messaging *[FDE]: Full Disk Encryption *[FIDO]: Fast IDentity Online +*[FS]: Forward Secrecy *[fork]: A new software project created by copying an existing project and adding to it independently *[GDPR]: General Data Protection Regulation *[GPG]: GNU Privacy Guard (PGP implementation) diff --git a/includes/abbreviations.nl.txt b/includes/abbreviations.nl.txt index d0ee5611..a9e3ff07 100644 --- a/includes/abbreviations.nl.txt +++ b/includes/abbreviations.nl.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase Cloud Messaging *[FDE]: Full Disk Encryption *[FIDO]: Fast IDentity Online +*[FS]: Forward Secrecy *[fork]: Een nieuw software project gemaakt door een bestaand project te kopiëren en er zelfstandig iets aan toe te voegen *[GDPR]: General Data Protection Regulation *[GPG]: GNU Privacy Guard (PGP implementation) diff --git a/includes/abbreviations.pl.txt b/includes/abbreviations.pl.txt index 7e54f9ae..2e98cc67 100644 --- a/includes/abbreviations.pl.txt +++ b/includes/abbreviations.pl.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase Cloud Messaging *[FDE]: Full Disk Encryption *[FIDO]: Fast IDentity Online +*[FS]: Forward Secrecy *[fork]: A new software project created by copying an existing project and adding to it independently *[GDPR]: General Data Protection Regulation *[GPG]: GNU Privacy Guard (PGP implementation) diff --git a/includes/abbreviations.pt-BR.txt b/includes/abbreviations.pt-BR.txt index cb079a07..37ea2c1a 100644 --- a/includes/abbreviations.pt-BR.txt +++ b/includes/abbreviations.pt-BR.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase Cloud Messaging *[FDE]: Criptografia total de disco *[FIDO]: Fast IDentity Online +*[FS]: Forward Secrecy *[fork]: Um novo projeto de software criado copiando um projeto existente e desenvolvendo ele independentemente *[GDPR]: Regulamento Geral de Proteção de Dados *[GPG]: GNU Privacy Guard (implementação do PGP) diff --git a/includes/abbreviations.pt.txt b/includes/abbreviations.pt.txt index b747ba8b..d48cf9e5 100644 --- a/includes/abbreviations.pt.txt +++ b/includes/abbreviations.pt.txt @@ -24,6 +24,7 @@ *[FCM]: Mensagens em nuvem do Firebase *[FDE]: Encriptação completa do disco *[FIDO]: Identidade rápida online +*[FS]: Forward Secrecy *[fork]: Um novo projeto de software criado através da cópia de um projeto existente e do seu melhoramento feito de forma independente *[GDPR]: Regulamento Geral de Proteção de Dados (RGPD) *[GPG]: GNU Privacy Guard (implementação do PGP) diff --git a/includes/abbreviations.ru.txt b/includes/abbreviations.ru.txt index 258119bf..12ad0ac8 100644 --- a/includes/abbreviations.ru.txt +++ b/includes/abbreviations.ru.txt @@ -24,6 +24,7 @@ *[FCM]: Обмен сообщениями Firebase Cloud *[FDE]: Полное шифрование диска *[FIDO]: Быстрая идентификация онлайн +*[ПС]: Прямая секретность (Forward Secrecy) *[форк]: Новое программное обеспечение, созданное путем модификации открытого кода существующего проекта *[GDPR]: Общий регламент по защите данных *[GPG]: GNU Privacy Guard (реализация PGP) diff --git a/includes/abbreviations.sv.txt b/includes/abbreviations.sv.txt index cc8ff0fc..567cac2f 100644 --- a/includes/abbreviations.sv.txt +++ b/includes/abbreviations.sv.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase Cloud Messaging *[FDE]: Fullständig diskkryptering *[FIDO]: Snabb IDentitet online +*[FS]: Forward Secrecy *[fork]: Ett nytt programvaruprojekt som skapas genom att ett befintligt projekt kopieras och kompletteras självständigt *[GDPR]: Allmän dataskyddsförordning *[GPG]: GNU Privacy Guard (PGP-implementering) diff --git a/includes/abbreviations.tr.txt b/includes/abbreviations.tr.txt index 24adeb09..5aa6dea8 100644 --- a/includes/abbreviations.tr.txt +++ b/includes/abbreviations.tr.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase Cloud Messaging *[FDE]: Full Disk Encryption *[FIDO]: Fast IDentity Online +*[FS]: Forward Secrecy *[fork]: A new software project created by copying an existing project and adding to it independently *[GDPR]: General Data Protection Regulation *[GPG]: GNU Privacy Guard (PGP implementation) diff --git a/includes/abbreviations.uk.txt b/includes/abbreviations.uk.txt index 27700d25..329f6bc8 100644 --- a/includes/abbreviations.uk.txt +++ b/includes/abbreviations.uk.txt @@ -24,6 +24,7 @@ *[FCM]: Хмарний обмін повідомленнями Firebase (Firebase Cloud Messaging) *[FDE]: Повне шифрування диска (Full Disk Encryption) *[FIDO]: Швидка ідентифікація особи онлайн (Fast IDentity Online) +*[FS]: Forward Secrecy *[форк]: Новий програмний проєкт, створений шляхом копіювання наявного проєкту та самостійного його доповнення *[GDPR]: Загальний регламент про захист даних ЄС (General Data Protection Regulation) *[GPG]: GNU Privacy Guard (реалізація PGP) diff --git a/includes/abbreviations.vi.txt b/includes/abbreviations.vi.txt index db766c5e..b6e948d5 100644 --- a/includes/abbreviations.vi.txt +++ b/includes/abbreviations.vi.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase Cloud Messaging *[FDE]: Full Disk Encryption *[FIDO]: Fast IDentity Online +*[FS]: Forward Secrecy *[fork]: A new software project created by copying an existing project and adding to it independently *[GDPR]: General Data Protection Regulation *[GPG]: GNU Privacy Guard (PGP implementation) diff --git a/includes/abbreviations.zh-Hant.txt b/includes/abbreviations.zh-Hant.txt index 344673bf..7155411b 100644 --- a/includes/abbreviations.zh-Hant.txt +++ b/includes/abbreviations.zh-Hant.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase 雲消息 *[FDE]: 完整磁碟加密 *[FIDO]: 快速線上身份驗證(FIDO) +*[FS]: Forward Secrecy *[fork]: 從現有軟體專案複製再另外分隔出來的新獨立專案。 *[GDPR]: 一般資料保護法規 *[GPG]: GNU Privacy Guard (PGP 實行) diff --git a/includes/abbreviations.zh.txt b/includes/abbreviations.zh.txt index 7b8d1483..a5ee8e7b 100644 --- a/includes/abbreviations.zh.txt +++ b/includes/abbreviations.zh.txt @@ -24,6 +24,7 @@ *[FCM]: Firebase Cloud Messaging *[FDE]: Full Disk Encryption *[FIDO]: Fast IDentity Online +*[FS]: Forward Secrecy *[fork]: A new software project created by copying an existing project and adding to it independently *[GDPR]: General Data Protection Regulation *[GPG]: GNU Privacy Guard (PGP implementation)