News for hackers. Stuff that matters.
Re:Crypto 101 by skrowl on Wednesday March 19, 2014 @03:52PM (#7431338)
Anyone else only get:

<html><head><title>Processing Failed</title></head><body><b>Processing Failed</b></body></html>

Re:Crypto 101 by lvh on Wednesday March 19, 2014 @03:53PM (#7431344)
Yep. Too many open file descriptors. I'm trying to figure out how to fix that without taking the site down now.

EDIT: It should be hopefully slightly better right now...

Re:Crypto 101 by Mithrandir on Wednesday March 19, 2014 @04:27PM (#7431622)
Re:Crypto 101 by kmtrowbr on Wednesday March 19, 2014 @04:42PM (#7431716)
The "processing failed" banner is quite ironic considering our recent collective experiences with cryptography. Why the Mt.Gox failure and so many other hackings and exposures of supposedly-private data? "Processing Failed"
Re:Crypto 101 by marshray on Thursday March 20, 2014 @04:59AM (#7434484)
I don't read "Processing Failed" as an indication of hacking or a data breach.

Sounds to me more like an overloaded website falling back to a small static error page.

Re:Crypto 101 by lvh on Thursday March 20, 2014 @05:42AM (#7434581)
Yep, that's exactly what happened. Combination of:

1) me not understanding docker and forgetting to increase the host nofiles;

2) me not understanding upstart (because I don't normally use ubuntu...) and not realizing that it conveniently ignores /etc/security/limits.conf :)

It's obviously not a data breach: I don't actually store anyone's data :)