Feature Addition: Additional flag to specify which user's ~/.ssh/authorized_keys to add/rm from

[zph]

Thanks for your work on this project @chrishunt !!!

Conversation on Twitter: https://twitter.com/marksim/status/343024276699500546

I'm considering pair programming (with @marksim) to add an option to github-auth, which would add an additional commandline flag.

The feature: be able to specify which /home/USER/.ssh/authorized_keys will have key added or removed from.

The use-case: I'd prefer to not need to 'su pair' & then run github-auth as pair. Instead, I'd prefer to have github-auth request sudo access and do that task from my primary user account.

Does this sound like a useful feature for anyone else?

@zph

[marksim]

Not having this feature is nearly the entire reason for making the script at the top of this blog post here: http://blog.quarternotecoda.com/blog/2013/06/06/quick-script-for-tmux-pair-sessions/

[zph]

And here's the stab that I've taken so far at this issue (along with generally discussing how to pair & setup a box):

http://www.civet.ws/2013/06/dont-fear-pair-programming-a-guide-to-starting/

But after @marksim mentioned github-auth, it seems like a good idea to patch github-auth for this use-case :)

[chrishunt]

Cool! I read that blog post earlier. I like the feature.

The constructor of KeysFile takes a path in the options, so it shouldn't be too much work: keys_file.rb#L11

You may want add a --path option that takes the absolute path (not just user).

$ gh-auth --path /Users/pair/.ssh/authorized_keys add chrishunt

You could rescue GitHub::Auth::KeysFile::PermissionDeniedError and ask for sudo or something.

[chrishunt]

or maybe --keys-file ?

Not sure, whatever you think is best 😃

[marksim]

Thanks for the suggestions Chris!

[zph]

Thanks for the suggestions and pointing us to the appropriate constructor 🎯

Guess we're setup for something to do during our next pairing session @marksim 😄

[chrishunt]

🎈 🎉

[chrishunt]

Closed via #18