3 ms·
i think i read all the blog posts and announcements, yet i can't for the life of me find a technical explanation of what exactly this does. it looks like it c
by a-dub 4y ago
i think i read all the blog posts and announcements, yet i can't for the life of me find a technical explanation of what exactly this does.
it looks like it could be like s/mime, or possibly a scheme for encrypting the contents of messages stored in gmail accounts. where are the keys stored? what is the threat model?
can anyone enlighten?
- _23sd 4y agoIt’s primarily for industries with strict regulatory/compliance requirements on managing sensitive data. The more detailed description is at [1]. Keys are stored in a cloud service, admins and end users use SSO to retrieve a key whenever they need to access an encrypted document. This is supposed to let companies do things like enforce rules on forwarding or printing sensitive emails, revoke access to particular documents if needed, and reduce the scale and risk of leaks if Google or an individual user account was breached. Of course, it’s not perfect in practice. [1] https://support.google.com/a/answer/10741897 https://support.google.com/a/answer/10741897
- a-dub 4y agook so it's basically like 0bin for google apps storage. that's a step in the right direction... it's confusing because they present it in the context of email. although i suppose that's probably what customers are most worried about. corporate scandals tend to frequently be rooted in leaked internal communications.
- zugi 4y agoCan you only send encrypted messages to recipients who also use Google? If it isn't S/MIME then as far as I'm concerned it almost isn't email. Anyone can already make encrypted ZIP files or other proprietary encrypted attachments and send them via email. If it's not S/MIME, it feels like just a convenience layer on top of that.