Month: April 2015

Posted on

My Twitter Digest for 04/24/2015

Posted on

Adding 2 Factor Authentication to a Linux Laptop With Google Authenticator

Have you ever wondered how to provide additional security to your Linux desktop? Google Authenticator can help provide a two-step authentication process that requires both an authentication token and your password to log into your Linux desktop. This would require that an attacker know both your password and have your authentication device to successfully log in to your system.
A pluggable authentication module (PAM) is a way to integrate authentication methods into an API that enables different programs to be developed independent of the underlying OS authentication scheme. Linux provides a PAM system which we would take advantage of in this tutorial to integrate an additional check, along with user password, to grant access to the system.

How to Log in to Linux Desktop With Google Authenticator http://www.maketecheasier.com/login-linux-desktop-google-authenticator/

I think I’ll give 2 factor authentication a whirl on my laptop this weekend. What could possibly go wrong?

Posted on

My Twitter Digest for 04/21/2015

Posted on

Gerrit is a web-based code review tool built on top of the git version control system

Gerrit is intended to provide a light weight framework for reviewing every commit before it is accepted into the code base. Changes are uploaded to Gerrit but don’t actually become a part of the project until they’ve been reviewed and accepted. In many ways this is simply tooling to support the standard open source process of submitting patches which are then reviewed by the project members before being applied to the code base. However Gerrit goes a step further making it simple for all committers on a project to ensure that changes are checked over before they’re actually applied. Because of this Gerrit is equally useful where all users are trusted committers such as may be the case with closed-source commercial development. Either way it’s still desirable to have code reviewed to improve the quality and maintainability of the code. After all, if only one person has seen the code it may be a little difficult to maintain when that person leaves.

via Gerrit Code Review – A Quick Introduction.

This is like something that may be worth doing to help make sure at least one other person is looking over code before it gets committed. Deploying code that only one of us has ever seen is a bit of a problem around here especially when it fails.

Posted on

My Twitter Digest for 04/16/2015