minisign
age-plugin-yubikey
minisign | age-plugin-yubikey | |
---|---|---|
12 | 11 | |
1,967 | 504 | |
- | - | |
4.8 | 4.9 | |
about 1 month ago | 26 days ago | |
C | Rust | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
minisign
- Ask HN: What are your favorite tiny, single purpose tools?
- Minisign A dead simple tool to sign files and verify signatures
-
PGP signatures on PyPI: worse than useless
There are alternatives, minisign and signify.
-
Can a program be the only thing able to have access to a private key?
You don't have to attach identities to public and private keys. If all you need it for is signing, then check out minisign.
-
How should I encrypt files for sharing over the internet?
If you need signatures, minisign is a similar hard-to-misuse program.
-
Beginner: how to do basic cryptography for a blog
In your case, use a tool such as https://jedisct1.github.io/minisign/ to do signing/verification. GPG is another choice which is very common. It will produce a "signature" which can be embedded alongside your posts verifying that the text of the post was endorsed by someone bearing the given public key.
-
Is it worth it to make the move to ProtonMail & VPN?
Claiming it's not ancient because Linux desktop distributions still use it for signing packages is a very odd argument. Most Cryptography experts (note: I'm not talking about programmers, IT professionals or people who know a thing or two about cryptography, I mean actual cryptographers) would agree that we should start using something like signify or minisign instead of the bloated mess that is GPG for signing package repositories.
-
Hacker News top posts: Dec 23, 2021
minisign\ (5 comments)
- minisign
- Show HN: Pagesign – A Python Wrapper for Age and Minisign
age-plugin-yubikey
-
Age: Modern file encryption format with multiple pluggable recipients
_o/ hi all, age author here!
The OP link is the spec, here's a few other things you might find interesting
- the Go reference implementation https://age-encryption.org
- the Go library docs https://pkg.go.dev/filippo.io/age
- the CLI man page https://filippo.io/age/age.1
- an interoperable Rust implementation by @str4d https://github.com/str4d/rage
- a YubiKey plugin by @str4d https://github.com/str4d/age-plugin-yubikey
- the draft plugin protocol specification (which we should really merge) https://github.com/C2SP/C2SP/pull/5/files?short_path=07bf8cc...
- a Windows GUI by @spieglt https://github.com/spieglt/winage
- a discussion of the authentication properties of age https://words.filippo.io/dispatches/age-authentication/
- a discussion of a potential post-quantum plugin https://words.filippo.io/dispatches/post-quantum-age/
- a password-store fork that uses age instead of gpg https://github.com/FiloSottile/passage (see also: how I use it with a YubiKey https://words.filippo.io/dispatches/passage/)
-
Add the same key to a retired PIV slot of two different Yubikey's
I am using the yubikey plug-in for age (https://github.com/str4d/age-plugin-yubikey). It creates a private key and writes it to one of the retired PIV slot. What I want to do is to write the same private key to two different Yubikeys.
-
age.el: age encryption support for Emacs
So with age I can also just use my ssh public key to encrypt and my ssh private key to decrypt my files. If I want to get fancy, I can use something like https://github.com/str4d/age-plugin-yubikey to provide the key material for my age operations (which should compose with age.el quite well also, i.e. you can have every decrypt operation have a touch requirement in Emacs that way).
-
age v1.1.0-rc.1: plugin and Yubikeys support
> A good feature of PIV applet of Yubikey 5 is that it stores 24 keys.
Note that not all 24 of those keys are suitable for age usage. The 4 main keys have specific usage definitions in the PIV specification that mean hardware tokens alter how those key slots behave. Only one of them (the KeyManagement slot) has a definition that allows encryption, and even that I was somewhat suspicious of overlapping with, as I couldn't predict how those existing keys were being used, and didn't want to support every possible key type that might be in that slot (which users likely wouldn't be able to alter).
age-plugin-yubikey avoids this complexity by only interacting with the 20 "retired" slots, which have no constraining definitions. (I am considering adding restricted support for the KeyManagement slot specifically for CAC card users who aren't allowed to add new keys to their cards [0], but this would be behind a default-off feature flag to keep the primary UX simple.)
[0] https://github.com/str4d/age-plugin-yubikey/issues/62
- Age encryption plugin for Yubikey exits beta
- Ask HN: CLI Tool for File Encryption?
-
Passage: A fork of password-store that uses age instead of GnuPG
We designed the plugin protocol (https://hackmd.io/@str4d/age-plugin-spec) and generally the age recipient/identity structure specifically to enable the use of hardware or remote keys!
For example, https://github.com/str4d/age-plugin-yubikey makes it very easy to use PIV tokens, including YubiKeys, with age. (Well, for now with rage, since plugin support is coming in age v1.1.0.)
I argue against password-protecting keys by default because, unlike using hardware tokens, it doesn't protect against many threat models.
- Clever uses of pass, the Unix password manager
-
Age v1.0.0 – simple, modern and secure file encryption
Hardware? I assume if someone was concerned about key access they wouldn't want keys on their filesystem at all but move them into an HSM instead. Since age identities can come from standard input I assume it'd be feasible to put together a workflow there coming from one of the various cli utilities for interacting with keys. There is already a YubiKey specific age plugin [0] getting worked on as well. Currently in beta but looks interesting. Hopefully that will continue to expand to cover other common options. HSM support is pretty important for a modern encryption utility IMO but unfortunately the landscape is pretty all over the place too, so makes sense to just leave it to plugins or as part of a unix flow.
----
0: https://github.com/str4d/age-plugin-yubikey
-
Yubikey PIV encrypted messaging system
age also has a notion of plugins, one of which is age-plugin-yubikey (written in Rust, there is also yubage written in Go) which allows you to create an age identity whose private key is stored via PIV.
What are some alternatives?
signify - OpenBSD tool to sign and verify signatures on files. Portable version.
age - A simple, modern and secure encryption tool (and Go library) with small explicit keys, no config options, and UNIX-style composability.
gopass - The slightly more awesome standard unix password manager for teams
ed25519 - Minimal ed25519 Haskell package, binding to the ref10 SUPERCOP implementation.
rage - A simple, secure and modern file encryption tool (and Rust library) with small explicit keys, no config options, and UNIX-style composability.
kyber
yubikey-agent - yubikey-agent is a seamless ssh-agent for YubiKeys.
mkp224o - vanity address generator for tor onion v3 (ed25519) hidden services
passforios - Pass for iOS - an iOS client compatible with Pass command line application.
sign - Digital file signing and signature verfication utility
kakoune-lsp - Kakoune Language Server Protocol Client