4 ms·

Any idea when the high level crate will have parity with the CLI? Or perhaps, UX parity? I ask because the CLI looks fairly understandable (to a crypto-dunce l

Any idea when the high level crate will have parity with the CLI? Or perhaps, UX parity? I ask because the CLI looks fairly understandable (to a crypto-dunce like me), but the high level API in readme says: > Please note that as of this writing the high-level API is very incomplete. I'm also not sure what crate they refer to, because there is no `sequoia` crate on docs.rs, and their link points to the root of the repo which is a workspace without a crate. Perhaps they mean sequoia-openpgp[1], but so far that interface does not look similarly high level to that of the CLI. Anyway, just asking because i often write apps that use signing/encryption/etc for data at rest, and Sq looks neat. [1]: https://docs.rs/sequoia-openpgp/1.0.0/sequoia_openpgp/index.html https://docs.rs/sequoia-openpgp/1.0.0/sequoia_openpgp/index....

nwalfield 6y ago
Sequoia consists of a number of components. There is the low-level crate. We released version 1.0 of that in Dec. 2020. There is sq, the CLI tool. We released that a few weeks ago. We've barely started work on the high-level interface. Just because we plan to write a high-level tool, doesn't mean the low-level crate is hard to use. On the contrary, our experience is that it is pretty easy to use and actually does a good job hiding a lot of the low level details that don't need to be tweaked. For instance, I ported the pep engine from gpgme (GnuPG's high-level interface) to Sequoia's low-level interface. The initial port required about half as many lines of code.