Re:Do-nothing scripting: the key to gradual automation
by wtetzner on Monday July 22, 2019 @09:22AM
(#20497725)
Yeah, at our company things are done in the reverse of that script: the user generates their SSH keys, and there's a process they use to register the public key with the rest of the system.
[ Parent
| on HN ]
Re:Do-nothing scripting: the key to gradual automation
by minxomat on Monday July 22, 2019 @10:44AM
(#20498429)
I sometimes use GitHub for this. A developer's most up to date keychain is probably their GitHub account, so granting them access is as simple as
curl -Ls github.com/turbo.keys >> ~/.ssh/authorized_keys
Simplified of course. A script is usually used to revoke that access shortly after. Plus 2FA SSH.
Re:Do-nothing scripting: the key to gradual automation
by rmetzler on Monday July 22, 2019 @11:59AM
(#20499283)
Gitlab also has a keys URL, but I can’t say if it’s available for unauthorized clients from the top of my head (currently on mobile). For me it’s usually the fastest way to authorize other team members.
Re:Do-nothing scripting: the key to gradual automation
by yellowapple on Tuesday July 23, 2019 @08:22PM
(#20511365)
I had no idea about github.com/$USER.keys. That's handy as hell.
Re:Do-nothing scripting: the key to gradual automation
by NikolaeVarius on Monday July 22, 2019 @10:54AM
(#20498542)
Huh, never occurred to me to do it this way.