Why does GMail hate end-to-end encryption?
Its idea of enterprise S/MIME support is asking users to upload their *private* keys in PKCS12 bundle so Google can decrypt their messages for them
1/3pic.twitter.com/06RKtGpxhM
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
That's an odd question, we've already established this isn't end-to-end encryption, so the key is needed for normal operation of the client, right? I think implication is there are no benefits from managing S/MIME this way, but that doesn't seem true (certainly a tradeoff tho).
Agreed that being able to send encrypted email from web UI is useful But most S/MIME usage is selective & only small fraction of incoming is encrypted Does escrowing private key to Gmail for the 1% make sense vs falling back on desktop client?
Or, can we separate encryption a& decryption sides of this feature, and make the latter optional? IMO more people could benefit that way (including those who won't escrow their keys by policy or can't because keys are in hardware)
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.