Today I ran into something similar, but we have a larger user base that uses different (public and self-hosted) platforms, so just one URL won't be enough. I thought about a more general solution to the problem.
As many platforms offer a similar protocol, it would make sense to allow admins to register protos (like lp and gh) in /etc/ssh/ssh_import_id.
My ideal format for that file would look as following:
Today I ran into something similar, but we have a larger user base that uses different (public and self-hosted) platforms, so just one URL won't be enough. I thought about a more general solution to the problem.
As many platforms offer a similar protocol, it would make sense to allow admins to register protos (like lp and gh) in /etc/ssh/ ssh_import_ id.
My ideal format for that file would look as following:
{ /launchpad. net/~%s/ +sshkeys", /launchpad. net/~%s/ +sshkeys" /api.github. com/users/ %s/keys" /gitlab. com/%s. keys" /api.self- hosted- server. example. com/users/ %s/keys"
"_comment_": "...",
"URL": "https:/
"protos": {
"lp": {
"URL": "https:/
},
"gh": {
"URL": "https:/
},
"gl": {
"URL": "https:/
},
"home": {
"URL": "https:/
}
}
}
This would offer much greater flexibility and would allow us to draw on our different solutions without touching the defaults.
It might be possible even to add a hint, if the format is GH's JSON or ssh's authorized_keys as used by LP.