kmoe

Makefiles and Go vendoring

TL;DR

Vendoring in Go 1.13+ probably doesn't work the way you expect, and neither do environment variables in Makefiles. If you maintain a Terraform provider, it's likely your vendor/ directory is being completely ignored during builds and releases.

Add this to the top of your Makefile/GNUMakefile:

.EXPORT_ALL_VARIABLES:

kmoe

❤@libr ➜  ~  vagrant plugin install vagrant-vmware-desktop --debug                        
 INFO global: Vagrant version: 2.0.3
 INFO global: Ruby version: 2.5.1
 INFO global: RubyGems version: 2.7.6
 INFO global: VAGRANT_EXECUTABLE="/opt/vagrant/embedded/gems/gems/vagrant-2.0.3/bin/vagrant"
 INFO global: VAGRANT_INSTALLER_VERSION="2"
 INFO global: VAGRANT_DETECTED_OS="archlinux"
 INFO global: VAGRANT_INSTALLER_EMBEDDED_DIR="/opt/vagrant/embedded"
 INFO global: VAGRANT_INSTALLER_ENV="1"
 INFO global: VAGRANT_NO_PLUGINS="1"

kmoe

var ws = require("nodejs-websocket")


let Game = function() {
	this.gameProgress = 1;
	this.playerConnections = [];

	this.startGame = function() {
		this.demandResponse();
	};

kmoe

0 info it worked if it ends with ok
1 verbose cli [ '/home/travis/.nvm/versions/node/v8.5.0/bin/node',
1 verbose cli   '/home/travis/.nvm/versions/node/v8.5.0/bin/npm',
1 verbose cli   'i' ]
2 info using npm@5.3.0
3 info using node@v8.5.0
4 verbose npm-session ea0ebb0ccedf29ce
5 silly install runPreinstallTopLevelLifecycles
6 silly preinstall mercury@
7 info lifecycle mercury@~preinstall: mercury@

kmoe

package main

import (
	"log"
	"time"

	"golang.org/x/net/context"
	"google.golang.org/grpc"

	pb "github.com/jzelinskie/grpc/simple"

kmoe

IoT Security

Talks

All links are to slide decks.

title	author	year
A surface area approach to pen-testing the IoT	Daniel Miessler	2015
Cameras, Thermostats, and Home Automation Controllers - Hacking 14 IoT Devices	Wesley Wineberg	2015

kmoe

This presentation is going to be about the past—so we gain more understanding of the history we’re working with and what we mean when we say ‘magic’ and ‘witchcraft’. Also some of the dangers and problems in the history.

First a note: I’m going to use the words ‘spirituality’ and ‘religion’ interchangeably. Many people are averse to the word ‘religion’ because they associate with any number of oppressive institutions. But I feel spirituality is unnecessarily vague and also focuses on a spirit vs matter dualism.By religion I mean reverence for some kind of power beyond everyday human experience.

Not going to focus on witch-burnings or WITCH, but 19th and 20th c intellectual history leading up to modern witchcraft.

Also I'm going to focus mostly on England because that's where we are + what I know the most about. 

[slide]

kmoe

module['exports'] = function kahootDeskbeers(hook) {
  
  // Usage:
  // /deskbeers balance - gets your balance
  // /deskbeers drink [number] - records that you drank [number] beers
  // /deskbeers pay [amount] - records that you paid the pig/George £[amount]
  
  var DESKBEERS_ADMIN_USERNAME = 'george';
  var USAGE = 'Usage: `/deskbeers balance` to get your balance, `/deskbeers drink [number]` to record that you drank [number] beers, `/deskbeers pay [amount]` to record that you paid £[amount] to George or the pig.';
  

kmoe

module['exports'] = function echoHttp (hook) {

  console.log("Console messages are sent to /logs");

  console.log(hook.params);

  console.log(hook.req.path);

  console.log(hook.req.method);
  

kmoe

module['exports'] = function highFive(hook) {

  // hook.io has a range of node modules available - see
  // https://hook.io/modules.
  // We use request (https://www.npmjs.com/package/request) for an easy way to
  // make the HTTP request.
  var request = require('request');

  // The parameters passed in via the slash command POST request.
  var params = hook.params;