Skip to main content


An Open Letter to My Friends in Sales and Biz Dev

To my Friends in Sales:
I get a lot of sales calls, and I don't mind it, but it means that I've got to keep them quick or they quickly take up too much time. So I created this list of tips for you so we can make the best of your time and mine: I will ask questions on the introductory call about features and prices. Please be ready to answer those. I want that information so I can decide if it would be worth your and my time for a demo. If you don't have the information or can't give it to me, then that's probably as far as the call will go.I appreciate that you are trying to be friendly by talking sports and weather etc., but I'd rather get to the point. Keep it on topic please.Please don't use leading questions like: "If you could succeed in this difficulty, how would that help you?" and such. I know my own situation just fine, what I don't know is your product. So let's keep the conversation on that please.If I decide to get your product,…
Recent posts

Strengthening the Weakest Link

Employees are frequently cited as being the weakest link in security. Rather than argue this point, I'm just going to reference a few articles here and move on (Fortune, Fraud-magazine, Forbes). Now, in general, employees are considered the weakest link because they don't always make smart decisions.

For example, in one company I was at, a phishing email was sent out to many of the employees. The email was from "Emily", the subject was "New Pics" and the body was simply "Check out my latest pics" with a link. I was amazed at how many people clicked on that link and consequently installed a virus. A similar attack came a few months later, but spread over chat instead. I felt that we needed to train our employees better.

I should note here that there is a good argument for security software that is idiot proof, that prevents employees from hurting their networks or losing information. I entirely believe in using such software, but hackers are very s…

Helping our Children to Succeed in this New Digital World

I was asked by to write an article for them about my time teaching kids how to code. If you'd like to read it, you can see it here.

I was in 6th grade, and we were brought into the computer lab for our last lesson in coding. On the screen blinked a green cursor in one section of a screen, and there was a solid green triangle in the other. About two dozen children anxiously awaited for their next challenge. ...  Read the rest here.

Remote two-factor authentication, with ssh public keys, and google authenticator

Installing and using the Google Authenticator was pretty easy. I give credit to for their straight forward instructions on using it. However, I wanted to change some things about their setup. You'll find my instructions to be similar to theirs, but with some important differences. This was done on Ubuntu 14.04.

Install the google auth pam module:
sudo apt-get install libpam-google-authenticator Login as the user you will be using the authenticator with, and run the following command:
google-authenticator Set up Google Authenticator on your phone using either the QR code it generates, or manually type it in.

Now, this is where I diverge a little from the howtogeek version. Open up the /etc/pam.d/sshd file on your machine. Put this at the very top of the file:
auth sufficient accessfile=/etc/security/access-local.conf auth sufficient And then comment out the following line in the same file:
#@include common-auth  Now, open up y…

Which rpm did this file come from?

Need to know what rpm a certain file came from? Sometimes I want a certain program on one machine that I have on another, and my rpm searches come up blank. This happened with a program that I needed called lockfile, that I couldn't figure out how to install. It ended up being in the procmail-3.22-203.1 rpm.

The command I used was this:
rpm -qf /usr/bin/lockfile I found that tip here: