I'd just like to reassure everyone that we aren't vulnerable to the "Heartbleed" security issue that was recently found in OpenSSL. Given our...alternate security measures, not only do the tests for it (such as ) not find it, they actually get confused by what we're doing.
We've known about this one for a while (right around the time it was introduced, back in 2012), and in fact have been using it in some of our mining / controller software. It's being stomped out rapidly now, but even though it'll still linger on for a good bit, certain...parties might be honey-potting scanners now, so I'm recommending we pull it, or at least modify it to only continue on sites it's succeeding at, auto-remove sites that get fixed, and drop the piece that scans for new targets. My full run-down on it can be found in the chained room, in the shape of that nice Heartbleed logo that they're using. (Looking at you here, Ramon, since you've been a lot more involved in that piece of it.)