/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 243 0168aabeca0ad5278c2d99874e2287736f81f73a AUTHORS
100644 blob 1132 dd65951315f3de6d52d52a82fca59889d1d95187 Certs.txt
100644 blob 1107 d3ecc1d13c5841910bb70ea66f70cfc522dbcaae Compare.txt
100644 blob 549 41c3bdbba8ec2523fe24b84bdd46777fc13e8345 History.txt
100644 blob 34520 dba13ed2ddf783ee8118c6a581dbf75305f816a3 LICENSE
100644 blob 2505 2a3b9382b6ef298355340aa5931d3df1c9c75f5c Makefile.in
100644 blob 4626 95543a17ab303aedbac21c45e4fc1b73537afca4 README
100644 blob 96938 a8bfdcf3a35fa1786cfcde07386075e45847e027 TODO
100644 blob 1294 f22911eb777f0695fcf81ad686eac133eb11fcc4 TODO-plans
100644 blob 203 a2863c67c3da44126b61a15a6f09738c25e0fbe0 TODO.perf
100644 blob 373 ca2fd2e49069f5d13d557928e0bf53135782530f TODO.vm
040000 tree - 21928e906ad2907a55c2e81c2a8b0502b586b8a0 artwork
100755 blob 30 92c4bc48245c00408cd7e1fd89bc1a03058f4ce4 configure
040000 tree - 403694c3687794b9650d283972091da5f614f0c4 debian
040000 tree - db495a9db69e13bf194c0ffeb145c945e4362187 docker
040000 tree - f67d3605efbd6422a8acdd953578991139266391 docs
100755 blob 16590 083fd22b7a03cd587efc6c6055cbf340e2d167a5 duilder
100644 blob 536 05aa2d6ca2ac158e91a557ad1809554afe67ce5d duilder.conf
040000 tree - 8b195ea587c2ea8a6feb12ea27aefccbd74fa4c9 hooks
040000 tree - 5d0452c865360a55027d789e4bfee02fca5055fa inc
100644 blob 3652 8486d6daf590268933705ec951089308596d225e rocketgit.spec.in
040000 tree - eced0a404444cb8118da15061b8e2496136a4ef3 root
040000 tree - 3c17292868ce779a1a807a17e037b37533200e6c samples
040000 tree - b3d25351eb3f7d85748de4e849528d17535bd9f4 scripts
040000 tree - 3501c84ce7a73f4b4a79c2a75037b924a611dac1 selinux
100755 blob 242 bfcfb00931a643571fec9082e3308c6b68ca9189 spell_check.sh
040000 tree - cb54e074b3ca35943edfcda9dd9cfcd281bcd9e7 techdocs
040000 tree - cab602b6bb63ea77d81a0127ef8db59866fc6ce0 tests
040000 tree - d39824f9d9ba0f8b2f00f4a101f5cd5aeebc2f83 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