Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ring-change-sshkeys #43

Closed
job opened this issue Apr 26, 2012 · 3 comments
Closed

ring-change-sshkeys #43

job opened this issue Apr 26, 2012 · 3 comments

Comments

@job
Copy link
Member

job commented Apr 26, 2012

Some kind of wrapper that can manage the sshkeys for users would be nice. I imagine the following:

user types ring-change-sshkeys on a ring-node, and it will open up the preferred editor and it should like like typing 'crontab -e'.

The first few lines of the authorized_keys file that is displayed should be some comments which contain warnings and what the file means.

The user can then edit the file to it's liking and when quiting the editor the resulting data should be validated:

  • empty file is error
  • invalid keys error
  • etc

If an error is found the user should be presented with a choice: discard all changes or open the editor again.

If the file is valid, it can be emailed to ring-admins@ in puppetized format and incorporated in the repos. In the future we can automate this if we have reason to trust the system.

@ghost ghost assigned madeddie Apr 26, 2012
@job
Copy link
Member Author

job commented Apr 26, 2012

A good starting point would be if the current ~/.ssh/authorized_keys file is copied to an temporary file and the temp file is opened in the editor.

@madeddie
Copy link
Member

madeddie commented Oct 2, 2017

is this still an issue? :) should we close it?

@madeddie madeddie removed their assignment Oct 2, 2017
@teunvink
Copy link
Member

this has been implemented, any improvement on the way we're handling this can be written in issues in the ring-ansible repository. There is already one on improving the speed of deploying keys.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants