As someone who had to automate OpenSSL workflows often enough (fortunately, way in the past), the described automated signing workflow sounds much like an autom

As someone who had to automate OpenSSL workflows often enough (fortunately, way in the past), the described automated signing workflow sounds much like an automated signing workflow. While I hope that the mentioned 200 character line width is being used more as a literary device (elevating snarkiness) than for an actual argument, I fear the latter. Having said that, don't all (public) SSL signing workflows use web technologies in some way? To me, using some web technologies (aka 'kool aid') specifically made for this purpose, such as jwk, feels better than having some intermediaries sending back and forth CSRs, keys, and whatsoever using home-made interfaces and data structures.