All Projects → samuel-lucas6 → Kryptor

samuel-lucas6 / Kryptor

Licence: GPL-3.0 license
A simple, modern, and secure encryption and signing tool that aims to be a better version of age and Minisign.

Programming Languages

C#
18002 projects

Projects that are alternatives of or similar to Kryptor

Halite
High-level cryptography interface powered by libsodium
Stars: ✭ 933 (+249.44%)
Mutual labels:  argon2, libsodium, ed25519, curve25519
Sodium compat
Pure PHP polyfill for ext/sodium
Stars: ✭ 736 (+175.66%)
Mutual labels:  libsodium, ed25519, curve25519
rawr-x3dh
TypeScript Implementation of X3DH
Stars: ✭ 51 (-80.9%)
Mutual labels:  libsodium, ed25519, x25519
Tweetnacl Js
Port of TweetNaCl cryptographic library to JavaScript
Stars: ✭ 1,176 (+340.45%)
Mutual labels:  libsodium, ed25519, curve25519
Nsec
A modern and easy-to-use cryptographic library for .NET Core based on libsodium
Stars: ✭ 217 (-18.73%)
Mutual labels:  libsodium, ed25519, curve25519
noble-ed25519
Fastest JS implementation of ed25519, x25519 & ristretto255. Independently audited, high-security, 0-dependency EDDSA signatures and ECDH key agreement
Stars: ✭ 220 (-17.6%)
Mutual labels:  ed25519, curve25519, x25519
Ed25519 Dalek
Fast and efficient ed25519 signing and verification in Rust.
Stars: ✭ 383 (+43.45%)
Mutual labels:  signing, ed25519, curve25519
Cryptography-Guidelines
Guidance on implementing cryptography as a developer.
Stars: ✭ 15 (-94.38%)
Mutual labels:  ed25519, x25519, blake2b
cryptopocket
🔐 Encrypt anything, then Decrypt by providing a required key.
Stars: ✭ 22 (-91.76%)
Mutual labels:  signing, portable, file-encryption
Signatory
Multi-provider digital signature library for Rust
Stars: ✭ 136 (-49.06%)
Mutual labels:  libsodium, ed25519
lazysodium-java
A Java implementation of the Libsodium crypto library. For the lazy dev.
Stars: ✭ 110 (-58.8%)
Mutual labels:  argon2, libsodium
Globaleaks
GlobaLeaks is free, open source software enabling anyone to easily set up and maintain a secure whistleblowing platform.
Stars: ✭ 832 (+211.61%)
Mutual labels:  argon2, libsodium
Rbnacl
Ruby FFI binding to the Networking and Cryptography (NaCl) library (a.k.a. libsodium)
Stars: ✭ 910 (+240.82%)
Mutual labels:  libsodium, ed25519
Lazysodium Android
An Android implementation of the Libsodium cryptography library. For the lazy dev.
Stars: ✭ 69 (-74.16%)
Mutual labels:  argon2, libsodium
httpsig
Golang implementation of the HTTP Signatures RFC draft, with SSH support!
Stars: ✭ 58 (-78.28%)
Mutual labels:  signing, signatures
yubihsm-rs
Pure Rust client for YubiHSM2 devices
Stars: ✭ 70 (-73.78%)
Mutual labels:  ed25519, digital-signatures
libsodium-xchacha20-siv
Deterministic/nonce-reuse resistant authenticated encryption scheme using XChaCha20, implemented on libsodium.
Stars: ✭ 25 (-90.64%)
Mutual labels:  libsodium, xchacha20
Jwt
Go JWT signing, verifying and validating
Stars: ✭ 394 (+47.57%)
Mutual labels:  signing, ed25519
sodalite
tweetnacl in rust
Stars: ✭ 26 (-90.26%)
Mutual labels:  libsodium, ed25519
Sigtool
Ed25519 signing, verification and encryption, decryption for arbitary files; like OpenBSD signifiy but with more functionality and written in Golang - only easier and simpler
Stars: ✭ 49 (-81.65%)
Mutual labels:  ed25519, curve25519

License: GPLv3 CodeQL Specification

Kryptor

Kryptor is a simple, modern, and secure file encryption and signing tool for Windows, Linux, and macOS.

It aims to be a better version of age and Minisign to provide a leaner, user friendly alternative to GPG.

kryptor

Features

  • The latest and greatest cryptographic primitives, with no config options.
  • Encrypt multiple files/directories with a password, symmetric key, or asymmetric keys.
  • Encrypt to multiple recipients for sender authenticated, one-way file sharing.
  • Encrypted files are indistinguishable from random. File names can also be encrypted.
  • Create and verify digital signatures, with support for an authenticated comment and prehashing.
  • Small public keys. Private keys are encrypted for protection at rest.
  • UNIX style password entry and random passphrase generation.
  • Pre-shared keys can be used for post-quantum secure key exchange.

For more information, please go to kryptor.co.uk.

Usage

If you're just getting started, check out the tutorial instead.

Usage: kryptor [options] <file>

Arguments:
  file            specify a file/directory path

Options:
  -e|--encrypt    encrypt files/directories
  -d|--decrypt    decrypt files/directories
  -p|--password   specify a password (empty for interactive entry)
  -k|--key        specify or randomly generate a symmetric key or keyfile
  -x|--private    specify your private key (unused or empty for default key)
  -y|--public     specify a public key
  -n|--names      encrypt file/directory names
  -o|--overwrite  overwrite files
  -g|--generate   generate a new key pair
  -r|--recover    recover your public key from your private key
  -s|--sign       create a signature
  -c|--comment    add a comment to a signature
  -l|--prehash    sign large files by prehashing
  -v|--verify     verify a signature
  -t|--signature  specify a signature file (unused for default name)
  -u|--update     check for updates
  -a|--about      view the program version and license
  -h|--help       show help information

Examples:
  --encrypt [file]
  --encrypt -p [file]
  --encrypt [-y recipient's public key] [file]
  --decrypt [-y sender's public key] [file]
  --sign [-c comment] [file]
  --verify [-y public key] [file]

Specifying files

When referencing file names/paths that contain spaces, you must surround them with "speech marks":

$ kryptor -e -p "GitHub Logo.png"
$ kryptor -e -p "C:\Users\samuel-lucas6\Downloads\GitHub Logo.png"

Files in the same directory as the kryptor executable can be specified using their file name:

$ kryptor -e -p file.txt

However, files that aren't in the same directory must be specified using a file path:

$ kryptor -e -p C:\Users\samuel-lucas6\Documents\file.txt

Multiple files and/or directories can be specified at once:

$ kryptor -e file1.txt file2.jpg file3.mp4 Photos Videos

Specifying your private key

You can perform encryption, decryption, and signing with your default private key as follows:

$ kryptor -e file.txt
$ kryptor -d file.txt.bin
$ kryptor -s file.txt

This is the recommended approach, but it means your private keys must be kept in the default folder, which varies depending on your operating system:

  • Windows: %USERPROFILE%/.kryptor
  • Linux: /home/.kryptor
  • macOS: /Users/USERNAME/.kryptor

To specify a private key for -r|--recover or a private key not stored in the default folder, you must use the -x|--private option followed by :[file] like so:

$ kryptor -r -x:"C:\Users\samuel-lucas6\Documents\encryption.private"
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].