/Certs.txt (c4293c8abbcc8446af598c33486e1ec4561388d4) (1131 bytes) (mode 100644) (type blob)

This document tries to find a way to get rid of authorized_keys file.

Certificates may be used for user (auth user to serv) or host authentication
(auth servers to users).

Certificate has a public key, identity information, zero or more principal
(user or host) names and a set of options signed by CA key.

Generate a user cerificate:
	ssh-keygen -f ~/.ssh/key1
	ssh-keygen -s CA.key -I key_id ~/.ssh/key1.pub
	Output will be in ~/.ssh/key1-cert.pub

Host certificates:
	ssh-keygen -f ~/ssh/host1
	ssh-keygen -s CA.key -I key_id -h ~/.ssh/host1.pub
	Output will be in ~/.ssh/host1-cert.pub

Lets see how we generate CA.key. Seems that is a normal key, but, in
authorized_keys file is marked with option cert-authority.


Plan:
Create a user (A).
Create a CA key.
Add it to authorized_keys file and mark it as cert-authority.
Generate a key for a connection user (B) and sign it with the CA key.
Add the cert to B's ~/.ssh/
Try to connect with user B to userA@host.

Seems we can specify "-z serial" to ssh-keygen. But ssh-keygen crashes.

Questions:
- How to revoke a key?
- Seems the key_id is not exported in environment. :(



Mode Type Size Ref File
100644 blob 9 f3c7a7c5da68804a1bdf391127ba34aed33c3cca .exclude
100644 blob 96 5ca30a3adc6cef38f30cbc1e111154c2b5154229 .gitignore
100644 blob 179 df01c6306393e7a8b180470b4beb8831e6c421e0 AUTHORS
100644 blob 1131 c4293c8abbcc8446af598c33486e1ec4561388d4 Certs.txt
100644 blob 363 d4c20576e85575b16d877a289679fd5bcf5f2ed2 Compare.txt
100644 blob 35147 94a9ed024d3859793618152ea559a168bbcbb5e2 LICENSE
100644 blob 2135 01d625ed60feef5ebf6fe48f970adc8f00bc4eb9 Makefile.in
100644 blob 2998 bac3d29eb9b0b903d361b6b18c7aab20f6ca93f1 README
100644 blob 42501 4b379bb9e4d6e405f14e99663e178a02989f4b01 TODO
100644 blob 1294 f22911eb777f0695fcf81ad686eac133eb11fcc4 TODO-plans
040000 tree - b4b819554d96f8798ec6030c583263c80f73ff4c admin
040000 tree - 76a16691bc48bbe42bdc63a6d1244d2d49e4da2d artwork
100755 blob 30 92c4bc48245c00408cd7e1fd89bc1a03058f4ce4 configure
040000 tree - f67d3605efbd6422a8acdd953578991139266391 docs
100755 blob 13319 abc39a1cd64d5484f57b4ac0cd6534f555d67a23 duilder
100644 blob 291 9e1e58c00a1422b1415d30359e713b30eb5d706a duilder.conf
040000 tree - 84ce58e019da8a942e80794fcd5280250407b60f hooks
040000 tree - c6af494aa7d1f70ba9c0e1e677a8e09c36e94834 inc
100644 blob 3350 222c88ec7ba5f4409c202f0d52953c10451e2acb rocketgit.spec.in
040000 tree - d27ab809d418b9c9a8d05af05af70b16d297ec2b root
040000 tree - 43d7f82c3284d470d34dbe4b8a77e94f3099ca34 samples
040000 tree - 4c682568ec22eb41fc2c89f188626d87c19dac48 scripts
040000 tree - 783200bb5dbca39dc01aad7dd0d2f57a5374db93 selinux
040000 tree - 017eac549ce835210dba43aa8a73aa0919107cee tests
Hints:
Before first commit, do not forget to setup your git environment:
git config --global user.name "your_name_here"
git config --global user.email "your@email_here"

Clone this repository using HTTP(S):
git clone https://rocketgit.com/user/catalinux/rocketgit

Clone this repository using ssh (do not forget to upload a key first):
git clone ssh://rocketgit@ssh.rocketgit.com/user/catalinux/rocketgit

Clone this repository using git:
git clone git://git.rocketgit.com/user/catalinux/rocketgit

You are allowed to anonymously push to this repository.
This means that your pushed commits will automatically be transformed into a merge request:
... clone the repository ...
... make some changes and some commits ...
git push origin main