privacyguides/i18n
1
0
Fork 0
mirror of https://github.com/privacyguides/i18n.git synced 2025-08-26 08:09:15 +00:00
Code Activity

New Crowdin translations by GitHub Action

Browse Source
This commit is contained in:
Crowdin Bot
2023-06-29 04:04:24 +00:00
parent d0ee0080a9
commit 0dd27603db
96 changed files with 361 additions and 329 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
i18n/pt-BR/real-time-communication.md
View File

@@ -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.

4
i18n/pt-BR/vpn.md
View File

@@ -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.