| #!/usr/bin/env bash | |
| # names of latest versions of each package | |
| export NGINX_VERSION=1.15.5 | |
| export VERSION_NGINX=nginx-$NGINX_VERSION | |
| export VERSION_LIBRESSL=libressl-2.8.1 | |
| export VERSION_PCRE=pcre-8.42 | |
| #export NPS_VERSION=1.9.32.10 | |
| #export VERSION_PAGESPEED=v${NPS_VERSION}-beta | |
This is a guide on how to email securely.
There are many guides on how to install and use PGP to encrypt email. This is not one of them. This is a guide on secure communication using email with PGP encryption. If you are not familiar with PGP, please read another guide first. If you are comfortable using PGP to encrypt and decrypt emails, this guide will raise your security to the next level.
... or Why Pipelining Is Not That Easy
Golang Concurrency Patterns for brave and smart.
By @kachayev
How to install Ubuntu 14.04.1 LTS 64-bit on a MacBook Pro Retina 15" Mid 2014 (11,3)
There are three easy to make mistakes in go. I present them here in the way they are often found in the wild, not in the way that is easiest to understand.
All three of these mistakes have been made in Kubernetes code, getting past code review at least once each that I know of.
What do these lines do? Make predictions and then scroll down.
func print(pi *int) { fmt.Println(*pi) }
| /* | |
| * Demonstrates that an RSA signature does not uniquely identify a public key. | |
| * Given a signature, s, and a message m, it's possible to construct a new RSA key | |
| * pair such that s is a valid signature for m under the new key pair. | |
| * | |
| * Requires Go version >= 1.5. Go <= 1.4 doesn't work due to a bug in the bignum | |
| * package: https://github.com/golang/go/issues/9826 | |
| * | |
| * Written in 2015 by Andrew Ayer <[email protected]> | |
| * |
| #!/usr/bin/env ruby | |
| # We're going to need a private key. | |
| require 'openssl' | |
| # Initialize the client | |
| require 'acme/client' | |
| # We need an ACME server to talk to, see github.com/letsencrypt/boulder | |
| ENDPOINT = 'https://acme-v01.api.letsencrypt.org/' | |
| #ENDPOINT = 'https://acme-staging.api.letsencrypt.org' | |
| ACCOUNT_FILE = 'account_key.pem' |
| package main | |
| import ( | |
| "fmt" | |
| "os" | |
| "os/exec" | |
| "syscall" | |
| ) | |
| func main() { |
Around 2006-2007, it was a bit of a fashion to hook lava lamps up to the build server. Normally, the green lava lamp would be on, but if the build failed, it would turn off and the red lava lamp would turn on.
By coincidence, I've actually met, about that time, (probably) the first person to hook up a lava lamp to a build server. It was Alberto Savoia, who'd founded a testing tools company (that did some very interesting things around generative testing that have basically never been noticed). Alberto had noticed that people did not react with any urgency when the build broke. They'd check in broken code and go off to something else, only reacting to the breakage they'd caused when some other programmer pulled the change and had problems.
