age encryption tool

“This ensures privileged data is protected at rest and in transit”

“Highly trusted / audited / scrutinised / maintained code.”

“Just use `age` and encrypt your message with sender public key.”

“Age encryption allows devs to use the same ssh keys they use to access git repos”

“sops combined with age is great! Benefit is that it doesn't tie you into 1Password's ecosystem”

“age over GPG. Simpler, auditable, handles multi-recipient natively, no web of trust complexity.”

“Ssh/age/minisign just work for my use cases.”

“It’s open source and has multiple mature implementations by well-regarded cryptographic engineers.”

“You can also use age to encrypt payloads targeting ssh public keys.”

“Restic, gocryptfs, and/or age are far more flexible, generic and flat out better”

“much neater stack that does basically everything I would need to use PGP for”

“age is the real replacement for pgp in terms of sending encrypted files”

“The overall experience was annoying given that the problems with pgp/gpg are esoteric and abstract”

“discovered multiple vulnerabilities in cryptographic utilities, namely in GnuPG, Sequoia PGP, age, and minisign”

“the ansible recipe for building and installing age broke within a year”

“I've been using it directly and indirectly for 5+ years and haven't had any compatibility or runtime issues with it”

“Apart from the fact that it really slowed down my deployments, the thing broke within a year.”

“there is no keyring and you have to supply people's public key each time”

“using SSH keys for signatures and age[1] for encryption targeting SSH keys”

“If you're just using it to encrypt files (even between pointwise parties), you can probably just switch to age.”

“The way you secure this is by moving to alternative, purpose-built tools.”

“I'm looking at age as a pure isolated thing, according to the spec”

“I found age and I found it to be brilliant for what its worth”

“age is designed to be composable and very stable”

“Ideally it would be in the format that the `age` utility supports.”

“You can use the age tool to encrypt secrets based on ssh public keys.”

“I love that age lets one reuse ssh identities”

“The incremental improvement from going GPG to age seems pointless given the timelines.”

“128 bits of symmetric keys are enough for post-quantum security”

“Age is cool, but really the only use-case I have is for my password manager”

“Both the choice of symmetric key length AND the choice of public key algorithms independent of each other make this format not PQ.”

“I know of no solutions even close to this for Minisign or Age keys”

“But this means that the symmetric key is entirely vulnerable to quantum computers.”

“more professional environments have integrated age and minisign than have integrated PGP”

“Age is maybe useful for personal encryption use cases, but it is no way a replacement for all encryption use cases of PGP”

“it does not even do that thing as well as PGP does in most situations I can think of”

“If you need these various features, then age et al. do not fit the bill.”

“Age has Yubikey support with no reasonable long term key discovery, backup, or rotation strategy as far as I can tell.”

“age is so clean precisely because it does only one thing”

“Encrypting secrets with age will keep them confidential even if the project is Open Source”