On Wed 2015-03-18 09:08:26 -0400, Phillip Hallam-Baker wrote:
This makes it a lot easier for folk who have an S/MIME implementation to
add OpenPGP support. It is also the approach that has been debugged and is
known to work with legacy mail infrastructure.
One of the main challenges with end-to-end mail is Webmail which is now
used by most mail users. It is possible to get end-to-end to work with
webmail on the receiver side but it requires a mechanism that allows the
server to say 'here is an encrypted blob in format X, decrypt it with the
key you hold locally and present it to the user'. On the sender side you
need an editing widget that can be called out that will deliver the content
to be encrypted.
That is going to be easiest to get from the browser community if there is
least variation between the E2E email formats.
Please take a look at the "end-to-end" website API:
https://github.com/google/end-to-end/wiki/Website-API
I don't think it covers all the cases you describe, but it's nicely
concise at the moment, and maybe just needs a few tweaks to be able to
reach some of the mechanisms you're looking for.
--dkg
_______________________________________________
openpgp mailing list
openpgp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/openpgp