From 6fa43f789f44e9f7e2d77f96d808e86d63a59fa2 Mon Sep 17 00:00:00 2001 From: Crowdin Bot Date: Wed, 5 Jul 2023 04:04:17 +0000 Subject: [PATCH] New Crowdin translations by GitHub Action --- i18n/ja/CODE_OF_CONDUCT.md | 62 +++++++------- i18n/ja/about/privacy-policy.md | 22 ++--- i18n/ja/about/privacytools.md | 4 +- i18n/ja/basics/common-threats.md | 6 +- i18n/ja/basics/why-privacy-matters.md | 4 +- i18n/ja/email.md | 40 ++++----- i18n/ja/index.md | 2 +- i18n/ja/meta/brand.md | 14 ++-- i18n/ja/meta/git-recommendations.md | 14 ++-- i18n/ja/meta/uploading-images.md | 28 +++---- i18n/ja/notebooks.md | 2 +- i18n/ja/tools.md | 8 +- i18n/ja/vpn.md | 104 ++++++++++++------------ i18n/pt/basics/common-misconceptions.md | 81 +++++++++--------- i18n/pt/file-sharing.md | 48 +++++------ i18n/ru/about/index.md | 42 +++++----- i18n/ru/about/notices.md | 18 ++-- i18n/ru/android.md | 2 +- i18n/ru/meta/brand.md | 14 ++-- i18n/ru/meta/git-recommendations.md | 4 +- i18n/ru/meta/uploading-images.md | 20 ++--- i18n/ru/news-aggregators.md | 14 ++-- i18n/ru/os/linux-overview.md | 22 ++--- i18n/ru/os/qubes-overview.md | 52 ++++++------ i18n/ru/real-time-communication.md | 2 +- includes/abbreviations.ja.txt | 8 +- includes/strings.ja.yml | 2 +- 27 files changed, 316 insertions(+), 323 deletions(-) diff --git a/i18n/ja/CODE_OF_CONDUCT.md b/i18n/ja/CODE_OF_CONDUCT.md index 88a0e910..7c409f69 100644 --- a/i18n/ja/CODE_OF_CONDUCT.md +++ b/i18n/ja/CODE_OF_CONDUCT.md @@ -1,53 +1,53 @@ -# Community Code of Conduct +# コミュニティ行動規範 -**We pledge** to make our community a harassment-free experience for everyone. +**私たちは誓います** 誰にとってもハラスメントのないコミュニティにすることを誓います。 -**We strive** to create a positive environment, using welcoming and inclusive language, and being respectful of the viewpoints of others. +**私たちは努力します** 歓迎と包括的な言葉を使い、他者の視点を尊重しながら、前向きな環境づくりに努めています。 -**We do not allow** inappropriate or otherwise unacceptable behavior, such as sexualized language, trolling and insulting comments, or otherwise promoting intolerance or harassment. +**私たちは許可しません** 性的な表現、荒らしや侮辱的なコメント、不寛容やハラスメントの助長など、不適切な行為やその他の容認できない行為を許可しません。 -## Community Standards +## コミュニティ規定 -What we expect from members of our communities: +コミュニティのメンバーに期待されること -1. **Don't spread misinformation** +1. **誤った情報を広めない** - We are creating an evidence-based educational community around information privacy and security, not a home for conspiracy theories. For example, when making a claim that a certain piece of software is malicious or that certain telemetry data is privacy invasive, explain in detail what is collected and how it collected. Claims of this nature must be backed by technical evidence. + 私たちは、陰謀論の本拠地ではなく、情報プライバシーとセキュリティに関する証拠に基づいた教育コミュニティを構築しています。 たとえば、特定のソフトウェアが悪意のあるものであると主張する場合、または特定のテレメトリーデータがプライバシーを侵害していると主張する場合、 収集される内容と収集方法を詳細に説明してください。 このような主張は、技術的な証拠によって裏付けられている必要があります。 -1. **Don't abuse our willingness to help** +1. **私たちの助けたいという意志を悪用しないでください** - Our community members are not your free tech support. We are happy to help you with specific steps on your privacy journey if you are willing to put in effort on your end. We are not willing to answer endlessly repeated questions about generic computer problems you could have answered yourself with a 30-second internet search. Don't be a [help vampire](https://slash7.com/2006/12/22/vampires/). + 私たちのコミュニティメンバーは、あなたの無料の技術サポートではありません。 私たちは、あなたが自身によって努力を惜しまないのであれば、あなたのプライバシーへの取り組みにおける具体的なステップを喜んでお手伝いします。 インターネットで 30 秒検索すれば答えられるような一般的なコンピューターの問題について、際限なく繰り返される質問に答えるつもりはありません。 [help vampire](https://slash7.com/2006/12/22/vampires/) にならないでください。 -1. **Behave in a positive and constructive manner** +1. **前向きかつ建設的な態度で行動する** - Examples of behavior that contributes to a positive environment for our community include: + 前向きな環境を作り上げることに貢献する行動の例： - - Demonstrating empathy and kindness toward other people - - Being respectful of differing opinions, viewpoints, and experiences - - Giving and gracefully accepting constructive feedback - - Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience - - Focusing on what is best not just for us as individuals, but for the overall community + - 他人に対する共感と優しさを示す + - 異なる意見、視点、経験を尊重する + - 建設的なフィードバックを提供し、適切に受け入れる + - 自らの過ちによって影響を受けた人々に責任を認めて謝罪し、経験から学ぶ + - 私たち個人だけでなく、コミュニティ全体にとって何が最善であるかに焦点を当てる -### Unacceptable Behavior +### 容認できない行為 -The following behaviors are considered harassment and are unacceptable within our community: +以下の行為はハラスメントとみなされ、私たちのコミュニティでは容認されません： -- The use of sexualized language or imagery, and sexual attention or advances of any kind -- Trolling, insulting or derogatory comments, and personal or political attacks -- Public or private harassment -- Publishing others' private information, such as a physical or email address, without their explicit permission -- Other conduct which could reasonably be considered inappropriate in a professional setting +- 性的な言葉や画像の使用、およびあらゆる種類の性的注目や性的誘い +- 荒らし行為、侮辱的または軽蔑的なコメント、個人的または政治的な攻撃 +- 公的または私的な嫌がらせ +- 明示的な許可なしに、住所やメールアドレスなどの他人の個人情報を公開すること +- その他、プロフェッショナルとして不適切であると合理的に考えられる行為 -## Scope +## 対象範囲 -Our Code of Conduct applies within all project spaces, as well as when an individual is representing the Privacy Guides project in other communities. +私たちの行動規範は、すべてのプロジェクトスペースで適用されるだけでなく、個人が他のコミュニティでPrivacy Guides プロジェクトを代表する場合にも適用されます。 -We are responsible for clarifying the standards of our community, and have the right to remove or alter the comments of those participating within our community, as necessary and at our discretion. +私たちはコミュニティの基準を明確にする責任があり、必要に応じて私たちの裁量でコミュニティに参加している人のコメントを削除または変更する権利を有します。 -### Contact +### 連絡先 -If you observe a problem on a platform like Matrix or Reddit, please contact our moderators on that platform in chat, via DM, or through any designated "Modmail" system. +MatrixやRedditのようなプラットフォームで問題が発生した場合は、そのプラットフォームのモデレーターにチャット、DM、または指定された「Modmail」システムを通じて連絡してください。 -If you have a problem elsewhere, or a problem our community moderators are unable to resolve, reach out to `jonah@privacyguides.org` and/or `dngray@privacyguides.org`. +他の場所で問題が発生した場合、またはコミュニティのモデレーターが解決できない場合は、 `jonah@privacyguides.org` および/または `dngray@privacyguides.org`までご連絡ください。 -All community leaders are obligated to respect the privacy and security of the reporter of any incident. +すべてのコミュニティのリーダーは、あらゆる事件の報告者のプライバシーと安全を尊重する義務があります。 diff --git a/i18n/ja/about/privacy-policy.md b/i18n/ja/about/privacy-policy.md index 8abb84fc..34b6f341 100644 --- a/i18n/ja/about/privacy-policy.md +++ b/i18n/ja/about/privacy-policy.md @@ -2,26 +2,26 @@ title: "プライバシーポリシー" --- -Privacy Guides is a community project operated by a number of active volunteer contributors. The public list of team members [can be found on GitHub](https://github.com/orgs/privacyguides/people). +Privacy Guidesは、多数の積極的なボランティア貢献者によって運営されているコミュニティプロジェクトです。 チームメンバーの公開リストは[GitHubで確認](https://github.com/orgs/privacyguides/people)できます。 ## 私たちが閲覧者から収集するデータ -私たちは、ウェブサイト閲覧者のプライバシーを重視しているため、各個人を追跡することはありません。 As a visitor to our website: +私たちは、ウェブサイト閲覧者のプライバシーを重視しているため、各個人を追跡することはありません。 私たちのウェブサイトの訪問者として： - 個人情報を収集しません - Cookieなどの情報をブラウザに保存しません - 第三者に情報を共有・送信・販売しません - 広告会社に情報を共有しません -- No information is mined and harvested for personal and behavioral trends +- 個人情報および行動傾向のために情報が収集されることはありません。 - 情報を収益化しません -You can view the data we collect on our [statistics](statistics.md) page. +収集したデータは[統計](statistics.md)ページで確認できます。 -We run a self-hosted installation of [Plausible Analytics](https://plausible.io) to collect some anonymous usage data for statistical purposes. The goal is to track overall trends in our website traffic, it is not to track individual visitors. All the data is in aggregate only. No personal data is collected. +私たちは[Plausible Analytics](https://plausible.io)の自己ホスト型インストールを実行し、統計目的で匿名の使用状況データを収集します。 目的は、ウェブサイトのトラフィックの全体的な傾向を追跡することであり、個々の訪問者を追跡することではありません。 データはすべて集計値です。 個人情報は収集されません。 Data collected includes referral sources, top pages, visit duration, information from the devices (device type, operating system, country and browser) used during the visit and more. You can learn more about how Plausible works and collects information in a privacy-respecting manner [here](https://plausible.io/data-policy). -## Data We Collect From Account Holders +## アカウント所有者から収集するデータ On some websites and services we provide, many features may require an account. For example, an account may be required to post and reply to topics on a forum platform. @@ -42,7 +42,7 @@ We will store your account data as long as your account remains open. After clos ## 連絡先 -The Privacy Guides team generally does not have access to personal data outside of limited access granted via some moderation panels. Inquiries regarding your personal information should be sent directly to: +Privacy Guidesチームは通常、一部のモデレーションパネルを介して許可された限定的なアクセス以外で、個人データにアクセスすることはできません。 個人情報に関するお問い合わせは、以下に直接お送りください： ```text Jonah Aragon @@ -50,12 +50,12 @@ Jonah Aragon jonah@privacyguides.org ``` -For all other inquiries, you can contact any member of our team. +その他すべてのお問い合わせについては、チームのメンバーに連絡することができます。 -For complaints under GDPR more generally, you may lodge complaints with your local data protection supervisory authorities. In France it's the Commission Nationale de l'Informatique et des Libertés which take care and handle the complaints. They provide a [template of complaint letter](https://www.cnil.fr/en/plaintes) to use. +より一般的なGDPRに基づく申し立てについては、各地域のデータ保護監督当局に申し立てることができます。 フランスでは、 Commission Nationale de l'Informatique et des Libertés が申し立てを処理します。 使用できる[申し立てのテンプレート](https://www.cnil.fr/en/plaintes)が提供されています。 ## このポリシーについて -We will post any new versions of this statement [here](privacy-policy.md). We may change how we announce changes in future versions of this document. In the meantime we may update our contact information at any time without announcing a change. Please refer to the [Privacy Policy](privacy-policy.md) for the latest contact information at any time. +このステートメントに新しいバージョンがあれば、[ここ](privacy-policy.md)に掲載します。 このドキュメントの将来のバージョンでは、変更の発表方法が変更される可能性があります。 それまでの間、変更を告知することなく、いつでも連絡先情報を更新することができます。 最新の連絡先情報については、[プライバシーポリシー](privacy-policy.md)を随時参照してください。 -A full revision [history](https://github.com/privacyguides/privacyguides.org/commits/main/docs/about/privacy-policy.md) of this page can be found on GitHub. +このページの完全な改訂[履歴](https://github.com/privacyguides/privacyguides.org/commits/main/docs/about/privacy-policy.md)はGitHubにあります。 diff --git a/i18n/ja/about/privacytools.md b/i18n/ja/about/privacytools.md index 515c21f5..478ab98e 100644 --- a/i18n/ja/about/privacytools.md +++ b/i18n/ja/about/privacytools.md @@ -1,8 +1,8 @@ --- -title: "PrivacyTools FAQ" +title: "PrivacyToolsに関するよくある質問" --- -# Why we moved on from PrivacyTools +# PrivacyToolsから移行した理由 In September 2021, every active contributor unanimously agreed to move from PrivacyTools to work on this site: Privacy Guides. This decision was made because PrivacyTools’ founder and controller of the domain name had disappeared for an extended period of time and could not be contacted. diff --git a/i18n/ja/basics/common-threats.md b/i18n/ja/basics/common-threats.md index e278c0cb..713f48c0 100644 --- a/i18n/ja/basics/common-threats.md +++ b/i18n/ja/basics/common-threats.md @@ -1,5 +1,5 @@ --- -title: "Common Threats" +title: "一般的な脅威" icon: 'material/eye-outline' description: Your threat model is personal to you, but these are some of the things many visitors to this site care about. --- @@ -85,7 +85,7 @@ Mass surveillance is the intricate effort to monitor the "behavior, many activit Governments often justify mass surveillance programs as necessary means to combat terrorism and prevent crime. However, breaching human rights, it's most often used to disproportionately target minority groups and political dissidents, among others. -!!! quote "ACLU: [*The Privacy Lesson of 9/11: Mass Surveillance is Not the Way Forward*](https://www.aclu.org/news/national-security/the-privacy-lesson-of-9-11-mass-surveillance-is-not-the-way-forward)" +!!! 引用元：「ACLU（アメリカ自由人権協会）：[*9.11のプライバシーに関する教訓：大量監視は進むべき道ではない*](https://www.aclu.org/news/national-security/the-privacy-lesson-of-9-11-mass-surveillance-is-not-the-way-forward)」 In the face of [Edward Snowden's disclosures of government programs such as [PRISM](https://en.wikipedia.org/wiki/PRISM) and [Upstream](https://en.wikipedia.org/wiki/Upstream_collection)], intelligence officials also admitted that the NSA had for years been secretly collecting records about virtually every American’s phone calls — who’s calling whom, when those calls are made, and how long they last. This kind of information, when amassed by the NSA day after day, can reveal incredibly sensitive details about people’s lives and associations, such as whether they have called a pastor, an abortion provider, an addiction counselor, or a suicide hotline. @@ -145,4 +145,4 @@ You must always consider the risks of trying to bypass censorship, the potential [^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). +[^5]: 国連：[*世界人権宣言*](https://www.un.org/en/about-us/universal-declaration-of-human-rights) diff --git a/i18n/ja/basics/why-privacy-matters.md b/i18n/ja/basics/why-privacy-matters.md index 127bc3c5..41f30de7 100644 --- a/i18n/ja/basics/why-privacy-matters.md +++ b/i18n/ja/basics/why-privacy-matters.md @@ -11,12 +11,12 @@ icon: 'material/shield-account' 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. -**Privacy** +**プライバシー** : ==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. -**Security** +**セキュリティ** : Security is the ability to trust the applications you use—that the parties involved are who they say they are—and keep those applications safe. In the context of browsing the web, for example, security can be provided by HTTPS certificates. diff --git a/i18n/ja/email.md b/i18n/ja/email.md index 94c0053c..de7d342a 100644 --- a/i18n/ja/email.md +++ b/i18n/ja/email.md @@ -10,7 +10,7 @@ cover: email.png [おすすめのインスタントメッセンジャ](real-time-communication.md ""){.md-button} -それ以外のことについては、持続可能なビジネスモデル、組み込まれたセキュリティとプライバシー機能に基づいていろんな電子メールプロバイダをお勧めします。 +それ以外のことについては、持続可能なビジネスモデル、組み込まれたセキュリティとプライバシー機能に基づいて様々な電子メールプロバイダをお勧めします。 - [OpenPGP対応電子メールプロバイダ :material-arrow-right-drop-circle:](#openpgp-compatible-services) - [その他の暗号化プロバイダ :material-arrow-right-drop-circle:](#more-providers) @@ -344,11 +344,11 @@ For a more manual approach we've picked out these two articles: - [Setting up a mail server with OpenSMTPD, Dovecot and Rspamd](https://poolp.org/posts/2019-09-14/setting-up-a-mail-server-with-opensmtpd-dovecot-and-rspamd/) (2019) - [How To Run Your Own Mail Server](https://www.c0ffee.net/blog/mail-server-guide/) (August 2017) -## Criteria +## 基準 **Please note we are not affiliated with any of the providers we recommend.** In addition to [our standard criteria](about/criteria.md), we have developed a clear set of requirements for any Email provider wishing to be recommended, including implementing industry best practices, modern technology and more. We suggest you familiarize yourself with this list before choosing an Email provider, and conduct your own research to ensure the Email provider you choose is the right choice for you. -### Technology +### テクノロジー We regard these features as important in order to provide a safe and optimal service. You should consider whether the provider which has the features you require. @@ -359,7 +359,7 @@ We regard these features as important in order to provide a safe and optimal ser - Allow users to use their own [domain name](https://en.wikipedia.org/wiki/Domain_name). Custom domain names are important to users because it allows them to maintain their agency from the service, should it turn bad or be acquired by another company which doesn't prioritize privacy. - Operates on owned infrastructure, i.e. not built upon third-party email service providers. -**Best Case:** +**最良の場合：** - Encrypts all account data (Contacts, Calendars, etc.) at rest with zero-access encryption. - Integrated webmail E2EE/PGP encryption provided as a convenience. @@ -370,9 +370,9 @@ We regard these features as important in order to provide a safe and optimal ser - 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. -### Privacy +### プライバシー -We prefer our recommended providers to collect as little data as possible. +私たちは、推奨するプロバイダーができるだけデータを収集しないことを望んでいます。 **Minimum to Qualify:** @@ -380,12 +380,12 @@ We prefer our recommended providers to collect as little data as possible. - Don't require personally identifiable information (PII) besides a username and a password. - Privacy policy that meets the requirements defined by the GDPR. -**Best Case:** +**最良の場合：** - Accepts [anonymous payment options](advanced/payments.md) ([cryptocurrency](cryptocurrency.md), cash, gift cards, etc.) - Hosted in a jurisdiction with strong email privacy protection laws. -### Security +### セキュリティ 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. @@ -407,7 +407,7 @@ Email servers deal with a lot of very sensitive data. We expect that providers w - [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. -**Best Case:** +**最良の場合：** - 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). - [DNS Certification Authority Authorization (CAA) Resource Record](https://tools.ietf.org/html/rfc6844) in addition to DANE support. @@ -417,20 +417,20 @@ Email servers deal with a lot of very sensitive data. We expect that providers w - [Content Security Policy (CSP)](https://en.wikipedia.org/wiki/Content_Security_Policy) - [RFC9163 Expect-CT](https://datatracker.ietf.org/doc/rfc9163/) -### Trust +### 信頼 You wouldn't trust your finances to someone with a fake identity, so why trust them with your email? We require our recommended providers to be public about their ownership or leadership. We also would like to see frequent transparency reports, especially in regard to how government requests are handled. **Minimum to Qualify:** -- Public-facing leadership or ownership. +- 公の場でのリーダーシップやオーナーシップ。 -**Best Case:** +**最良の場合：** -- Public-facing leadership. -- Frequent transparency reports. +- 公の場でのリーダーシップ。 +- 頻繁な透明性レポート。 -### Marketing +### マーケティング With the email providers we recommend we like to see responsible marketing. @@ -438,18 +438,18 @@ With the email providers we recommend we like to see responsible marketing. - 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 not have any marketing which is irresponsible: +無責任なマーケティングをしてはいけない： - 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. -- Making guarantees of protecting anonymity 100%. When someone makes a claim that something is 100% it means there is no certainty for failure. We know people can quite easily deanonymize themselves in a number of ways, e.g.: +- 匿名性を100％保証すること。 誰かが何かを100％だと主張するとき、それは失敗の確実性がないことを意味します。 私たちは、人々が多くの方法で簡単に匿名化を解除できることを知っています： - Reusing personal information e.g. (email accounts, unique pseudonyms, etc.) that they accessed without anonymity software (Tor, VPN, etc.) -- [Browser fingerprinting](https://en.wikipedia.org/wiki/Device_fingerprint#Browser_fingerprint) +- [ブラウザフィンガープリント](https://en.wikipedia.org/wiki/Device_fingerprint#Browser_fingerprint) -**Best Case:** +**最良の場合：** - Clear and easy to read documentation. This includes things like, setting up 2FA, email clients, OpenPGP, etc. -### Additional Functionality +### 追加機能 While not strictly requirements, there are some other convenience or privacy factors we looked into when determining which providers to recommend. diff --git a/i18n/ja/index.md b/i18n/ja/index.md index 0b9733b3..6ed884a7 100644 --- a/i18n/ja/index.md +++ b/i18n/ja/index.md @@ -38,7 +38,7 @@ schema: ## なぜ気にする必要があるのですか？ -##### 「私には隠し事がありません。 なぜ、自分のプライバシーについて気にする必要があるのですか？」 +##### 「隠すものは何もありません。 なぜ、自分のプライバシーについて気にする必要があるのですか？」 異人種間の結婚、女性参政権、言論の自由など多くの権利と同様に、私たちのプライバシー権は常に認められているわけではありません。 いくつかの独裁政権は、プライバシー権に否定的です。 一世代前の人々は、私たちのプライバシー権のために戦ってきました。 ==プライバシーは私たち全員に固有の人権であり、==差別なく全員がこの権利を享受できます。 diff --git a/i18n/ja/meta/brand.md b/i18n/ja/meta/brand.md index 53cb9ac4..11222f1f 100644 --- a/i18n/ja/meta/brand.md +++ b/i18n/ja/meta/brand.md @@ -1,8 +1,8 @@ --- -title: Branding Guidelines +title: ブランドガイドライン --- -The name of the website is **Privacy Guides** and should **not** be changed to: +ウェブサイトの名前は **Privacy Guides** であり、次のように変更**しない**でください：
- PrivacyGuides @@ -11,12 +11,12 @@ The name of the website is **Privacy Guides** and should **not** be changed to: - PG.org
-The name of the subreddit is **r/PrivacyGuides** or **the Privacy Guides Subreddit**. +サブレディットの名前は **r/PrivacyGuides** または **the Privacy Guides Subreddit** です。 -Additional branding guidelines can be found at [github.com/privacyguides/brand](https://github.com/privacyguides/brand) +その他のブランドガイドラインについては、次のサイトを参照してください。 [github.com/privacyguides/brand](https://github.com/privacyguides/brand) -## Trademark +## 商標 -"Privacy Guides" and the shield logo are trademarks owned by Jonah Aragon, unlimited usage is granted to the Privacy Guides project. +「Privacy Guides」と盾のロゴはJonah Aragonが所有する商標であり、Privacy Guidesプロジェクトには無制限の使用が認められています。 -Without waiving any of its rights, Privacy Guides does not advise others on the scope of its intellectual property rights. Privacy Guides does not permit or consent to any use of its trademarks in any manner that is likely to cause confusion by implying association with or sponsorship by Privacy Guides. If you are aware of any such use, please contact Jonah Aragon at jonah@privacyguides.org. Consult your legal counsel if you have questions. +Privacy Guidesは、その権利を放棄することなく、その知的財産権の範囲について他者に助言することはありません。 Privacy Guidesは、Privacy Guidesとの関連または後援を暗示することによって混乱を引き起こす可能性のある方法での商標の使用を許可または同意しません。 そのような使用に気付いた場合は、Jonah Aragon (jonah@privacyguides.org) までご連絡ください。 質問がある場合は、弁護士に相談してください。 diff --git a/i18n/ja/meta/git-recommendations.md b/i18n/ja/meta/git-recommendations.md index f59b5f81..b0434938 100644 --- a/i18n/ja/meta/git-recommendations.md +++ b/i18n/ja/meta/git-recommendations.md @@ -1,25 +1,25 @@ --- -title: Git Recommendations +title: Gitの推奨事項 --- -If you make changes to this website on GitHub.com's web editor directly, you shouldn't have to worry about this. If you are developing locally and/or are a long-term website editor (who should probably be developing locally!), consider these recommendations. +GitHub.comのウェブエディターでこのウェブサイトに直接変更を加える場合は、この心配する必要はありません。 ローカルで開発している場合、および/または長期的なウェブサイトエディタ（おそらくローカルで開発しているはずです！）である場合は、これらの推奨事項を検討してください。 -## Enable SSH Key Commit Signing +## SSHキーのコミット署名を有効にする -You can use an existing SSH key for signing, or [create a new one](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent). +署名に既存の SSH キーを使用することも、[新しいSSH キーを作成することもできます。](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) -1. Configure your Git client to sign commits and tags by default (remove `--global` to only sign by default for this repo): +1. デフォルトでコミットとタグに署名するように Git クライアントを設定する (remove `--global` to only sign by default for this repo): ``` git config --global commit.gpgsign true git config --global gpg.format ssh git config --global tag.gpgSign true ``` -2. Copy your SSH public key to your clipboard, for example: +2. SSH公開鍵をクリップボードにコピーします。例： ``` pbcopy < ~/.ssh/id_ed25519.pub # Copies the contents of the id_ed25519.pub file to your clipboard ``` -3. Set your SSH key for signing in Git with the following command, replacing the last string in quotes with the public key in your clipboard: +3. 次のコマンドを使用して、Git に署名するための SSH キーを設定します。引用符で囲まれた最後の文字列をクリップボード内の公開キーに置き換えます。 ``` git config --global user.signingkey 'ssh-ed25519 AAAAC3(...) user@example.com' ``` diff --git a/i18n/ja/meta/uploading-images.md b/i18n/ja/meta/uploading-images.md index 55f136f8..088fe6a3 100644 --- a/i18n/ja/meta/uploading-images.md +++ b/i18n/ja/meta/uploading-images.md @@ -1,23 +1,23 @@ --- -title: Uploading Images +title: 画像のアップロード --- -Here are a couple of general rules for contributing to Privacy Guides: +プライバシーガイドに投稿する際の一般的なルールをいくつか紹介します： -## Images +## 画像 -- We **prefer** SVG images, but if those do not exist we can use PNG images +- 私たちはSVG画像を**推奨**しますが、存在しない場合は PNG 画像を使用できます -Company logos have canvas size of: +企業ロゴのキャンバスサイズ： - 128x128px - 384x128px -## Optimization +## 最適化 ### PNG -Use the [OptiPNG](https://sourceforge.net/projects/optipng/) to optimize the PNG image: +[OptiPNG](https://sourceforge.net/projects/optipng/)を使用してPNG画像を最適化します。 ```bash optipng -o7 file.png @@ -27,16 +27,16 @@ optipng -o7 file.png #### Inkscape -[Scour](https://github.com/scour-project/scour) all SVG images. +すべてのSVG画像に[Scour](https://github.com/scour-project/scour)を使用します。 -In Inkscape: +Inkscapeで： -1. File Save As.. -2. Set type to Optimized SVG (*.svg) +1. 名前を付けてファイルを保存... +2. タイプを最適化されたSVG (*.svg)に設定する -In the **Options** tab: +**オプション** タブで： -- **Number of significant digits for coordinates** > **5** +- **座標の有効桁数** > **5** - [x] Turn on **Shorten color values** - [x] Turn on **Convert CSS attributes to XML attributes** - [x] Turn on **Collapse groups** @@ -71,7 +71,7 @@ In the **IDs** tab: #### CLI -The same can be achieved with the [Scour](https://github.com/scour-project/scour) command: +同じことが [Scour](https://github.com/scour-project/scour) コマンドでも可能です： ```bash scour --set-precision=5 \ diff --git a/i18n/ja/notebooks.md b/i18n/ja/notebooks.md index e124cf23..9a4bf717 100644 --- a/i18n/ja/notebooks.md +++ b/i18n/ja/notebooks.md @@ -60,7 +60,7 @@ cover: notebooks.png - [:simple-firefoxbrowser: Firefox](https://notesnook.com/notesnook-web-clipper/) - [:simple-googlechrome: Chrome](https://chrome.google.com/webstore/detail/notesnook-web-clipper/kljhpemdlcnjohmfmkogahelkcidieaj) -Notesnook does not support password/PIN protection on the web & desktop apps. However, you can still lock individual notes, and your data is always encrypted in transit and on your device using your master key. +Notesnookは、Web アプリとデスクトップアプリでのパスワード/PIN 保護をサポートしていません。 ただし、個々のメモをロッ​​クすることはでき、データは転送中およびデバイス上でマスター キーを使用して常に暗号化されます。 ### Joplin diff --git a/i18n/ja/tools.md b/i18n/ja/tools.md index 1ee63c2d..8fe77805 100644 --- a/i18n/ja/tools.md +++ b/i18n/ja/tools.md @@ -1,13 +1,13 @@ --- -meta_title: "The Best Privacy Tools, Services, and Ad-Free Recommendations - Privacy Guides" -title: "Privacy Tools" +meta_title: "最高のプライバシーツール、サービス、広告なしの推奨事項 - Privacy Guides" +title: "プライバシーツール" icon: material/tools hide: - toc -description: Privacy Guides is the most transparent and reliable website for finding software, apps, and services that protect your personal data from mass surveillance programs and other internet threats. +description: Privacy Guidesは、大規模監視プログラムやその他のインターネットの脅威から個人データを保護するソフトウェア、アプリ、サービスを見つけるための最も透明性が高く信頼できる Web サイトです。 --- -If you're looking for a specific solution to something, these are the hardware and software tools we recommend in a variety of categories. Our recommended privacy tools are primarily chosen based on security features, with additional emphasis on decentralized and open-source tools. They are applicable to a variety of threat models ranging from protection against global mass surveillance programs and avoiding big tech companies to mitigating attacks, but only you can determine what will work best for your needs. +何か特定のソリューションをお探しなら、様々なカテゴリーでお勧めのハードウェアとソフトウェアのツールをご紹介します。 私たちが推奨するプライバシーツールは、主にセキュリティ機能に基づいて選択されており、さらに分散型やオープンソースのツールに重点を置いています。 これらは、世界的な大規模監視プログラムからの保護や大手ハイテク企業の回避から攻撃の緩和まで、さまざまな脅威モデルに適用できます。しかし、あなただけがあなたのニーズに最適であるかを判断できます。 If you want assistance figuring out the best privacy tools and alternative programs for your needs, start a discussion on our [forum](https://discuss.privacyguides.net/) or our [Matrix](https://matrix.to/#/#privacyguides:matrix.org) community! diff --git a/i18n/ja/vpn.md b/i18n/ja/vpn.md index 93f4b7d2..62824972 100644 --- a/i18n/ja/vpn.md +++ b/i18n/ja/vpn.md @@ -2,11 +2,11 @@ meta_title: "プライベートVPNサービスのおすすめと比較、スポンサーや広告なし - Privacy Guides" title: "VPNサービス" icon: material/vpn -description: These are the best VPN services for protecting your privacy and security online. Find a provider here that isn’t out to spy on you. +description: これらは、あなたのプライバシーとセキュリティをオンラインで保護するための最高のVPNサービスです。 ここで、あなたを監視しようとしないプロバイダーを見つけてください。 cover: vpn.png --- -ISPや公共Wi-Fiネットワークでの、またはファイルのトレンド中の、追加の**プライバシー保護**手段をお探しの場合で、リスクを理解している場合は、VPNはあなたにとっての解決策になるかもしれません。 以下のプロバイダは他のプロバイダと比較して洗練されていると、私たちは考えています。 +ISPや公共Wi-Fiネットワーク、またはファイルのTorrent中の、追加の**プライバシー保護**手段をお探しの場合で、リスクを理解している場合は、VPNはあなたにとっての解決策になるかもしれません。 以下のプロバイダは他のプロバイダと比較して洗練されていると、私たちは考えています。
@@ -24,13 +24,13 @@ ISPや公共Wi-Fiネットワークでの、またはファイルのトレンド 追加の**セキュリティ**を確保したい場合は、ウェブサイトへの接続に常にHTTPSを使用するのが有効です。 VPNは、優れたセキュリティ対策の代わりにはなりません。 - [Download Tor](https://www.torproject.org/){ .md-button .md-button--primary } [Tor Myths & FAQ](advanced/tor-overview.md){ .md-button } + [Torをダウンロード](https://www.torproject.org/){ .md-button .md-button--primary } [Torの神話とよくある質問](advanced/tor-overview.md){ .md-button } -[Detailed VPN Overview :material-arrow-right-drop-circle:](basics/vpn-overview.md ""){.md-button} +[VPNの詳細な概要 :material-arrow-right-drop-circle:](basics/vpn-overview.md ""){.md-button} -## おすすめのプロバイダ +## 推奨プロバイダー -私たちがおすすめするプロバイダは、暗号化を使用し、Moneroを受け入れ、WireGuardとOpenVPNに対応し、ノーログポリシーを持っています。 Read our [full list of criteria](#criteria) for more information. +私たちがおすすめするプロバイダは、暗号化を使用し、Moneroを受け入れ、WireGuardとOpenVPNに対応し、ノーログポリシーを持っています。 詳細については、[基準の完全なリスト](#criteria)をお読みください。 ### Proton VPN @@ -38,7 +38,7 @@ ISPや公共Wi-Fiネットワークでの、またはファイルのトレンド ![Proton VPN logo](assets/img/vpn/protonvpn.svg){ align=right } - **Proton VPN** is a strong contender in the VPN space, and they have been in operation since 2016. Proton AG is based in Switzerland and offers a limited free tier, as well as a more featured premium option. + **Proton VPN**はVPN分野の強力な候補であり、2016 年から運営されています。 Proton AGはスイスに本社を置き、限定的な無料層と、より機能的なプレミアムオプションを提供している。 [:octicons-home-16: Homepage](https://protonvpn.com/){ .md-button .md-button--primary } [:octicons-eye-16:](https://protonvpn.com/privacy-policy){ .card-link title="Privacy Policy" } @@ -153,7 +153,7 @@ IVPN previously supported port forwarding, but removed the option in [June 2023] In addition to providing standard OpenVPN configuration files, IVPN has mobile clients for [App Store](https://apps.apple.com/us/app/ivpn-serious-privacy-protection/id1193122683), [Google Play](https://play.google.com/store/apps/details?id=net.ivpn.client), and [GitHub](https://github.com/ivpn/android-app/releases) allowing for easy connections to their servers. -#### :material-information-outline:{ .pg-blue } Additional Functionality +#### :material-information-outline:{ .pg-blue } 追加機能 IVPN clients support two factor authentication (Mullvad's clients do not). IVPN also provides "[AntiTracker](https://www.ivpn.net/antitracker)" functionality, which blocks advertising networks and trackers from the network level. @@ -163,7 +163,7 @@ IVPN clients support two factor authentication (Mullvad's clients do not). IVPN ![Mullvad logo](assets/img/vpn/mullvad.svg){ align=right } - **Mullvad** is a fast and inexpensive VPN with a serious focus on transparency and security. They have been in operation since **2009**. Mullvadの拠点はスウェーデンで、フリートライアルはありません。 + **Mullvad**は、透明性とセキュリティに重点を置いた、高速で安価なVPNです。 **2009年**から運営されています。 Mullvadの拠点はスウェーデンで、フリートライアルはありません。 [:octicons-home-16: Homepage](https://mullvad.net){ .md-button .md-button--primary } [:simple-torbrowser:](http://o54hon2e2vj6c7m3aqqu6uyece65by3vgoxxhlqlsvkmacw6a7m7kiad.onion){ .card-link title="Onion Service" } @@ -227,19 +227,19 @@ Mullvad previously supported port forwarding, but removed the option in [May 202 Mullvad has published [App Store](https://apps.apple.com/app/mullvad-vpn/id1488466513) and [Google Play](https://play.google.com/store/apps/details?id=net.mullvad.mullvadvpn) clients, both supporting an easy-to-use interface as opposed to requiring you to manually configure your WireGuard connection. The Android client is also available on [GitHub](https://github.com/mullvad/mullvadvpn-app/releases). -#### :material-information-outline:{ .pg-blue } Additional Functionality +#### :material-information-outline:{ .pg-blue } 追加機能 -Mullvad is very transparent about which nodes they [own or rent](https://mullvad.net/en/servers/). They use [ShadowSocks](https://shadowsocks.org/) in their ShadowSocks + OpenVPN configuration, making them more resistant against firewalls with [Deep Packet Inspection](https://en.wikipedia.org/wiki/Deep_packet_inspection) trying to block VPNs. Supposedly, [China has to use a different method to block ShadowSocks servers](https://github.com/net4people/bbs/issues/22). Mullvad's website is also accessible via Tor at [o54hon2e2vj6c7m3aqqu6uyece65by3vgoxxhlqlsvkmacw6a7m7kiad.onion](http://o54hon2e2vj6c7m3aqqu6uyece65by3vgoxxhlqlsvkmacw6a7m7kiad.onion). +Mullvadは、どのノードを[所有またはレンタル](https://mullvad.net/en/servers/)しているのかについて非常に透明性があります。 They use [ShadowSocks](https://shadowsocks.org/) in their ShadowSocks + OpenVPN configuration, making them more resistant against firewalls with [Deep Packet Inspection](https://en.wikipedia.org/wiki/Deep_packet_inspection) trying to block VPNs. Supposedly, [China has to use a different method to block ShadowSocks servers](https://github.com/net4people/bbs/issues/22). Mullvad's website is also accessible via Tor at [o54hon2e2vj6c7m3aqqu6uyece65by3vgoxxhlqlsvkmacw6a7m7kiad.onion](http://o54hon2e2vj6c7m3aqqu6uyece65by3vgoxxhlqlsvkmacw6a7m7kiad.onion). -## Criteria +## 基準 -!!! danger +!!! 危険 It is important to note that using a VPN provider will not make you anonymous, but it will give you better privacy in certain situations. A VPN is not a tool for illegal activities. Don't rely on a "no log" policy. **Please note we are not affiliated with any of the providers we recommend. This allows us to provide completely objective recommendations.** In addition to [our standard criteria](about/criteria.md), we have developed a clear set of requirements for any VPN provider wishing to be recommended, including strong encryption, independent security audits, modern technology, and more. We suggest you familiarize yourself with this list before choosing a VPN provider, and conduct your own research to ensure the VPN provider you choose is as trustworthy as possible. -### Technology +### テクノロジー We require all our recommended VPN providers to provide OpenVPN configuration files to be used in any client. **If** a VPN provides their own custom client, we require a killswitch to block network data leaks when disconnected. @@ -250,81 +250,81 @@ We require all our recommended VPN providers to provide OpenVPN configuration fi - Multihop support. Multihopping is important to keep data private in case of a single node compromise. - If VPN clients are provided, they should be [open-source](https://en.wikipedia.org/wiki/Open_source), like the VPN software they generally have built into them. We believe that [source code](https://en.wikipedia.org/wiki/Source_code) availability provides greater transparency about what your device is actually doing. -**Best Case:** +**最良の場合：** -- WireGuard and OpenVPN support. -- Killswitch with highly configurable options (enable/disable on certain networks, on boot, etc.) -- Easy-to-use VPN clients -- Supports [IPv6](https://en.wikipedia.org/wiki/IPv6). We expect that servers will allow incoming connections via IPv6 and allow you to access services hosted on IPv6 addresses. -- Capability of [remote port forwarding](https://en.wikipedia.org/wiki/Port_forwarding#Remote_port_forwarding) assists in creating connections when using P2P ([Peer-to-Peer](https://en.wikipedia.org/wiki/Peer-to-peer)) file sharing software or hosting a server (e.g., Mumble). +- WireGuardとOpenVPNをサポート。 +- 高度に構成可能なオプションを備えたキルスイッチ（特定のネットワークや起動時などで有効/無効） +- 使いやすいVPNクライアント +- [IPv6](https://en.wikipedia.org/wiki/IPv6)をサポートする。 サーバーがIPv6経由の着信接続を許可し、IPv6アドレスでホストされているサービスにアクセスできるようになることを期待しています。 +- [リモートポート転送](https://en.wikipedia.org/wiki/Port_forwarding#Remote_port_forwarding) 機能はP2P（[Peer-to-Peer](https://en.wikipedia.org/wiki/Peer-to-peer)）ファイル共有ソフトウェアの使用時やサーバー（Mumbleなど）のホスト時に接続を作成するのに役立ちます。 -### Privacy +### プライバシー -We prefer our recommended providers to collect as little data as possible. Not collecting personal information on registration, and accepting anonymous forms of payment are required. +私たちは、推奨するプロバイダーができるだけデータを収集しないことを望んでいます。 登録時に個人情報を収集しないこと、匿名の支払い方法を受け入れることが求められます。 -**Minimum to Qualify:** +**最低条件：** -- [Anonymous cryptocurrency](cryptocurrency.md) **or** cash payment option. -- No personal information required to register: Only username, password, and email at most. +- [匿名の仮想通貨](cryptocurrency.md)**もしくは**現金支払いオプション。 +- 登録に個人情報が必要ありません。最大でもユーザー名、パスワード、電子メールのみです。 -**Best Case:** +**最良の場合：** -- Accepts multiple [anonymous payment options](advanced/payments.md). -- No personal information accepted (autogenerated username, no email required, etc.). +- 複数の[匿名支払いオプション](advanced/payments.md)に対応。 +- 個人情報が一切必要ありません。（自動生成されたユーザー名、電子メールは必要ないなど） -### Security +### セキュリティ A VPN is pointless if it can't even provide adequate security. We require all our recommended providers to abide by current security standards for their OpenVPN connections. Ideally, they would use more future-proof encryption schemes by default. We also require an independent third-party to audit the provider's security, ideally in a very comprehensive manner and on a repeated (yearly) basis. -**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. - Forward Secrecy. - Published security audits from a reputable third-party firm. -**Best Case:** +**最良の場合：** - Strongest Encryption: RSA-4096. - Forward Secrecy. - Comprehensive published security audits from a reputable third-party firm. - Bug-bounty programs and/or a coordinated vulnerability-disclosure process. -### Trust +### 信頼 You wouldn't trust your finances to someone with a fake identity, so why trust them with your internet data? We require our recommended providers to be public about their ownership or leadership. We also would like to see frequent transparency reports, especially in regard to how government requests are handled. -**Minimum to Qualify:** +**最低条件：** -- Public-facing leadership or ownership. +- 公の場でのリーダーシップやオーナーシップ。 -**Best Case:** +**最良の場合：** -- Public-facing leadership. -- Frequent transparency reports. +- 公の場でのリーダーシップ。 +- 頻繁な透明性レポート。 -### Marketing +### マーケティング -With the VPN providers we recommend we like to see responsible marketing. +私たちが推薦するVPNプロバイダーには、責任あるマーケティングを求めます。 -**Minimum to Qualify:** +**最低条件：** -- Must self-host analytics (i.e., no Google Analytics). The provider's site must also comply with [DNT (Do Not Track)](https://en.wikipedia.org/wiki/Do_Not_Track) for people who want to opt-out. +- アナリティクスを自己ホストする必要があります。（つまり、Googleアナリティクスは不可） プロバイダーのサイトは、オプトアウトを希望するユーザーのために [DNT (Do Not Track)](https://en.wikipedia.org/wiki/Do_Not_Track) に準拠しなければならない。 -Must not have any marketing which is irresponsible: +無責任なマーケティングをしてはいけない： -- Making guarantees of protecting anonymity 100%. When someone makes a claim that something is 100% it means there is no certainty for failure. We know people can quite easily deanonymize 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.) - - [Browser fingerprinting](https://en.wikipedia.org/wiki/Device_fingerprint#Browser_fingerprint) -- Claim that a single circuit VPN is "more anonymous" than Tor, which is a circuit of three or more hops that regularly changes. -- Use responsible language: i.e., it is okay to say that a VPN is "disconnected" or "not connected", however claiming that someone is "exposed", "vulnerable" or "compromised" is needless use of alarming language that may be incorrect. For example, that person might simply be on another VPN provider's service or using Tor. +- 匿名性を100％保証すること。 誰かが何かを100％だと主張するとき、それは失敗の確実性がないことを意味します。 私たちは、人々が多くの方法で簡単に匿名化を解除できることを知っています： + - 匿名化ソフトウェア（Tor、VPNなど）を使用せずにアクセスした個人情報（メールアカウント、固有のペンネームなど）を再利用する。 + - [ブラウザフィンガープリント](https://en.wikipedia.org/wiki/Device_fingerprint#Browser_fingerprint) +- 単一回線のVPNは、定期的に変更される3ホップ以上の回線であるTorよりも「匿名性が高い」と主張する。 +- 責任ある言葉を使用してください：つまり、VPNが「切断されている」または「接続されていない」と言うのは問題ありませんが、誰かが「公開されている」、「脆弱」、または「侵害されている」と主張することは、正しくない可能性のある憂慮すべき言葉を不必要に使用することです。 例えば、その人は単に他のVPNプロバイダーのサービスを利用しているだけかもしれないし、Torを使っているだけかもしれない。 -**Best Case:** +**最良の場合：** -Responsible marketing that is both educational and useful to the consumer could include: +教育的かつ消費者にとって有用な責任あるマーケティングには以下のものがあります: -- An accurate comparison to when [Tor](tor.md) should be used instead. -- Availability of the VPN provider's website over a [.onion service](https://en.wikipedia.org/wiki/.onion) +- 代わりに[Tor](tor.md)を使用する必要がある場合との正確な比較。 +- [.onion サービス](https://en.wikipedia.org/wiki/.onion)を介したVPNプロバイダーのウェブサイトの利用可能性 -### Additional Functionality +### 追加機能 While not strictly requirements, there are some factors we looked into when determining which providers to recommend. These include adblocking/tracker-blocking functionality, warrant canaries, multihop connections, excellent customer support, the number of allowed simultaneous connections, etc. diff --git a/i18n/pt/basics/common-misconceptions.md b/i18n/pt/basics/common-misconceptions.md index f5bc7733..bbde2f34 100644 --- a/i18n/pt/basics/common-misconceptions.md +++ b/i18n/pt/basics/common-misconceptions.md @@ -1,7 +1,7 @@ --- -title: "Common Misconceptions" +title: "Equívocos Comuns" icon: 'material/robot-confused' -description: Privacy isn't a straightforward topic, and it's easy to get caught up in marketing claims and other disinformation. +description: A privacidade não é um tema simples, e é fácil ser apanhado por alegações de marketing e outras desinformações. schema: - "@context": https://schema.org @@ -9,87 +9,86 @@ schema: mainEntity: - "@type": Question - name: Is open source software inherently secure? + name: É o software de código aberto inerentemente seguro? acceptedAnswer: "@type": Answer text: | - Whether the source code is available and how software is licensed does not inherently affect its security in any way. Open-source software has the potential to be more secure than proprietary software, but there is absolutely no guarantee this is the case. When you evaluate software, you should look at the reputation and security of each tool on an individual basis. + O facto de o código-fonte estar ou não disponível e a forma como o software é licenciado não afetam de forma alguma a sua segurança. O software de código aberto tem potencial para ser mais seguro do que o software proprietário, mas não há nenhuma garantia de que seja esse o caso. Ao avaliar o software, deve ter em conta a reputação e a segurança de cada ferramenta numa base individual. - "@type": Question - name: Can shifting trust to another provider increase privacy? + name: Pode a transferência de confiança para outro fornecedor aumentar a privacidade? acceptedAnswer: "@type": Answer text: | - We talk about "shifting trust" a lot when discussing solutions like VPNs (which shift the trust you place in your ISP to the VPN provider). While this protects your browsing data from your ISP specifically, the VPN provider you choose still has access to your browsing data: Your data isn't completely secured from all parties. + Falamos muito de "transferência de confiança" quando discutimos soluções como as VPN (que transferem a confiança que deposita no seu ISP para o fornecedor de VPN). Embora isto proteja especificamente os seus dados de navegação do seu ISP, o fornecedor de VPN que escolher continua a ter acesso aos seus dados de navegação: os seus dados não estão completamente protegidos de todas as partes. - "@type": Question - name: Are privacy-focused solutions inherently trustworthy? + name: São as soluções centradas na privacidade intrinsecamente fiáveis? acceptedAnswer: "@type": Answer text: | - Focusing solely on the privacy policies and marketing of a tool or provider can blind you to its weaknesses. When you're looking for a more private solution, you should determine what the underlying problem is and find technical solutions to that problem. For example, you may want to avoid Google Drive, which gives Google access to all of your data. The underlying problem in this case is lack of E2EE, so you should make sure that the provider you switch to actually implements E2EE, or use a tool (like Cryptomator) which provides E2EE on any cloud provider. Switching to a "privacy-focused" provider (that doesn't implement E2EE) doesn't solve your problem: it just shifts trust from Google to that provider. + Concentrar-se apenas nas políticas de privacidade e no marketing de uma ferramenta ou fornecedor pode cegá-lo para os seus pontos fracos. Quando procura uma solução mais privada, deve determinar qual é o problema subjacente e encontrar soluções técnicas para esse problema. Por exemplo, pode querer evitar o Google Drive, que dá ao Google acesso a todos os seus dados. O problema subjacente neste caso é a falta de E2EE, pelo que deve certificar-se de que o fornecedor para o qual muda implementa efetivamente o E2EE, ou utilizar uma ferramenta (como o Cryptomator) que fornece E2EE em qualquer fornecedor de serviços em nuvem. Mudar para um fornecedor "centrado na privacidade" (que não implementa o E2EE) não resolve o seu problema: apenas transfere a confiança da Google para esse fornecedor. - "@type": Question - name: How complicated should my threat model be? + name: Quão complicado deve ser o meu modelo de ameaça? acceptedAnswer: "@type": Answer text: | - We often see people describing privacy threat models that are overly complex. Often, these solutions include problems like many different email accounts or complicated setups with lots of moving parts and conditions. The replies are usually answers to "What is the best way to do X?" - Finding the "best" solution for yourself doesn't necessarily mean you are after an infallible solution with dozens of conditions—these solutions are often difficult to work with realistically. As we discussed previously, security often comes at the cost of convenience. + É frequente vermos pessoas a descrever modelos de ameaças à privacidade que são demasiado complexos. Muitas vezes, estas soluções incluem problemas como muitas contas de correio eletrónico diferentes ou configurações complicadas com muitas partes móveis e condições. As respostas são geralmente respostas a "Qual é a melhor forma de fazer X?" + Encontrar a "melhor" solução para si não significa necessariamente que está à procura de uma solução infalível com dezenas de condições — estas soluções são muitas vezes difíceis de trabalhar de forma realista. Tal como referimos anteriormente, a segurança tem muitas vezes um custo em termos de conveniência. --- -## "Open-source software is always secure" or "Proprietary software is more secure" +## "O software de código aberto é sempre seguro" ou "O software proprietário é mais seguro" -These myths stem from a number of prejudices, but whether the source code is available and how software is licensed does not inherently affect its security in any way. ==Open-source software has the *potential* to be more secure than proprietary software, but there is absolutely no guarantee this is the case.== When you evaluate software, you should look at the reputation and security of each tool on an individual basis. +Estes mitos têm origem numa série de preconceitos, mas o facto de o código-fonte estar ou não disponível e como o software é licenciado não afetam de forma alguma a sua segurança. ==O software de código aberto tem o *potencial* de ser mais seguro do que o software proprietário, mas não há qualquer garantia de que seja esse o caso.== Ao avaliar o software, deve analisar a reputação e a segurança de cada ferramenta numa base individual. -Open-source software *can* be audited by third-parties, and is often more transparent about potential vulnerabilities than proprietary counterparts. It also allows you to review the code and disable any suspicious functionality you find yourself. However, *unless you do so*, there is no guarantee that code has ever been evaluated, especially with smaller software projects. The open development process has also sometimes been exploited to introduce new vulnerabilities into even large projects.[^1] +O software de código aberto *pode* ser auditado por terceiros e é frequentemente mais transparente relativamente a potenciais vulnerabilidades do que as contrapartes proprietárias. Permite-lhe também rever o código e desativar qualquer funcionalidade suspeita que encontre. No entanto, *a menos que o faça*, não há garantia de que o código tenha sido alguma vez avaliado, especialmente em projetos de software menores. O processo de desenvolvimento aberto também foi por vezes explorado para introduzir novas vulnerabilidades até em grandes projetos.[^1] -On the flip side, proprietary software is less transparent, but that doesn't imply that it's not secure. Major proprietary software projects can be audited internally and by third-party agencies, and independent security researchers can still find vulnerabilities with techniques like reverse engineering. +Por outro lado, o software proprietário é menos transparente, mas isso não significa que não seja seguro. Os principais projetos de software proprietário podem ser auditados internamente e por agências terceiras, e os investigadores de segurança independentes podem ainda encontrar vulnerabilidades com técnicas como a engenharia inversa. -To avoid biased decisions, it's *vital* that you evaluate the privacy and security standards of the software you use. +Para evitar decisões tendenciosas, é *vital* que avalie as normas de privacidade e segurança do software que utiliza. -## "Shifting trust can increase privacy" +## "A mudança de confiança pode aumentar a privacidade" -We talk about "shifting trust" a lot when discussing solutions like VPNs (which shift the trust you place in your ISP to the VPN provider). While this protects your browsing data from your ISP *specifically*, the VPN provider you choose still has access to your browsing data: Your data isn't completely secured from all parties. This means that: +Falamos muito de "transferência de confiança" quando discutimos soluções como as VPN (que transferem a confiança que deposita no seu ISP para o fornecedor de VPN). Embora isto *especificamente* proteja os seus dados de navegação do seu ISP, o fornecedor de VPN que escolher continua a ter acesso aos seus dados de navegação: os seus dados não estão completamente protegidos de todas as partes. Isto significa que: -1. You must exercise caution when choosing a provider to shift trust to. -2. You should still use other techniques, like E2EE, to protect your data completely. Merely distrusting one provider to trust another is not securing your data. +1. Deve exercitar cuidado ao escolher um provedor para mudar confiança. +2. Deve ainda utilizar outras técnicas, como a E2EE, para proteger completamente os seus dados. O simples facto de desconfiar de um fornecedor para confiar noutro não protege os seus dados. -## "Privacy-focused solutions are inherently trustworthy" +## "As soluções centradas na privacidade são inerentemente fiáveis" -Focusing solely on the privacy policies and marketing of a tool or provider can blind you to its weaknesses. When you're looking for a more private solution, you should determine what the underlying problem is and find technical solutions to that problem. For example, you may want to avoid Google Drive, which gives Google access to all of your data. The underlying problem in this case is lack of E2EE, so you should make sure that the provider you switch to actually implements E2EE, or use a tool (like [Cryptomator](../encryption.md#cryptomator-cloud)) which provides E2EE on any cloud provider. Switching to a "privacy-focused" provider (that doesn't implement E2EE) doesn't solve your problem: it just shifts trust from Google to that provider. +Concentrar-se apenas nas políticas de privacidade e no marketing de uma ferramenta ou fornecedor pode cegá-lo para os seus pontos fracos. Quando procura uma solução mais privada, deve determinar qual é o problema subjacente e encontrar soluções técnicas para esse problema. Por exemplo, pode querer evitar o Google Drive, que dá ao Google acesso a todos os seus dados. O problema subjacente neste caso é a falta de E2EE, pelo que deve certificar-se de que o fornecedor para o qual muda implementa efetivamente o E2EE, ou utilizar uma ferramenta (como o [Cryptomator](../encryption.md#cryptomator-cloud)) que fornece E2EE em qualquer fornecedor de serviços em nuvem. Mudar para um fornecedor "centrado na privacidade" (que não implementa o E2EE) não resolve o seu problema: apenas transfere a confiança da Google para esse fornecedor. -The privacy policies and business practices of providers you choose are very important, but should be considered secondary to technical guarantees of your privacy: You shouldn't shift trust to another provider when trusting a provider isn't a requirement at all. +As políticas de privacidade e as práticas comerciais dos fornecedores que escolher são muito importantes, mas devem ser consideradas secundárias relativamente às garantias técnicas da sua privacidade: não se deve transferir a confiança para outro fornecedor quando a confiança num fornecedor não é de todo um requisito. -## "Complicated is better" +## "Complicado é melhor" -We often see people describing privacy threat models that are overly complex. Often, these solutions include problems like many different email accounts or complicated setups with lots of moving parts and conditions. The replies are usually answers to "What is the best way to do *X*?" +É frequente vermos pessoas a descrever modelos de ameaças à privacidade que são demasiado complexos. Muitas vezes, estas soluções incluem problemas como muitas contas de correio eletrónico diferentes ou configurações complicadas com muitas partes móveis e condições. As respostas são geralmente respostas a "Qual é a melhor maneira de fazer *X*?" -Finding the "best" solution for yourself doesn't necessarily mean you are after an infallible solution with dozens of conditions—these solutions are often difficult to work with realistically. As we discussed previously, security often comes at the cost of convenience. Below, we provide some tips: +Encontrar a "melhor" solução para si não significa necessariamente que está à procura de uma solução infalível com dezenas de condições — estas soluções são muitas vezes difíceis de trabalhar de forma realista. Tal como referimos anteriormente, a segurança tem muitas vezes um custo em termos de conveniência. Em seguida, apresentamos alguns conselhos: -1. ==Actions need to serve a particular purpose:== think about how to do what you want with the fewest actions. -2. ==Remove human failure points:== We fail, get tired, and forget things. To maintain security, avoid relying on manual conditions and processes that you have to remember. -3. ==Use the right level of protection for what you intend.== We often see recommendations of so-called law-enforcement or subpoena-proof solutions. These often require specialist knowledge and generally aren't what people want. There's no point in building an intricate threat model for anonymity if you can be easily de-anonymized by a simple oversight. +1. ==As ações têm de servir um determinado objetivo:== pense em como fazer o que pretende com o menor número de ações. +2. ==Remova os pontos de falha humanos:== Falhamos, cansamo-nos e esquecemo-nos de coisas. Para manter a segurança, evite depender de condições e processos manuais dos quais tem de se lembrar. +3. ==Utilize o nível de proteção adequado para o que pretende== É frequente vermos recomendações das chamadas soluções à prova de intimação ou de aplicação da lei. Estes requerem frequentemente conhecimentos especializados e não são geralmente o que as pessoas querem. Não adianta criar um modelo de ameaças complexo para o anonimato se pode ser facilmente desanonimizado por um simples descuido. -So, how might this look? +Então, o que isto pode parecer? -One of the clearest threat models is one where people *know who you are* and one where they do not. There will always be situations where you must declare your legal name and there are others where you don't need to. +Um dos modelos de ameaça mais claros é aquele no qual as pessoas *sabem quem é* e aquele em que não sabem. Haverá sempre situações em que tem de declarar o seu nome legal e outras em que não precisa de o fazer. -1. **Known identity** - A known identity is used for things where you must declare your name. There are many legal documents and contracts where a legal identity is required. This could range from opening a bank account, signing a property lease, obtaining a passport, customs declarations when importing items, or otherwise dealing with your government. These things will usually lead to credentials such as credit cards, credit rating checks, account numbers, and possibly physical addresses. +1. **Identidade conhecida** - A identidade conhecida é utilizada para situações em que é necessário declarar o seu nome. Existem muitos documentos jurídicos e contratos que exigem uma identidade legal. Pode tratar-se da abertura de uma conta bancária, da assinatura de um contrato de arrendamento de um imóvel, da obtenção de um passaporte, de declarações aduaneiras aquando da importação de artigos ou de qualquer outra forma de contacto com o seu governo. Estas coisas conduzem normalmente a credenciais como cartões de crédito, verificações de notação de crédito, números de conta e, possivelmente, endereços físicos. - We don't suggest using a VPN or Tor for any of these things, as your identity is already known through other means. + Não sugerimos utilizar uma VPN ou Tor para qualquer uma destas coisas, uma vez que a sua identidade já é conhecida mediante outros meios. - !!! aviso - Backup `BitLocker-Recovery-Key.txt` em um dispositivo de armazenamento separado. + !!! dica - When shopping online, the use of a [parcel locker](https://en.wikipedia.org/wiki/Parcel_locker) can help keep your physical address private. + Nas compras online, a utilização de um [armário de encomendas](https://en.wikipedia.org/wiki/Parcel_locker) pode ajudar a manter o seu endereço físico privado. -2. **Unknown identity** - An unknown identity could be a stable pseudonym that you regularly use. It is not anonymous because it doesn't change. If you're part of an online community, you may wish to retain a persona that others know. This pseudonym isn't anonymous because—if monitored for long enough—details about the owner can reveal further information, such as the way they write, their general knowledge about topics of interest, etc. +2. **Identidade desconhecida** - Uma identidade desconhecida pode ser um pseudónimo estável que utiliza regularmente. Não é anónimo porque não muda. Se faz parte de uma comunidade online, pode querer manter uma personalidade que os outros conheçam. Este pseudónimo não é anónimo porque — se for monitorizado durante tempo suficiente — os detalhes sobre o proprietário podem revelar mais informações, como a forma como escreve, o seu conhecimento geral sobre tópicos de interesse, etc. - You may wish to use a VPN for this, to mask your IP address. Financial transactions are more difficult to mask: You could consider using anonymous cryptocurrencies, such as [Monero](https://www.getmonero.org/). Employing altcoin shifting may also help to disguise where your currency originated. Typically, exchanges require KYC (know your customer) to be completed before they'll allow you to exchange fiat currency into any kind of cryptocurrency. Local meet-up options may also be a solution; however, those are often more expensive and sometimes also require KYC. + Para o efeito, poderá utilizar uma VPN para ocultar o seu endereço IP. As transações financeiras são mais difíceis de mascarar: pode considerar a utilização de criptomoedas anónimas, como [Monero](https://www.getmonero.org/). A utilização da mudança de altcoin também pode ajudar a disfarçar a origem da sua moeda. Normalmente, as bolsas exigem que o COSC (conheça o seu cliente) seja concluído antes de permitirem a troca de moeda fiduciária por qualquer tipo de moeda criptográfica. As opções de encontros locais também podem ser uma solução; no entanto, estas são frequentemente mais caras e, por vezes, também exigem COSC. -3. **Anonymous identity** - Even with experience, anonymous identities are difficult to maintain over long periods of time. They should be short-term and short-lived identities which are rotated regularly. +3. **Identidade anónima** - Mesmo com experiência, as identidades anónimas são difíceis de manter durante longos períodos de tempo. Devem ser identidades de curto prazo e de curta duração, sendo objeto de rotação regular. - Using Tor can help with this. It is also worth noting that greater anonymity is possible through asynchronous communication: Real-time communication is vulnerable to analysis of typing patterns (i.e. more than a paragraph of text, distributed on a forum, via email, etc.) + A utilização do Tor pode ajudar neste aspeto. É também de salientar que é possível um maior anonimato através da comunicação assíncrona: A comunicação em tempo real é vulnerável à análise de padrões de digitação (ou seja, mais do que um parágrafo de texto, distribuído num fórum, por correio eletrónico, etc.) -[^1]: One notable example of this is the [2021 incident in which University of Minnesota researchers introduced three vulnerabilities into the Linux kernel development project](https://cse.umn.edu/cs/linux-incident). +[^1]: Um exemplo notável é o incidente [2021 em que investigadores da Universidade do Minnesota introduziram três vulnerabilidades no projeto de desenvolvimento do kernel Linux](https://cse.umn.edu/cs/linux-incident). diff --git a/i18n/pt/file-sharing.md b/i18n/pt/file-sharing.md index 0c74ad63..24eef964 100644 --- a/i18n/pt/file-sharing.md +++ b/i18n/pt/file-sharing.md @@ -1,5 +1,5 @@ --- -title: "Partilha e sincronização de ficheiros" +title: "Partilha e Sincronização de Ficheiros" icon: material/share-variant description: Descubra como partilhar os seus ficheiros em privado entre os seus dispositivos, com os seus amigos e família, ou anonimamente online. cover: file-sharing.png @@ -14,55 +14,49 @@ Descubra como partilhar os seus ficheiros em privado entre os seus dispositivos, !!! nota Consulte o [Tabela de Hardware](https://openwrt.org/toh/start) para verificar se o seu dispositivo é suportado. - ![logotipo OnionShare](/assets/img/file-sharing-sync/onionshare.svg){ align=right } + ![Send logo](assets/img/file-sharing-sync/send.svg){ align=right } - **OnionShare** é uma ferramenta de código aberto que lhe permite partilhar de forma segura e anónima um ficheiro de qualquer tamanho. Funciona iniciando um servidor web acessível como um serviço Tor onion, com um URL indiscutível que você pode compartilhar com os destinatários para baixar ou enviar arquivos. [Visite onionshare.org](https://onionshare.org){ .md-button .md-button--primary } [:pg-tor:](http://lldan5gahapx5k7iafb3s4ikijc4ni7gx5iywdflkba5y2ezyg6sjgyd.onion){ .md-button } + **Send** é um fork do serviço Firefox Send, descontinuado pela Mozilla, que lhe permite enviar ficheiros para outros com uma hiperligação. Os ficheiros são encriptados no seu dispositivo para não poderem ser lidos pelo servidor e, opcionalmente, também podem ser protegidos por palavra-passe. O responsável pelo envio aloja uma [instância pública](https://send.vis.ee/). Pode utilizar outras instâncias públicas ou pode alojar o Send por si. - **Downloads*** - - [:fontawesome-brands-windows: Windows](https://onionshare.org/#download) - - [:fontawesome-brands-apple: macOS](https://onionshare.org/#download) - - [:fontawesome-brands-linux: Linux](https://onionshare.org/#download) - - [:fontawesome-brands-github: Fonte](https://github.com/onionshare/onionshare) You can use other public instances, or you can host Send yourself. - - [:octicons-home-16: Homepage](https://send.vis.ee){ .md-button .md-button--primary } - [:octicons-server-16:](https://github.com/timvisee/send-instances){ .card-link title="Public Instances"} - [:octicons-info-16:](https://github.com/timvisee/send#readme){ .card-link title=Documentation} - [:octicons-code-16:](https://github.com/timvisee/send){ .card-link title="Source Code" } - [:octicons-heart-16:](https://github.com/sponsors/timvisee){ .card-link title=Contribute } + [:octicons-home-16: Página Inicial](https://send.vis.ee){ .md-button .md-button--primary } + [:octicons-server-16:](https://github.com/timvisee/send-instances){ .card-link title="Instâncias Públicas"} + [:octicons-info-16:](https://github.com/timvisee/send#readme){ .card-link title=Documentação} + [:octicons-code-16:](https://github.com/timvisee/send){ .card-link title="Código fonte" } + [:octicons-heart-16:](https://github.com/sponsors/timvisee){ .card-link title=Contribuir } -Send can be used via its web interface or via the [ffsend](https://github.com/timvisee/ffsend) CLI. If you are familiar with the command-line and send files frequently, we recommend using the CLI client to avoid JavaScript-based encryption. You can specify the `--host` flag to use a specific server: +O Send pode ser utilizado através da sua interface web ou através do [ffsend](https://github.com/timvisee/ffsend) CLI. Se estiver familiarizado com a linha de comandos e enviar ficheiros frequentemente, recomendamos a utilização do cliente CLI para evitar a encriptação baseada em JavaScript. Pode especificar o sinalizador `--host` para utilizar um servidor específico: ```bash ffsend upload --host https://send.vis.ee/ FILE ``` -### Buraco de Verme Mágico +### OnionShare !!! nota Consulte o [Tabela de Hardware](https://openwrt.org/toh/start) para verificar se o seu dispositivo é suportado. - ![logotipo FreedomBox](/assets/img/file-sharing-sync/freedombox.svg){ align=right } + ![Logótipo OnionShare](assets/img/file-sharing-sync/onionshare.svg){ align=right } - **FreedomBox** é um sistema operacional projetado para ser executado em um [computador de placa única (SBC)](https://en.wikipedia.org/wiki/Single-board_computer). O objetivo é facilitar a configuração de aplicações de servidor que você pode querer auto-hospedar. + **OnionShare** é uma ferramenta de código aberto que lhe permite partilhar segura e anonimamente um ficheiro de qualquer tamanho. Funciona iniciando um servidor web acessível como um serviço Tor onion, com um URL indetetável que pode ser partilhado com os destinatários para descarregar ou enviar ficheiros. - [Visite freedombox.org](https://freedombox.org){ .md-button .md-button--primary } + [:octicons-home-16: Página Inicial](https://onionshare.org){ .md-button .md-button--primary } + [:simple-torbrowser:](http://lldan5gahapx5k7iafb3s4ikijc4ni7gx5iywdflkba5y2ezyg6sjgyd.onion){ .card-link title="Serviço Onion" } + [:octicons-info-16:](https://docs.onionshare.org){ .card-link title=Documentação} + [:octicons-code-16:](https://github.com/onionshare/onionshare){ .card-link title="Código fonte" } - **Downloads*** - - [:fontawesome-brands-git: Fonte](https://salsa.debian.org/freedombox-team/freedombox) downloads + ??? downloads - [:simple-windows11: Windows](https://onionshare.org/#download) - [:simple-apple: macOS](https://onionshare.org/#download) - [:simple-linux: Linux](https://onionshare.org/#download) -### Framadate +### Critérios -**Please note we are not affiliated with any of the projects we recommend.** In addition to [our standard criteria](about/criteria.md), we have developed a clear set of requirements to allow us to provide objective recommendations. We suggest you familiarize yourself with this list before choosing to use a project, and conduct your own research to ensure it's the right choice for you. +**Por favor note que não somos afiliados a nenhum dos projetos que recomendamos.** Para além dos [nossos critérios padrões](about/criteria.md), nós desenvolvemos um conjunto claro de requisitos que nos permitem fornecer recomendações objetivas. Sugerimos que se familiarize com esta lista antes de optar por utilizar um projeto e que faça a sua própria investigação para garantir que é a escolha certa para si. -!!! Considere o auto-hospedagem para mitigar esta ameaça. +!!! exemplo "Esta secção é nova" - ![logo PrivateBin](/assets/img/productivity/privatebin.svg){ align=right } - - **PrivateBin** é um pastebin online minimalista e de código aberto onde o servidor tem zero conhecimento de dados colados. Os dados são criptografados/descriptografados no navegador usando AES de 256 bits. Psono suporta compartilhamento seguro de senhas, arquivos, marcadores e e-mails. + Estamos a trabalhar no sentido de estabelecer critérios definidos para cada secção do nosso sítio, o que pode estar sujeito a alterações. Os dados são criptografados/descriptografados no navegador usando AES de 256 bits. Psono suporta compartilhamento seguro de senhas, arquivos, marcadores e e-mails. - Must not store decrypted data on a remote server. - O software deve ser de código aberto. diff --git a/i18n/ru/about/index.md b/i18n/ru/about/index.md index 5c5b4dcc..5738d770 100644 --- a/i18n/ru/about/index.md +++ b/i18n/ru/about/index.md @@ -19,33 +19,33 @@ schema: ![Лого Privacy Guides](../assets/brand/PNG/Square/pg-yellow.png){ align=right } -**Privacy Guides** is a socially motivated website that provides [information](/kb) for protecting your data security and privacy. Our mission is to inform the public about the value of digital privacy, and global government initiatives which aim to monitor your online activity. We are a non-profit collective operated entirely by volunteer [team members](https://discuss.privacyguides.net/g/team) and contributors. Our website is free of advertisements and not affiliated with any of the listed providers. +**Privacy Guides** - это социально мотивированный сайт, предоставляющий [информацию](/kb) по защите безопасности и конфиденциальности ваших данных. Наша миссия - информировать общественность о ценности цифровой конфиденциальности и о глобальных правительственных инициативах, направленных на мониторинг вашей активности в интернете. Мы являемся некоммерческим коллективом, который полностью управляется [волонтёрами](https://discuss.privacyguides.net/g/team) и помогающими нам людьми. Наш сайт не содержит рекламы и не связан ни с одним из перечисленных провайдеров. -[:octicons-home-16:](https://www.privacyguides.org/){ .card-link title=Homepage } -[:octicons-code-16:](https://github.com/privacyguides/privacyguides.org){ .card-link title="Source Code" } -[:octicons-heart-16:](donate.md){ .card-link title=Contribute } +[:octicons-home-16:](https://www.privacyguides.org/){ .card-link title=Домашняя страница } +[:octicons-code-16:](https://github.com/privacyguides/privacyguides.org){ .card-link title="Исходный код" } +[:octicons-heart-16:](donate.md){ .card-link title=Поддержать } -> To find [privacy-focused alternative] apps, check out sites like Good Reports and **Privacy Guides**, which list privacy-focused apps in a variety of categories, notably including email providers (usually on paid plans) that aren’t run by the big tech companies. +> Чтобы найти [ориентированные на конфиденциальность альтернативы], посетите такие сайты, как Good Reports и **Privacy Guides**. На этих сайтах в различных категориях перечислены ориентированные на конфиденциальность приложения, в частности, включая провайдеров электронной почты (обычно платных), которые не принадлежат крупным технологическим компаниям. -— [New York Times](https://www.nytimes.com/wirecutter/guides/online-security-social-media-privacy/) +— [New York Times](https://www.nytimes.com/wirecutter/guides/online-security-social-media-privacy/) [Переведено с английского] -> If you're looking for a new VPN, you can go to the discount code of just about any podcast. If you are looking for a **good** VPN, you need professional help. The same goes for email clients, browsers, operating systems and password managers. How do you know which of these is the best, most privacy-friendly option? For that there is **Privacy Guides**, a platform on which a number of volunteers search day in, day out for the best privacy-friendly tools to use on the internet. +> Если вы ищете новый VPN, вы можете найти скидочный код практически в любом подкасте. Если вы ищете **хороший** VPN, вам нужна помощь профессионалов. То же самое касается почтовых клиентов, браузеров, операционных систем и менеджеров паролей. Как узнать, какой из этих вариантов является лучшим, наиболее благоприятным для конфиденциальности? Для этого существует **Privacy Guides**, платформа, на которой несколько добровольцев изо дня в день ищут лучшие инструменты для обеспечения конфиденциальности в интернете. -— [Tweakers.net](https://tweakers.net/reviews/10568/op-zoek-naar-privacyvriendelijke-tools-niek-de-wilde-van-privacy-guides.html) [Translated from Dutch] +— [Tweakers.net](https://tweakers.net/reviews/10568/op-zoek-naar-privacyvriendelijke-tools-niek-de-wilde-van-privacy-guides.html) [Переведено с голландского] -Also featured on: [Ars Technica](https://arstechnica.com/gadgets/2022/02/is-firefox-ok/), [Wirecutter](https://www.nytimes.com/wirecutter/guides/practical-guide-to-securing-windows-pc/) [[2](https://www.nytimes.com/wirecutter/guides/practical-guide-to-securing-your-mac/)], [NPO Radio 1](https://www.nporadio1.nl/nieuws/binnenland/8eaff3a2-8b29-4f63-9b74-36d2b28b1fe1/ooit-online-eens-wat-doms-geplaatst-ga-jezelf-eens-googlen-en-kijk-dan-wat-je-tegenkomt), and [Wired](https://www.wired.com/story/firefox-mozilla-2022/). +Нас также упоминали: [Ars Technica](https://arstechnica.com/gadgets/2022/02/is-firefox-ok/), [Wirecutter](https://www.nytimes.com/wirecutter/guides/practical-guide-to-securing-windows-pc/) [[2](https://www.nytimes.com/wirecutter/guides/practical-guide-to-securing-your-mac/)], [NPO Radio 1](https://www.nporadio1.nl/nieuws/binnenland/8eaff3a2-8b29-4f63-9b74-36d2b28b1fe1/ooit-online-eens-wat-doms-geplaatst-ga-jezelf-eens-googlen-en-kijk-dan-wat-je-tegenkomt) и [Wired](https://www.wired.com/story/firefox-mozilla-2022/). -## History +## История -Privacy Guides was launched in September 2021 as a continuation of the [defunct](privacytools.md) "PrivacyTools" open-source educational project. We recognized the importance of independent, criteria-focused product recommendations and general knowledge in the privacy space, which is why we needed to preserve the work that had been created by so many contributors since 2015 and make sure that information had a stable home on the web indefinitely. +Privacy Guides был запущен в сентябре 2021 года как продолжение [недействующего](privacytools.md) образовательного проекта с открытым исходным кодом "PrivacyTools". Мы распознали важность независимых, ориентированных на критерии рекомендаций продуктов и общих знаний в области конфиденциальности, поэтому нам необходимо сохранить работу, проделанную многими участниками с 2015 года, и убедиться, что информация будет иметь стабильный дом в интернете на неопределенный срок. -In 2022, we completed the transition of our main website framework from Jekyll to MkDocs, using the `mkdocs-material` documentation software. This change made open-source contributions to our site significantly easier for outsiders, because instead of needing to know complicated syntax to write posts effectively, contributing is now as easy as writing a standard Markdown document. +В 2022 году мы завершили переход нашей основной структуры сайта с Jekyll на MkDocs, используя программное обеспечение для работы с документацией `mkdocs-material`. Это изменение значительно облегчило сторонним пользователям внесение вклада в наш сайт, поскольку вместо того, чтобы знать сложный синтаксис для эффективного написания постов, теперь вносить вклад стало так же просто, как писать стандартный документ в формате Markdown. -We additionally launched our new discussion forum at [discuss.privacyguides.net](https://discuss.privacyguides.net/) as a community platform to share ideas and ask questions about our mission. This augments our existing community on Matrix, and replaced our previous GitHub Discussions platform, decreasing our reliance on proprietary discussion platforms. +Кроме того, мы запустили новый форум для обсуждений на сайте [discuss.privacyguides.net](https://discuss.privacyguides.net/) в качестве платформы сообщества, где можно делиться идеями и задавать вопросы о нашей миссии. Это дополнит наше существующее сообщество на Matrix и заменит нашу предыдущую платформу GitHub Discussions, снизив нашу зависимость от проприетарных дискуссионных платформ. -So far in 2023 we've launched international translations of our website in [French](/fr/), [Hebrew](/he/), and [Dutch](/nl/), with more languages on the way, made possible by our excellent translation team on [Crowdin](https://crowdin.com/project/privacyguides). We plan to continue carrying forward our mission of outreach and education, and finding ways to more clearly highlight the dangers of a lack of privacy awareness in the modern digital age, and the prevalence and harms of security breaches across the technology industry. +К настоящему времени в 2023 году мы запустили международные переводы нашего сайта на [французском](/fr/), [иврите](/he/) и [голландском](/nl/) языках, и еще больше языков на подходе, что стало возможным благодаря нашей замечательной команде переводчиков на [Crowdin](https://crowdin.com/project/privacyguides). Мы планируем продолжать выполнять нашу миссию по информированию и просвещению, а также искать пути более четкого освещения опасностей, связанных с недостаточной осведомленностью о конфиденциальности в современную цифровую эпоху, а также распространенности и вреда от нарушений безопасности в технологической отрасли. -## Our Team +## Наша команда ??? person "@jonah" @@ -88,16 +88,16 @@ So far in 2023 we've launched international translations of our website in [Fren - [:simple-github: GitHub](https://github.com/hook9 "@hook9") - [:simple-mastodon: Mastodon](https://mastodon.neat.computer/@oliviablob "@oliviablob@neat.computer"){rel=me} -Additionally, [many people](https://github.com/privacyguides/privacyguides.org/graphs/contributors) have made contributions to the project. You can too, we're open sourced on GitHub, and accepting translation suggestions on [Crowdin](https://crowdin.com/project/privacyguides). +Кроме них, [множество других людей](https://github.com/privacyguides/privacyguides.org/graphs/contributors) внесли свой вклад в проект. Вы можете тоже, у нас открытый исходный код на GitHub и мы принимаем предложения по переводу на [Crowdin](https://crowdin.com/project/privacyguides). -Our team members review all changes made to the website and handle administrative duties such as web hosting and financials, however they do not personally profit from any contributions made to this site. Our financials are transparently hosted by the Open Collective Foundation 501(c)(3) at [opencollective.com/privacyguides](https://opencollective.com/privacyguides). Donations to Privacy Guides are generally tax-deductible in the United States. +Члены нашей команды проверяют все изменения, вносимые на сайт, и выполняют административные обязанности, такие как веб-хостинг и управление финансами, однако они не получают личной прибыли от этого сайта. Наша финансовая отчетность прозрачно размещена фондом Open Collective Foundation 501(c)(3) по адресу [opencollective.com/privacyguides](https://opencollective.com/privacyguides). Денежные пожертвования для Privacy Guides подлежат налоговым вычетам в США. -## Site License +## Лицензия Сайта !!! danger "" - The following is a human-readable summary of (and not a substitute for) the [license](/license). + Следующий текст является человеко-читаемым кратким изложением (но не заменой) [лицензии](/license). -:fontawesome-brands-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-nd: Unless otherwise noted, the original content on this website is made available under the [Creative Commons Attribution-NoDerivatives 4.0 International Public License](https://github.com/privacyguides/privacyguides.org/blob/main/LICENSE). This means that you are free to copy and redistribute the material in any medium or format for any purpose, even commercially; as long as you give appropriate credit to `Privacy Guides (www.privacyguides.org)` and provide a link to the license. Однако вы **не можете** использовать бренд PrivacyGuides в своем проекте без нашего специального разрешения. If you remix, transform, or build upon the content of this website, you may not distribute the modified material. +:fontawesome-brands-creative-commons: :fontawesome-brands-creative-commons-by: :fontawesome-brands-creative-commons-nd: Если не указано иное, оригинальное содержание этого сайта доступно на условиях [Creative Commons Attribution-NoDerivatives 4.0 International Public License](https://github.com/privacyguides/privacyguides.org/blob/main/LICENSE). Это означает, что вы можете свободно копировать и распространять материал на любом носителе или в любом формате для любых целей, даже коммерческих; при условии, что вы укажете соответствующую ссылку на `Privacy Guides (www.privacyguides.org)` и дадите ссылку на лицензию. Вы можете делать это любым способом в рамках разумного, но не говорить, что Privacy Guides одобряет ваш проект или ваше использование материалов. Если вы смешиваете, преобразовываете или создаете что-то на основе содержимого этого сайта, вы не имеете права распространять измененный материал. -This license is in place to prevent people from sharing our work without giving proper credit, and to prevent people from modifying our work in a way that could be used to mislead people. If you find the terms of this license too restrictive for the project you're working on, please reach out to us at `jonah@privacyguides.org`. We are happy to provide alternative licensing options for well-intentioned projects in the privacy space! +Эта лицензия существует для того, чтобы предотвратить распространение нашей работы без должной благодарности, а также для того, чтобы предотвратить изменение нашей работы таким образом, который может быть использован для введения людей в заблуждение. Если вы считаете условия этой лицензии слишком ограничивающими для проекта, над которым вы работаете, пожалуйста, свяжитесь с нами по адресу `jonah@privacyguides.org`. Мы рады предоставить альтернативные варианты лицензирования для проектов с благими намерениями в сфере конфиденциальности! diff --git a/i18n/ru/about/notices.md b/i18n/ru/about/notices.md index 41f66b8a..19552d15 100644 --- a/i18n/ru/about/notices.md +++ b/i18n/ru/about/notices.md @@ -12,26 +12,26 @@ PrivacyGuides - это проект с открытым исходным код Кроме того, PrivacyGuides не гарантирует, что данный веб-сайт будет постоянно доступен или доступен вообще. -## Licensing Overview +## Обзор лицензирования !!! danger "" - The following is a human-readable summary of (and not a substitute for) the [license](/license). + Следующий текст является человеко-читаемым кратким изложением (но не заменой) [лицензии](/license). -Unless otherwise noted, all **content** on this website is made available under the terms of the [Creative Commons Attribution-NoDerivatives 4.0 International Public License](https://github.com/privacyguides/privacyguides.org/blob/main/LICENSE). The underlying **source code** used to generate this website and display that content is released under the [MIT License](https://github.com/privacyguides/privacyguides.org/tree/main/LICENSE-CODE). +Если не указано иное, все **содержимое** этого сайта находится в свободном доступе на условиях лицензии [Creative Commons Attribution-NoDerivatives 4.0 International Public License](https://github.com/privacyguides/privacyguides.org/blob/main/LICENSE). **Исходный код**, используемый для генерации этого сайта и отображения его содержимого, выпущен под лицензией [MIT License](https://github.com/privacyguides/privacyguides.org/tree/main/LICENSE-CODE). Это не относится к коду сторонних разработчиков, встроенному в данный репозиторий, или к коду, в котором так или иначе указана другая лицензия. Ниже приведены яркие примеры, но этот список не является исчерпывающим: -* [MathJax](https://github.com/privacyguides/privacyguides.org/blob/main/theme/assets/javascripts/mathjax.js) is licensed under the [Apache License 2.0](https://github.com/privacyguides/privacyguides.org/blob/main/docs/assets/javascripts/LICENSE.mathjax.txt). -* The [Bagnard](https://github.com/privacyguides/brand/tree/main/WOFF/bagnard) heading font is licensed under the [SIL Open Font License 1.1](https://github.com/privacyguides/brand/blob/main/WOFF/bagnard/LICENSE.txt). -* The [Public Sans](https://github.com/privacyguides/brand/tree/main/WOFF/public_sans) font used for most text on the site is licensed under the terms detailed [here](https://github.com/privacyguides/brand/blob/main/WOFF/public_sans/LICENSE.txt). -* The [DM Mono](https://github.com/privacyguides/brand/tree/main/WOFF/dm_mono) font used for monospaced text on the site is licensed under the [SIL Open Font License 1.1](https://github.com/privacyguides/brand/blob/main/WOFF/dm_mono/LICENSE.txt). +* [MathJax](https://github.com/privacyguides/privacyguides.org/blob/main/theme/assets/javascripts/mathjax.js) лицензирован с помощью [Apache License 2.0](https://github.com/privacyguides/privacyguides.org/blob/main/docs/assets/javascripts/LICENSE.mathjax.txt). +* Шрифт заголовков [Bagnard](https://github.com/privacyguides/brand/tree/main/WOFF/bagnard) лицензирован с помощью [SIL Open Font License 1.1](https://github.com/privacyguides/brand/blob/main/WOFF/bagnard/LICENSE.txt). +* Шрифт [Public Sans](https://github.com/privacyguides/brand/tree/main/WOFF/public_sans), используемый для большинства текстов на сайте, лицензирован на условиях, подробно описанных [здесь](https://github.com/privacyguides/brand/blob/main/WOFF/public_sans/LICENSE.txt). +* Шрифт [DM Mono](https://github.com/privacyguides/brand/tree/main/WOFF/dm_mono), используемый для моноширинного текста на сайте, лицензирован с помощью [SIL Open Font License 1.1](https://github.com/privacyguides/brand/blob/main/WOFF/dm_mono/LICENSE.txt). Это означает, что вы можете использовать контент из этого репозитория в личных целях на условиях, изложенных в тексте Creative Commons Attribution-NoDerivatives 4.0 International Public License. Вы можете делать это любым способом в рамках разумного, но не говорить, что Privacy Guides одобряет ваш проект или ваше использование материалов. Однако вы **не можете** использовать бренд PrivacyGuides в своем проекте без нашего специального разрешения. Торговые марки бренда PrivacyGuides включают в себя название "Privacy Guides" и логотип в виде щита. Мы считаем, что логотипы и другие изображения в `assets`, полученные от сторонних лиц, являются либо публичным достоянием, либо находятся в **добросовестном использовании**. В двух словах, правовая доктрина [добросовестного использования](https://ru.wikipedia.org/wiki/Добросовестное_использование) разрешает использование изображений, защищенных авторским правом, для идентификации предмета в целях общественного обсуждения. Тем не менее, эти логотипы и другие изображения могут подпадать под действие законов о товарных знаках в тех или иных юрисдикциях. Перед использованием этого контента, пожалуйста, убедитесь, что он используется для идентификации юридического лица или организации, которой принадлежит товарный знак, и что у вас есть право использовать его в соответствии с законами, которые применяются в обстоятельствах вашего предполагаемого использования. *При копировании материалов с этого сайта вы несете полную ответственность за то, что не нарушаете авторские права.* -When you contribute to our website you are doing so under the above licenses, and you are granting Privacy Guides a perpetual, worldwide, non-exclusive, transferable, royalty-free, irrevocable license with the right to sublicense such rights through multiple tiers of sublicensees, to reproduce, modify, display, perform and distribute your contribution as part of our project. +Когда вы вносите свой вклад на наш сайт, вы делаете это на основании вышеуказанных лицензий, и вы предоставляете Privacy Guides бессрочную, всемирную, неисключительную, передаваемую, безвозмездную, безотзывную лицензию с правом сублицензирования таких прав через несколько уровней сублицензиатов, на воспроизведение, изменение, отображение, исполнение и распространение вашего вклада в рамках нашего проекта. ## Допустимое использование @@ -47,4 +47,4 @@ When you contribute to our website you are doing so under the above licenses, an --- -*Часть этого описания была взята из [opensource.guide](https://github.com/github/opensource.guide/blob/master/notices.md) на GitHub. That resource and this page itself are released under [CC-BY-4.0](https://creativecommons.org/licenses/by-sa/4.0/).* +*Часть этого описания была взята из [opensource.guide](https://github.com/github/opensource.guide/blob/master/notices.md) на GitHub. Этот ресурс и сама веб-страница выпущены под [CC-BY-4.0](https://creativecommons.org/licenses/by-sa/4.0/).* diff --git a/i18n/ru/android.md b/i18n/ru/android.md index b630d03c..c26d1c69 100644 --- a/i18n/ru/android.md +++ b/i18n/ru/android.md @@ -97,7 +97,7 @@ schema: !!! note "Примечание" - End-of-life devices (such as GrapheneOS or CalyxOS's "extended support" devices) do not have full security patches (firmware updates) due to the OEM discontinuing support. Эти устройства нельзя считать полностью безопасными, независимо от установленного программного обеспечения. + Устройства с истекшим сроком службы (например устройства с GrapheneOS или с "расширенной поддержкой" CalyxOS) не имеют полных исправлений безопасности (обновлений прошивки) из-за прекращения поддержки OEM-производителем. Эти устройства нельзя считать полностью безопасными, независимо от установленного программного обеспечения. ### GrapheneOS diff --git a/i18n/ru/meta/brand.md b/i18n/ru/meta/brand.md index 53cb9ac4..d7c417d7 100644 --- a/i18n/ru/meta/brand.md +++ b/i18n/ru/meta/brand.md @@ -1,8 +1,8 @@ --- -title: Branding Guidelines +title: Гайдлайн по брендингу --- -The name of the website is **Privacy Guides** and should **not** be changed to: +Название сайта **Privacy Guides** **не** должно быть изменено на:
- PrivacyGuides @@ -11,12 +11,12 @@ The name of the website is **Privacy Guides** and should **not** be changed to: - PG.org
-The name of the subreddit is **r/PrivacyGuides** or **the Privacy Guides Subreddit**. +Название сабреддита - **r/PrivacyGuides** или **the Privacy Guides Subreddit**. -Additional branding guidelines can be found at [github.com/privacyguides/brand](https://github.com/privacyguides/brand) +Дополнительные рекомендации по брендингу можно найти на сайте [github.com/privacyguides/brand](https://github.com/privacyguides/brand) -## Trademark +## Товарный знак -"Privacy Guides" and the shield logo are trademarks owned by Jonah Aragon, unlimited usage is granted to the Privacy Guides project. +"Privacy Guides" и логотип щита являются торговыми марками, принадлежащими Jonah Aragon, неограниченное использование предоставляется проекту Privacy Guides. -Without waiving any of its rights, Privacy Guides does not advise others on the scope of its intellectual property rights. Privacy Guides does not permit or consent to any use of its trademarks in any manner that is likely to cause confusion by implying association with or sponsorship by Privacy Guides. If you are aware of any such use, please contact Jonah Aragon at jonah@privacyguides.org. Consult your legal counsel if you have questions. +Не отказываясь от каких-либо своих прав, Privacy Guides не консультирует других относительно объема своих прав на интеллектуальную собственность. Privacy Guides не разрешает и не дает согласия на использование своих торговых марок любым способом, который может вызвать путаницу, подразумевая связь с Privacy Guides или спонсорство с их стороны. Если вам известно о любом таком использовании, пожалуйста, свяжитесь с Jonah Aragon по адресу jonah@privacyguides.org. При возникновении вопросов проконсультируйтесь с юристом. diff --git a/i18n/ru/meta/git-recommendations.md b/i18n/ru/meta/git-recommendations.md index f59b5f81..9dfe9b1c 100644 --- a/i18n/ru/meta/git-recommendations.md +++ b/i18n/ru/meta/git-recommendations.md @@ -1,8 +1,8 @@ --- -title: Git Recommendations +title: Рекомендации по Git --- -If you make changes to this website on GitHub.com's web editor directly, you shouldn't have to worry about this. If you are developing locally and/or are a long-term website editor (who should probably be developing locally!), consider these recommendations. +Если вы вносите изменения на этом сайте непосредственно в веб-редакторе GitHub.com, вам не стоит беспокоиться об этом. If you are developing locally and/or are a long-term website editor (who should probably be developing locally!), consider these recommendations. ## Enable SSH Key Commit Signing diff --git a/i18n/ru/meta/uploading-images.md b/i18n/ru/meta/uploading-images.md index 55f136f8..7e829014 100644 --- a/i18n/ru/meta/uploading-images.md +++ b/i18n/ru/meta/uploading-images.md @@ -1,23 +1,23 @@ --- -title: Uploading Images +title: Загрузка изображений --- Here are a couple of general rules for contributing to Privacy Guides: -## Images +## Изображения -- We **prefer** SVG images, but if those do not exist we can use PNG images +- Мы **предпочитаем** SVG-изображения, но если их нет, мы можем использовать PNG-изображения -Company logos have canvas size of: +Логотипы компании имеют размер холста: - 128x128px - 384x128px -## Optimization +## Оптимизация ### PNG -Use the [OptiPNG](https://sourceforge.net/projects/optipng/) to optimize the PNG image: +Используйте [OptiPNG](https://sourceforge.net/projects/optipng/) для оптимизации PNG-изображения: ```bash optipng -o7 file.png @@ -27,12 +27,12 @@ optipng -o7 file.png #### Inkscape -[Scour](https://github.com/scour-project/scour) all SVG images. +Используйте [Scour](https://github.com/scour-project/scour) для всех SVG-изображений. -In Inkscape: +В Inkscape: -1. File Save As.. -2. Set type to Optimized SVG (*.svg) +1. Файл Сохранить как.. +2. Установите тип Оптимизированный SVG (*.svg) In the **Options** tab: diff --git a/i18n/ru/news-aggregators.md b/i18n/ru/news-aggregators.md index 7d41f957..f94f1e94 100644 --- a/i18n/ru/news-aggregators.md +++ b/i18n/ru/news-aggregators.md @@ -140,10 +140,10 @@ cover: news-aggregators.png ### Reddit -Reddit allows you to subscribe to subreddits via RSS. +Reddit позволяет подписываться на сабреддиты через RSS. -!!! example - Replace `subreddit_name` with the subreddit you wish to subscribe to. +!!! example "Пример" + Замените `subreddit_name` названием сабреддита, на который вы хотите подписаться. ```text https://www.reddit.com/r/{{ subreddit_name }}/new/.rss @@ -151,11 +151,11 @@ Reddit allows you to subscribe to subreddits via RSS. ### Twitter -Using any of the Nitter [instances](https://github.com/zedeus/nitter/wiki/Instances) you can easily subscribe using RSS. +Используя любой из [экземпляров](https://github.com/zedeus/nitter/wiki/Instances) Nitter, вы можете легко подписаться, используя RSS. !!! example "Пример" - 1. Pick an instance and set `nitter_instance`. - 2. Replace `twitter_account` with the account name. + 1. Выберите экземпляр и установите `nitter_instance`. + 2. Замените `twitter_account` на имя аккаунта. ```text https://{{ nitter_instance }}/{{ twitter_account }}/rss @@ -167,7 +167,7 @@ Using any of the Nitter [instances](https://github.com/zedeus/nitter/wiki/Instan !!! example "Пример" - To subscribe to a YouTube channel with an RSS client, first look for your [channel code](https://support.google.com/youtube/answer/6180214), replace `[CHANNEL ID]` below: + Чтобы подписаться на канал YouTube с помощью RSS-клиента, сначала найдите свой [код канала](https://support.google.com/youtube/answer/6180214), замените `[Идентификатор канала]` ниже: ```text https://www.youtube.com/feeds/videos.xml?channel_id=[Идентификатор канала] ``` diff --git a/i18n/ru/os/linux-overview.md b/i18n/ru/os/linux-overview.md index 3b3a5345..ad2f9e52 100644 --- a/i18n/ru/os/linux-overview.md +++ b/i18n/ru/os/linux-overview.md @@ -117,26 +117,26 @@ description: Linux - это альтернативная настольная о Многие настольные дистрибутивы Linux (Fedora, openSUSE и т.д.) поставляются с [NetworkManager](https://en.wikipedia.org/wiki/NetworkManager), для настройки параметров Ethernet и Wi-Fi. -Можно [рандомизировать](https://fedoramagazine.org/randomize-mac-address-nm/) [MAC-адрес](https://ru.wikipedia.org/wiki/MAC-%D0%B0%D0%B4%D1%80%D0%B5%D1%81) при использовании NetworkManager. This provides a bit more privacy on Wi-Fi networks as it makes it harder to track specific devices on the network you’re connected to. It does [**not**](https://papers.mathyvanhoef.com/wisec2016.pdf) make you anonymous. +Можно [рандомизировать](https://fedoramagazine.org/randomize-mac-address-nm/) [MAC-адрес](https://ru.wikipedia.org/wiki/MAC-%D0%B0%D0%B4%D1%80%D0%B5%D1%81) при использовании NetworkManager. Это обеспечивает большую конфиденциальность в сетях Wi-Fi, так как затрудняет отслеживание конкретных устройств в сети, к которой вы подключены. Это [**не**](https://papers.mathyvanhoef.com/wisec2016.pdf) делает вас анонимным. -We recommend changing the setting to **random** instead of **stable**, as suggested in the [article](https://fedoramagazine.org/randomize-mac-address-nm/). +Мы рекомендуем изменить настройки на **random** вместо **stable**, как предлагается в [статье](https://fedoramagazine.org/randomize-mac-address-nm/). -If you are using [systemd-networkd](https://en.wikipedia.org/wiki/Systemd#Ancillary_components), you will need to set [`MACAddressPolicy=random`](https://www.freedesktop.org/software/systemd/man/systemd.link.html#MACAddressPolicy=) which will enable [RFC 7844 (Anonymity Profiles for DHCP Clients)](https://www.freedesktop.org/software/systemd/man/systemd.network.html#Anonymize=). +Если вы используете [systemd-networkd](https://en.wikipedia.org/wiki/Systemd#Ancillary_components), вам необходимо установить [`MACAddressPolicy=random`](https://www.freedesktop.org/software/systemd/man/systemd.link.html#MACAddressPolicy=), что позволит включить [RFC 7844 (профили анонимности для клиентов DHCP)](https://www.freedesktop.org/software/systemd/man/systemd.network.html#Anonymize=). -There isn’t many points in randomizing the MAC address for Ethernet connections as a system administrator can find you by looking at the port you are using on the [network switch](https://en.wikipedia.org/wiki/Network_switch). Randomizing Wi-Fi MAC addresses depends on support from the Wi-Fi’s firmware. +Нет особого смысла в рандомизации MAC-адресов для Ethernet-подключений, поскольку системный администратор может найти вас, посмотрев на порт, который вы используете на [сетевом коммутаторе](https://en.wikipedia.org/wiki/Network_switch). Рандомизация MAC-адресов Wi-Fi зависит от поддержки встроенного программного обеспечения Wi-Fi. ### Другие идентификаторы -There are other system identifiers which you may wish to be careful about. You should give this some thought to see if it applies to your [threat model](../basics/threat-modeling.md): +Существуют и другие системные идентификаторы, с которыми следует быть осторожными. Вам следует подумать, применимо ли это к вашей [модели угрозы](../basics/threat-modeling.md): -- **Hostnames:** Your system's hostname is shared with the networks you connect to. You should avoid including identifying terms like your name or operating system in your hostname, instead sticking to generic terms or random strings. -- **Usernames:** Similarly, your username is used in a variety of ways across your system. Consider using generic terms like "user" rather than your actual name. -- **Machine ID:**: During installation a unique machine ID is generated and stored on your device. Consider [setting it to a generic ID](https://madaidans-insecurities.github.io/guides/linux-hardening.html#machine-id). +- **Хост-имена:** Имя хоста вашей системы является общим для сетей, к которым вы подключаетесь. Вам следует избегать включения в имя хоста идентифицирующих терминов, таких как ваше имя или операционная система, вместо этого следует использовать общие термины или случайные строки. +- **Имена пользователей:** Аналогично, ваше имя пользователя используется различными способами в вашей системе. Рассмотрите возможность использования общих терминов, таких как "пользователь", вместо вашего настоящего имени. +- **Идентификатор устройства:**: Во время установки генерируется уникальный идентификатор устройства, который сохраняется на вашем устройстве. Рассмотрите возможность [установки случайного идентификатора](https://madaidans-insecurities.github.io/guides/linux-hardening.html#machine-id). ### Подсчёт систем -The Fedora Project [counts](https://fedoraproject.org/wiki/Changes/DNF_Better_Counting) how many unique systems access its mirrors by using a [`countme`](https://fedoraproject.org/wiki/Changes/DNF_Better_Counting#Detailed_Description) variable instead of a unique ID. Fedora does this to determine load and provision better servers for updates where necessary. +Проект Fedora [подсчитывает](https://fedoraproject.org/wiki/Changes/DNF_Better_Counting), сколько уникальных систем обращаются к его зеркалам, используя переменную [`countme`](https://fedoraproject.org/wiki/Changes/DNF_Better_Counting#Detailed_Description) вместо уникального ID. Fedora делает это для определения нагрузки и предоставления лучших серверов для обновлений, где это необходимо. -This [option](https://dnf.readthedocs.io/en/latest/conf_ref.html#options-for-both-main-and-repo) is currently off by default. We recommend adding `countme=false` to `/etc/dnf/dnf.conf` just in case it is enabled in the future. On systems that use `rpm-ostree` such as Silverblue, the countme option is disabled by masking the [rpm-ostree-countme](https://fedoramagazine.org/getting-better-at-counting-rpm-ostree-based-systems/) timer. +Эта [опция](https://dnf.readthedocs.io/en/latest/conf_ref.html#options-for-both-main-and-repo) в настоящее время по умолчанию выключена. Мы рекомендуем добавить `countme=false` в `/etc/dnf/dnf.conf` на случай, если она будет включена в будущем. В системах, использующих `rpm-ostree`, например Silverblue, опция countme отключается путем маскировки таймера [rpm-ostree-countme](https://fedoramagazine.org/getting-better-at-counting-rpm-ostree-based-systems/). -openSUSE also uses a [unique ID](https://en.opensuse.org/openSUSE:Statistics) to count systems, which can be disabled by deleting the `/var/lib/zypp/AnonymousUniqueId` file. +openSUSE также использует [уникальный идентификатор](https://en.opensuse.org/openSUSE:Statistics) для подсчета систем, который можно отключить, удалив файл `/var/lib/zypp/AnonymousUniqueId`. diff --git a/i18n/ru/os/qubes-overview.md b/i18n/ru/os/qubes-overview.md index b5fee448..97e12abb 100644 --- a/i18n/ru/os/qubes-overview.md +++ b/i18n/ru/os/qubes-overview.md @@ -1,55 +1,55 @@ --- -title: "Qubes Overview" +title: "Обзор Qubes" icon: pg/qubes-os description: Qubes - это операционная система, построенная на изоляции приложений в виртуальных машинах для обеспечения повышенной безопасности. --- -[**Qubes OS**](../desktop.md#qubes-os) - операционная система, использующая гипервизор [Xen](https://ru.wikipedia.org/wiki/Xen) для обеспечения надёжной защиты компьютера с помощью изолированных виртуальных машин (далее - ВМ). Каждая ВМ называется *Qube*, и вы можете назначить каждому Qube уровень доверия в зависимости от его назначения. As Qubes OS provides security by using isolation, and only permitting actions on a per case basis, it is the opposite of [badness enumeration](https://www.ranum.com/security/computer_security/editorials/dumb/). +[**Qubes OS**](../desktop.md#qubes-os) - операционная система, использующая гипервизор [Xen](https://ru.wikipedia.org/wiki/Xen) для обеспечения надёжной защиты компьютера с помощью изолированных виртуальных машин (далее - ВМ). Каждая ВМ называется *Qube*, и вы можете назначить каждому Qube уровень доверия в зависимости от его назначения. Поскольку Qubes OS обеспечивает безопасность, используя изоляцию и разрешая действия только в каждом конкретном случае, она противоположна [перечислению плохого](https://www.ranum.com/security/computer_security/editorials/dumb/). ## Как работает Qubes OS? -Qubes uses [compartmentalization](https://www.qubes-os.org/intro/) to keep the system secure. Qubes are created from templates, the defaults being for Fedora, Debian and [Whonix](../desktop.md#whonix). Qubes OS also allows you to create once-use [disposable](https://www.qubes-os.org/doc/how-to-use-disposables/) virtual machines. +Qubes использует [компартментализацию(разделение)](https://www.qubes-os.org/intro/) для обеспечения безопасности системы. Qubes создаются на основе шаблонов, по умолчанию Fedora, Debian и [Whonix](../desktop.md#whonix). Qubes OS также позволяет создавать [одноразовые](https://www.qubes-os.org/doc/how-to-use-disposables/) виртуальные машины. -![Qubes architecture](../assets/img/qubes/qubes-trust-level-architecture.png) +![Архитектура Qubes](../assets/img/qubes/qubes-trust-level-architecture.png)
Qubes Architecture, Credit: What is Qubes OS Intro
-Each Qubes application has a [colored border](https://www.qubes-os.org/screenshots/) that can help you keep track of the virtual machine it is running in. You could, for example, use a specific color for your banking browser, while using a different color for a general untrusted browser. +Каждое приложение Qubes имеет [цветную рамку](https://www.qubes-os.org/screenshots/), которая помогает вам понять, в какой виртуальной машине оно запущено. Например, вы можете использовать определенный цвет для банковского браузера, а другой цвет - для общего ненадежного браузера. -![Colored border](../assets/img/qubes/r4.0-xfce-three-domains-at-work.png) +![Цветная рамка](../assets/img/qubes/r4.0-xfce-three-domains-at-work.png)
Qubes window borders, Credit: Qubes Screenshots
-## Why Should I use Qubes? +## Почему мне стоит использовать Qubes? -Qubes OS is useful if your [threat model](../basics/threat-modeling.md) requires strong compartmentalization and security, such as if you think you'll be opening untrusted files from untrusted sources. A typical reason for using Qubes OS is to open documents from unknown sources. +Qubes OS полезна, если ваша [модель угроз](../basics/threat-modeling.md) требует сильного разделения и безопасности, например, если вы думаете, что будете открывать недоверенные файлы из недоверенных источников. Типичная причина использования Qubes OS - открытие документов из неизвестных источников. -Qubes OS utilizes [Dom0](https://wiki.xenproject.org/wiki/Dom0) Xen VM (i.e., an "AdminVM") for controlling other guest VMs or Qubes on the host OS. Other VMs display individual application windows within Dom0's desktop environment. It allows you to color code windows based on trust levels and run apps that can interact with each other with very granular control. +Qubes OS использует ВМ [Dom0](https://wiki.xenproject.org/wiki/Dom0) Xen (т.е. "AdminVM") для управления другими гостевыми ВМ или Qubes на хостовой ОС. Другие ВМ отображают отдельные окна приложений в среде рабочего стола Dom0. Это позволяет вам выделять окна цветом в зависимости от уровня доверия и запускать приложения, которые могут взаимодействовать друг с другом с очень детальным контролем. -### Copying and Pasting Text +### Копирование и вставка текста -You can [copy and paste text](https://www.qubes-os.org/doc/how-to-copy-and-paste-text/) using `qvm-copy-to-vm` or the below instructions: +Вы можете [копировать и вставлять текст](https://www.qubes-os.org/doc/how-to-copy-and-paste-text/), используя `qvm-copy-to-vm` или приведенные ниже инструкции: -1. Press **Ctrl+C** to tell the VM you're in that you want to copy something. -2. Press **Ctrl+Shift+C** to tell the VM to make this buffer available to the global clipboard. -3. Press **Ctrl+Shift+V** in the destination VM to make the global clipboard available. -4. Press **Ctrl+V** in the destination VM to paste the contents in the buffer. +1. Нажмите **Ctrl+C**, чтобы сообщить ВМ, в которой вы находитесь, что вы хотите что-то скопировать. +2. Нажмите **Ctrl+Shift+C**, чтобы указать ВМ сделать этот буфер доступным для глобального буфера обмена. +3. Нажмите **Ctrl+Shift+V** в ВМ назначения, чтобы сделать доступным глобальный буфер обмена. +4. Нажмите **Ctrl+V** в целевой ВМ, чтобы вставить содержимое в буфер. -### File Exchange +### Обмен файлами -To copy and paste files and directories (folders) from one VM to another, you can use the option **Copy to Other AppVM...** or **Move to Other AppVM...**. The difference is that the **Move** option will delete the original file. Either option will protect your clipboard from being leaked to any other Qubes. This is more secure than air-gapped file transfer because an air-gapped computer will still be forced to parse partitions or file systems. That is not required with the inter-qube copy system. +Для копирования и вставки файлов и каталогов (папок) из одной ВМ в другую можно воспользоваться опцией **Copy to Other AppVM...** или **Move to Other AppVM...**. Разница в том, что опция **Move** удалит исходный файл. Любой из этих вариантов защитит ваш буфер обмена от утечки к другим Qubes. Это более безопасно, чем передача файлов по воздуху, поскольку компьютер с передачей по воздуху все равно будет вынужден парсить разделы или файловые системы. Этого не требуется при использовании системы копирования между несколькими Qubes. -??? info "AppVMs or qubes do not have their own file systems" +??? info "AppVMs или qubes не имеют собственных файловых систем" - You can [copy and move files](https://www.qubes-os.org/doc/how-to-copy-and-move-files/) between Qubes. When doing so the changes aren't immediately made and can be easily undone in case of an accident. + Вы можете [копировать и перемещать файлы](https://www.qubes-os.org/doc/how-to-copy-and-move-files/) между Qubes. При этом изменения вносятся не сразу и могут быть легко отменены в случае аварии. -### Inter-VM Interactions +### Взаимодействие между ВМ -The [qrexec framework](https://www.qubes-os.org/doc/qrexec/) is a core part of Qubes which allows virtual machine communication between domains. It is built on top of the Xen library *vchan*, which facilitates [isolation through policies](https://www.qubes-os.org/news/2020/06/22/new-qrexec-policy-system/). +[Фреймворк qrexec](https://www.qubes-os.org/doc/qrexec/) является основной частью Qubes, которая позволяет виртуальным машинам взаимодействовать между доменами. Он построен на базе библиотеки Xen *vchan*, которая обеспечивает изоляцию [с помощью политик](https://www.qubes-os.org/news/2020/06/22/new-qrexec-policy-system/). ## Дополнительные советы -For additional information we encourage you to consult the extensive Qubes OS documentation pages located on the [Qubes OS Website](https://www.qubes-os.org/doc/). Offline copies can be downloaded from the Qubes OS [documentation repository](https://github.com/QubesOS/qubes-doc). +Для получения дополнительной информации мы рекомендуем вам обратиться к обширной документации Qubes OS, расположенной на сайте [Qubes OS Website](https://www.qubes-os.org/doc/). Офлайн копии можно загрузить из [репозитория документации](https://github.com/QubesOS/qubes-doc) Qubes OS. -- Open Technology Fund: [*Arguably the world's most secure operating system*](https://www.opentech.fund/news/qubes-os-arguably-the-worlds-most-secure-operating-system-motherboard/) -- J. Rutkowska: [*Software compartmentalization vs. physical separation*](https://invisiblethingslab.com/resources/2014/Software_compartmentalization_vs_physical_separation.pdf) -- J. Rutkowska: [*Partitioning my digital life into security domains*](https://blog.invisiblethings.org/2011/03/13/partitioning-my-digital-life-into.html) -- Qubes OS: [*Related Articles*](https://www.qubes-os.org/news/categories/#articles) +- Фонд открытых технологий: [*Пожалуй, самая безопасная операционная система в мире*](https://www.opentech.fund/news/qubes-os-arguably-the-worlds-most-secure-operating-system-motherboard/) +- J. Rutkowska: [*Программная компартментализация против физического разделения*](https://invisiblethingslab.com/resources/2014/Software_compartmentalization_vs_physical_separation.pdf) +- J. Rutkowska: [*Разделение моей цифровой жизни по доменам безопасности*](https://blog.invisiblethings.org/2011/03/13/partitioning-my-digital-life-into.html) +- Qubes OS: [*Связанные статьи*](https://www.qubes-os.org/news/categories/#articles) diff --git a/i18n/ru/real-time-communication.md b/i18n/ru/real-time-communication.md index 76c04787..06b28887 100644 --- a/i18n/ru/real-time-communication.md +++ b/i18n/ru/real-time-communication.md @@ -138,7 +138,7 @@ Briar поддерживает прямую секретность пересы Сам протокол Matrix [теоретически поддерживает PFS](https://gitlab.matrix.org/matrix-org/olm/blob/master/docs/megolm.md#partial-forward-secrecy), однако он [в настоящее время не поддерживается в Element](https://github.com/vector-im/element-web/issues/7101) из-за того, что это нарушает некоторые аспекты работы пользователей, такие как резервное копирование ключей и общая история сообщений. -Протокол прошел независимый [аудит](https://matrix.org/blog/2016/11/21/matrixs-olm-end-to-end-encryption-security-assessment-released-and-implemented-cross-platform-on-riot-at-last) в 2016 году. Спецификацию протокола Matrix можно найти в их [документации](https://spec.matrix.org/latest/). The [Olm](https://matrix.org/docs/projects/other/olm) cryptographic ratchet used by Matrix is an implementation of Signal’s [Double Ratchet algorithm](https://signal.org/docs/specifications/doubleratchet/). +Протокол прошел независимый [аудит](https://matrix.org/blog/2016/11/21/matrixs-olm-end-to-end-encryption-security-assessment-released-and-implemented-cross-platform-on-riot-at-last) в 2016 году. Спецификацию протокола Matrix можно найти в их [документации](https://spec.matrix.org/latest/). Криптографический ratchet [Olm](https://matrix.org/docs/projects/other/olm), используемый Matrix, является реализацией алгоритма [Double Ratchet](https://signal.org/docs/specifications/doubleratchet/) в Signal. ### Session diff --git a/includes/abbreviations.ja.txt b/includes/abbreviations.ja.txt index 1827a995..bcd389e9 100644 --- a/includes/abbreviations.ja.txt +++ b/includes/abbreviations.ja.txt @@ -1,8 +1,8 @@ *[2FA]: 二要素認証（2-Factor Authentication） *[ADB]: Android Debug Bridge -*[AOSP]: Android Open Source Project +*[AOSP]: Android オープンソース プロジェクト（Android Open Source Project） *[ATA]: Advanced Technology Attachment -*[attack surface]: The total number of possible entry points for unauthorized access to a system +*[攻撃対象領域]: システムへ不正にアクセスできる可能性のある侵入口の総数。 *[AVB]: Android Verified Boot *[cgroups]: Control Groups *[CLI]: Command Line Interface @@ -43,7 +43,7 @@ *[IP]: Internet Protocol *[IPv4]: Internet Protocol version 4 *[IPv6]: Internet Protocol version 6 -*[ISP]: Internet Service Provider +*[ISP]: インターネットサービスプロバイダ（Internet Service Provider） *[ISPs]: Internet Service Providers *[JNI]: Java Native Interface *[KYC]: Know Your Customer @@ -87,7 +87,7 @@ *[TEE]: Trusted Execution Environment *[TLS]: Transport Layer Security *[ToS]: 利用規約（Terms of Service） -*[TOTP]: Time-based One-Time Password +*[TOTP]: タイムベースドワンタイムパスワード（Time-based One-Time Password） *[TPM]: Trusted Platform Module *[U2F]: Universal 2nd Factor *[UEFI]: Unified Extensible Firmware Interface diff --git a/includes/strings.ja.yml b/includes/strings.ja.yml index 96536392..ffb631b5 100644 --- a/includes/strings.ja.yml +++ b/includes/strings.ja.yml @@ -32,7 +32,7 @@ nav: Technology Essentials: 技術の概要 Operating Systems: OS Advanced Topics: 高度なトピック - Recommendations: おすすめ + Recommendations: 推奨事項 Internet Browsing: インターネットブラウジング Providers: プロバイダ Software: ソフトウェア