3,020 karma · joined March 15, 2010
https://signal.me/#eu/tJgEd9pEdyiankVrQI3j1y2n5jPNLW7y4cZ09RJ0Vhjh2mihvq9IwL6toyfg8Kma
Yes.
> if they start now
We started last year with e10s, testpilot and dozens of other improvements.
If you haven't used this, try it out, it's a fantastic feature. I use it all the time to send a page I'm reading on my phone to my laptop, and vice versa.
If you leak a password to any public location, there is only one reasonable course of action: CHANGE IT!
Don't even bother rewriting the commit. Focus on changing that password right away, and while you're at it, figure out a better way to manage your secrets outside of your source code in the future. Mistakes happen, but they shouldn't be repeated.
Just change the leaked passwords, don't try to hide the commits.
More info: https://wiki.mozilla.org/Security/Guidelines/OpenSSH
It might be easier to resell someone else's certificates.
> In cryptography, a zero-knowledge proof or zero-knowledge protocol is a method by which one party (the prover) can prove to another party (the verifier) that a given statement is true, without conveying any information apart from the fact that the statement is indeed true.
source: https://en.wikipedia.org/wiki/Zero-knowledge_proof
z.cash is a zero knowledge system and has a good definition of it on its FAQ:
> Zero knowledge proofs are a scientific breakthrough in the field of cryptography: they allow you to prove knowledge of some facts about hidden information without revealing that information. The property of allowing both verifiability and privacy of data makes for a strong use case in all kinds of transactions, and we’re integrating this concept into a block chain for encrypting the sender address, the recipient address, and the amount. A block chain that encrypts transaction data (making it private) and lacks zero-knowledge proofs also lacks the assurance that all the transactions are valid. This is because the nodes in the network can’t determine whether the sender really had that money or whether they previously sent it to someone else, or never had it in the first place. The encrypted data becomes unverifiable by network nodes.
The focus on automation, and it being called DevOps, is simply an evolution of the work of sysadmins. The same way devs evolved toward TDD and other modern programming techniques.
The trackpoint is the only thing that keeps me on Lenovo laptops (Carbon X1, probably P50 next). I keep the touchpad disabled on my laptop.
At least the Lenovo Carbon X1 has a dongle for RJ45. Useful when that `docker pull` ends up downloading a 1.5GB container...
It's not for the faint of the heart - the volume of events to filter through requires some serious infrastructure - but it's an important component of a mature secops program.
A decade and a half ago, one of my professor once told me: "You don't learn to master Linux, you learn to accept that you can't master it." Same point, different context.
http://shop.lenovo.com/us/en/laptops/thinkpad/x-series/x1-ca...
Sure you can. Just ask a CA that has an old root trusted by XP but no longer trusted by modern browsers, and they'll issue a SHA-1 cert for you without risking to get kicked out of the truststores.
That's a multi-year process, unless they can get another CA to cross-sign their root, like LE did. I doubt other CAs will be willing to carry that level of risk given the reputation of WoSign/StartCom.