mirror of
https://github.com/privacyguides/i18n.git
synced 2025-11-16 21:32:39 +00:00
New Crowdin translations by GitHub Action
This commit is contained in:
Crowdin Bot
@@ -13,15 +13,11 @@ cover: real-time-communication.webp
|
||||
- [:material-eye-outline: 監視社会](basics/common-threats.md#mass-surveillance-programs ""){.pg-blue}
|
||||
- [:material-account-cash: 監視資本主義](basics/common-threats.md#surveillance-as-a-business-model ""){.pg-brown}
|
||||
|
||||
These are our recommendations for encrypted **real-time communication**. These come in the form of many [types of communication networks](./advanced/communication-network-types.md).
|
||||
These recommendations for encrypted **real-time communication** are great for securing your sensitive communications. These instant messengers come in the form of many [types of communication networks](./advanced/communication-network-types.md).
|
||||
|
||||
[:material-movie-open-play-outline: Video: It's time to stop using SMS](https://www.privacyguides.org/videos/2025/01/24/its-time-to-stop-using-sms-heres-why ""){.md-button}
|
||||
|
||||
## 暗号化されたメッセンジャー
|
||||
|
||||
以下のメッセンジャーは、機密性の高い通信を保護するのに適しています。
|
||||
|
||||
### Signal
|
||||
## Signal
|
||||
|
||||
<div class="admonition recommendation" markdown>
|
||||
|
||||
@@ -69,7 +65,7 @@ We have some additional tips on configuring and hardening your Signal installati
|
||||
|
||||
[Signal Configuration and Hardening :material-arrow-right-drop-circle:](https://blog.privacyguides.org/2022/07/07/signal-configuration-and-hardening)
|
||||
|
||||
#### Molly (Android)
|
||||
### Molly (Android)
|
||||
|
||||
If you use Android and your threat model requires protecting against [:material-target-account: Targeted Attacks](basics/common-threats.md#attacks-against-specific-individuals ""){.pg-red} you may consider using this alternative app, which features a number of security and usability improvements, to access the Signal network.
|
||||
|
||||
@@ -106,7 +102,7 @@ All versions of Molly provide the same security improvements.
|
||||
|
||||
Molly and Molly-FOSS support [reproducible builds](https://github.com/mollyim/mollyim-android/tree/main/reproducible-builds), meaning it's possible to confirm that the compiled APKs match the source code.
|
||||
|
||||
### SimpleX Chat
|
||||
## SimpleX Chat
|
||||
|
||||
<div class="admonition recommendation" markdown>
|
||||
|
||||
@@ -141,7 +137,7 @@ You can find a full list of the privacy and security [features](https://github.c
|
||||
|
||||
SimpleX Chat was independently audited in [July 2024](https://simplex.chat/blog/20241014-simplex-network-v6-1-security-review-better-calls-user-experience.html#simplex-cryptographic-design-review-by-trail-of-bits) and in [October 2022](https://simplex.chat/blog/20221108-simplex-chat-v4.2-security-audit-new-website).
|
||||
|
||||
### Briar
|
||||
## Briar
|
||||
|
||||
<div class="admonition recommendation" markdown>
|
||||
|
||||
@@ -175,76 +171,28 @@ Briar has a fully [published specification](https://code.briarproject.org/briar/
|
||||
|
||||
Briar supports forward secrecy[^1] 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.
|
||||
|
||||
## 追加のオプション
|
||||
|
||||
<div class="admonition warning" markdown>
|
||||
<p class="admonition-title">注意</p>
|
||||
|
||||
These messengers do not have forward secrecy[^1], 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.
|
||||
|
||||
</div>
|
||||
|
||||
### Session
|
||||
|
||||
<div class="admonition recommendation" markdown>
|
||||
|
||||
{ align=right }
|
||||
|
||||
**Session** is a decentralized messenger with a focus on private, secure, and anonymous communications. Session offers support for direct messages, group chats, and voice calls.
|
||||
|
||||
Session uses the decentralized [Oxen Service Node Network](https://oxen.io) to store and route messages. Every encrypted message is routed through three nodes in the Oxen Service Node Network, making it virtually impossible for the nodes to compile meaningful information on those using the 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" }
|
||||
|
||||
<details class="downloads" markdown>
|
||||
<summary>Downloads</summary>
|
||||
|
||||
- [: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)
|
||||
- [:simple-github: GitHub](https://github.com/oxen-io/session-android/releases)
|
||||
- [:fontawesome-brands-windows: Windows](https://getsession.org/download)
|
||||
- [:simple-apple: macOS](https://getsession.org/download)
|
||||
- [:simple-linux: Linux](https://getsession.org/download)
|
||||
|
||||
</details>
|
||||
|
||||
</div>
|
||||
|
||||
Session allows for E2EE in one-on-one chats or closed groups which allow for up to 100 members. It is also possible to [set up](https://docs.oxen.io/oxen-docs/products-built-on-oxen/session/guides/open-group-setup) or join open groups which can host thousands of members, but messages in these open groups are **not** end-to-end encrypted between participants.
|
||||
|
||||
Session was previously based on Signal Protocol before replacing it with their own in December 2020. Session Protocol does [not](https://getsession.org/blog/session-protocol-technical-information) support forward secrecy.[^1]
|
||||
|
||||
Oxen requested an independent audit for Session in March 2020. The audit [concluded](https://getsession.org/session-code-audit) in April 2021:
|
||||
|
||||
> The overall security level of this application is good and makes it usable for privacy-concerned people.
|
||||
|
||||
Session has a [white paper](https://arxiv.org/pdf/2002.04609.pdf) describing the technical details of the app and protocol.
|
||||
|
||||
## 規準
|
||||
|
||||
**私たちは、推薦するどのプロジェクトとも提携していません。**客観的に推薦できるよう、[標準となる規準](about/criteria.md)に加えて、一連の明確な要件を定めています。 プロジェクトを利用する前に、このリストをよく理解し、ご自身で調査を行って、そのプロジェクトがあなたにとって適切な選択かどうかをご確認ください。
|
||||
|
||||
### 最低要件
|
||||
|
||||
- Has open-source clients.
|
||||
- Does not require sharing personal identifiers (phone numbers or emails in particular) with contacts.
|
||||
- Uses E2EE for private messages by default.
|
||||
- Supports E2EE for all messages.
|
||||
- Has been independently audited.
|
||||
- Must have open-source clients.
|
||||
- Must not require sharing personal identifiers (particuarly phone numbers or emails) with contacts.
|
||||
- Must use E2EE for private messages by default.
|
||||
- Must support E2EE for all messages.
|
||||
- Must support forward secrecy[^1]
|
||||
- Must have a published audit from a reputable, independent third party.
|
||||
|
||||
### 満たされることが望ましい基準
|
||||
|
||||
満たされることが望ましい基準には、このカテゴリーの完璧なプロジェクトに私たちが望むものを示しています。 私たちが推薦するプロジェクトは、この機能の一部または全部を含んでいないかもしれませんが、もし含んでいれば、このページで他のプロジェクトよりも上位にランクされるかもしれません。
|
||||
|
||||
- Supports forward secrecy[^1]
|
||||
- Supports Future Secrecy (Post-Compromise Security)[^2]
|
||||
- Has open-source servers.
|
||||
- Decentralized, i.e. [federated or P2P](advanced/communication-network-types.md).
|
||||
- Uses E2EE for all messages by default.
|
||||
- Supports Linux, macOS, Windows, Android, and iOS.
|
||||
- Should support future secrecy (post-compromise security)[^2]
|
||||
- Should have open-source servers.
|
||||
- Should use a decentralized network, i.e. [federated or P2P](advanced/communication-network-types.md).
|
||||
- Should use E2EE for all messages by default.
|
||||
- Should support Linux, macOS, Windows, Android, and iOS.
|
||||
|
||||
[^1]: [Forward secrecy](https://en.wikipedia.org/wiki/Forward_secrecy) is where keys are rotated very frequently, so that if the current encryption key is compromised, it does not expose **past** messages as well.
|
||||
[^2]: Future Secrecy (or Post-Compromise Security) is a feature where an attacker is prevented from decrypting **future** messages after compromising a private key, unless they compromise more session keys in the future as well. This effectively forces the attacker to intercept all communication between parties, since they lose access as soon as a key exchange occurs that is not intercepted.
|
||||
[^2]: Future secrecy (or [post-compromise security](https://eprint.iacr.org/2016/221.pdf)) is a feature where an attacker is prevented from decrypting **future** messages after compromising a private key, unless they compromise more session keys in the future as well. This effectively forces the attacker to intercept all communication between parties since they lose access as soon as a key exchange occurs that is not intercepted.
|
||||
|
||||
@@ -597,7 +597,6 @@ For encrypting your OS drive, we typically recommend using the encryption tool y
|
||||
- { .twemoji loading=lazy } [Signal](real-time-communication.md#signal)
|
||||
- { .twemoji loading=lazy } [Briar](real-time-communication.md#briar)
|
||||
- { .twemoji loading=lazy } [SimpleX Chat](real-time-communication.md#simplex-chat)
|
||||
- { .twemoji loading=lazy } [Session](real-time-communication.md#session)
|
||||
|
||||
</div>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user