Danny Fowler dannykansas

The problem

There's enough trouble with puppet's ssl model (mandatory client certs) that people go and do odd things to get around it. The primary problem is that for lab/preproduction environments, if you reinstall machines frequently, you lose access to the private key that generated the original cert but (absent some puppet cert --clean [node] operation) the cert still exists, leading to the dreaded Retrieved certificate doesn't match private key error.

A solution

Generate a single client certificate which all your nodes use, and have the master determine node names from facter rather than the SSL DN. This way you can re-install nodes with impunity and as long as your bootstrap plops down the correct config and the cert+key, you don't have any more SSL issues.

The caveats

If you have autosign turned on, this change represents a shift in security tradeoffs: you can turn off autosign and therefore more tightly control which clients can talk to your server because they need to have your clie

	git clean -xfd
	git submodule foreach --recursive git clean -xfd
	git reset --hard
	git submodule foreach --recursive git reset --hard
	git submodule update --init --recursive

	var attempts = 1;

	function createWebSocket () {
	var connection = new WebSocket();

	connection.onopen = function () {
	// reset the tries back to 1 since we have a new connection opened.
	attempts = 1;

	// ...Your app's logic...

	# Start by checking if they fixed it upstream:

	brew update
	brew upgrade reattach-to-user-namespace

	# If it says it's already installed, they haven't fixed it upstream. So do this:

	# Edit the recipe:
	brew edit reattach-to-user-namespace