Archive for April, 2021

First Vaccine Shot Done!

Sunday, April 18th, 2021

Microbe

I just got back from Walgreens, where I had signed up on Friday for an appointment to get the COVID-19 vaccine. Going in I had no idea what they would have in the way of lines, or which vaccine to provide, but I showed up at 9:10 am today to Get My Shot.

As it turns out, it's the Moderna vaccine, and it didn't take long because I had downloaded the Vaccine Waiver form from the Walgreens website, and filled it out before I arrived. This made it a lot easier - I just sat there, after checking in, and when it was my turn, I got the run-down from the pharmacist, and got my shot.

Simple and easy.

I giggled to myself about the band-aid, and how every kid goes through that phase of loving to have a band-aid on... 🙂 So not bad at all.

My arm felt a little stiff, as if I'd over-exercised, but not to the touch... just like a deeper, muscular ache. But it was fine.

In a few weeks, I'll go back and get my second shot. I already have my appointment, and it'll be just as quick and easy as this one was. It'll be nice to be covered.

Nice OWASP Update Tools for Node/JS

Wednesday, April 7th, 2021

NodeJS

This morning I did a little security updating on a project at The Shop - a few OWASP issues for dependencies. One had risen to a high level, so it seemed like a good time to dig into the updating process.

In the past, for Java and Clojure projects, I've had to go and look up the recent versions of each library and see if they correct the security issue, and if they do, are there other updates that I have to do in order to handle any changes from these security-related updates? It was often times a very tedious process, and doing it for Java Spring projects was almost something like Black Magic.

Imagine my surprise when I find that Node/JS already has this covered. Simply run:

  $ npm audit

and not only will it list all the OWASP security vulnerabilities, but it will also provide you with the specific npm commands to update (aka install) the specific package, and how far down the nesting tree that package sits.

Run the commands specified by the npm audit command, and you'll update just what's needed, and not have to go through the process manually. What a refreshing change to my previous encounters with fixing OWASP vulnerabilities. 🙂