You know what? I don't trust Google enough to allow them to lock me out of my own systems, and I'm surprised other obviously technologically inclined people do.
You know what? I don't trust Google enough to allow them to lock me out of my own systems, and I'm surprised other obviously technologically inclined people do.
This is a common misconception of Authenticator. It is an open source implementation of OATH which works entirely offline once the initial secrets have been shared.
Using Google Authenticator for SSH accounts (via PAM) does not give Google the ability to lock you out of your systems.
Excluding severe bugs and overly paranoid scenarios, e.g. the entire Authenticator system being a convoluted plan for Google to take over your servers.
As far as I know Google Authenticator allows both time and counter based accounts. Not that it changes anything regarding the GP's misconception about accessing external services.
The application I wrote works for all the mentioned websites, e.g. Drupal, Amazon, Dreamhost, Dropbox, etc since it implements the standard HOTP specification. It is merely named G since this is the most well-known implementation and was my first use-case.