4 ms·
This is a pretty great article. We do a lot of this as standard status quo at my company (https://verygoodsecurity.com https://verygoodsecurity.com) and we're a
by mahmoudimus 8y ago
This is a pretty great article. We do a lot of this as standard status quo at my company (https://verygoodsecurity.com https://verygoodsecurity.com) and we're about to deploy a full suite of google pixelbooks as well as primary computers instead of macs.
If there's more interest here, email me and I'll write up a lot of what we do -- but this post is a great start! We are planning on open-sourcing a lot of the tools that we built to achieve SOC2, PCI DSS, HIPAA, etc.
- gustavmarwin 8y agoI'd love to read more on what you guys do! The first question I would have would be: since you're about to be using Pixelbooks, what happens if someday your Google login get disabled for some random internal Google reason? I'd love it actually if Pixelbooks could be de-googlized, or even better, if Qubes-OS could run on Chromebooks. One can dream. :-)
- gustavmarwin 8y agoJust to clarify: I know many things can be done once you put your Chromebook in dev mode, however once in that mode, your Chromebook becomes a lot more vulnerable. As opposed to on Android, where you can unlock without compromising on security, particularly true on and only on Pixel phones, as can be seen with CopperheadOS.