4 ms·
Agreed, but even if your laptop HDD is encrypted, you still need to do a risk assessment as to the value of the data/code before trusting the drive encryption t
by packetslave 15y ago
Agreed, but even if your laptop HDD is encrypted, you still need to do a risk assessment as to the value of the data/code before trusting the drive encryption technology.
Example: Google doesn't allow source code on laptop HDDs, even though we use full-disk encryption. The risk of a bug/attack on FDE is non-zero, even though it is probably pretty small, so it's enough to tip the scale.
(edit: grammar)
- sliverstorm 15y agoSo does that just mean no programming via laptops, or do you do your work on network drives? Or perhaps remote interactive session?
- packetslave 15y agoProgramming via laptop is fine, as long as the source (or build artifacts) aren't stored on the local HDD. Some engineers use VNC/NX remote sessions, some use SSH+emacs/VIM, some use sshfs or NFS and run Eclipse or whatever locally.
- webjprgm 15y agoI was going to ask wether using full-disk-encryption on Apple's Lion OS (aka "File Vault 2") would be sufficient. It sounds like Google is uncertain that it is. Still, Apple's FDE is much better than no encryption at all! No excuse, NASA should require FDE on all laptops (even if they're working on something better eventually).
- thatoneguy 15y agoHere's our solution that was recently open-sourced: http://google-opensource.blogspot.com/2012/02/cauliflower-vest-end-to-end-os-x.html http://google-opensource.blogspot.com/2012/02/cauliflower-ve...