September/October 2018 issue of acmqueue The September/October issue of acmqueue is out now

Subscribers and ACM Professional members login here

Kode Vicious


  Download PDF version of this article PDF

Error 526 Ray ID: 47c8c81c68f7c5de • 2018-11-20 06:15:22 UTC

Invalid SSL certificate








What happened?

The origin web server does not have a valid SSL certificate.

What can I do?

If you're a visitor of this website:

Please try again in a few minutes.

If you're the owner of this website:

The SSL certificate presented by the server did not pass validation. This could indicate an expired SSL certificate or a certificate that does not include the requested domain name. Please contact your hosting provider to ensure that an up-to-date and valid SSL certificate issued by a Certificate Authority is configured for this domain name on the origin server. Additional troubleshooting information here.


Originally published in Queue vol. 13, no. 6
see this item in the ACM Digital Library


Follow Kode Vicious on Twitter
and Facebook

Have a question for Kode Vicious? E-mail him at [email protected]. If your question appears in his column, we'll send you a rare piece of authentic Queue memorabilia. We edit e-mails for style, length, and clarity.


Alpha Lam - Using Remote Cache Service for Bazel
Save time by sharing and reusing build and test output

Jez Humble - Continuous Delivery Sounds Great, but Will It Work Here?
It's not magic, it just requires continuous, daily improvement at all levels.

Nicole Forsgren, Mik Kersten - DevOps Metrics
Your biggest mistake might be collecting the wrong data.

Alvaro Videla - Metaphors We Compute By
Code is a story that explains how to solve a particular problem.


(newest first)

ARaybould | Sun, 28 Jun 2015 13:26:09 UTC

It is a false dichotomy to conclude that because being able to test with null encryption is important, we should accept that it is OK to ship code that could have null encryption enabled in the field. While your reply is narrowly correct, I would like to see the several paragraphs that are devoted to explaining the usefulness of null testing support being balanced with a discussion about how this could be done while protecting against it being released. Off the top of my head, I would probably go with conditional compilation (assuming that's an option here; I am guessing it is) that also puts a secret token in the binary so that release builds can be scanned for its accidental use.

I am aware that 'test what you ship' is a wise principle, but I do not think it needs to encompass all testing, and particularly not the testing of or using features that are not intended for field use.

Leave this field empty

Post a Comment:

© 2018 ACM, Inc. All Rights Reserved.