Ars is reporting that Yahoo will offer a browser plugin to offer end-to-end PGP encryption. Speculation is that it will be a JavaScript plugin, similar to what Google offered.
The problem with any of these plugins is that the browser (or at least the plug in) will have access to your private key. Nobody is quite sure that anything developed for a browser can be trusted not to leak your private key, or if Yahoo or Google could be compelled to harvest keys just as other companies like Lavabit were forced to turn over their own ssl keys.
The Google plugin was released in Beta in June.
Both would seem to get over the learning curve and offer opportunistic encryption when ever both parties are using the same service. Whether or not the plugins will try to fetch public keys from key servers is yet to be determined.
So will you trust either of these plugins?
Would you switch to reading mail in a browser for this feature?
(Score: 4, Insightful) by hoochiecoochieman on Friday August 08 2014, @04:46PM
Yahoo wants me to install a browser plugin plus some local binaries so I can read my webmail. WTF? Is HTML + Javascript not enough?
What about Android? It wants me to install an app to read my mail. It used to let me refuse and instead read it in a mobile site, but lately, when I click on the "mobile website" link it hangs forever. When trying to install the app, it asks me for permission for everything and then something else, which I can't imagine why they would ever need just to show me my email. And they've been adding more permissions to it. Fortunately they aren't asking for permission for anal probes, but I fear they'll come up with that one too, eventually.
Trust Yahoo? No fucking way.
(Score: 3, Informative) by Nerdfest on Friday August 08 2014, @06:23PM
Doesn't Yahoo support IMAP and POP? Use a different mail app, ideally open-source. I like K9, which also has a nice PGP plug-in. Why trust someone when you don't need to.
Unrelated to the parent post, but related to the topic ... is the browser plug-in open-source? If not, why not? When we talk about trust, we really should be talking about open source software. You can't trust closed source software, and even open-source must be reviewed.
(Score: 2) by frojack on Friday August 08 2014, @06:48PM
Plus 1 for K9 and APG (PGP) plugin.
According to a recent article [campaignmonitor.com] most people are reading mail on mobile devices. Of course these devices leak like sieves and we assume both K9 and APG are secure, but the permission system on android is less than ideal.
IMAP on Yahoo is flakey at best. They favor their own client, but K9 works.
Part of the problem is IMAP.
People storing tons of mail on other people's servers, where historically no warrant was required [cnet.com] to obtain it if it had been there for 180 days. The 180-day rule stems from the Electronic Communications Privacy Act, which was adopted in the era of telephone modems, BBSs, and UUCP links, and long before gigabytes of e-mail stored in the cloud was ever envisioned.
Supposedly this has changed with recent court rulings but there are conflicting rulings in different areas. Congress is still dithering [propublica.org] with different bills in house an senate.
No, you are mistaken. I've always had this sig.
(Score: 3, Informative) by Nerdfest on Friday August 08 2014, @07:48PM
If you use Android (without ART runtime), have a look at XPrivacy in the Xposed framework. It allows very fine-grained control over permissions ... too fine for most probably. I'm hoping someone manages to implement the same thing under ART.