| 1. | | The Unreasonable Effectiveness of C (damienkatz.net) |
| 431 points by daschl1 on Jan 10, 2013 | 384 comments |
|
| 2. | | Save your eyes, start using f.lux (stereopsis.com) |
| 423 points by jarospisak on Jan 10, 2013 | 255 comments |
|
| 3. | | Metasploit Rails 3 Remote Code Execution Hours Away (rapid7.com) |
| 398 points by tptacek on Jan 10, 2013 | 166 comments |
|
| 4. | | IBM's Watson Memorized 'Urban Dictionary,' Then His Overlords Had to Delete It (theatlantic.com) |
| 388 points by mxfh on Jan 10, 2013 | 151 comments |
|
| 5. | | Why I Won’t Be Using BetaPunch for User Testing (daniellemorrill.com) |
| 359 points by dmor on Jan 10, 2013 | 139 comments |
|
| 6. | | How to Fold a Julia Fractal (acko.net) |
| 325 points by 80x86 on Jan 10, 2013 | 49 comments |
|
| 7. | | Nokia: Yes, we decrypt your HTTPS data, but don’t worry about it (gigaom.com) |
| 321 points by rmk2 on Jan 10, 2013 | 152 comments |
|
| |
|
|
| 9. | | Amazon to Provide CD Buyers With Cloud-Based MP3s For Free (amazon.com) |
| 164 points by derpenxyne on Jan 10, 2013 | 113 comments |
|
| 10. | | Google Flu Trends (google.org) |
| 158 points by sethbannon on Jan 10, 2013 | 25 comments |
|
| 11. | | Ruby on Rails Bootcamp in Seattle (codefellows.org) |
| 158 points by danso on Jan 10, 2013 | 118 comments |
|
| 12. | | More on Postgres Performance (craigkerstiens.com) |
| 154 points by icey on Jan 10, 2013 | 42 comments |
|
| 13. | | Improved wikis with more markup options (blog.bitbucket.org) |
| 155 points by amarsahinovic on Jan 10, 2013 | 23 comments |
|
| 14. | | GIMP 2.9/2.10 Feature Preview (gimpusers.com) |
| 155 points by diminish on Jan 10, 2013 | 64 comments |
|
| 15. | | The Minimum Viable Kitchen (priceonomics.com) |
| 153 points by rohin on Jan 10, 2013 | 206 comments |
|
| 16. | | How should I deal with an employee who has slept with my wife? (workplace.stackexchange.com) |
| 147 points by DigitalSea on Jan 10, 2013 | 196 comments |
|
| 17. | | Instacart adds Trader Joe's (thenextweb.com) |
| 146 points by apoorvamehta on Jan 10, 2013 | 76 comments |
|
| 18. | | Google Effect (wikipedia.org) |
| 137 points by rsiqueira on Jan 10, 2013 | 52 comments |
|
| |
|
|
| 20. | | New Zero Day Java Vulnerability Being Exploited in the Wild (thenextweb.com) |
| 129 points by derpenxyne on Jan 10, 2013 | 89 comments |
|
| |
|
|
| 22. | | Companies that support remote workers win against those that don’t (davidtate.org) |
| 107 points by tate on Jan 10, 2013 | 29 comments |
|
| 23. | | Zurb Acquires Forrst (zurb.com) |
| 109 points by ojr on Jan 10, 2013 | 33 comments |
|
| |
|
|
| |
|
|
| 26. | | How to price something (37signals.com) |
| 96 points by mh_ on Jan 10, 2013 | 59 comments |
|
| 27. | | Rejection Therapy: A Hundred Days of 'No' (businessweek.com) |
| 95 points by eplanit on Jan 10, 2013 | 43 comments |
|
| |
|
|
| |
|
|
| 30. | | Your ATM does not use transactions (ayende.com) |
| 85 points by sabya on Jan 10, 2013 | 57 comments |
|
|
| More |
If you've never dealt with a problem like this, you may not be ready. So, here's the most important thing you need to understand:
If you have a vulnerable application anywhere, on any port it will be found and compromised. This is a spray-and-pray vulnerability. It costs attackers nothing to try, attempts don't crash servers, and so people will try everywhere.
If you lose an application in your data center / hosting environment, that's the ballgame. It doesn't matter that the app you lost was the testing instance of a status dashboard with no real data in it, because the exploit coughs up shell access on that server. If there is one thing every black-hat attacker in the world is truly gifted at, it is pivoting from shell access on one server to shell access on every goddam server.
Please make sure you didn't just patch the app servers you know/care about. THEY ALL NEED TO BE PATCHED OR RETIRED.
Additionally:
* If you are one of those "same password on a whole bunch of services people", now is a good time to make sure nothing you care about has that password. Some app somewhere is about to lose that password.
* Now would not be the worst time in the world to go to your Twitter config, hit Settings -> Apps, and scrub out all the stuff you don't use.
* Now you know why you never give 3rd party web apps your Gmail password.