git - progit ebook

how often do you get to (legally) download a $25 dollar book that has a 4.5-star review average after 80+ ratings?  once.  and here it is:

https://progit.org/

Http/2

background

1. HTTP/2 standard was published as RFC 7540 on May 14, 2015
2. based on SPDY (by google).

important stuff

1. Negotiation mechanism:  for picking http version
2. Compatibilty:  mostly backwards compatible
3. Multiplexing & Concurrency: Several requests can be sent in rapid succession on the same TCP connection, and responses can be received out of order - eliminating the need for multiple connections between the client and the server
4. Server push: The server can send resources the client has not yet requested
5. Header compression: HTTP header size is drastically reduced
6. Stream dependencies: the client can indicate to the server which of the resources are more important than the others
   
   

Strut Job

1) Stupid rusted brake line bolt.  I <3 wd40

 

2) 2 foot, 1/2" drive breaker bar.  I also <3 this thing.

 

3) the pickle fork... for popping the tie-rod end

 4) and also for killing the boot thingy and letting our the magic grease :(

 5) new strut, old strut

 

 6) old strut, bolt fits (obviously)

 7) new strut, bolt NO FIT.  (damn you amazon, you lied to me)

CarBible

awesome:
http://www.carbibles.com/

LXD, LXC and Docker

http://www.flockport.com/lxc-guide/
LXC 1.0: https://lists.linuxcontainers.org/pipermail/lxc-devel/2014-February/008165.html


http://www.flockport.com/lxc-vs-docker/

http://www.flockport.com/lxc-vs-lxd-vs-docker-making-sense-of-the-rapidly-evolving-container-ecosystem/

https://docs.docker.com/faq/
    >> What does Docker add to just plain LXC?

Docker drops LXC
    >> http://www.infoq.com/news/2014/03/docker_0_9

http://en.wikipedia.org/wiki/Cgroups

HTTPS and Certs

Currently working with the security guys to get new certificates deployed.

Our current certs are sha1 signed.. and nobody seems to like that anymore.
Google does 'security shaming' and puts a 'X-ed out lock' as imaged below:

 

Apparently when chrome v42 came out, they no longer trust sha1 signed certs with expiration dates into 2017.

Also working on replacing the SSL-termination component of our infrastructure.  Seems that when you disable SSL (to thwart poodle) it seems to disable TLS v1.2 as well.   so damnit.

Along my travels, a colleague showed me this awesome analysis tool. 

I pointed it at a really shitty configuration and it gave a nice report: