3 ms·
"Assume breach" was the phrase they taught us at Microsoft (at least in 2016). I assume everything is compromised. So I make public and distribute/decentralize
by breck 4y ago
"Assume breach" was the phrase they taught us at Microsoft (at least in 2016). I assume everything is compromised. So I make public and distribute/decentralize as much as possible.
I #BuildInPublic as much as possible on GitHub and GitLab and dedicate everything to public domain (http://pledge.pub/ http://pledge.pub/).
I have a number of computers and can be up and running on a new Macbook in under an hour.
I run multiple mirrored web sites.
I distribute crypto keys across ledgers and safety deposit boxes in multiple states.
Most importantly: I don't pay for insurance (except for mandated auto and homeowners). Instead, everyday I go out there and try to deliver as much good to as many people as possible, knowing that the best insurance when bad luck strikes isn't some check from some corporation, but the helping hands from your fellow neighbors.
- tete 4y ago> "Assume breach" was the phrase they taught us at Microsoft (at least in 2016) security(7) man pages on FreeBSD and DragonFly, I think originally written by Matt Dillon also tells you to assume breach for example for the root password, which is why you shouldn't allow password based logins over SSH, etc. This is the earliest I could find, and it already contains assuming breach in 1998. https://github.com/freebsd/freebsd-src/commit/f063d76ae36ca42484455bf5275782b00543ce20#diff-871514060890c6597efd2bf37271654b1f056ef51290df75ecdde2b67978baf2R90-R91 https://github.com/freebsd/freebsd-src/commit/f063d76ae36ca4... Does anyone have an idea on how to see the file and its history from where it was moved? I checked 4.4 BSD, because the copyright mentions Berkley, bit I failed to find anything in the man1 directory.