Does the sequoia CLI have support for smartcards like yubikeys? I checked the issue tracker and didn't see any information.
Sq, Sequoia PGP's CLI, Released
11–16 of 16 posts
Re: Sq, Sequoia PGP's CLI, Released
#12Is there a guide for switching from gpg on the cli to sq? Specifically, I'm not sure how to move keys from my gpg keyring to sq.
Several important components are missing including a public key store. In GnuPG, the public key store is mandatory. In our discussions with application developers, in particular, developers working on server software, this requirement was more of a hindrance than a help. Thus, in Sequoia we decided it needs to be as easy to bring your own key store (e.g., an existing database) as to use ours.
That said, on the desktop, it is quite useful to have a shared key store--you don't want to import keys into each of your OpenPGP-using applications. We hope to finish our [public key store](https://docs.sequoia-pgp.org/sequoia_store/index.html) this year along with other features that end users need and expect.
Re: Sq, Sequoia PGP's CLI, Released
#13Does the sequoia CLI have support for smartcards like yubikeys? I checked the issue tracker and didn't see any information.
Re: Sq, Sequoia PGP's CLI, Released
#14Does the sequoia CLI have support for smartcards like yubikeys? I checked the issue tracker and didn't see any information.
aren't those only to fetch/store certs? can't you just pipe the proprietary(?) utility?
An advantage of a open and well documented offline cryptography standard. You can do stuff like that.
Re: Sq, Sequoia PGP's CLI, Released
#15Earlier quoted context omitted.
aren't those only to fetch/store certs? can't you just pipe the proprietary(?) utility?
They can just be used for key storage. But for OpenPGP the device is normally used as a sort of an air gapped system. The secret key information is kept on the device and the operations requiring that information are done directly on the device. It is possible and normal for even the owner to have no access to the secret key information. An advantage of a open and well documented offline cryptography standard. You ca…
I mean any implementation can handle the signing etc, as the operations are an open standard. But running the actual pgp implementation on a system you have no access to sources, can't really see the advantage of just using an old laptop to have truly airgapped system (plugging your proprietary device on a connected computer doesn't look that airgapped to me)
Re: Sq, Sequoia PGP's CLI, Released
#16Earlier quoted context omitted.
They can just be used for key storage. But for OpenPGP the device is normally used as a sort of an air gapped system. The secret key information is kept on the device and the operations requiring that information are done directly on the device. It is possible and normal for even the owner to have no access to the secret key information. An advantage of a open and well documented offline cryptography standard. You ca…
isn't a closed implementation adversarial to those benefits? I mean any implementation can handle the signing etc, as the operations are an open standard. But running the actual pgp implementation on a system you have no access to sources, can't really see the advantage of just using an old laptop to have truly airgapped system (plugging your proprietary device on a connected computer doesn't look that airgapped to m…