News for hackers. Stuff that matters.
Re:Return of Bleichenbacher's Oracle Threat by smhenderson on Tuesday December 12, 2017 @01:42PM (#15908204)
Anyone else get this when using the test server feature?

Host xyz.zyx added to queue.

It can take a few minutes till the test is finished. This page will be automatically reloaded.

But then the page never actually reloads?

Re:Return of Bleichenbacher's Oracle Threat by hannob on Tuesday December 12, 2017 @02:49PM (#15908843)
Sorry, this was all created in a rush. I must have removed the reloading metatag.

At the moment the queue is overfull anyway... I will make sure I improve this tomorrow, in the meantime download our tool, use testssl.sh or use the ssllabs dev test.

Re:Return of Bleichenbacher's Oracle Threat by smhenderson on Tuesday December 12, 2017 @02:53PM (#15908864)
Hey, thanks for the reply. Will do!
Re:Return of Bleichenbacher's Oracle Threat by tptacek on Tuesday December 12, 2017 @02:37PM (#15908736)
For whatever it's worth: if you're using a standard TLS stack --- Amazon's, or a stock OS distro's packaging of OpenSSL, or OpenSSL built from source, or Golang, or even at this point Java's TLS, which had this bug a few years ago and now has been pretty well tested --- it is vanishingly unlikely that you have this problem.

The things you want to test are sites behind middleboxes and sites with custom TLS implementations.

Re:Return of Bleichenbacher's Oracle Threat by greyface- on Tuesday December 12, 2017 @01:57PM (#15908330)
Yes.

The page has no javascript whatsoever, and no <meta> refresh. It can't reload itself. Manually reloading the page for hosts that have been in the queue for more than an hour yields no change. Does anyone have any evidence the test server feature does anything at all?