apazgo's comments

Problem with `kr add user@bastion` is that you as `user1` won't normally have access to ssh as `user2`, but "authenticating as one user but modifying another" would work of course. Maybe add a option for team-members to save their username for servers, then mass-add would be easy :)

1. All team actions should be prefixed under "kr team", right now i don't know what happens if i run "kr add" if i only want to add myself to a server, ie outside my team.

2. What user's 'authorized_keys' would "kr add" write with a team? I don't want a team to share a single user.... luxury problem, but hey.

3. Make it possible to try local keys before krypton

4. Great work!