mirror of
https://github.com/privacyguides/i18n.git
synced 2026-07-07 07:35:47 +00:00
New Crowdin translations by GitHub Action
This commit is contained in:
+17
-18
@@ -10,7 +10,6 @@ global:
|
||||
- "table tbody"
|
||||
---
|
||||
|
||||
<!-- markdownlint-disable MD024 -->
|
||||
O "email" é praticamente uma necessidade para usar qualquer serviço “online”, contudo não o recomendamos para conversas pessoais. Ao invés de utilizar email para falar com outras pessoas, considere utilizar um meio de mensagens instantâneas que suporte sigilo encaminhado.
|
||||
|
||||
[Mensageiros Instantâneos Recomendados](real-time-communication.md ""){.md-button}
|
||||
@@ -55,7 +54,7 @@ OpenPGP also does not support Forward secrecy, which means if either your or the
|
||||
|
||||
{ align=right }
|
||||
|
||||
**Proton Mail** é um serviço de email com foco na privacidade, criptografia, segurança, e facilidade de uso. Eles estão operando desde **2013**. Proton AG é localizado em Genève, Suíça. The Proton Mail Free plan comes with 500MB of Mail storage, which you can increase up to 1GB for free.
|
||||
**Proton Mail** é um serviço de email com foco na privacidade, criptografia, segurança, e facilidade de uso. They have been in operation since 2013. Proton AG é localizado em Genève, Suíça. The Proton Mail Free plan comes with 500MB of Mail storage, which you can increase up to 1GB for free.
|
||||
|
||||
[:octicons-home-16: Homepage](https://proton.me/mail){ .md-button .md-button--primary }
|
||||
[:simple-torbrowser:](https://protonmailrmez3lotccipshtkleegetolb73fuirgj7r4o4vfu7ozyd.onion){ .card-link title="Onion Service" }
|
||||
@@ -192,7 +191,7 @@ Estes provedores armazenam os seus e-mails com criptografia de conhecimento zero
|
||||
{ align=right }
|
||||
{ align=right }
|
||||
|
||||
**Tuta** is an email service with a focus on security and privacy through the use of encryption. Tuta has been in operation since **2011** and is based in Hanover, Germany. Free accounts start with 1GB of storage.
|
||||
**Tuta** (formerly *Tutanota*) is an email service with a focus on security and privacy through the use of encryption. Tuta has been in operation since 2011 and is based in Hanover, Germany. Free accounts start with 1GB of storage.
|
||||
|
||||
[:octicons-home-16: Homepage](https://tuta.com){ .md-button .md-button--primary }
|
||||
[:octicons-eye-16:](https://tuta.com/privacy){ .card-link title="Privacy Policy" }
|
||||
@@ -257,7 +256,7 @@ Administratores de sistema avançados podem considerar a possibilidade de config
|
||||
|
||||
{ align=right }
|
||||
|
||||
**Mailcow** is a more advanced mail server perfect for those with a bit more Linux experience. It has everything you need in a Docker container: A mail server with DKIM support, antivirus and spam monitoring, webmail and ActiveSync with SOGo, and web-based administration with 2FA support.
|
||||
**Mailcow** is a more advanced mail server perfect for those with a bit more Linux experience. It has everything you need in a Docker container: a mail server with DKIM support, antivirus and spam monitoring, webmail and ActiveSync with SOGo, and web-based administration with 2FA support.
|
||||
|
||||
[:octicons-home-16: Homepage](https://mailcow.email){ .md-button .md-button--primary }
|
||||
[:octicons-info-16:](https://docs.mailcow.email){ .card-link title=Documentation}
|
||||
@@ -306,8 +305,8 @@ Consideramos esses recursos importantes para fornecer um serviço seguro e otimi
|
||||
- Support for a temporary mailbox for external users. This is useful when you want to send an encrypted email, without sending an actual copy to your recipient. These emails usually have a limited lifespan and then are automatically deleted. They also don't require the recipient to configure any cryptography like OpenPGP.
|
||||
- Availability of the email provider's services via an [onion service](https://en.wikipedia.org/wiki/.onion).
|
||||
- [Sub-addressing](https://en.wikipedia.org/wiki/Email_address#Sub-addressing) support.
|
||||
- Catch-all or alias functionality for those who own their own domains.
|
||||
- Use of standard email access protocols such as IMAP, SMTP or [JMAP](https://en.wikipedia.org/wiki/JSON_Meta_Application_Protocol). Standard access protocols ensure customers can easily download all of their email, should they want to switch to another provider.
|
||||
- Catch-all or alias functionality for those who use their own domains.
|
||||
- Use of standard email access protocols such as IMAP, SMTP, or [JMAP](https://en.wikipedia.org/wiki/JSON_Meta_Application_Protocol). Standard access protocols ensure customers can easily download all of their email, should they want to switch to another provider.
|
||||
|
||||
### Privacidade
|
||||
|
||||
@@ -315,7 +314,7 @@ Preferimos que nossos provedores recomendados coletem o mínimo possível de dad
|
||||
|
||||
**Mínimo Para Qualificação:**
|
||||
|
||||
- Protect sender's IP address. Filter it from showing in the `Received` header field.
|
||||
- Protect sender's IP address, which can involve filtering it from showing in the `Received` header field.
|
||||
- Don't require personally identifiable information (PII) besides a username and a password.
|
||||
- Privacy policy that meets the requirements defined by the GDPR.
|
||||
|
||||
@@ -326,12 +325,12 @@ Preferimos que nossos provedores recomendados coletem o mínimo possível de dad
|
||||
|
||||
### Segurança
|
||||
|
||||
Email servers deal with a lot of very sensitive data. We expect that providers will adopt best industry practices in order to protect their members.
|
||||
Email servers deal with a lot of very sensitive data. We expect that providers will adopt best industry practices in order to protect their customers.
|
||||
|
||||
**Mínimo Para Qualificação:**
|
||||
|
||||
- Protection of webmail with 2FA, such as TOTP.
|
||||
- Zero access encryption, builds on encryption at rest. The provider does not have the decryption keys to the data they hold. This prevents a rogue employee leaking data they have access to or remote adversary from releasing data they have stolen by gaining unauthorized access to the server.
|
||||
- Zero access encryption, which builds on encryption at rest. The provider does not have the decryption keys to the data they hold. This prevents a rogue employee leaking data they have access to or remote adversary from releasing data they have stolen by gaining unauthorized access to the server.
|
||||
- [DNSSEC](https://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions) support.
|
||||
- No TLS errors or vulnerabilities when being profiled by tools such as [Hardenize](https://hardenize.com), [testssl.sh](https://testssl.sh), or [Qualys SSL Labs](https://ssllabs.com/ssltest); this includes certificate related errors and weak DH parameters, such as those that led to [Logjam](https://en.wikipedia.org/wiki/Logjam_(computer_security)).
|
||||
- A server suite preference (optional on TLSv1.3) for strong cipher suites which support forward secrecy and authenticated encryption.
|
||||
@@ -344,13 +343,14 @@ Email servers deal with a lot of very sensitive data. We expect that providers w
|
||||
- Website security standards such as:
|
||||
- [HTTP Strict Transport Security](https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security)
|
||||
- [Subresource Integrity](https://en.wikipedia.org/wiki/Subresource_Integrity) if loading things from external domains.
|
||||
- Must support viewing of [Message headers](https://en.wikipedia.org/wiki/Email#Message_header), as it is a crucial forensic feature to determine if an email is a phishing attempt.
|
||||
- Must support viewing of [message headers](https://en.wikipedia.org/wiki/Email#Message_header), as it is a crucial forensic feature to determine if an email is a phishing attempt.
|
||||
|
||||
**Melhor Caso:**
|
||||
|
||||
- Support for hardware authentication, i.e. U2F and [WebAuthn](https://en.wikipedia.org/wiki/WebAuthn). U2F and WebAuthn are more secure as they use a private key stored on a client-side hardware device to authenticate people, as opposed to a shared secret that is stored on the web server and on the client side when using TOTP. Furthermore, U2F and WebAuthn are more resistant to phishing as their authentication response is based on the authenticated [domain name](https://en.wikipedia.org/wiki/Domain_name).
|
||||
- Support for hardware authentication, i.e. U2F and [WebAuthn](basics/multi-factor-authentication.md#fido-fast-identity-online).
|
||||
- [DNS Certification Authority Authorization (CAA) Resource Record](https://tools.ietf.org/html/rfc6844) in addition to DANE support.
|
||||
- Implementation of [Authenticated Received Chain (ARC)](https://en.wikipedia.org/wiki/Authenticated_Received_Chain), this is useful for people who post to mailing lists [RFC8617](https://tools.ietf.org/html/rfc8617).
|
||||
- Implementation of [Authenticated Received Chain (ARC)](https://en.wikipedia.org/wiki/Authenticated_Received_Chain), which is useful for people who post to mailing lists [RFC8617](https://tools.ietf.org/html/rfc8617).
|
||||
- Auditorias 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.
|
||||
- Website security standards such as:
|
||||
- [Content Security Policy (CSP)](https://en.wikipedia.org/wiki/Content_Security_Policy)
|
||||
@@ -366,28 +366,27 @@ You wouldn't trust your finances to someone with a fake identity, so why trust t
|
||||
|
||||
**Melhor Caso:**
|
||||
|
||||
- Liderança orientada para o público (usuário).
|
||||
- Relatórios de transparência frequentes.
|
||||
|
||||
### Marketing
|
||||
|
||||
With the email providers we recommend we like to see responsible marketing.
|
||||
With the email providers we recommend, we like to see responsible marketing.
|
||||
|
||||
**Mínimo Para Qualificação:**
|
||||
|
||||
- Must self-host analytics (no Google Analytics, Adobe Analytics, etc.). The provider's site must also comply with [DNT (Do Not Track)](https://en.wikipedia.org/wiki/Do_Not_Track) for those who wish to opt-out.
|
||||
- Must self-host analytics (no Google Analytics, Adobe Analytics, etc.). The provider's site must also comply with [DNT (Do Not Track)](https://en.wikipedia.org/wiki/Do_Not_Track) for those who wish to opt out.
|
||||
|
||||
Não deve ter nenhum marketing irresponsável:
|
||||
Must not have any irresponsible marketing, which can include the following:
|
||||
|
||||
- Claims of "unbreakable encryption." Encryption should be used with the intention that it may not be secret in the future when the technology exists to crack it.
|
||||
- Garantir 100% de proteção ao anonimato. When someone makes a claim that something is 100% it means there is no certainty for failure. Sabemos que as pessoas podem se desanonimizar facilmente de várias maneiras, por exemplo:
|
||||
- Garantir 100% de proteção ao anonimato. When someone makes a claim that something is 100% it means there is no certainty for failure. We know people can quite easily de-anonymize themselves in a number of ways, e.g.:
|
||||
|
||||
- Reusing personal information e.g. (email accounts, unique pseudonyms, etc.) that they accessed without anonymity software (Tor, VPN, etc.)
|
||||
- [Impressão digital do navegador](https://en.wikipedia.org/wiki/Device_fingerprint#Browser_fingerprint)
|
||||
|
||||
**Melhor Caso:**
|
||||
|
||||
- Clear and easy to read documentation. This includes things like, setting up 2FA, email clients, OpenPGP, etc.
|
||||
- Clear and easy to read documentation for tasks like setting up 2FA, email clients, OpenPGP, etc.
|
||||
|
||||
### Funções Adicionais
|
||||
|
||||
|
||||
Reference in New Issue
Block a user