mirror of
https://github.com/privacyguides/i18n.git
synced 2025-09-07 22:08:49 +00:00
436 lines
24 KiB
Markdown
436 lines
24 KiB
Markdown
---
|
|
meta_title: "Recommended Encryption Software: VeraCrypt, Cryptomator, PicoCrypt, and OpenPGP - Privacy Guides"
|
|
title: "암호화 소프트웨어"
|
|
icon: material/file-lock
|
|
description: 데이터 암호화는 데이터에 접근 가능한 사람을 통제하는 유일한 방법입니다. These tools allow you to encrypt your emails and any other files.
|
|
cover: encryption.webp
|
|
---
|
|
|
|
**Encryption** is the only secure way to control who can access your data. If you are currently not using encryption software for your hard disk, emails, or files, you should pick an option here.
|
|
|
|
## Multi-platform
|
|
|
|
The options listed here are available on multiple platforms and great for creating encrypted backups of your data.
|
|
|
|
### Cryptomator (클라우드)
|
|
|
|
<small>Protects against the following threat(s):</small>
|
|
|
|
- [:material-bug-outline: 수동적 공격(Passive Attacks)](basics/common-threats.md#security-and-privacy ""){.pg-orange}
|
|
|
|
<div class="admonition recommendation" markdown>
|
|
|
|
{ align=right }
|
|
|
|
**Cryptomator** is an encryption solution designed for privately saving files to any cloud [:material-server-network: Service Provider](basics/common-threats.md#privacy-from-service-providers){ .pg-teal }, eliminating the need to trust that they won't access your files. 가상 드라이브에 Vault라고 불리는 파일 저장소를 생성할 수 있고, 여기에 저장된 파일들은 암호화되며 자동으로 클라우드와 동기화됩니다.
|
|
|
|
[:octicons-home-16: Homepage](https://cryptomator.org){ .md-button .md-button--primary }
|
|
[:octicons-eye-16:](https://cryptomator.org/privacy){ .card-link title="Privacy Policy" }
|
|
[:octicons-info-16:](https://docs.cryptomator.org){ .card-link title="Documentation" }
|
|
[:octicons-code-16:](https://github.com/cryptomator){ .card-link title="Source Code" }
|
|
[:octicons-heart-16:](https://cryptomator.org/donate){ .card-link title="Contribute" }
|
|
|
|
<details class="downloads" markdown>
|
|
<summary>Downloads</summary>
|
|
|
|
- [:simple-googleplay: Google Play](https://play.google.com/store/apps/details?id=org.cryptomator)
|
|
- [:simple-appstore: App Store](https://apps.apple.com/app/id1560822163)
|
|
- [:simple-android: Android](https://cryptomator.org/android)
|
|
- [:fontawesome-brands-windows: Windows](https://cryptomator.org/downloads)
|
|
- [:simple-apple: macOS](https://cryptomator.org/downloads)
|
|
- [:simple-linux: Linux](https://cryptomator.org/downloads)
|
|
- [:simple-flathub: Flathub](https://flathub.org/apps/details/org.cryptomator.Cryptomator)
|
|
|
|
</details>
|
|
|
|
</div>
|
|
|
|
Cryptomator uses AES-256 encryption to encrypt both files and filenames. Cryptomator cannot encrypt metadata such as access, modification, and creation timestamps, nor the number and size of files and folders.
|
|
|
|
Cryptomator is free to use on all desktop platforms, as well as on iOS in "read only" mode. Cryptomator offers [paid](https://cryptomator.org/pricing) apps with full functionality on iOS and Android. The Android version can be purchased anonymously via [ProxyStore](https://cryptomator.org/coop/proxystore).
|
|
|
|
Some Cryptomator cryptographic libraries have been [audited](https://community.cryptomator.org/t/has-there-been-a-security-review-audit-of-cryptomator/44) by Cure53. The scope of the audited libraries includes: [cryptolib](https://github.com/cryptomator/cryptolib), [cryptofs](https://github.com/cryptomator/cryptofs), [siv-mode](https://github.com/cryptomator/siv-mode) and [cryptomator-objc-cryptor](https://github.com/cryptomator/cryptomator-objc-cryptor). The audit did not extend to [cryptolib-swift](https://github.com/cryptomator/cryptolib-swift), which is a library used by Cryptomator for iOS.
|
|
|
|
Cryptomator's documentation details its intended [security target](https://docs.cryptomator.org/en/latest/security/security-target), [security architecture](https://docs.cryptomator.org/en/latest/security/architecture), and [best practices](https://docs.cryptomator.org/en/latest/security/best-practices) for use in further detail.
|
|
|
|
### Picocrypt (파일)
|
|
|
|
<small>Protects against the following threat(s):</small>
|
|
|
|
- [:material-target-account: 표적 공격(Targeted Attacks)](basics/common-threats.md#attacks-against-specific-individuals ""){.pg-red}
|
|
|
|
<div class="admonition recommendation" markdown>
|
|
|
|
{ align=right }
|
|
|
|
**Picocrypt** is a small and simple encryption tool that provides modern encryption. Picocrypt uses the secure XChaCha20 cipher and the Argon2id key derivation function to provide a high level of security. It uses Go's standard x/crypto modules for its encryption features.
|
|
|
|
[:octicons-repo-16: Repository](https://github.com/Picocrypt/Picocrypt#readme){ .md-button .md-button--primary }
|
|
[:octicons-code-16:](https://github.com/Picocrypt/Picocrypt){ .card-link title="Source Code" }
|
|
[:octicons-heart-16:](https://opencollective.com/picocrypt){ .card-link title="Contribute" }
|
|
|
|
<details class="downloads" markdown>
|
|
<summary>Downloads</summary>
|
|
|
|
- [:fontawesome-brands-windows: Windows](https://github.com/Picocrypt/Picocrypt/releases)
|
|
- [:simple-apple: macOS](https://github.com/Picocrypt/Picocrypt/releases)
|
|
- [:simple-linux: Linux](https://github.com/Picocrypt/Picocrypt/releases)
|
|
|
|
</details>
|
|
|
|
</div>
|
|
|
|
Picocrypt has been [audited](https://github.com/Picocrypt/storage/blob/main/Picocrypt.Audit.Report.pdf) by Radically Open Security in August 2024, and [most](https://github.com/Picocrypt/Picocrypt/issues/32#issuecomment-2329722740) of the issues found in the audit were subsequently fixed.
|
|
|
|
### VeraCrypt (디스크)
|
|
|
|
<small>Protects against the following threat(s):</small>
|
|
|
|
- [:material-target-account: 표적 공격(Targeted Attacks)](basics/common-threats.md#attacks-against-specific-individuals ""){.pg-red}
|
|
|
|
<div class="admonition recommendation" markdown>
|
|
|
|
{ align=right }
|
|
{ align=right }
|
|
|
|
**VeraCrypt** is a source-available freeware utility used for on-the-fly encryption. It can create a virtual encrypted disk within a file, encrypt a partition, or encrypt the entire storage device with pre-boot authentication.
|
|
|
|
[:octicons-home-16: Homepage](https://veracrypt.fr){ .md-button .md-button--primary }
|
|
[:octicons-info-16:](https://veracrypt.fr/en/Documentation.html){ .card-link title="Documentation" }
|
|
[:octicons-code-16:](https://veracrypt.fr/code){ .card-link title="Source Code" }
|
|
[:octicons-heart-16:](https://veracrypt.fr/en/Donation.html){ .card-link title="Contribute" }
|
|
|
|
<details class="downloads" markdown>
|
|
<summary>Downloads</summary>
|
|
|
|
- [:fontawesome-brands-windows: Windows](https://veracrypt.fr/en/Downloads.html)
|
|
- [:simple-apple: macOS](https://veracrypt.fr/en/Downloads.html)
|
|
- [:simple-linux: Linux](https://veracrypt.fr/en/Downloads.html)
|
|
|
|
</details>
|
|
|
|
</div>
|
|
|
|
VeraCrypt is a fork of the discontinued TrueCrypt project. According to its developers, security improvements have been implemented and issues raised by the initial TrueCrypt code audit have been addressed.
|
|
|
|
When encrypting with VeraCrypt, you have the option to select from different [hash functions](https://en.wikipedia.org/wiki/VeraCrypt#Encryption_scheme). We suggest you **only** select [SHA-512](https://en.wikipedia.org/wiki/SHA-512) and stick to the [AES](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard) block cipher.
|
|
|
|
TrueCrypt has been [audited a number of times](https://en.wikipedia.org/wiki/TrueCrypt#Security_audits), and VeraCrypt has also been [audited separately](https://en.wikipedia.org/wiki/VeraCrypt#VeraCrypt_audit).
|
|
|
|
## Operating System Encryption
|
|
|
|
<small>Protects against the following threat(s):</small>
|
|
|
|
- [:material-target-account: 표적 공격(Targeted Attacks)](basics/common-threats.md#attacks-against-specific-individuals ""){.pg-red}
|
|
|
|
Built-in OS encryption solutions generally leverage hardware security features such as a [secure cryptoprocessor](basics/hardware.md#tpmsecure-cryptoprocessor). Therefore, we recommend using the built-in encryption solutions for your operating system. For cross-platform encryption, we still recommend [cross-platform tools](#multi-platform) for additional flexibility and to avoid vendor lock-in.
|
|
|
|
### BitLocker
|
|
|
|
<div class="admonition recommendation" markdown>
|
|
|
|
{ align=right }
|
|
|
|
**BitLocker** is the full volume encryption solution bundled with Microsoft Windows that uses the Trusted Platform Module ([TPM](https://learn.microsoft.com/windows/security/information-protection/tpm/how-windows-uses-the-tpm)) for hardware-based security.
|
|
|
|
[:octicons-info-16:](https://learn.microsoft.com/windows/security/information-protection/BitLocker/BitLocker-overview){ .card-link title="Documentation" }
|
|
|
|
</details>
|
|
|
|
</div>
|
|
|
|
BitLocker is [officially supported](https://support.microsoft.com/windows/turn-on-device-encryption-0c453637-bc88-5f74-5105-741561aae838) on the Pro, Enterprise, and Education editions of Windows. It can be enabled on Home editions provided that they meet the following prerequisites.
|
|
|
|
<details class="example" markdown>
|
|
<summary>Enabling BitLocker on Windows Home</summary>
|
|
|
|
To enable BitLocker on "Home" editions of Windows, you must have partitions formatted with a [GUID Partition Table](https://en.wikipedia.org/wiki/GUID_Partition_Table) and have a dedicated TPM (v1.2, 2.0+) module. You may need to [disable the non-Bitlocker "Device encryption" functionality](https://discuss.privacyguides.net/t/enabling-bitlocker-on-the-windows-11-home-edition/13303/5) (which is inferior because it sends your recovery key to Microsoft's servers) if it is enabled on your device already before following this guide.
|
|
|
|
1. Open a command prompt and check your drive's partition table format with the following command. You should see "**GPT**" listed under "Partition Style":
|
|
|
|
```powershell
|
|
powershell Get-Disk
|
|
```
|
|
|
|
2. Run this command (in an admin command prompt) to check your TPM version. You should see `2.0` or `1.2` listed next to `SpecVersion`:
|
|
|
|
```powershell
|
|
powershell Get-WmiObject -Namespace "root/cimv2/security/microsofttpm" -Class WIN32_tpm
|
|
```
|
|
|
|
3. Access [Advanced Startup Options](https://support.microsoft.com/windows/advanced-startup-options-including-safe-mode-b90e7808-80b5-a291-d4b8-1a1af602b617). You need to reboot while pressing the F8 key before Windows starts and go into the *command prompt* in **Troubleshoot** → **Advanced Options** → **Command Prompt**.
|
|
4. Login with your admin account and type this in the command prompt to start encryption:
|
|
|
|
```powershell
|
|
manage-bde -on c: -used
|
|
```
|
|
|
|
5. Close the command prompt and continue booting to regular Windows.
|
|
6. Open an admin command prompt and run the following commands:
|
|
|
|
```powershell
|
|
manage-bde c: -protectors -add -rp -tpm
|
|
manage-bde -protectors -enable c:
|
|
manage-bde -protectors -get c: > %UserProfile%\Desktop\BitLocker-Recovery-Key.txt
|
|
```
|
|
|
|
<div class="admonition tip" markdown>
|
|
<p class="admonition-title">Tip</p>
|
|
|
|
데스크톱의 `BitLocker-Recovery-Key.txt`를 별도 저장 장치에 백업하세요. 해당 복구 코드를 분실하면 데이터를 잃어버리게 될 수 있습니다.
|
|
|
|
</div>
|
|
|
|
</details>
|
|
|
|
### FileVault
|
|
|
|
<div class="admonition recommendation" markdown>
|
|
|
|
{ align=right }
|
|
|
|
**FileVault**는 macOS에 기본 내장된, 즉시 사용 가능한 볼륨 암호화 솔루션입니다. FileVault takes advantage of the [hardware security capabilities](os/macos-overview.md#hardware-security) present on an Apple Silicon SoC or T2 Security Chip.
|
|
|
|
[:octicons-info-16:](https://support.apple.com/guide/mac-help/encrypt-mac-data-with-filevault-mh11785/mac){ .card-link title="Documentation" }
|
|
|
|
</details>
|
|
|
|
</div>
|
|
|
|
We advise against using your iCloud account for recovery; instead, you should securely store a local recovery key on a separate storage device.
|
|
|
|
### Linux Unified Key Setup
|
|
|
|
<div class="admonition recommendation" markdown>
|
|
|
|
{ align=right }
|
|
|
|
**LUKS**는 Linux에서 기본으로 사용하는 FDE 방식입니다. 전체 볼륨, 파티션을 암호화하거나 암호화 컨테이너를 만들 수 있습니다.
|
|
|
|
[:octicons-repo-16: Repository](https://gitlab.com/cryptsetup/cryptsetup#what-the-){ .md-button .md-button--primary }
|
|
[:octicons-info-16:](https://gitlab.com/cryptsetup/cryptsetup/-/wikis/home){ .card-link title="Documentation" }
|
|
[:octicons-code-16:](https://gitlab.com/cryptsetup/cryptsetup){ .card-link title="Source Code" }
|
|
|
|
</details>
|
|
|
|
</div>
|
|
|
|
<details class="example" markdown>
|
|
<summary>Creating and opening encrypted containers</summary>
|
|
|
|
```bash
|
|
dd if=/dev/urandom of=/path-to-file bs=1M count=1024 status=progress
|
|
sudo cryptsetup luksFormat /path-to-file
|
|
```
|
|
|
|
#### Opening encrypted containers
|
|
|
|
We recommend opening containers and volumes with `udisksctl` as this uses [Polkit](https://en.wikipedia.org/wiki/Polkit). Most file managers, such as those included with popular desktop environments, can unlock encrypted files. Tools like [udiskie](https://github.com/coldfix/udiskie) can run in the system tray and provide a helpful user interface.
|
|
|
|
```bash
|
|
udisksctl loop-setup -f /path-to-file
|
|
udisksctl unlock -b /dev/loop0
|
|
```
|
|
|
|
</details>
|
|
|
|
<div class="admonition note" markdown>
|
|
<p class="admonition-title">Remember to back up volume headers</p>
|
|
|
|
We recommend you always [back up your LUKS headers](https://wiki.archlinux.org/title/Dm-crypt/Device_encryption#Backup_and_restore) in case of partial drive failure. This can be done with:
|
|
|
|
```bash
|
|
cryptsetup luksHeaderBackup /dev/device --header-backup-file /mnt/backup/file.img
|
|
```
|
|
|
|
</div>
|
|
|
|
## 커맨드라인
|
|
|
|
<small>Protects against the following threat(s):</small>
|
|
|
|
- [:material-target-account: 표적 공격(Targeted Attacks)](basics/common-threats.md#attacks-against-specific-individuals ""){.pg-red}
|
|
|
|
커맨드라인 인터페이스가 존재하는 툴은 [Shell 스크립트](https://ko.wikipedia.org/wiki/%EC%85%B8_%EC%8A%A4%ED%81%AC%EB%A6%BD%ED%8A%B8)에 통합하는 용도로 유용합니다.
|
|
|
|
### Kryptor
|
|
|
|
<div class="admonition recommendation" markdown>
|
|
|
|
{ align=right }
|
|
|
|
**Kryptor**는 현대적이고 안전한 암호화 알고리즘을 사용하는 무료 오픈 소스 툴로, 파일 암호화 및 서명 기능을 제공합니다. It aims to be a better version of [age](https://github.com/FiloSottile/age) and [Minisign](https://jedisct1.github.io/minisign) to provide a simple, easier alternative to GPG.
|
|
|
|
[:octicons-home-16: Homepage](https://kryptor.co.uk){ .md-button .md-button--primary }
|
|
[:octicons-eye-16:](https://kryptor.co.uk/features#privacy){ .card-link title="Privacy Policy" }
|
|
[:octicons-info-16:](https://kryptor.co.uk/tutorial){ .card-link title="Documentation" }
|
|
[:octicons-code-16:](https://github.com/samuel-lucas6/Kryptor){ .card-link title="Source Code" }
|
|
[:octicons-heart-16:](https://kryptor.co.uk/#donate){ .card-link title="Contribute" }
|
|
|
|
<details class="downloads" markdown>
|
|
<summary>Downloads</summary>
|
|
|
|
- [:fontawesome-brands-windows: Windows](https://kryptor.co.uk)
|
|
- [:simple-apple: macOS](https://kryptor.co.uk)
|
|
- [:simple-linux: Linux](https://kryptor.co.uk)
|
|
|
|
</details>
|
|
|
|
</div>
|
|
|
|
### Tomb
|
|
|
|
<div class="admonition recommendation" markdown>
|
|
|
|
{ align=right }
|
|
|
|
**Tomb**는 LUKS의 커맨드라인 Shell 래퍼(Wrapper)입니다. It supports steganography via [third-party tools](https://dyne.org/software/tomb/#advanced-usage).
|
|
|
|
[:octicons-home-16: Homepage](https://dyne.org/software/tomb){ .md-button .md-button--primary }
|
|
[:octicons-info-16:](https://github.com/dyne/Tomb/wiki){ .card-link title="Documentation" }
|
|
[:octicons-code-16:](https://github.com/dyne/Tomb){ .card-link title="Source Code" }
|
|
[:octicons-heart-16:](https://dyne.org/donate){ .card-link title="Contribute" }
|
|
|
|
</details>
|
|
|
|
</div>
|
|
|
|
## OpenPGP
|
|
|
|
<small>Protects against the following threat(s):</small>
|
|
|
|
- [:material-target-account: 표적 공격(Targeted Attacks)](basics/common-threats.md#attacks-against-specific-individuals ""){.pg-red}
|
|
- [:material-bug-outline: 수동적 공격(Passive Attacks)](basics/common-threats.md#security-and-privacy ""){.pg-orange}
|
|
- [:material-server-network: 서비스 제공자/제공 업체(Service Providers)](basics/common-threats.md#privacy-from-service-providers ""){.pg-teal}
|
|
|
|
OpenPGP is sometimes needed for specific tasks such as digitally signing and encrypting email. PGP has many features and is [complex](https://latacora.micro.blog/2019/07/16/the-pgp-problem.html) as it has been around a long time. For tasks such as signing or encrypting files, we suggest the above options.
|
|
|
|
When encrypting with PGP, you have the option to configure different options in your `gpg.conf` file. We recommend staying with the standard options specified in the [GnuPG user FAQ](https://gnupg.org/faq/gnupg-faq.html#new_user_gpg_conf).
|
|
|
|
<div class="admonition tip" markdown>
|
|
<p class="admonition-title">Use future defaults when generating a key</p>
|
|
|
|
When [generating keys](https://gnupg.org/gph/en/manual/c14.html) we suggest using the `future-default` command as this will instruct GnuPG use modern cryptography such as [Curve25519](https://en.wikipedia.org/wiki/Curve25519#History) and [Ed25519](https://ed25519.cr.yp.to):
|
|
|
|
```bash
|
|
gpg --quick-gen-key alice@example.com future-default
|
|
```
|
|
|
|
</div>
|
|
|
|
### GNU Privacy Guard
|
|
|
|
<div class="admonition recommendation" markdown>
|
|
|
|
{ align=right }
|
|
|
|
**GnuPG** is a GPL-licensed alternative to the PGP suite of cryptographic software. GnuPG is compliant with [RFC 4880](https://tools.ietf.org/html/rfc4880), which is the current IETF specification of OpenPGP. The GnuPG project has been working on an [updated draft](https://datatracker.ietf.org/doc/draft-ietf-openpgp-crypto-refresh) in an attempt to modernize OpenPGP. GnuPG is a part of the Free Software Foundation's GNU software project and has received major [funding](https://gnupg.org/blog/20220102-a-new-future-for-gnupg.html) from the German government.
|
|
|
|
[:octicons-home-16: Homepage](https://gnupg.org){ .md-button .md-button--primary }
|
|
[:octicons-eye-16:](https://gnupg.org/privacy-policy.html){ .card-link title="Privacy Policy" }
|
|
[:octicons-info-16:](https://gnupg.org/documentation/index.html){ .card-link title="Documentation" }
|
|
[:octicons-code-16:](https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git){ .card-link title="Source Code" }
|
|
|
|
<details class="downloads" markdown>
|
|
<summary>Downloads</summary>
|
|
|
|
- [:simple-googleplay: Google Play](https://play.google.com/store/apps/details?id=org.sufficientlysecure.keychain)
|
|
- [:fontawesome-brands-windows: Windows](https://gpg4win.org/download.html)
|
|
- [:simple-apple: macOS](https://gpgtools.org)
|
|
- [:simple-linux: Linux](https://gnupg.org/download/index.html#binary)
|
|
|
|
</details>
|
|
|
|
</div>
|
|
|
|
### GPG4win
|
|
|
|
<div class="admonition recommendation" markdown>
|
|
|
|
{ align=right }
|
|
|
|
**GPG4win** is a package for Windows from [Intevation and g10 Code](https://gpg4win.org/impressum.html). It includes [various tools](https://gpg4win.org/about.html) that can assist you in using GPG on Microsoft Windows. The project was initiated and originally [funded by](https://web.archive.org/web/20190425125223/https://joinup.ec.europa.eu/news/government-used-cryptography) Germany's Federal Office for Information Security (BSI) in 2005.
|
|
|
|
[:octicons-home-16: Homepage](https://gpg4win.org){ .md-button .md-button--primary }
|
|
[:octicons-eye-16:](https://gpg4win.org/privacy-policy.html){ .card-link title="Privacy Policy" }
|
|
[:octicons-info-16:](https://gpg4win.org/documentation.html){ .card-link title="Documentation" }
|
|
[:octicons-code-16:](https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpg4win.git;a=summary){ .card-link title="Source Code" }
|
|
[:octicons-heart-16:](https://gpg4win.org/donate.html){ .card-link title="Contribute" }
|
|
|
|
<details class="downloads" markdown>
|
|
<summary>Downloads</summary>
|
|
|
|
- [:fontawesome-brands-windows: Windows](https://gpg4win.org/download.html)
|
|
|
|
</details>
|
|
|
|
</div>
|
|
|
|
### GPG Suite
|
|
|
|
<div class="admonition recommendation" markdown>
|
|
|
|
{ align=right }
|
|
|
|
**GPG Suite** provides OpenPGP support for [Apple Mail](email-clients.md#apple-mail-macos) and other email clients on macOS.
|
|
|
|
We recommend taking a look at their [First steps](https://gpgtools.tenderapp.com/kb/how-to/first-steps-where-do-i-start-where-do-i-begin-setup-gpgtools-create-a-new-key-your-first-encrypted-email) and [Knowledge Base](https://gpgtools.tenderapp.com/kb) for support.
|
|
|
|
[:octicons-home-16: Homepage](https://gpgtools.org){ .md-button .md-button--primary }
|
|
[:octicons-eye-16:](https://gpgtools.org/privacy){ .card-link title="Privacy Policy" }
|
|
[:octicons-info-16:](https://gpgtools.tenderapp.com/kb){ .card-link title="Documentation" }
|
|
[:octicons-code-16:](https://github.com/GPGTools){ .card-link title="Source Code" }
|
|
|
|
<details class="downloads" markdown>
|
|
<summary>Downloads</summary>
|
|
|
|
- [:simple-apple: macOS](https://gpgtools.org)
|
|
|
|
</details>
|
|
|
|
</div>
|
|
|
|
Currently, GPG Suite does [not yet](https://gpgtools.com/sequoia) have a stable release for macOS Sonoma and later.
|
|
|
|
### OpenKeychain
|
|
|
|
<div class="admonition recommendation" markdown>
|
|
|
|
{ align=right }
|
|
|
|
**OpenKeychain** is an implementation of GnuPG for Android. It's commonly required by mail clients such as [Thunderbird](email-clients.md#thunderbird), [FairEmail](email-clients.md#fairemail-android), and other Android apps to provide encryption support.
|
|
|
|
[:octicons-home-16: Homepage](https://openkeychain.org){ .md-button .md-button--primary }
|
|
[:octicons-eye-16:](https://openkeychain.org/help/privacy-policy){ .card-link title="Privacy Policy" }
|
|
[:octicons-info-16:](https://openkeychain.org/faq){ .card-link title="Documentation" }
|
|
[:octicons-code-16:](https://github.com/open-keychain/open-keychain){ .card-link title="Source Code" }
|
|
|
|
<details class="downloads" markdown>
|
|
<summary>Downloads</summary>
|
|
|
|
- [:simple-googleplay: Google Play](https://play.google.com/store/apps/details?id=org.sufficientlysecure.keychain)
|
|
|
|
</details>
|
|
|
|
</div>
|
|
|
|
Cure53 completed a [security audit](https://openkeychain.org/openkeychain-3-6) of OpenKeychain 3.6 in October 2015. The published audit and OpenKeychain's solutions to the issues raised in the audit can be found [here](https://github.com/open-keychain/open-keychain/wiki/cure53-Security-Audit-2015).
|
|
|
|
## 평가 기준
|
|
|
|
**Privacy Guides는 권장 목록의 어떠한 프로젝트와도 제휴를 맺지 않았습니다.** 객관적인 권장 목록을 제공하기 위해, [일반적인 평가 기준](about/criteria.md)에 더해 명확한 요구 사항을 정립하였습니다. 어떠한 프로젝트를 선택해 사용하기 전에, 이러한 요구 사항들을 숙지하고 여러분 스스로 조사하는 과정을 거쳐 적절한 선택을 하시기 바랍니다.
|
|
|
|
### 최소 요구 사항
|
|
|
|
- Cross-platform encryption apps must be open source.
|
|
- File encryption apps must support decryption on Linux, macOS, and Windows.
|
|
- External disk encryption apps must support decryption on Linux, macOS, and Windows.
|
|
- Internal (OS) disk encryption apps must be cross-platform or built in to the operating system natively.
|
|
|
|
### 우대 사항
|
|
|
|
평가 기준에서 '우대 사항'은 해당 부문에서 완벽한 프로젝트에 기대하는 바를 나타냅니다. 다음의 우대 사항에 해당하지 않더라도 권장 목록에 포함될 수 있습니다. 단, 우대 사항에 해당할수록 이 페이지의 다른 항목보다 높은 순위를 갖습니다.
|
|
|
|
- Operating System (FDE) encryption apps should utilize hardware security such as a TPM or Secure Enclave.
|
|
- File encryption apps should have first- or third-party support for mobile platforms.
|