HN user

iliasku

30 karma

[ my public key: https://keybase.io/iliasku; my proof: https://keybase.io/iliasku/sigs/x26lYxkW8MHx0oXKhnB5yTmYRAoiQ_nkRcfOksA84MA ]

Posts4
Comments20
View on HN

I found this article useful, mostly for people who don't have similar experience dealing with large databases. It gives so many reasons on why following this path is such a bad idea. Please people, stop writing custom scripts and then run them untested on the production db. If the company doesn't pay to give you enough disk space to take a proper backup to test just quit or buy it yourself. It will save you 11 months and many hours of sleep.

"Alain Prost — Appears as Coronavirus, the Roman champion chariot driver in Asterix and the Chariot Race." say what now?

ok here's one thing almost no one mentions and is hard for me to understand: i do almost all of my development work on my desk, where i have an external keyboard of my liking connected to my macbook. i only use the macbook's keyboard when i'm travelling, and mostly for typing the first 2 letters of the website i want to open on my browser. don't understand why people fuss about so much about the keyboard: if you don't like it just use an external one. what am i missing?

tlds: they used the side-channel leakage together with rowhammer to flip bits in ssh public keys in memory from authorized_keys to convert them so they could factor them, generate a new private key and eventually log in. also, sources.list and the system gpg-keychain to point the system to a malicious repo and install a backdoored /bin/ls