From 6d140f53b83197268ca0c4f44e5ed7281d33f823 Mon Sep 17 00:00:00 2001 From: Crowdin Bot Date: Mon, 27 Nov 2023 05:32:13 +0000 Subject: [PATCH] New Crowdin translations by GitHub Action --- i18n/ja/basics/vpn-overview.md | 4 ++-- includes/abbreviations.ja.txt | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/i18n/ja/basics/vpn-overview.md b/i18n/ja/basics/vpn-overview.md index 761b1c9f..10673056 100644 --- a/i18n/ja/basics/vpn-overview.md +++ b/i18n/ja/basics/vpn-overview.md @@ -1,5 +1,5 @@ --- -meta_title: "How Do VPNs Protect Your Privacy? VPNの概要 - Privacy Guides" +meta_title: "VPNがプライバシーを守る方法について。 VPNの概要 - Privacy Guides" title: VPNの概要 icon: material/vpn description: Virtual Private Networks shift risk away from your ISP to a third-party you trust. You should keep these things in mind. @@ -54,7 +54,7 @@ You also should not trust a VPN to secure your connection to an unencrypted, HTT Unless your VPN provider hosts the encrypted DNS servers themselves, **probably not**. Using DOH/DOT (or any other form of encrypted DNS) with third-party servers will simply add more entities to trust. Your VPN provider can still see which websites you visit based on the IP addresses and other methods. All this being said, there may be some advantages to enabling encrypted DNS in order to enable other security features in your browser, such as ECH. Browser technologies which are reliant on in-browser encrypted DNS are relatively new and not yet widespread, so whether they are relevant to you in particular is an exercise we will leave to you to research independently. -Another common reason encrypted DNS is recommended is that it prevents DNS spoofing. However, your browser should already be checking for [TLS certificates](https://en.wikipedia.org/wiki/Transport_Layer_Security#Digital_certificates) with **HTTPS** and warn you about it. If you are not using **HTTPS**, then an adversary can still just modify anything other than your DNS queries and the end result will be little different. +Another common reason encrypted DNS is recommended is that it prevents DNS spoofing. しかし、ブラウザは既に**HTTPS**で[TLS証明書](https://en.wikipedia.org/wiki/Transport_Layer_Security#Digital_certificates)を確認し、警告しているはずです。 If you are not using **HTTPS**, then an adversary can still just modify anything other than your DNS queries and the end result will be little different. ## Should I use Tor *and* a VPN? diff --git a/includes/abbreviations.ja.txt b/includes/abbreviations.ja.txt index bc80f01d..d9376f95 100644 --- a/includes/abbreviations.ja.txt +++ b/includes/abbreviations.ja.txt @@ -16,7 +16,7 @@ *[DoH3]: DNS over HTTP/3 *[DoT]: DNS over TLS *[E2EE]: エンドツーエンド暗号化（End-to-End Encryption/Encrypted） -*[ECS]: EDNS Client Subnet +*[ECS]: EDNSクライアントサブネット（EDNS Client Subnet） *[EEA]: 欧州経済領域 *[entropy]： 予測不可能性の尺度 *[EOL]: サポート終了（End-of-Life） @@ -35,7 +35,7 @@ *[HOTP]: HMAC（ハッシュベースのメッセージ認証コード）ベースのワンタイムパスワード *[HTTPS]: Hypertext Transfer Protocol Secure *[HTTP]: ハイパーテキスト転送プロトコル（Hypertext Transfer Protocol） -*[hypervisor]： Computer software, firmware, or hardware that splits the resources of a CPU among multiple operating systems +*[hypervisor]： CPUのリソースを複数のオペレーティングシステムに分割するコンピュータソフトウェア、ファームウェア、またはハードウェア *[ICCID]: Integrated Circuit Card Identifier *[IMAP]: Internet Message Access Protocol（インターネットメッセージアクセスプロトコル） *[IMEI]: International Mobile Equipment Identity @@ -70,7 +70,7 @@ *[PGP]: プリティグッドプライバシー(OpenPGPを参照) *[PII]: 個人を特定できる情報（Personally Identifiable Information） *[QNAME]: Qualified Name -*[rolling release]: Updates which are released frequently rather than set intervals +*[ローリング・リリース]： Updates which are released frequently rather than set intervals *[RSS]: Really Simple Syndication *[SELinux]: Security-Enhanced Linux *[SIM]: 加入者識別モジュール