The usefulness of this library would be tremendously extended if support for the OPENPGPKEY standard (RFC 7929) was added. It would allow to send e2e-encrypted email to people with whom no key has been exchanged, given that the recipient has made their public key available through the DNS.
I am aware that the implementation of this feature is not straight-forward. The technique requires performing DNS lookups for rather unusual record types, and demands DNSSEC validation, both of which are currently infeasible using client-side JavaScript.
However, these issues can be outsourced to a trusted DNS resolver that is accessible through HTTPS. If ran on similar infrastructure as the keyservers used by e2email in connection with GMail, the trust level will be the same as right now.
The usefulness of this library would be tremendously extended if support for the OPENPGPKEY standard (RFC 7929) was added. It would allow to send e2e-encrypted email to people with whom no key has been exchanged, given that the recipient has made their public key available through the DNS.
I am aware that the implementation of this feature is not straight-forward. The technique requires performing DNS lookups for rather unusual record types, and demands DNSSEC validation, both of which are currently infeasible using client-side JavaScript.
However, these issues can be outsourced to a trusted DNS resolver that is accessible through HTTPS. If ran on similar infrastructure as the keyservers used by e2email in connection with GMail, the trust level will be the same as right now.