This is part of a blog post I wrote: https://debugging.works/blog/tpm-explained/
- I use it on Arch Linux (systemd 257.3-1)
- Install dependency:
yay tpm2-tools(5.7-1)
This is part of a blog post I wrote: https://debugging.works/blog/tpm-explained/
yay tpm2-tools (5.7-1)| package main | |
| import ( | |
| "context" | |
| "fmt" | |
| "log" | |
| "net/http" | |
| "golang.org/x/oauth2" | |
| "golang.org/x/oauth2/google" |
| FROM madnight/docker-alpine-wkhtmltopdf as wkhtmltopdf_savior | |
| # STAGE for bundle & yarn install | |
| FROM ruby:2.4.3-alpine3.7 as builder | |
| ENV CA_CERTS_PATH /etc/ssl/certs/ | |
| ENV RAILS_ENV production | |
| ENV RAILS_LOG_TO_STDOUT true | |
| ENV RAILS_SERVE_STATIC_FILES true |
The Z-Stick does bi-directional communication over a UART. The connection speed is 115200, '8N1'. There are "requests" and "responses". The client software can make requests to the Z-Stick, and it will send responses. But it seems the Z-Stick can make requests of the client software too. I have yet to figure out the requests the Z-Stick sends to the client software.
| const async = require('async'); | |
| const google = require('googleapis'); | |
| const k8s = require('kubernetes-client'); | |
| const container = google.container('v1'); | |
| const PROJECT_ID = 'node-example-gke'; | |
| const ZONE = 'us-east1-b'; | |
| const CLUSTER_ID = 'node-example-cluster'; | |
| const NAMESPACE = 'default'; |
| 'use strict' | |
| var gulp, sass, babelify, browserify, watchify, source, util; | |
| gulp = require('gulp'); | |
| sass = require('gulp-sass'); | |
| babelify = require('babelify') | |
| browserify = require('browserify'); | |
| watchify = require('watchify'); | |
| source = require('vinyl-source-stream'); |
| var production = process.env.APP_ENV === "test"; | |
| var gulp = require('gulp'); | |
| var gutil = require('gulp-util'); | |
| var sass = require('gulp-sass'); | |
| var cssmin = require('gulp-minify-css'); | |
| var prefix = require('gulp-autoprefixer'); | |
| var newer = require('gulp-newer'); | |
| var print = require('gulp-print'); | |
| var notify = require('gulp-notify'); | |
| var batch = require('gulp-batch'); |
I've been using a lot of Ansible lately and while almost everything has been great, finding a clean way to implement ansible-vault wasn't immediately apparent.
What I decided on was the following: put your secret information into a vars file, reference that vars file from your task, and encrypt the whole vars file using ansible-vault encrypt.
Let's use an example: You're writing an Ansible role and want to encrypt the spoiler for the movie Aliens.