Skip to content

Latest commit

 

History

History
62 lines (38 loc) · 2.48 KB

FAQ.md

File metadata and controls

62 lines (38 loc) · 2.48 KB
Raw

FAQs

Is rPGP aiming to support V6 keys as defined by the IETF OpenPGP working group?

Yes.

We aim to step-wise introduce support for the V6 IETF CryptoRefresh during 2024.

Is rPGP considering adding support for Post Quantum Cryptography (PQC)?

Yes, it is tracked in #356.

We are following the IETF Post-Quantum Cryptography in OpenPGP work and discussed with some of its authors but have not fully assessed yet the work needed to support it in rPGP.

What other standards are you considering for implementation?

IETF standards currently tracked for implementation in rPGP use the "ietf-draft" label on the issues.

If you want to help either with coding or with funding, please get in contact.

We are also participating in renewed Autocrypt specification efforts, a multi-stakeholder community-driven specification for automated e-mail encryption.

Is rPGP considering support for LibrePGP?

No, at least not soon.

While we might not agree with, or not praise every detail of the V6 crypto refresh, we highly appreciate the work of the IETF OpenPGP WG and the contributors and stakeholders around it.

If LibrePGP evolves towards a multi-stakeholder community-driven specification, we might consider partially supporting LibrePGP keys after the work on supporting IETF OpenPGP V6 keys is done.

Helping to smoothly and securely move the many Delta Chat users of rPGP to V6 keys is sufficiently challenging for us without considering LibrePGP.

How is rPGP different from Sequoia?

The Sequoia project offers an alternative Rust implementation of OpenPGP. Here are some key differences, without claiming to exhaust the question:

  • rPGP has a more permissive license than Sequoia.

  • rPGP is a library with a low-level API and relatively small feature-set (with higher level APIs evolving in https://codeberg.org/heiko/rpgpie ) whereas Sequoia has a comprehensive set of crates and also offers the sq CLI and aims to be a replacement for the GPG command line tool.

  • All cryptographic primitives used in rPGP are implemented in Rust, whereas Sequoia by default uses Nettle, which is implemented in C, but also offers optional Rust backends.