Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The only thing I can think of is they were trying to defend from a very severe threat very quickly. But... it seems like if they tested this on one machine they'd have found it.



Unless that threat was a 0day bug that allows anyone to SSH to any machine with any public key, it was not worth pushing it out in haste. Full stop. No excuses.


Can't boot, can't get cracked! Big brain thinking.


That’s the most charitable hypothesis, and I agree could be possible!

I myself have ninja-shipped a fix a minor problem, but then caused a worse problem since I rushed it.


I pushed a one-character fix and broke it a second time


I'd love to know what the original threat was. I hope it was something dumb like applying new branding colors to the systray indicator.


"works on my machine" at Internet scale. What a scary thought




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: