rage is a simple, modern, and secure file encryption tool, using the age format


rage: Rust implementation of age

rage is a simple, modern, and secure file encryption tool, using the age format. It features small explicit keys, no config options, and UNIX-style composability.

The format specification is at age-encryption.org/v1. To discuss the spec or other age related topics, please email the mailing list at [email protected]. age was designed by @Benjojo12 and @FiloSottile.

The reference interoperable Go implementation is available at filippo.io/age.


  rage [--encrypt] -r RECIPIENT [-i IDENTITY] [-a] [-o OUTPUT] [INPUT]
  rage --decrypt [-i IDENTITY] [-o OUTPUT] [INPUT]

Positional arguments:
  INPUT                       Path to a file to read from.

Optional arguments:
  -h, --help                  Print this help message and exit.
  -V, --version               Print version info and exit.
  -e, --encrypt               Encrypt the input (the default).
  -d, --decrypt               Decrypt the input.
  -p, --passphrase            Encrypt with a passphrase instead of recipients.
  --max-work-factor WF        Maximum work factor to allow for passphrase decryption.
  -a, --armor                 Encrypt to a PEM encoded format.
  -r, --recipient RECIPIENT   Encrypt to the specified RECIPIENT. May be repeated.
  -R, --recipients-file PATH  Encrypt to the recipients listed at PATH. May be repeated.
  -i, --identity IDENTITY     Use the identity file at IDENTITY. May be repeated.
  -o, --output OUTPUT         Write the result to the file at path OUTPUT.

INPUT defaults to standard input, and OUTPUT defaults to standard output.

- An age public key, as generated by rage-keygen ("age1...").
- An SSH public key ("ssh-ed25519 AAAA...", "ssh-rsa AAAA...").

PATH is a path to a file containing age recipients, one per line
(ignoring "#" prefixed comments and empty lines).

IDENTITY is a path to a file with age identities, one per line
(ignoring "#" prefixed comments and empty lines), or to an SSH key file.
Passphrase-encrypted age identity files can be used as identity files.
Multiple identities may be provided, and any unused ones will be ignored.

Multiple recipients

Files can be encrypted to multiple recipients by repeating -r/--recipient. Every recipient will be able to decrypt the file.

$ rage -o example.png.age -r age1uvscypafkkxt6u2gkguxet62cenfmnpc0smzzlyun0lzszfatawq4kvf2u \
    -r age1ex4ty8ppg02555at009uwu5vlk5686k3f23e7mac9z093uvzfp8sxr5jum example.png

Recipient files

Multiple recipients can also be listed one per line in one or more files passed with the -R/--recipients-file flag.

$ cat recipients.txt
# Alice
# Bob
$ rage -R recipients.txt example.jpg > example.jpg.age


Files can be encrypted with a passphrase by using -p/--passphrase. By default rage will automatically generate a secure passphrase.

$ rage -p -o example.png.age example.png
Type passphrase (leave empty to autogenerate a secure one): [hidden]
Using an autogenerated passphrase:
$ rage -d example.png.age >example.png
Type passphrase: [hidden]

Passphrase-protected identity files

If an identity file passed to -i/--identity is a passphrase-encrypted age file, it will be automatically decrypted.

$ rage -p -o key.age <(rage-keygen)
Public key: age1pymw5hyr39qyuc950tget63aq8vfd52dclj8x7xhm08g6ad86dkserumnz
Type passphrase (leave empty to autogenerate a secure one): [hidden]
Using an autogenerated passphrase:
$ rage -r age1pymw5hyr39qyuc950tget63aq8vfd52dclj8x7xhm08g6ad86dkserumnz secrets.txt > secrets.txt.age
$ rage -d -i key.age secrets.txt.age > secrets.txt
Type passphrase: [hidden]

Passphrase-protected identity files are not necessary for most use cases, where access to the encrypted identity file implies access to the whole system. However, they can be useful if the identity file is stored remotely.

SSH keys

As a convenience feature, rage also supports encrypting to ssh-rsa and ssh-ed25519 SSH public keys, and decrypting with the respective private key file. (ssh-agent is not supported.)

$ rage -R ~/.ssh/id_ed25519.pub example.png > example.png.age
$ rage -d -i ~/.ssh/id_ed25519 example.png.age > example.png

Note that SSH key support employs more complex cryptography, and embeds a public key tag in the encrypted file, making it possible to track files that are encrypted to a specific public key.


On macOS or Linux, you can use Homebrew:

brew tap str4d.xyz/rage https://str4d.xyz/rage
brew install rage

On Windows, Linux, and macOS, you can use the pre-built binaries.

If your system has Rust 1.51+ installed (either via rustup or a system package), you can build directly from source:

cargo install rage

Note: previously the rage suite of tools was provided in the age Rust crate. This is no longer the case; age now only contains the Rust library.

Help from new packagers is very welcome.

Feature flags

  • mount enables the rage-mount tool, which can mount age-encrypted TAR or ZIP archives as read-only. It is currently only usable on Unix systems, as it relies on libfuse.

  • ssh (enabled by default) enables support for reusing existing SSH key files for age encryption.

  • unstable enables in-development functionality. Anything behind this feature flag has no stability or interoperability guarantees.


Licensed under either of

at your option.


Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

  • rage-mount: update dependencies fuse_mt, time and zip

    rage-mount: update dependencies fuse_mt, time and zip

    I picked the first commit of fuse_mt that switched from using fuse to fuser (fuse_mt hasn't had any new releases since 0.5.1). That way rage-mount can be built against libfuse3. time and zip dependencies update is a side effect due to TimeSpec being obsolete.

    WARNING: I've never written any Rust code before, so please bear with my ignorance in the PR.

    opened by FollieHiyuki 16
  • Unicode feast in time of COVID19 plague

    Unicode feast in time of COVID19 plague

    Windows 7, rage 0.5.1

    [?] marks are related neither to the chosen console font, nor to the code page (866, 1251, 65001). 0.4.0 was the last one w/o them. Consider figuring out who’s responsible for this freaking decoration.

    opened by sergeevabc 12
  • YubiKey plugin

    YubiKey plugin

    Discuss this draft on the age-dev mailing list thread!

    Current draft specification:

    age PIV identities use ECC P-256 keys, generated on the hardware token, with certificates that never expire.

    For hardware tokens that support PIN and/or touch policies (such as YubiKeys), the default PIN policy is "once per session", and the default touch policy is "every decryption".

    A PIV recipient has the following form:

    Bech32("age1piv", SEC-1-C(public key))

    where SEC-1-C is the 33-byte compressed SEC-1 encoding.

    A PIV recipient line is of the form:

    -> piv encode(SHA-256(recipient)[:4]) encode(SEC-1-C(ECDH(ephemeral secret, p256-basepoint)))\n
    encode(encrypt[HKDF[salt, label](ECDH(ephemeral secret, public key))](file key))\n

    where ephemeral secret is a random scalar within the scalar field of P-256 and MUST be new for every file key, salt is SEC-1-C(ECDH(ephemeral secret, basepoint)) || SEC-1-C(public key), and label is age-encryption.org/v1/piv.

    A YubiKey "identity" is managed locally as a key stub with the following form:

    Uppercase(Bech32("age-yubikey-stub-", serial || slot || SHA-256(recipient)[:4]))

    The stub may exist in files alongside age X25519 secret keys, and is similarly passed to the age / rage binary with the -i flag.

    Note that the common tag in the recipient line and key stub means that recipients can trivially identify whether they can decrypt a particular recipient line, at the cost of making recipients linkable across different encrypted files.

    Usage example (responses out-of-date):

    $ cargo install --path . --features yubikey
    $ rage-keygen --yubikey -o keystub.txt
    Enter PIN for YubiKey with serial 12345678: [hidden]
    Use the up/down arrow keys to select a PIV slot (q to quit): Retired(R1) (Empty)
    Select a PIN policy: Once   (A PIN is required once per session, if set)
    Select a touch policy: Always (A physical touch is required for every decryption),
    Generate new key in Retired(R1) slot? yes
    $ cat keystub.txt 
    # created: 2019-12-07T23:13:09Z
    # yubikey:A_y2TWFFIZ8AhuFCjpxGzt_qiZrwMfEyDG6M8fqgG3ET
    $ echo "YubiKey FTW!" | rage -o test.age -r yubikey:A_y2TWFFIZ8AhuFCjpxGzt_qiZrwMfEyDG6M8fqgG3ET
    $ rage -d -i keystub.txt test.age
    Enter PIN for YubiKey with serial 12345678: [hidden]
    YubiKey FTW!
    opened by str4d 11
  • rage package naming

    rage package naming

    While wanting to package your rage program I realized package and binary name will probably conflict with Rage [0] that is already available in the target linux distribution as "rage".

    Do you know if others ran into this situation as well and how they solved it?

    Does this upstream project has preferences if and what alternative name I can use instead (rustage, ager, ...) ?

    Do you have experience/ideas what parts of the code have to be touched/changed downstream to use a different name than "rage"?

    Is it maintainable by replacing some strings programatically or are issues and new bugs likely if I have to change name, man pages, bash completetion, ... and propably more in order to make it work with a different name?

    Thank you for this software!

    [0] https://www.enlightenment.org/about-rage

    opened by cunyx 10
  • `cargo install rage` fails

    `cargo install rage` fails


    • OS: Linux
    • rage version: v0.5.0

    What were you trying to do

    What happened

       stable-x86_64-unknown-linux-gnu unchanged - rustc 1.49.0 (e1884a8e3 2020-12-29)
     $ cargo install rage
         Updating crates.io index
      Installing rage v0.5.0
     error[E0599]: no method named `insert_and_get` found for struct `DOMAINS` in the current scope
       --> /home/gw/.cargo/registry/src/github.com-1ecc6299db9ec823/i18n-embed-fl-0.2.0/src/lib.rs:360:17
    136 | / lazy_static::lazy_static! {
    137 | |     /// Cached data specific to each localization domain, to improve
    138 | |     /// performance of subsequent macro invokations.
    139 | |     static ref DOMAINS: dashmap::DashMap<String, DomainSpecificData> =
    140 | |         dashmap::DashMap::new();
    141 | | }
        | |_- method `insert_and_get` not found for this
    360 |           DOMAINS.insert_and_get(domain.clone(), data)
        |                   ^^^^^^^^^^^^^^ method not found in `DOMAINS`
    error: aborting due to previous error
    For more information about this error, try `rustc --explain E0599`.
    error: could not compile `i18n-embed-fl`
    To learn more, run the command again with --verbose.
    warning: build failed, waiting for other jobs to finish...
    error: failed to compile `rage v0.5.0`, intermediate artifacts can be found at `/tmp/cargo-installJwMnWy`
    Caused by:
      build failed
    opened by gwpl 10
  • Performance improvements

    Performance improvements

    The performance improvement comes from the upgraded chacha20 dependency. Performance is slightly improved by default, and compiling with RUSTFLAGS="-Ctarget-feature=+avx2" will boost performance significantly.

    Part of #57.

    opened by str4d 10
  • Link to musl instead of glibc for .deb files

    Link to musl instead of glibc for .deb files


    • OS: Debian stretch/buster
    • rage version: 0.6.0

    I recently set up an apt repo for Rust command line tools at https://apt.0xe.me, and I was hoping to add rage. However, to support the widest set of OS versions, linking to musl libc seems to give the best portability.

    Would you consider linking your .deb files to musl instead of glibc?

    Edit: See e.g. this ripgrep issue where linking to glibc was an issue: https://github.com/BurntSushi/ripgrep/issues/1890

    opened by ethanhs 9
  • Rage refuses to write to stdout even when armor is enabled

    Rage refuses to write to stdout even when armor is enabled

    PS C:\Users\Alice> rage -r age1wssqv0rf9ctp5w7j3dfmngurhe2xrj5869rv9x8a0gex5r0f6ejqy0prkw -a .\Desktop\age.txt
    Error: not printing to stdout
    [ Did rage not do what you expected? Could an error be more useful? ]
    [ Tell us: https://github.com/str4d/rage/issues/new/choose          ]
    opened by alajpie 7
  • Some questions about using

    Some questions about using

    Hi @str4d,

    Thanks for your great project. I have some questions during using rage.

    Why it spend almost same time for encrypting 100MB's video or 14KB's text file?

    I have use the crate made a test. The time is a second or so.

    Does passphrase support non-ASCII characters?

    Generally, we use ASCII characters to generate a passphrase. But I am curious if it has potential risk to use non-ASCII characters for a passphrase. I have tested with Chinese, it seems all right.

    opened by percy507 6
  • add Identity support for RSA PKCS#8 nocrypt

    add Identity support for RSA PKCS#8 nocrypt

    Hi @str4d,

    I realize that this feature is unlikely to see much use in practice, but I picked an old issue that seemed simple enough for a very new rustacean to be able to tackle (first real attempt at Rust).

    fully parse unencrypted PKCS#8 RSA private key

    parse encrypted PKCS#8 enough to recognize it as an unsupported key format

    add test coverage for key format support

    • PEM (PKCS#1) unencrypted RSA (supported)
    • PEM (PKCS#1) encrypted RSA (never support)
    • PKCS#8 unencrypted RSA (supported)
    • PKCS#8 encrypted (not supported, yet?)

    fixes #14

    opened by dwhjames 6
  • Add -j flag for invoking data-less plugins

    Add -j flag for invoking data-less plugins

    Some plugins (like yubikey-agent, or an sshpass equivalent) just need the user to inform rage that they exist and should be used, but not to actually pass any data across. A user can currently achieve this with an "empty plugin identity", which looks like:


    where name is the plugin name, and SIXCHR is the Bech32 checksum. This has two UX flaws:

    • The empty identity is a "magic string", that users need to know about in order to use these plugins.
    • It needs to go into a file (since -i only accepts files). For a user that only uses yubikey-agent this would mean having a loose file around with a single magic string, the location of which they need to remember.

    In a long UX discussion with @FiloSottile and @benjojo, we decided to add a new -j flag, which does this all for the user. When rage sees -j name, it internally behaves as if it had seen a -i file where the file contained AGE-PLUGIN-NAME-1SIXCHR (with valid checksum).

    This has a downstream effect on plugins: they can now distinguish a "default" behaviour. If a plugin only normally gives out plugin identities containing data, they can behave differently if they are sent (via the plugin protocol) an add-identity command with a known plugin name but empty data. This could be used to e.g. decrypt with a default set of identities, instead of a specific one.

    -j is intended to be handled in-line with -i for deterministic decryption (#236). For simplicity, rage will only support a single -j flag, and make it incompatible with -i flags.

    opened by str4d 6
  • Ensure Encryptor implements trait Send

    Ensure Encryptor implements trait Send

    By adding the Send trait as a requirement to the recipients vec, we gain the Send trait on Encryptor. This is useful for other async frameworks that require Send across await's.

    opened by alexgartrell 0
  • build(deps): bump codecov/codecov-action from 3.1.0 to 3.1.1

    build(deps): bump codecov/codecov-action from 3.1.0 to 3.1.1

    Bumps codecov/codecov-action from 3.1.0 to 3.1.1.

    Release notes

    Sourced from codecov/codecov-action's releases.


    What's Changed

    New Contributors

    Full Changelog: https://github.com/codecov/codecov-action/compare/v3.1.0...v3.1.1


    Sourced from codecov/codecov-action's changelog.



    • #661 Update deprecation warning
    • #593 Create codeql-analysis.yml
    • #712 README: fix typo
    • #725 fix: Remove a blank row
    • #726 Update README.md with correct badge version
    • #633 Create scorecards-analysis.yml
    • #747 fix: add more verbosity to validation
    • #750 Regenerate scorecards-analysis.yml
    • #774 Switch to v3
    • #783 Fix network entry in table
    • #791 Trim arguments after splitting them
    • #769 Plumb failCi into verification function.


    • #713 build(deps-dev): bump typescript from 4.6.3 to 4.6.4
    • #714 build(deps): bump node-fetch from 3.2.3 to 3.2.4
    • #724 build(deps): bump github/codeql-action from 1 to 2
    • #717 build(deps-dev): bump @​types/jest from 27.4.1 to 27.5.0
    • #729 build(deps-dev): bump @​types/node from 17.0.25 to 17.0.33
    • #734 build(deps-dev): downgrade @​types/node to 16.11.35
    • #723 build(deps): bump actions/checkout from 2 to 3
    • #733 build(deps): bump @​actions/github from 5.0.1 to 5.0.3
    • #732 build(deps): bump @​actions/core from 1.6.0 to 1.8.2
    • #737 build(deps-dev): bump @​types/node from 16.11.35 to 16.11.36
    • #749 build(deps): bump ossf/scorecard-action from 1.0.1 to 1.1.0
    • #755 build(deps-dev): bump typescript from 4.6.4 to 4.7.3
    • #759 build(deps-dev): bump @​types/node from 16.11.36 to 16.11.39
    • #762 build(deps-dev): bump @​types/node from 16.11.39 to 16.11.40
    • #746 build(deps-dev): bump @​vercel/ncc from 0.33.4 to 0.34.0
    • #757 build(deps): bump ossf/scorecard-action from 1.1.0 to 1.1.1
    • #760 build(deps): bump openpgp from 5.2.1 to 5.3.0
    • #748 build(deps): bump actions/upload-artifact from 2.3.1 to 3.1.0
    • #766 build(deps-dev): bump typescript from 4.7.3 to 4.7.4
    • #799 build(deps): bump openpgp from 5.3.0 to 5.4.0
    • #798 build(deps): bump @​actions/core from 1.8.2 to 1.9.1
    • d9f34f8 release: update changelog and version to 3.1.1 (#828)
    • 0e9e7b4 Plumb failCi into verification function. (#769)
    • 7f20bd4 build(deps): bump @​actions/core from 1.8.2 to 1.9.1 (#798)
    • 13bc253 build(deps): bump openpgp from 5.3.0 to 5.4.0 (#799)
    • 5c0da1b Trim arguments after splitting them (#791)
    • 68d5f6d Fix network entry in table (#783)
    • 2a829b9 Switch to v3 (#774)
    • 8e09eaf build(deps-dev): bump typescript from 4.7.3 to 4.7.4 (#766)
    • 39e2229 build(deps): bump actions/upload-artifact from 2.3.1 to 3.1.0 (#748)
    • b2b7703 build(deps): bump openpgp from 5.2.1 to 5.3.0 (#760)
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    opened by dependabot[bot] 1
  • Key/finger server for

    Key/finger server for


    I tried to reach out to @str4d on Twitter to discuss if there would be an interest in adding a key server to rage. We are adopting it in our small team and I have few ideas that I'm keen to bounce few ideas around that if you guys think that this endeavour is worthy to pursuit.

    Best, Yevhenii

    opened by lessless 0
  • UX: weird unknown gui pops up when using cli

    UX: weird unknown gui pops up when using cli

    What were you trying to do

    Encrypt a file with a passphrase

    What happened

    instead of prompting for my passphrase in the terminal like I expected from a cli tool, it opened a GUI prompt.

    Investigation shows this is related to something called pinentry, which has no way to be disabled except by making PATH empty? Which doesn't work, because.. then rage cant be found. Having to rewrite or construct a new PATH only pointing to rage, on the fly, or only use the absolute path, every time I want to use it, is just completely unacceptable.

    pinentry apparently lives in /usr/bin and is a transitive dependency of gnupg, which itself is a transitive dependency of pacman, meaning it will always exist on Arch, and likely many other linux distros, and I as a user have no control over this.

    More generally, rage is a command-line tool, and i do not expect such tools to open GUI windows unless explicitly told to, let alone ones from insecure legacy programs like gpg, and especially not when this behavior is documented nowhere, an open issue which has existed since 2021, #280.

    This is not the behavior I expected at all

    rage -p some_file -o some_file.age
    opened by DianaNites 0
  • UX: Streamlined API for the simplest use cases?

    UX: Streamlined API for the simplest use cases?

    We've been using and recommending age for a "small" use cases, like wrapping/unwrapping sensitive material, where there's only one X25519 or passphrase recipient and a tiny amount of data. This is very nice as the users of the software can easily be instructed to use the age CLI to prepare data, and nobody is rolling their own (combination of) crypto.

    For this, instead of using things like std::iter::once and the rest of the top-level example in https://docs.rs/age, it would be great to have simplified (not composable) high-level APIs directly in age itself.

    I imagine something like fn encrypt(recipient, plaintext: &[u8]) -> Result<Vec<u8>> and fn decrypt(identity, ciphertext) -> Result<Vec<u8>> as top-level library exports, with a few ergonomic additions to construct appropriate identities and recipients, so users can easily decrypt given a passphrase, or encrypt against say a SSH public key, etc.

    Is this in scope for the project or do you prefer to stick with the composable parts and let the user figure out how to combine them?

    opened by nickray 1
  • UX: non-existent identities aren't completely ignored

    UX: non-existent identities aren't completely ignored

    What were you trying to do / what happened

    $ rage --version
    rage 0.7.1
    $ rage -i /non-existent/path -i ~/.ssh/id_ed25519 -d secret.age
    Error: No such file or directory (os error 2)
    [ Did rage not do what you expected? Could an error be more useful? ]
    [ Tell us: https://str4d.xyz/rage/report 

    I was expecting that the non-existent path identity would be totally ignored because the private key path (~/.ssh/id_ed25519) exists and is able to decrypt the secret, instead it complains about not being able to open the non-existent path. I think this could be useful for situations where you want to have a fallback identity, or want to transition the location of an identity to a different path.

    opened by ryantm 1
  • v0.8.1(Jun 18, 2022)



    • Require age 0.8.1.



    • age::Decryptor did not previously require "contributory" behaviour for X25519 recipient stanzas. If an age file has an X25519 recipient stanza with an ephemeral share that is a small-order point, the file could previously be decrypted by any native age identity. To ensure we match the behaviour in the age specification, these files are now rejected as invalid.


    • age::Decryptor now rejects invalid or non-canonical X25519 recipient stanzas (instead of ignoring or accepting them respectively), matching the age specification.
    Source code(tar.gz)
    Source code(zip)
    rage-musl_0.8.1_amd64.deb(1.00 MB)
    rage-musl_0.8.1_arm64.deb(878.23 KB)
    rage-musl_0.8.1_armhf.deb(848.42 KB)
    rage-v0.8.1-arm64-linux.tar.gz(3.83 MB)
    rage-v0.8.1-armv7-linux.tar.gz(3.77 MB)
    rage-v0.8.1-x86_64-darwin.tar.gz(2.23 MB)
    rage-v0.8.1-x86_64-linux.tar.gz(6.26 MB)
    rage-v0.8.1-x86_64-windows.zip(1.73 MB)
    rage_0.8.1_amd64.deb(1.31 MB)
    rage_0.8.1_arm64.deb(874.46 KB)
    rage_0.8.1_armhf.deb(828.08 KB)
  • v0.8.0(May 2, 2022)



    • MSRV is now 1.56.0.
    • When both reading input from the terminal (e.g. if the user is typing the plaintext to be encrypted) and writing output to the terminal, rage now buffers the output until the input is finished, so the output doesn't get in the way of typing.
    • A warning is now displayed if rage detects that the file being encrypted starts with the age magic string or armor begin marker (indicating that an age-encrypted file is being double-encrypted). The file is still encrypted.
    • A message is now printed if a plugin takes longer than 10 seconds to encrypt or decrypt its header entry (for example, if the plugin is waiting on some user interaction that hasn't occurred yet).


    • Decryption now returns an error when given a passphrase-encrypted file if -i/--identity is present. Previously this could result in scripts hanging forever (given that passphrase decryption is intentionally not scriptable).



    • age::Callbacks::confirm to request that the user provides confirmation for some action.
    • age::cli_common::file_io::InputReader::is_terminal
    • age::ssh::ParseRecipientKeyError, which was previously in the public API but unnameable and could not be matched upon.


    • MSRV is now 1.56.0.
    • age::Callbacks now requires Clone + Send + Sync + 'static bounds.
    • age::cli_common::file_io::OutputWriter::new now takes an input_is_tty boolean argument. If input_is_tty is set to true, then if OutputWriter will write to a stdout TTY, it buffers the entire output so it doesn't get in the way of typing the input, and then writes the buffered output to stdout during OutputWriter::flush.
    • Ciphertexts are now required to end in a non-empty STREAM chunk, unless it is the only chunk (meaning that the plaintext is empty). Neither age nor rage generate non-empty files ending in an empty chunk, instead marking the final full chunk as the last chunk.

    age-plugin 0.3.0


    • age_plugin::Callbacks::confirm


    • MSRV is now 1.56.0.



    • age_core::io::{DebugReader, DebugWriter}
    • age_core::plugin::Error::Unsupported
    • age_core::plugin::Reply::ok_with_metadata


    • MSRV is now 1.56.0.
    • age_core::plugin:
      • Connection::open now returns the debugging-friendly concrete type Connection<DebugReader<ChildStdout>, DebugWriter<ChildStdin>>.
      • BidirSend::{send, send_stanza} now return Ok(Error::Unsupported) when an unsupported response is received, instead of Err(io::Error), making it easier for plugins to implement fallback strategies.
    Source code(tar.gz)
    Source code(zip)
    rage-musl_0.8.0_amd64.deb(1009.72 KB)
    rage-musl_0.8.0_arm64.deb(862.83 KB)
    rage-musl_0.8.0_armhf.deb(842.81 KB)
    rage-v0.8.0-arm64-linux.tar.gz(3.71 MB)
    rage-v0.8.0-armv7-linux.tar.gz(3.70 MB)
    rage-v0.8.0-x86_64-darwin.tar.gz(2.16 MB)
    rage-v0.8.0-x86_64-linux.tar.gz(6.05 MB)
    rage-v0.8.0-x86_64-windows.zip(1.72 MB)
    rage_0.8.0_amd64.deb(1.27 MB)
    rage_0.8.0_arm64.deb(858.56 KB)
    rage_0.8.0_armhf.deb(822.23 KB)
  • v0.7.1(Dec 27, 2021)



    • Fixed a bug in 0.7.0 where non-canonical recipient stanza bodies in an age file header would cause rage to crash instead of being rejected.



    • Bumped age-core to 0.7.1 to fix a bug where non-canonical recipient stanza bodies in an age file header would cause a panic instead of being rejected.

    age-plugin 0.2.1


    • Bumped age-core to 0.7.1 to fix a bug where non-canonical recipient stanza bodies in an age file header would cause a panic instead of being rejected.



    • In 0.7.0, Base64 decoding was moved to the AgeStanza::body method, with the stanza parser only checking for valid Base64 characters. This caused the parser to start accepting stanzas with non-canonical last body lines (where the Base64 encoding would have trailing bits that could not be decoded into full bytes); calling AgeStanza::body on these stanzas would cause a panic. This release fixes the parser to reject non-canonical last body lines, turning the panic back into an error.
    Source code(tar.gz)
    Source code(zip)
    rage-v0.7.1-arm64-linux.tar.gz(3.68 MB)
    rage-v0.7.1-armv7-linux.tar.gz(3.67 MB)
    rage-v0.7.1-x86_64-darwin.tar.gz(2.17 MB)
    rage-v0.7.1-x86_64-linux.tar.gz(6.08 MB)
    rage-v0.7.1-x86_64-windows.zip(1.73 MB)
    rage_0.7.1_amd64.deb(1.29 MB)
    rage_0.7.1_armhf.deb(811.44 KB)
  • v0.7.0(Oct 18, 2021)



    • -i/--identity now accepts passphrase-encrypted age identity files.
    • The -j PLUGIN_NAME flag, which allows decrypting with a plugin using its "default mode" (in which no identity-specific information is required). This flag is equivalent to using -i/--identity with an identity file containing the default plugin identity (containing no data).


    • MSRV is now 1.51.0.
    • *-linux.tar.gz release binaries are now built with Ubuntu 18.04, and require a system with a minimum of glibc 2.27.



    • age::encrypted::Identity, for decrypting files with passphrase-encrypted age identity files.
    • age::IdentityFileEntry enum, representing the possible kinds of entries within an age identity file.
    • age::{DecryptError, EncryptError, PluginError}: Clone bounds.
    • age::cli_common::UiCallbacks: Clone + Copy bounds.
    • age::cli_common::Passphrase::random, for generating a secure passphrase.
    • age::cli_common::ReadError
    • age::secrecy, which re-exports the secrecy crate.


    • MSRV is now 1.51.0.
    • age::IdentityFile::into_identities now returns Vec<IdentityFileEntry>.
    • age::cli_common::read_identities:
      • Encrypted age files will now be parsed and assumed to be encrypted age identities. This assumption is checked at file-decryption time.
      • New max_work_factor parameter for controlling the work factor when decrypting encrypted identities.
      • Identities are now returned in the same order as filenames (and top-to-bottom from within each file). Plugin identities are no longer coalesced; there is one Box<dyn Identity> per plugin identity.
      • age::cli_common::ReadError is now returned instead of a user-specified error type. The error constructor parameters have been removed from the function.
    • age::Callbacks::prompt has been renamed to Callbacks::display_message.
      • age::cli_common::UiCallbacks::display_message no longer uses pinentry (which displays a temporary prompt that can be dismissed), so the message is now part of the visible CLI output.


    • IdentityFile::split_into (replaced by IdentityFileEntry::Plugin).

    age-plugin 0.2.0


    • MSRV is now 1.51.0.
    • age_plugin::Callbacks methods now return age_core::plugin::Error instead of () for internal errors, following changes to age_core::plugin::Result.



    • age_core::secrecy, which re-exports the secrecy crate.
    • age_core::plugin::Error


    • MSRV is now 1.51.0.
    • The body property of age_core::format::AgeStanza has been replaced by the AgeStanza::body method, to enable enclosing parsers to defer Base64 decoding until the very end.
    • age_core::plugin::Result now only takes a single generic argument, and uses age_core::plugin::Error for its inner error type.
    Source code(tar.gz)
    Source code(zip)
    rage-v0.7.0-arm64-linux.tar.gz(3.55 MB)
    rage-v0.7.0-armv7-linux.tar.gz(3.58 MB)
    rage-v0.7.0-x86_64-darwin.tar.gz(2.14 MB)
    rage-v0.7.0-x86_64-linux.tar.gz(5.88 MB)
    rage-v0.7.0-x86_64-windows.zip(1.72 MB)
    rage_0.7.0_amd64.deb(1.27 MB)
    rage_0.7.0_arm64.deb(835.26 KB)
    rage_0.7.0_armhf.deb(819.07 KB)
  • v0.6.0(May 2, 2021)



    • Plugin support!
      • The new age-plugin crate provides a Rust API for building age plugins.
      • See https://hackmd.io/@str4d/age-plugin-spec for the beta specification.
    • The -R/--recipients-file flag, which accepts a path to a file containing age recipients, one per line (ignoring "#" prefixed comments and empty lines).
    • The -e/--encrypt flag, to allow encryption to be an explicit choice (instead of relying on -d/--decrypt not being present).


    • MSRV is now 1.47.0.
    • -o/--output will now overwrite existing files instead of returning an error. This makes the behaviour consistent with most UNIX tools, as well as when using pipes.
    • Files encrypted with this version of rage might not decrypt with previous beta versions, due to changes in how stanza bodies are canonically encoded. This should only affect a small fraction of files (if grease that triggers the change is added, which has a 3% chance per file).
    • -r/--recipient now has the specific type "recipient" which better reflects its name, rather than the ambiguous "source of recipients" it was previously.
    • -i/--identity can now be used when encrypting files. This requires the -e/--encrypt flag (to prevent ambiguity, e.g. if the user wants to decrypt but forgets the -d/--decrypt flag).


    • Recipients file support from -r/--recipient (use -R/--recipients-file instead).
    • HTTPS support. This added otherwise-unnecessary networking dependencies to rage, and there are many decisions that need to be made when downloading a file (e.g. what roots to trust?) that go beyond the APIs we want to focus on here. Users should use a tool like curl or wget to download a recipients file, and then pass it to rage.
    • The unstable GitHub feature (which relied on HTTPS support).
    • The unstable aliases feature.


    • Log output is now disabled by default, to prevent non-fatal error messages (such as an unset or invalid LANG variable) being printed to stderr while the program succeeds (which is confusing for users). The previous behaviour can be configured by setting the environment variable RUST_LOG=error.
    • Output files are now opened lazily, which avoids leaving behind an empty file when an error occurs before we write the header.



    • StreamReader::seek(SeekFrom::End(offset)) did not previously authenticate the ciphertext length; if the ciphertext had been truncated or extended by adversary_offset, it would instead seek to offset + adversary_offset. This allowed an adversary with temporary control of an encrypted age file to control the location of a plaintext read following a seek-from-end. age now returns an error if the last chunk is invalid.
      • rage was not affected by this security issue, as it does not use Seek.
      • rage-mount may have been affected; it does not use SeekFrom::End directly, but the tar or zip crates might do so.


    • Plugin support, enabled by the plugin feature flag:
      • age::plugin::{Identity, Recipient} structs for parsing plugin recipients and identities from strings.
      • age::plugin::RecipientPluginV1, which implements age::Recipient and runs the V1 recipient plugin protocol.
      • age::plugin::IdentityPluginV1, which implements age::Identity and runs the V1 identity plugin protocol.
    • The web-sys feature flag, which enables calculating the work factor for passphrase encryption with the Performance timer via the web-sys crate, when compiling for a WebAssembly target such as wasm32-unknown-unknown. This feature is ignored for the wasm32-wasi target, which supports std::time::SystemTime.
    • age::Callbacks::request_public_string to request non-private input from the user (which will not trigger any OS-level passphrase-style prompt, unlike Callbacks::request_passphrase).


    • MSRV is now 1.47.0.
    • age::cli_common::file_io::OutputWriter::File will now overwrite the file if it exists, instead of returning an error. This makes it consistent with age::cli_common::file_io::OutputWriter::Stdout, as well as most UNIX tools.
    • Files encrypted with this version of age might not decrypt with previous beta versions, due to changes in how stanza bodies are canonically encoded. This should only affect a small fraction of files (if grease that triggers the change is added, which has a 3% chance per file).
    • age::decryptor::RecipientsDecryptor now takes impl Iterator<Item = &'a dyn Identity> in its decryption methods, to make decrypting multiple files with the same identities easier.
    • age::cli_common::file_io::OutputWriter::File now wraps a LazyFile struct (instead of wrapping std::io::File directly), which does not open the file until it is first written to.
    • age::decryptor::Callbacks has been moved to age::Callbacks, as it is no longer decryption-specific.


    • age::cli_common::read_identities now allows either kind of line ending in SSH identity files.
    • Default en-US language strings are now always loaded, even if translations are not loaded by calling age::localizer().select(&requested_languages).
    • StreamReader::seek(SeekFrom::End(0)) now seeks to the correct position when the plaintext is an exact multiple of the chunk size.

    age-plugin 0.1.0

    Initial beta release!



    • age_core::primitives::aead_decrypt now takes a size argument, checked against the plaintext length. This is to mitigate multi-key attacks, where a ciphertext can be crafted that decrypts successfully under multiple keys. Short ciphertexts can only target two keys, which has limited impact. See this commit message for more details.


    • age_core::format::FILE_KEY_BYTES constant.
    • age_core::plugin module, which contains common backend logic used by both the age library (to implement client support for plugins) and the age-plugin library.


    • The stanza prefix -> and trailing newline are now formal parts of the age stanza; age_core::format::write::age_stanza now includes them in its output, and age_core::format::read::age_stanza expects them to be present.
    • Stanza bodies are now canonically serialized with a short (empty if necessary) last line. age_core::format::write::age_stanza outputs the new encoding, and age_core::format::read::age_stanza accepts only the new encoding. The new API age_core::format::read::legacy_age_stanza accepts either kind of stanza body encoding (the legacy minimal encoding, and the new explicit encoding).
    Source code(tar.gz)
    Source code(zip)
    rage-v0.6.0-arm64-linux.tar.gz(3.43 MB)
    rage-v0.6.0-armv7-linux.tar.gz(3.55 MB)
    rage-v0.6.0-x86_64-darwin.tar.gz(2.11 MB)
    rage-v0.6.0-x86_64-linux.tar.gz(5.86 MB)
    rage-v0.6.0-x86_64-windows.zip(1.68 MB)
    rage_0.6.0_amd64.deb(1.26 MB)
    rage_0.6.0_arm64.deb(825.24 KB)
    rage_0.6.0_armhf.deb(801.80 KB)
  • v0.5.0(Nov 22, 2020)



    • Italian, Spanish, and Chinese translations!
    • ssh feature flag, enabled by default. It can be disabled to remove support for ssh-rsa and ssh-ed25519 recipients and identities. ssh-rsa keys are now supported without the unstable feature flag.


    • MSRV is now 1.45.0.


    • Default identity path (identities should instead be set per-use).
    • Default alias path (for unstable aliases feature).



    • Italian, Spanish, and Chinese translations!
    • New core traits, implemented by all relevant age types:
      • age::Identity, representing an identity that can decrypt an age file.
      • age::Recipient, representing a potential recipient of an age file.
    • Separate modules and structs for different recipient types:
      • age::x25519
      • age::ssh (behind the ssh feature flag).
    • age::EncryptError, representing errors that can occur during encryption.
    • age::IdentityFile struct, for parsing a list of native age identities (currently only age::x25519::Identity) from a file.
    • Asynchronous APIs for encryption and decryption, enabled by the async feature flag:
      • age::Encryptor::wrap_async_output()
      • age::Decryptor::new_async()
      • age::decryptor::RecipientsDecryptor::decrypt_async()
      • age::decryptor::PassphraseDecryptor::decrypt_async()
    • Explicit armoring support, enabled by the armor feature flag:
      • age::armor::ArmoredReader, which can be wrapped around an input to handle a potentially-armored age file.
      • age::armor::ArmoredWriter, which can be wrapped around an output to optionally apply the armored age format.


    • MSRV is now 1.45.0.
    • Changes due to the new core traits:
      • age::Encryptor::with_recipients now takes Vec<Box<dyn Recipient>>.
      • age::decryptor::RecipientsDecryptor now takes impl Iterator<Item = Box<dyn Identity>> in its decryption methods.
      • age::cli_common::read_identities now returns Vec<Box<dyn Identity>>, as it abstracts over age::IdentityFile and age::ssh::Identity. When the ssh feature flag is enabled, it also takes an unsupported_ssh argument for handling unsupported SSH identities.
      • age::Error has been renamed to age::DecryptError.
    • Changes due to explicit armoring support:
      • age::Encryptor::wrap_output now only generates the non-malleable binary age format. To optionally generate armored age files, use encryptor.wrap_output(ArmoredWriter::wrap_output(output, format)).
      • age::Decryptor now only decrypts the non-malleable binary age format. To handle age files that are potentially armored, use Decryptor::new(ArmoredReader::new(input)).
      • age::Format has been moved to age::armor::Format.
    • SSH support is now disabled by default, behind the ssh feature flag. ssh-rsa keys are now supported without the unstable feature flag.
    • age::Callbacks has been moved to age::decryptor::Callbacks.


    • age::SecretKey (replaced by age::x25519::Identity and age::ssh::Identity).
    • age::keys::RecipientKey (replaced by age::x25519::Recipient and age::ssh::Recipient).
    • age::keys::{Identity, IdentityKey} (replaced by age::Identity trait on individual identities, and age::IdentityFile for parsing identities).
    • age::decryptor::RecipientsDecryptor::decrypt_with_callbacks() (identities are now expected to handle their own callbacks, and age::cli_common::read_identities now adds callbacks to SSH identities).
    • Default identity path:
      • age::cli_common::get_config_dir.
      • The no_default parameter for age::cli_common::read_identities.



    • Several structs used when implementing the age::Identity and age::Recipient traits:
      • age_core::format::FileKey
      • age_core::format::Stanza
    • age_core::format::grease_the_joint, for generating a random valid recipient stanza. No other guarantees are made about the stanza's fields.
    • age_core::primitives::{aead_decrypt, aead_encrypt, hkdf}, to enable these common primitives to be reused in plugins.


    • MSRV is now 1.41.0.
    • age_core::format::write::age_stanza now takes args: &[impl AsRef<str>].
    Source code(tar.gz)
    Source code(zip)
    rage-v0.5.0-arm64-linux.tar.gz(4.04 MB)
    rage-v0.5.0-armv7-linux.tar.gz(4.03 MB)
    rage-v0.5.0-x86_64-darwin.tar.gz(2.59 MB)
    rage-v0.5.0-x86_64-linux.tar.gz(6.30 MB)
    rage-v0.5.0-x86_64-windows.zip(2.16 MB)
    rage_0.5.0_amd64.deb(1.63 MB)
    rage_0.5.0_arm64.deb(1.15 MB)
    rage_0.5.0_armhf.deb(1.01 MB)
  • v0.4.0(Mar 25, 2020)



    • rage-mount can now mount ASCII-armored age files.


    • [rage] -p/--passphrase flag can no longer be used with -d/--decrypt (passphrase-encrypted files are now detected automatically).


    • -p/--passphrase flag from rage-mount (passphrase-encrypted files are now detected automatically).


    • [Unix] Files encrypted with a passphrase can now be decrypted with rage when piped over stdin.



    • age::Decryptor::new(R: Read), which parses an age file header and returns a context-specific decryptor.
    • age::decryptor module containing the context-specific decryptors.
      • Their decryption methods return the concrete type StreamReader<R>, enabling them to handle seekable readers.
    • age::Encryptor::with_recipients(Vec<RecipientKey>)
    • age::Encryptor::with_user_passphrase(SecretString)
    • Support for encrypted OpenSSH keys created with ssh-keygen prior to OpenSSH 7.6.
    • age::cli_common::file_io::OutputWriter::is_terminal


    • age::Decryptor has been refactored to auto-detect the decryption type. As a result, both identity-based and passphrase-based decryption need to be handled.
    • age::StreamReader has been moved into the age::stream module, along with StreamWriter which was previously public but has now been formally exposed in the API for documentation purposes.
    • age::Encryptor is now an opaque struct, and must be created via its new constructors.
    • age::Encryptor::wrap_output now consumes self, making it harder to accidentally reuse a passphrase for multiple encrypted files.
    • age::cli_common::read_identities now takes an additional file_not_found parameter for customising the error when an identity filename is not found.


    • age::Decryptor::trial_decrypt (replaced by context-specific decryptors).
    • age::Decryptor::trial_decrypt_seekable (merged into the context-specific decryptors).
    • age::Error::ArmoredWhenSeeking
    • age::Error::MessageRequiresKeys
    • age::Error::MessageRequiresPassphrase


    • Key files with Windows line endings are now correctly parsed.


    No changes; version bumped to keep it in sync with age.

    Source code(tar.gz)
    Source code(zip)
    rage-v0.4.0-arm64-linux.tar.gz(3.14 MB)
    rage-v0.4.0-armv7-linux.tar.gz(3.19 MB)
    rage-v0.4.0-x86_64-darwin.tar.gz(1.99 MB)
    rage-v0.4.0-x86_64-linux.tar.gz(3.27 MB)
    rage-v0.4.0-x86_64-windows.zip(1.72 MB)
    rage_0.4.0_amd64.deb(1.35 MB)
    rage_0.4.0_arm64.deb(983.72 KB)
    rage_0.4.0_armhf.deb(979.53 KB)
  • v0.3.0(Feb 9, 2020)

    Crates galore! The changes in the age library crate are reflected in the CLI tools in the rage crate.


    (relative to the CLI tools in age 0.2.0)


    • -V / --version flags to all binaries.
    • Completion files for Bash, Elvish, Fish, PowerShell, and Zsh can be generated with cargo run --example generate-completions.
    • The Debian package will install completion files for Bash, Fish, and Zsh.


    • If a pinentry binary is available, it will be used preferentially to request secrets such as passphrases. The previous CLI input will be used if pinentry is not available.



    • age::Callbacks, which encapsulates any requests that might be necessary during the decryption process.
    • age::cli_common::UiCallbacks, which implements Callbacks with requests to the user via age::cli_common::read_secret.
    • age::Decryptor::with_identities(Vec<Identity>)
    • age::Decryptor::with_identities_and_callbacks(Vec<Identity>, Box<dyn Callbacks>)
    • age::Encryptor will insert a random recipient stanza into the header, to keep age's joint well oiled.


    • The CLI tools have been moved into the rage crate.
    • The age::Decryptor::Keys enum case has been renamed to Identities and altered to store a Box<dyn Callbacks> internally.
    • age::Decryptor::trial_decrypt and age::Decryptor::trial_decrypt_seekable both no longer take a request_passphrase argument.
    • age::cli_common::read_secret:
      • Takes an additional prompt parameter.
      • Uses the system pinentry binary for requesting secrets if available.
      • Returns pinentry::Error instead of io::Error.
    • age::cli_common::read_or_generate_passphrase now returns pinentry::Error instead of io::Error.
    • Core age parsers and serializers have been moved into the age-core crate.


    • Fixed several crashes in the armored format reader, found by fuzzing. The reader also now correctly enforces a canonical armor marker and line lengths.
    • Recipient stanzas with empty bodies are correctly parsed.


    (relative to age 0.2.0)


    • Base64 padding is now correctly rejected by the age stanza parser.
    Source code(tar.gz)
    Source code(zip)
    rage-v0.3.0-arm64-linux.tar.gz(3.12 MB)
    rage-v0.3.0-armv7-linux.tar.gz(3.17 MB)
    rage-v0.3.0-x86_64-darwin.tar.gz(1.97 MB)
    rage-v0.3.0-x86_64-linux.tar.gz(3.25 MB)
    rage-v0.3.0-x86_64-windows.zip(1.71 MB)
    rage_0.3.0_amd64.deb(1.34 MB)
    rage_0.3.0_arm64.deb(970.74 KB)
    rage_0.3.0_armhf.deb(966.50 KB)
  • v0.2.0(Jan 11, 2020)


    • The library crate can be compiled to WASM.
    • When encrypting to a passphrase, rage will generate a secure passphrase if the user does not provide one.
    • SecretKey::to_string -> secrecy::SecretString, which zeroizes most internal state. (Zeroizing all internal state requires changes to the bech32 crate.)
    • RecipientKey implements Display, and can be converted to a string using recipient.to_string().
    • Decryptor::with_passphrase constructor.
    • --max-work-factor WF argument for rage and rage-mount, to enable overriding the default maximum (which is around 16 seconds of work).


    • age::Encryptor::wrap_output now takes an age::Format enum argument instead of a boolean flag.
    • Recipients are now parsed as filenames last instead of first. If a filename happens to also be a valid recipient format, the file will be ignored. This can be overridden by using an absolute file path.
    • The filename - (hyphen) is now treated as an explicit request to read from standard input or write to standard output when used as an input or output filename.
    • -o - will override protections for terminals when standard output is not being piped elsewhere: output will not be truncated, and binary data will be printed directly to the terminal.
    • Armored encrypted output can now be printed to the terminal. Large files will be truncated (to protect the terminal), corrupting the encryption. This can be overriden with -o -.
    • The Decryptor::Passphrase enum case has been altered to store an optional maximum work factor.


    • SecretKey::to_str (replaced by SecretKey::to_string).
    • RecipientKey::to_str (replaced by Display implementation and recipient.to_string()).


    • Corrected encoding of example recipients in manpages.
    • Re-enabled the default identities file (#41).
    • Fixed parser to reject encrypted OpenSSH keys if they contain invalid bcrypt_pbkdf parameters.
    • [Unix] rage-keygen -o filename now creates files with mode 600 (i.e. the output file is no longer world-readable).
    • Unknown recipient lines are now parsed and ignored during decryption, instead of causing a hard failure.
    Source code(tar.gz)
    Source code(zip)
    rage-v0.2.0-arm64-linux.tar.gz(3.05 MB)
    rage-v0.2.0-armv7-linux.tar.gz(3.11 MB)
    rage-v0.2.0-x86_64-darwin.tar.gz(1.91 MB)
    rage-v0.2.0-x86_64-linux.tar.gz(4.69 MB)
    rage-v0.2.0-x86_64-windows.zip(1.65 MB)
    rage_0.2.0_amd64.deb(1.29 MB)
    rage_0.2.0_arm64.deb(941.64 KB)
    rage_0.2.0_armhf.deb(944.64 KB)
  • v0.1.1(Dec 30, 2019)

    This time with binaries!


    • Debian packaging support via cargo deb. See docs/debian.md for details.


    • Moved the num_traits dependency behind the unstable feature flag.
    • The generate-docs example now generates (the equivalent of ) gzip -9 manpages, for ease of use in Debian packaging.


    • Decrypted chunks inside the STREAM implementation are now zeroized after use.
    Source code(tar.gz)
    Source code(zip)
    rage-v0.1.1-x86_64-darwin.tar.gz(1.88 MB)
    rage-v0.1.1-x86_64-linux.tar.gz(4.65 MB)
    rage-v0.1.1-x86_64-windows.zip(1.63 MB)
    rage_0.1.1_amd64.deb(1.27 MB)
  • v0.1.0(Dec 28, 2019)

    This is the first beta release of the age crate and rage tool suite.

    Note: The 0.X version series is being used for beta releases. The first non-beta release will be version 1.0.0.

    Source code(tar.gz)
    Source code(zip)
Diem’s mission is to build a trusted and innovative financial network that empowers people and businesses around the world.

Note to readers: On December 1, 2020, the Libra Association was renamed to Diem Association. The project repos are in the process of being migrated. A

Diem 16.5k Sep 22, 2022
The new, performant, and simplified version of Holochain on Rust (sometimes called Holochain RSM for Refactored State Model)

Holochain License: This repository contains the core Holochain libraries and binaries. This is the most recent and well maintained version of Holochai

Holochain 708 Sep 23, 2022
The Nervos CKB is a public permissionless blockchain, and the layer 1 of Nervos network.

Nervos CKB - The Common Knowledge Base master develop About CKB CKB is the layer 1 of Nervos Network, a public/permissionless blockchain. CKB uses Pro

Nervos Network 1k Sep 23, 2022
The fast, light, and robust client for the Ethereum mainnet.

OpenEthereum Fast and feature-rich multi-network Ethereum client. » Download the latest release « Table of Contents Description Technical Overview Bui

OpenEthereum 1.6k Sep 21, 2022
The Phala Network Blockchain, pRuntime and the bridge.

Phala Blockchain Phala Network is a TEE-Blockchain hybrid architecture implementing Confidential Contract. This repo includes: node/: the main blockch

Phala Network 291 Sep 23, 2022
Python bindings for rage (age in Rust)

pyrage Python bindings for the Rust implementation of age. Index Installation Usage Development Licensing Installation You can install pyrage with pip

William Woodruff 10 Aug 25, 2022
WebAssembly wrapper of the rage encryption library

rage-wasm: WebAssembly wrapper of rage rage is a simple, modern, and secure file encryption tool, using the age format. It features small explicit key

Kan-Ru Chen 30 Apr 17, 2022
A secure file encryption utility, written in rust.

Dexios Dexios What is it? Building notes Checksums Performance Output file sizes Environment Variables Key Inputs Usage Examples To Do What is it? Dex

brxken 138 Sep 21, 2022
Cyg will help you to secure files in your repository directly using PGP encryption

cyg: Secure files in your repository Cyg will help you to secure files in your repository directly using PGP encryption. The name "cyg" was inspired b

Hisam Fahri 2 Aug 31, 2022
Authenticated Encryption with Associated Data Algorithms: high-level encryption ciphers

RustCrypto: Authenticated Encryption with Associated Data (AEAD) Algorithms Collection of Authenticated Encryption with Associated Data (AEAD) algorit

Rust Crypto 413 Sep 22, 2022
A set of cryptographic primitives for building a multi-hop Proxy Re-encryption scheme, known as Transform Encryption.

recrypt A pure-Rust library that implements a set of cryptographic primitives for building a multi-hop Proxy Re-encryption scheme, known as Transform

IronCore Labs 114 Sep 13, 2022
Rust command-line tool to encrypt and decrypt files or directories with age

Bottle A Rust command-line tool that can compress and encrypt (and decrypt and extract) files or directories using age, gzip, and tar. Bottle has no c

Sam Schlinkert 1 Aug 1, 2022
Deno is a simple, modern and secure runtime for JavaScript and TypeScript that uses V8 and is built in Rust.

Deno Deno is a simple, modern and secure runtime for JavaScript and TypeScript that uses V8 and is built in Rust. Features Secure by default. No file,

Derek Jones 2 Aug 13, 2022
Simple file sharing with client-side encryption, powered by Rust and WebAssembly

Hako Simple file sharing with client-side encryption, powered by Rust and WebAssembly Not feature-packed, but basic functionalities are just working.

Jaehyeon Park 29 Jun 9, 2022
DexiosGUI - Simple cross-platform drag-and-drop Dexios file encryption

DexiosGUI Simple cross-platform drag-and-drop Dexios file encryption. Latest Windows x64 release is here. DexiosGUI is a Qt/C++ app for encrypt and de

Fabrice Corraire 4 Jul 25, 2022
CLI search and replace | Space Age seD

SAD! Space Age seD What does it do? Basically sad is a Batch File Edit tool. It will show you a really nice diff of proposed changes before you commit

i love my dog 934 Sep 13, 2022
age-encrypted secrets for NixOS; drop-in replacement for agenix

ragenix ragenix provides age-encrypted secrets for NixOS systems which live in the Nix store and are decrypted on system activation. Using ragenix to

YAXI 80 Sep 23, 2022
Expose local age identities to remote machines via SSH

age-plugin-remote TBD Design Notes Proxy identities act as bearer tokens. A proxy identity is only "active" if the authority provides it when starting

null 6 Aug 19, 2022
Single File Assets is a file storage format for images

SFA (Rust) Single File Assets is a file storage format for images. The packed images are not guaranteed to be of same format because the format while

null 1 Jan 23, 2022
Easy to use cryptographic framework for data protection: secure messaging with forward secrecy and secure data storage. Has unified APIs across 14 platforms.

Themis provides strong, usable cryptography for busy people General purpose cryptographic library for storage and messaging for iOS (Swift, Obj-C), An

Cossack Labs 1.6k Sep 21, 2022