3 ms·

I don't think they're being idiosyncratic. You start your post off with a paragraph that complains about how bad PGP is. Of course people will respond to that p

I don't think they're being idiosyncratic. You start your post off with a paragraph that complains about how bad PGP is. Of course people will respond to that part. I don't think PGP is that bad either. It's pretty standard asymmetric crypto. The implementations and especially the key sharing leaves a lot to be desired but for personal use I like it. And I love that there's lots of hardware key support. This is why I use it. I personally use my hardware OpenPGP keys also for SSH, on yubikeys and OpenPGP smartcards. I also use those for encrypting and signing data. So I'm already doing something similar to start you're saying, just the other way around. Having my keys on a hardware token is a must-have for me and I wonder if that's possible with your method. I also prefer having a token that requires a hardware input for each use like the Yubikeys can. You can set them up to require a touch for every signature or authentication. This stops a compromised server you log in to from milking your SSH agent. But how would I store the keys in hardware if not PGP? I tried PKCS11 modules with different cards before but the software chain with middleware is pretty terrible. PGP's is pretty sane (gpg --card-edit is much more user friendly than what was offered by the other more expensive cards I used!) And I don't like Fido2 either for this because it can't be used for content encryption/signing (which is what your blog post about) So, I'm pretty open to doing what you're doing but my requirement for hardware key storage makes it pretty hard I think. It would be nice to hear your thoughts on this, how this could work with hardware-backed keys.

yencabulator 5y ago
This whole thread is off-topic (talking about AEAD in a post about signing), but: You can use age's AEAD encryption with Yubikeys. Yubikeys can do ECDHE in PIV mode. I wrote https://github.com/tv42/yubage https://github.com/tv42/yubage as a subprocess plugin to https://github.com/str4d/rage https://github.com/str4d/rage (and hopefully https://github.com/FiloSottile/age https://github.com/FiloSottile/age once they think plugins are stable in enough to go in the reference implementation). The rage author also wrote their https://github.com/str4d/age-plugin-yubikey https://github.com/str4d/age-plugin-yubikey
coldacid 5y ago
Ditto on the hardware token. This SSH signing thing looks to require an actual file in the file system, which is a complete non-starter to those of us who don't keep our keys in ~/.ssh/id_* files.
- stormbrew 5y ago
  From the man page: > The key used for signing is specified using the -f option and may refer to either a private key, or a public key with the private half available via ssh-agent(1).

yencabulator 5y ago

This whole thread is off-topic (talking about AEAD in a post about signing), but: You can use age's AEAD encryption with Yubikeys. Yubikeys can do ECDHE in PIV mode. I wrote https://github.com/tv42/yubage https://github.com/tv42/yubage as a subprocess plugin to https://github.com/str4d/rage https://github.com/str4d/rage (and hopefully https://github.com/FiloSottile/age https://github.com/FiloSottile/age once they think plugins are stable in enough to go in the reference implementation). The rage author also wrote their https://github.com/str4d/age-plugin-yubikey https://github.com/str4d/age-plugin-yubikey

coldacid 5y ago

Ditto on the hardware token. This SSH signing thing looks to require an actual file in the file system, which is a complete non-starter to those of us who don't keep our keys in ~/.ssh/id_* files.

stormbrew 5y ago
From the man page: > The key used for signing is specified using the -f option and may refer to either a private key, or a public key with the private half available via ssh-agent(1).