I use sq for creating & managing my PGP keys and would like to use it as a signing backend for my jj changes/commits, but it is not compatible with any existing signing backend that jj provides.
I would like a SqBackend in jj-lib that uses the sq CLI to verify and sign commits.
Describe alternatives you've considered
- Configuring the
gpg backend to use sq instead (doesn't work, CLI arguments are different)
- Exporting my sequoia keys for use with
gpg/gpg-agent. While this technically works as a workaround, it means having to use both sq and gpg which is undesirable.
Additional context
I'm happy to contribute a PR to add this functionality. The existing GpgBackend and tests look very instructive as to what would be needed for a SqBackend. The SigningBackend trait looks flexible enough to be easily implemented with the sq CLI as a backend.
I use
sqfor creating & managing my PGP keys and would like to use it as a signing backend for myjjchanges/commits, but it is not compatible with any existing signing backend thatjjprovides.I would like a
SqBackendinjj-libthat uses thesqCLI to verify and sign commits.Describe alternatives you've considered
gpgbackend to use sq instead (doesn't work, CLI arguments are different)gpg/gpg-agent. While this technically works as a workaround, it means having to use bothsqandgpgwhich is undesirable.Additional context
I'm happy to contribute a PR to add this functionality. The existing
GpgBackendand tests look very instructive as to what would be needed for aSqBackend. TheSigningBackendtrait looks flexible enough to be easily implemented with thesqCLI as a backend.