mirror of
https://github.com/privacyguides/privacyguides.org.git
synced 2024-12-20 13:24:35 -05:00
9d05fe7cb2
Signed-off-by: fria <138676274+friadev@users.noreply.github.com> Signed-off-by: Daniel Gray <dngray@privacyguides.org>
440 lines
23 KiB
Markdown
440 lines
23 KiB
Markdown
---
|
|
meta_title: "Recommended Encryption Software: VeraCrypt, Cryptomator, PicoCrypt, and OpenPGP - Privacy Guides"
|
|
title: "Encryption Software"
|
|
icon: material/file-lock
|
|
description: Encryption of data is the only way to control who can access it. 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 (Cloud)
|
|
|
|
<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. It allows you to create vaults that are stored on a virtual drive, the contents of which are encrypted and synced with your cloud storage provider.
|
|
|
|
[: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.
|
|
|
|
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 (File)
|
|
|
|
<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){ .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 (Disk)
|
|
|
|
<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>
|
|
|
|
Backup `BitLocker-Recovery-Key.txt` on your Desktop to a separate storage device. Loss of this recovery code may result in loss of data.
|
|
|
|
</div>
|
|
|
|
</details>
|
|
|
|
### FileVault
|
|
|
|
<div class="admonition recommendation" markdown>
|
|
|
|
{ align=right }
|
|
|
|
**FileVault** is the on-the-fly volume encryption solution built into 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** is the default FDE method for Linux. It can be used to encrypt full volumes, partitions, or create encrypted containers.
|
|
|
|
[:octicons-home-16: Homepage](https://gitlab.com/cryptsetup/cryptsetup/-/blob/main/README.md){ .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>
|
|
|
|
## Command-line
|
|
|
|
<small>Protects against the following threat(s):</small>
|
|
|
|
- [:material-target-account: Targeted Attacks](basics/common-threats.md#attacks-against-specific-individuals){ .pg-red }
|
|
|
|
Tools with command-line interfaces are useful for integrating [shell scripts](https://en.wikipedia.org/wiki/Shell_script).
|
|
|
|
### Kryptor
|
|
|
|
<div class="admonition recommendation" markdown>
|
|
|
|
{ align=right }
|
|
|
|
**Kryptor** is a free and open-source file encryption and signing tool that makes use of modern and secure cryptographic algorithms. 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** is a command-line shell wrapper for LUKS. 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 note" markdown>
|
|
<p class="admonition-title">Note</p>
|
|
|
|
We suggest [Canary Mail](email-clients.md#canary-mail-ios) for using PGP with email on iOS devices.
|
|
|
|
</div>
|
|
|
|
<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).
|
|
|
|
## Criteria
|
|
|
|
**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.
|
|
|
|
### Minimum Qualifications
|
|
|
|
- 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.
|
|
|
|
### Best-Case
|
|
|
|
Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page.
|
|
|
|
- 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.
|