|
3 months ago | |
---|---|---|
cli | 3 months ago | |
docs | 3 months ago | |
server | 3 months ago | |
vendors | 3 months ago | |
README.md | 3 months ago | |
revoke_orchestration.yml | 3 months ago |
The simplest SSH CA I can think of.
Nowadays it's wide spread to save your public ssh keys in SCM Tools like GitLab, Gitea, Github etc.
So why not use this source for your SSH CA?
Most companies self-hosted a SCM Tool already and possible also bind it to a directory. When the linux server are also bind to the same directory - awesome. That are perfect conditions, because you even don't need to orchestrate the users to all your servers.
You only need to glue things together. Here comes hausschrat to play.
A user needs to create an access token in their SCM Tool with read_user
permissions only. With this access token, hausschrat can verify the user, fetch the users belonging public key, sign them and response with the certificate.
Take a look at docs/src/
folder or read it online: https://hausschrat.eu
Users just needs a ~/.config/hausschrat.yml
file.
default:
server: http://localhost:8080 # hausschrat backend
scm_url: https://git.osuv.de
api_token: ... # go to your scm tool and create a `read_user` access token.
user: m
key: markus@dell
expire: +5h
cert_file: ~/.ssh/test-cert.pub
$ hausschrat
start issuing certificate for default
done
Contributions and issues are welcome on github.com or gitlab.com
host | category |
---|---|
https://git.osuv.de/m/hausschrat | origin |
https://gitlab.com/markuman/hausschrat | pull mirror |
https://github.com/markuman/hausschrat | push mirror |