Julien R Pierre - Sun Microsystems wrote:
My insurance company chose to deploy webmail with an HTTPS interface with a shared-secret login (password) for secure messages between patient and doctors. As a result, I cannot (easily) archive the messages I receive and send locally. I have to login to a web site every time to look at them. And that web site sets the archiving policy.
Especially the lack of control over the archiving policy can really bite you.
However, it's obvious that the system they deployed is much simpler to use than S/MIME. Still, my dietitian finds it too complicated, and can only be contacted through regular insecure email to this day.
And that's exactly the point: Your dietitian don't have to use encrypted e-mail. If it would be a MUST (by law or similar regulations) he would. That's a non-technical issue and cannot be solved by yet another technical approach which looks more "easy" to some people.
Ciao, Michael. _______________________________________________ dev-tech-crypto mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-crypto
