If read, why not write?

Some time ago I wrote a script to create an arbitrary self signed certificate. Then I made a DevOps pipeline task out of it. Now, I'm wondering about the same logic, running interactively.

Full circle with a gap at 11 o'clock

Some time ago I've claimed that I've run a full circle on a TLS certificate lifecycle. Well, there was one more kink in that circle that I've failed to acknowledge at the time.

Full circle

Following up from my last post about generating a CSR, I went through the motions of testing the full cycle for said CSR. I'd sign it with a bogus (but locally trusted) authority certificate, install the signed cert locally, export the PFX, install it on a Web server, select the cert for TLS on an IIS website, and hit it with a bunch of desktop browsers. The certificate works as expected.

CSR with PowerShell

Following up from a past post, I've decided to put together a PowerShell script for generating a certificate signing request for a certificate authority to sign. Here's the script, but some commentary is in order.

CryptoAPI issue I've found

Continuing with the crypto theme, this is a story about an issue in Microsoft CryptoAPI that I've discovered a few years ago. It was originally posted at an MSDN forum, but I thought I'd rather republish it here. I've used some pretty deep magic to get to this result.

OpenSSL vs. the Microsoft crypto stack

UPDATE: the same with PowerShell.

I'd like to publish a Microsoft Word VBA macro for my co-workers. I would also like to have it digitally signed, so that Word doesn't complain about scary insecure macros.