HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
FiloSottile
age
Go2019–2026
FiloSottile / age

age

A simple, modern and secure encryption tool (and Go library) with small explicit keys, no config options, and UNIX-style composability.

107Distinct people
126Mentions
1Explicit recommenders
24.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A simple, modern and secure encryption tool (and Go library) with small explicit keys, no config options, and UNIX-style composability.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I recommend age as well. It offers encrypting for recipients for whom you have public keys. https://github.com/FiloSottile/age

ChrisGranger used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 8:59:02 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year126 dated mentions

Observed mentions: 2019-10-07 03:21:46 UTC to 2026-10-10 15:30:33 UTC.

01020302019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 11 mentions; 4 submissions, 7 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 15 mentions; 0 submissions, 15 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 29 mentions; 7 submissions, 22 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 24 mentions; 5 submissions, 19 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 12 mentions; 0 submissions, 12 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 12 mentions; 2 submissions, 10 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 16 mentions; 3 submissions, 13 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC1147
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC15015
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC29722
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC24519
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC12012
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC12210
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC16313
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC725

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
age is a simple, modern and secure file encryption tool, format, and Go library. It features small explicit keys, post-quantum support, no config options, and UNIX-style composability. $ age-keygen -o key.txt Public key: age1ql3z7hjy54pw3hyww5ayyfg7zqgvc7w3j2elw8zmrj2kg5sfn9aqmcac8p $ tar cvz ~/data | age -r age1ql3z7hjy54pw3hyww5ayyfg7zqgvc7w3j2elw8zmrj2kg5sfn9aqmcac8p > data.tar.gz.age $ age --decrypt -i key.txt data.tar.gz.age > data.tar.gz 📜 The format specification is at age-encryption.org/v1. age was designed by @benjojo and @FiloSottile. 🦀 An alternative interoperable Rust implementation is available at github.com/str4d/rage. 🌍 Typage is a TypeScript implementation. It works in the browser, Node.js, Deno, and Bun. 🔑 Hardware PIV tokens such as YubiKeys are supported through the age-plugin-yubikey plugin. ✨ For more plugins, implementations, tools, and integrations, check out the awesome age list. 💬 The author pronounces it [aɡe̞] with a hard g, like GIF, and it's always spelled lowercase. Installation Homebrew (macOS or Linux) brew install age MacPorts port install age Windows winget install --id FiloSottile.age Alpine Linux v3.15+ apk add age Arch Linux pacman -S age Debian 12+ (Bookworm) apt install age Debian 11 (Bullseye) apt install age/bullseye-backports (enable backports for age v1.0.0+) Fedora 33+ dnf install age Gentoo Linux emerge app-crypt/age Guix System guix package -i age NixOS / Nix nix-env -i age openSUSE Tumbleweed zypper install age Ubuntu 22.04+ apt install age Void Linux xbps-install age FreeBSD pkg install age (security/age) OpenBSD 6.7+ pkg_add age (security/age) Chocolatey (Windows) choco install age.portable Scoop (Windows) scoop bucket add extras && scoop install age On Windows, Linux, macOS, and FreeBSD you can use the pre-built binaries. https://dl.filippo.io/age/latest?for=linux/amd64 https://dl.filippo.io/age/v1.3.2?for=darwin/arm64 ... If you download the pre-built binaries, you can check their Sigsum proofs. If your system has a supported version of Go, you can build from source. go install filippo.io/age/cmd/...@latest Help from new packagers is very welcome. Usage For the full documentation, read the age(1) man page. Usage: age [--encrypt] (-r RECIPIENT | -R PATH)... [--armor] [-o OUTPUT] [INPUT] age [--encrypt] --passphrase [--armor] [-o OUTPUT] [INPUT] age --decrypt [-i PATH]... [-o OUTPUT] [INPUT] Options: -e, --encrypt Encrypt the input to the output. Default if omitted. -d, --decrypt Decrypt the input to the output. -o, --output OUTPUT Write the result to the file at path OUTPUT. -a, --armor Encrypt to a PEM encoded format. -p, --passphrase Encrypt with a passphrase. -r, --recipient RECIPIENT Encrypt to the specified RECIPIENT. Can be repeated. -R, --recipients-file PATH Encrypt to recipients listed at PATH. Can be repeated. -i, --identity PATH Use the identity file at PATH. Can be repeated. --version Print the version. INPUT defaults to standard input, and OUTPUT defaults to standard output. If OUTPUT exists, it will be overwritten. RECIPIENT can be an age public key generated by age-keygen ("age1...") or an SSH public key ("ssh-ed25519 AAAA...", "ssh-rsa AAAA..."). Recipient files contain one or more recipients, one per line. Empty lines and lines starting with "#" are ignored as comments. "-" may be used to read recipients from standard input. Identity files contain one or more secret keys ("AGE-SECRET-KEY-1..."), one per line, or an SSH key. Empty lines and lines starting with "#" are ignored as comments. Passphrase encrypted age files can be used as identity files. Multiple key files can be provided, and any unused ones will be ignored. "-" may be used to read identities from standard input. When --encrypt is specified explicitly, -i can also be used to encrypt to an identity file symmetrically, instead or in addition to normal recipients. Multiple recipients Files can be encrypted to multiple recipients by repeating -r/--recipient. Every recipient will be able to decrypt the file. $ age -o example.jpg.age -r age1ql3z7hjy54pw3hyww5ayyfg7zqgvc7w3j2elw8zmrj2kg5sfn9aqmcac8p \ -r age1lggyhqrw2nlhcxprm67z43rta597azn8gknawjehu9d9dl0jq3yqqvfafg example.jpg 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 age1ql3z7hjy54pw3hyww5ayyfg7zqgvc7w3j2elw8zmrj2kg5sfn9aqmcac8p # Bob age1lggyhqrw2nlhcxprm67z43rta597azn8gknawjehu9d9dl0jq3yqqvfafg $ age -R recipients.txt example.jpg > example.jpg.age If the argument to -R (or -i) is -, the file is read from standard input. Post-quantum keys To generate hybrid post-quantum keys, which are secure against future quantum computer attacks, use the -pq flag with age-keygen. This may become the default in the future. Post-quantum identities start with AGE-SECRET-KEY-PQ-1... and recipients with age1pq1.... The recipients are unfortunately ~2000 characters long. $ age-keygen -pq -o key.txt $ ag
Read the full README on GitHub

What Hacker News says

12 sources
Edit: (Apologies). Thank you! Even with "ssh-ed25519" [1]? I looked at a ssh-ed25519 example [2] but i don't see how it can be extracted from the minisign secret key format [3], for example: ssh-ed25519: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIK0wmN/Cr3JXqmLW7u+g9pTh+wyqDHpSQEIQczXkVx9q gleb@reys.net minisign secret key format: untrusted comment: minisign encrypted secret key RWRTY0IyNKMZZ+uqJdb8VtvSTo9EwylBlcsnitMtEyQzVLq/7tUAAAACAAAAAAAAAEAAAAAANLUi4xncsLbGKL+8y/n692Imrb9iURwzfnVfRqxqU5kAnVVrs98xMBqtIOiS63HZ3BQIGU6jpBWbX3ELCALfL/Le6UL3DunYfWqNPvhAKhlY4gQEjMzrL6ytxTFCXLGJpBSZHkK3DIQ= [1] https://github.com/FiloSottile/age#user-content-ssh-keys [2] https://www.unixtutorial.org/how-to-generate-ed25519-ssh-key... [3] https://jedisct1.github.io/minisign/#secret-key-format
In What to Use Instead of PGP
How would you compare this to existing tools in the space like https://github.com/FiloSottile/age? Seems like age has multiple implementations (rust, go), has a permissive license, a public specification (https://github.com/C2SP/C2SP/blob/main/age.md) and the spec/core implementation is developed by someone with a history with cryptography (I don't know if you do, but there is no indication or name attached to the repo). While many things can be built as a hobby or learning project I feel like cryptography is one of those spaces where you should be clear if it is that and if it is not you need to expressively argue its bona fides up front.
In Show HN: Ezcrypt – A file encryption tool (simple, strong, public domain)
I have been a fan of https://github.com/FiloSottile/age for a while now, but one thing that has always bothered me about encryption tools is how they don't offer a way to secure a whole directory which, IMO, is a much more common use-case. I decided to spend a couple hours tackling the problem myself and came up with agevault. It's a directory encryption tool using age file encryption. It locks/unlocks a vault (directory) with a passphrase-protected identity file and like age, it features no config options, allowing for a straightforward secure flow. I'll answer any questions regarding it. As always, use it at your own risk.
In New Directory Encryption Tool
Thanks for sharing, always happy when my projects inspire alternatives addressing different parts of the design space. Here are a few quick comments based on skimming the documentation, let me know if I misinterpreted anything. - signing support This has always been a non-goal for age. It makes the UX significantly more complex, but it's good if different tools have different goals. I can't quite make out from https://www.kryptor.co.uk/specification if it does proper signcryption, sign-then-encrypt (vulnerable to signature stripping and re-signing), or encrypt-then-sign (vulnerable to decrypt-reencrypt-forward, like OpenPGP). If the latter two, it's a missed opportunity to offer more security than age+minisign can offer and I encourage the author to look into it! - sender authentication I wrote about this. tl;dr age has authentication, bu
Read the rest
t I am not sure what a non-sharp UX around it would be, so I don't advertise it. https://words.filippo.io/dispatches/age-authentication/ - post-quantum security As https://www.kryptor.co.uk/security-limitations#post-quantum-... acknowledges, "the asymmetric algorithms in Kryptor aren't post-quantum secure". There is support for adding a pre-shared symmetric key, although I did not find the pre-shared key in the usage section, but I would argue that is not asymmetric encryption. In this sense, I would actually argue that Kryptor is just as post-quantum secure as age: age's symmetric encryption (the passphrase mode) is post-quantum (see https://words.filippo.io/dispatches/post-quantum-age/). We don't support adding a pre-shared symmetric key to asymmetric encryption, but if you have a secure channel to establish a pre-shared key, you should just use passphrase mode. age does have a third-party fully post-quantum asymmetric encryption plugin (https://github.com/keisentraut/age-plugin-sntrup761x25519) and I plan to make an ML-KEM one once the standard is out. - key commitment This is a pretty wonky topic. age as a whole is key committing (you can't make a file that decrypts with two age identities as different plaintexts, some academic researchers tried!). Our file key encryption is not (https://github.com/FiloSottile/age/commit/2194f6962c8bb3bca8...) which means that if you host an online service that accepts an age file and decrypts it with a passphrase and returns an error if it's incorrect, an attacker can do a bruteforce two passphrases at a time instead of one at a time. Given the online oracle is already unusual as a setting, I am not interested in adding complexity to solve this one. - private key encryption age supports that! https://github.com/FiloSottile/age?tab=readme-ov-file#passph... It's not the default because most threat models don't need it: if you have FDE, who's an attacker that can read files from your disk but not replace the age binary in $PATH? - indistinguishability from random Not an age goal, actually we very intentionally put "age-encryption.org/v1" in the header so you can run file(1), and specify the type of the recipients to help plugins disambiguate files. The default recipient type doesn't leak any other metadata (i.e. you can't link age files encrypted to the same recipient). - size padding This is a good idea and slated for age v2.
In Age is a simple, modern and secure file encryption tool, format, and Go library
I would love to see this used in a FIPS-compliant variant of age[1] for archival file encryption use cases. We had banking industry auditors veto age for this use case due to the use of ChaCha instead of AES (they were fine with the X25519 public key part of age which I think was somewhat recently approved by NIST). I’ve no experience with golang but it seems like it should drop right in based on the age spec. I might give it a shot if time ever permits. I guess I should call it “cage” as in “compliant actually good encryption” 1: https://github.com/FiloSottile/age
In The XAES-256-GCM extended-nonce AEAD

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.