Brewer, Beardsman, Geek, Godzilla Hunter Extraordinaire

Statement of GPG Key Transition

—–BEGIN PGP SIGNED MESSAGE—–
Hash: SHA1,SHA512

Fri Dec 9 11:49:22 EST 2016

Statement of GPG Key Transition
——————————-

In order to replace my older DSA-1024 key, I have set up a new OpenPGP key, and will be transitioning away from my old key.

The old key will continue to be valid until 2017-06-01, but future correspondence should come to the new key. I would like the new key to be integrated into the web of trust.

This message is signed by both keys to certify the transition.

The old key was:

pub dsa1024/B5EE841627F7BF37 2008-08-26 Christopher Collins
Primary key fingerprint: 69E6 0653 A1A3 0600 ADB2 B3AD B5EE 8416 27F7 BF37

And the new key is:

pub rsa2048/F5752BA146234FD4 2016-12-09 Christopher L. Collins
Primary key fingerprint: 923E 0218 77DB 3F70 F614 6F62 F575 2BA1 4623 4FD4

To fetch my key from a public key server, you can do:

gpg –keyserver pgp.mit.edu –recv-key F5752BA146234FD4

If you have my old key, you can verify the new key is signed by the old one:

gpg –check-sigs F5752BA146234FD4

To double-check the fingerprint against the one above:

gpg –fingerprint F5752BA146234FD4

Finally, once you are satisfied this key represents me and the UIDs match what you expect, please sign my key, if you don’t mind:

gpg –sign-key F5752BA146234FD4

Thank you, and sorry for any inconvenience.

-Chris

—–BEGIN PGP SIGNATURE—–
iEYEARECAAYFAlhK+2UACgkQte6EFif3vzcybACg+FO1UuIK3hKA/IUIoR1CsqiM
MvsAoJ4zmeh7JjKyhlfyFDFD95G5U1pDiQEcBAEBCgAGBQJYSvtpAAoJEPV1K6FG
I0/UjM4IAKqifcolct4klHutTD3fcBy3sMoseR7cvA9mpG/TvSUUhBGEK1R+ssKI
/lGjnR2vnJVUltnS6lAUHy0GafloPEdkQhlRFimtBW+3pBKGbqVHzDwYevEqt5Qv
dOvr4UgbOvjIdt2FTl24ht8Sf14LU+znlTF77PTP9CW6hbIcAZatLrSKcWbse4cu
kQRhQQystBHLohGkCYW52IrOz1Vyy5K0NtbQm1sAkbqZqOuAV98z0EkpnMeiP0Vf
A5bJjA+Nu4XIN+OLSxYsg32KpyfFPqPfQbf3zv5i9gr6hl/gdEl2QYRK+A89kAzf
qmT97XAQmNTczFuP/OLbjc0dMALl+zM=
=YUAx
—–END PGP SIGNATURE—–

  • Chris Collins
Chris Collins • 2 min read
Apache HTTPS configuration – June 2015

Apache HTTPS configuration – June 2015

HTTPS is HTTP over TLS.  It allows you to encrypt traffic to and from your web server, providing privacy and security for your clients.  As of this writing, the world is moving ever closer to HTTPS everywhere: thanks to the Snowden documents, there’s been a big push for more privacy and security.  Major companies like Google and Mozilla are securing traffic by default for all their applications.  Cloudflare is offering free HTTPS encryption between clients and their severs.  Let’sEncrypt, a new Certificate Authority offering free, secure certificates is scheduled to open it’s doors in September.

  • Chris Collins
Chris Collins • 8 min read
Some Real-World Info on POODLE (CVE-2014-3566)

Some Real-World Info on POODLE (CVE-2014-3566)

TL;DR: Remove SSLv3 - the impact is likely very small

We’ve now removed SSLv3 from about 1000 servers in our environment. So far, we’ve only had one issue - a script used to call an API started to fail. The issue was the ruby rest client > 1.7.0. (Yes, that’s greater-than.)

Removing from Apache

SSLv3 is easy to remove in Apache. You probably want this in your ssl.conf (or whatever the equivalent is for your distro):

  • Chris Collins
Chris Collins • 2 min read
“Cloud-style” Docker Demo Container

“Cloud-style” Docker Demo Container

Completed a first pass at a minimal “Cloud-style”#Docker container. It’s sort of like an EC2 instance. You generate an ssh pem file, and pass the public key in as an environmental variable at docker run:

sudo docker run -i -t -d -P \
-e PUBKEY="$(cat ~/.ssh/my.pem.pub)" cloudbase

You end up with a CentOS container, and a user “clouduser” that has sudo w/no password rights.

I think this would be a good way to get some folks interested in Docker - perhaps offering something like this as a playground/sandbox to build interest.

  • Chris Collins
Chris Collins • 1 min read