Repository navigation
Demo KeyBox at next WG Meeting #806
Description
I would like to demo KeyBox at the next Build WG meeting.
The main selling points to me:
- It's free! (it's all apache 2 license)
- It makes deploying new SSH keys very simple to all machines
- It makes revoking access for a certain key very quick and simple (great for temp access)
- It's very easy to audit who has access to what
- It also has some exciting other features such as web based terminals and easy script deployment
My plan would be to set up a KeyBox server on a small linux machine and configure this for the community to manage all of their machines. I have been successfully using this system for managing key access to the AdoptOpenJDK build farm and think that it's a suitable candidate for the Node.js Community to also use.
Please note that I am in no way affiliated with KeyBox, I just love how great it is!
Activity
rvagg commentedon Jul 21, 2017
this sounds promising, we've the times where we've had to revoke and replace the global keys we use have been pretty painful (Ansible has helped somewhat) and giving temporary access to collaborators usually involves forgetting that they were given access and leaving their keys in place
gdams commentedon Jul 21, 2017
@rvagg, this is the exact issue that I was experiencing with AdoptOpenJDK before I started using KeyBox
mhdawson commentedon Aug 17, 2017
Lets plan to have on the agenda for the next meeting which is Aug 22nd at 4 EST. Next week !
gibfahn commentedon Aug 22, 2017
@gdams agreement on this was that waiting till next meeting (3 weeks, 12th September) is fine, but if we don't hit that target it might be worth arranging a one off meeting to demo this. If you're going to be busy by the 12th, we should maybe look at organising something (probably on a Tuesday evening).
mhdawson commentedon Sep 14, 2017
Demo happened, closing
gibfahn commentedon Sep 14, 2017
@mhdawson I think at the meeting we said we should keep this open for other feedback, and for progress on getting it running.
Obviously it can just be a new issue, either way.