/Certs.txt (dd65951315f3de6d52d52a82fca59889d1d95187) (1132 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 certificate:
	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 102 eaeb7d777062c60a55cdd4b5734902cdf6e1790c .gitignore
100644 blob 341 4f4fc30b693128521d8deabbd0e1a09e46b6ced5 AUTHORS
100644 blob 1132 dd65951315f3de6d52d52a82fca59889d1d95187 Certs.txt
100644 blob 1133 f2d3e450d46e4f55fd21d2b3b46fc4926a396738 History.txt
100644 blob 34520 dba13ed2ddf783ee8118c6a581dbf75305f816a3 LICENSE
100644 blob 3398 cf75b360b8a3e6ef86bc4a42648e353bd58c2a80 Makefile.in
100644 blob 5649 0be60bc826db4b315efb6e15cb499a577c3340d2 README
100644 blob 136232 9a1643c1672b63d18b16775918520c7f559f0ddf TODO
100644 blob 1294 f22911eb777f0695fcf81ad686eac133eb11fcc4 TODO-plans
100644 blob 203 a2863c67c3da44126b61a15a6f09738c25e0fbe0 TODO.perf
100644 blob 1044 9bb3652b3937eb624dba0f2d8efff7ce6c0ce0e2 TODO.vm
040000 tree - 21928e906ad2907a55c2e81c2a8b0502b586b8a0 artwork
100644 blob 4707 0da219f933a61fe4d34eb59e1a3829e19e3d246e compare.csv
100755 blob 30 92c4bc48245c00408cd7e1fd89bc1a03058f4ce4 configure
040000 tree - 69114e8648f8e0e7173c76e30ca6bbfcece7df31 debian
040000 tree - e1f903261de934d6a656f07278d8c99446eaf9e9 docker
040000 tree - f67d3605efbd6422a8acdd953578991139266391 docs
100755 blob 16720 52405deef0d3708e7553022e1e9db73faa28d05c duilder
100644 blob 536 96c75f943c5bf93b54dbddf678e8a99d7ba4ff93 duilder.conf
040000 tree - 2f3d689ae2a6df46f805b6a1d7e0036ad8304874 hooks
040000 tree - 11e5a8a56d045d579b568ebb0a30cf80ccd33248 inc
040000 tree - c070ac2ad296b44903e5e3495d81a905802a3d78 misc
100644 blob 3766 a0f894a1e351d296c73467c75f4508a5ed85fc1e rocketgit.spec.in
040000 tree - ebabf40af80662ecb8b82a95bfd91800db6ca18a root
040000 tree - c6edd648d12e2e98861583d5a0d5eab8381b2c06 samples
040000 tree - 0f367aa33daf30ad4208252af4db6e45bbdb31ca scripts
040000 tree - f0806d955c8d64a3c1522c5ee97c4295a6203c5e selinux
100755 blob 256 462ccd108c431f54e380cdac2329129875a318b5 spell_check.sh
040000 tree - cb54e074b3ca35943edfcda9dd9cfcd281bcd9e7 techdocs
040000 tree - 7d8e19bde361970725938896f0b29af003d407bf tests
040000 tree - bc0ac4ce1d9e6c858f09fa0c615f1c9f55609b6f tools
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