22172 - Mcollective ssh key security should allow a custom per-identity authorized keys file

Node verifier should never use ssh agent.

mcollective is a long running process which is run as a daemon. It's never correct for the _server_
to use the user who starts it's agent forwarding to verify things with, as this will stop working
as soon as the user who started the daemon logs out
22172 - Mcollective ssh key security should allow a custom per-identity authorized keys file

Be able to interpolate the username into authorized_keys path

We don't want users to be able to add arbitrary ssh keys without oversight,
ergo we push out a set of authorized keys files to machines with puppet
in a directory the user doesn't have write access to.
22172 - Mcollective ssh key security should allow a custom per-identity authorized keys file

Bump version and update Changelog
maint: fix changelog
Fix typos in documentation
Merge pull request #3 from adamgibbins/documentation_typo_fixes

Fix typos in documentation
maint - add travis configuration

Add travis-ci configuration so we can auto-test pull requests.
Merge pull request #5 from richardc/add_travis

maint - add travis configuration
don't use Etc.getlogin

I discovered that `mco` would become confused when called after a `su` or via Jenkins.

additionally, RDoc states:
"Returns the short user name of the currently logged in user.
Unfortunately, it is often rather easy to fool getlogin().
Avoid getlogin() for security-related purposes. [1]

replacement code taken from a bug report on the `foreman_god` project. [2]

also includes updates to the rspec tests. thanks to richardc for help!

[1] http://ruby-doc.org/stdlib-1.9.3/libdoc/etc/rdoc/Etc.html#method-c-getlogin
[2] https://github.com/embarkmobile/foreman_god/issues/1
Merge pull request #6 from neoice/master

don't use Etc.getlogin