Nathan Basanese v6

This file was moved into the Mailveope wiki.

HOWTO: Installing Vault On AWS Linux

This is quick howto for installing vault on AWS Linux, mostly to remind myself. At the end of this tutorial, you'll have a working vault server, using s3 for the backend, self signed certificates for tls, and supervisord to ensure that the vault server is always running, and starts on reboot.

Setting up S3

First things first, let's set up an s3 bucket to use as the storage backend for our s3 instance.

From the AWS Mangement Console, go to the S3 console.
Click on the Create Bucket button

Keybase proof

I hereby claim:

I am v6 on github.
I am cx (https://keybase.io/cx) on keybase.
I have a public key whose fingerprint is CAF6 7506 C529 5624 CF6E 0C76 E183 23D2 1627 70CA

To claim this, I am signing this object:

Run Book / Operations Manual

Table of Contents
System Overview
- Service Overview
- Contributing Applications, Daemons, and Windows Services
- Hours of Operation
- Execution Design
- Infrastructure and Network Design
- Resilience, Fault Tolerance and High-Availability

Conditional Vagrant environments

2 options to start vagrant

command line with pass-through variable or alias

Run while passing variable to vagrantfile

$ ENV='local' vagrant up

Add an alias

Introduction

This is about documenting getting Linux running on the late 2016 and mid 2017 MPB's; the focus is mostly on the MacBookPro13,3 and MacBookPro14,3 (15inch models), but I try to make it relevant and provide information for MacBookPro13,1, MacBookPro13,2, MacBookPro14,1, and MacBookPro14,2 (13inch models) too. I'm currently using Fedora 27, but most the things should be valid for other recent distros even if the details differ. The kernel version is 4.14.x (after latest update).

The state of linux on the MBP (with particular focus on MacBookPro13,2) is also being tracked on https://github.com/Dunedan/mbp-2016-linux . And for Ubuntu users there are a couple tutorials (here and here) focused on that distro and the MacBook.

Note: For those who have followed these instructions ealier, and in particular for those who have had problems with the custom DSDT, modifying the DSDT is not necessary anymore - se

Open a webpage that uses the CA with Firefox
Click the lock-icon in the addressbar -> show information -> show certificate
the certificate viewer will open
click details and choose the certificate of the certificate-chain, you want to import to CentOS
click "Export..." and save it as .crt file
Copy the .crt file to /etc/pki/ca-trust/source/anchors on your CentOS machine
run update-ca-trust extract
test it with wget https://thewebsite.org

	# Please see the following blog post for more information:
	#
	# https://www.hashicorp.com/blog/using-hashicorp-vault-with-chef.html
	#

	resource_name :vault_secret

	property :path, String, name_property: true
	property :destination, String

	%YAML 1.2
	---
	Application:
	license_key: REPLACE_WITH_REAL_KEY
	wake_interval: 60
	#newrelic_api_timeout: 10
	#proxy: http://localhost:8080

	#apache_httpd:
	# name: hostname

	[Unit]
	Description=BCoin server
	After=network.target auditd.service

	[Service]
	User=root
	ExecStart=/home/bcoin/bcoin/bin/bcoin --network "testnet" --nodes "seed.tbtc.petertodd.org,testnet-seed.bluematt.me,testnet-seed.bitcoin.schildbach.de" --host "\'::\'" --public-host 104.197.196.156
	Type=simple
	RestartSec=60
	Restart=on-failure