Thanks for the feedback! As stated in the blog post the idea was not new and more a kick to get more people informed about registry mirroring. Also the biggest advantage as I see it is as described in post if you have a fleet of docker hosts.

I'm almost always using salt for orchestration to keeping containers running, there will be more posts about that later.

Did put in a pull-request with this info to "shellshocker-pocs" repo.

https://github.com/mubix/shellshocker-pocs/pull/14

The repo now contains a link to a POC. https://github.com/mubix/shellshocker-pocs/commit/43592293f9...

Using salt to push out updates, easy and fast. "salt * pkg.install bash refresh=True"

Saved a lot of time again today with salt! $ salt * pkg.install bash refresh=True and then check for right version $ salt * pkg.version bash

tcpdump for the win!

Like part - "No longer will infrastructure be a “feature” to be weighed and prioritized against others in our backlog. It’s the foundation of everything we have, everything we do, and it will be treated as such."

At last! This release is a significant milestone for us as it is the first release we consider to be production ready.

Keep up the great work!

If your on Debian it's as easy as 'disable monitor', restart ntp and your safe.

Isn't the default pretty ok anyhow ? Atleast looking at the ntp.conf on a raspbian/centos/fedora here, there's

   restrict  default kod notrap nomodify nopeer noquery

The noquery stops you from dumping the peer/monitor list.