Update README.md
This commit is contained in:
parent
606a6f70a4
commit
f847242113
16
README.md
16
README.md
@ -16,6 +16,7 @@ Custom configurations should be supplied in a `lixonet.conf` file in the `name=v
|
||||
6. Fill out `/etc/lixonet/(mesh)lixonet.conf` (see: **Configuration options**)
|
||||
7. Supply `/etc/lixonet/(mesh)/tinc.key`
|
||||
8. Supply `/etc/lixonet/id_rsa` and `/etc/lixonet/(yournetwork)/id_rsa`
|
||||
9. Supply `/etc/lixonet/known_hosts`
|
||||
|
||||
**Generating keypairs for tinc (`tinc.key`)**:
|
||||
|
||||
@ -23,6 +24,21 @@ Source: https://www.tinc-vpn.org/documentation/Generating-keypairs.html
|
||||
|
||||
Run: `tincd -n lixonet -K`
|
||||
|
||||
**Generating SSH keys (`id_rsa`)**:
|
||||
|
||||
1. I recommend PuTTYgen (https://www.puttygen.com/) on Windows, ssh-genkey on Linux.
|
||||
2. Generate at least **two** keys. One will be for `lixonet-ee`, one will be for whichever repositories you're a part of (i.e. `teamlixo.mesh`).
|
||||
3. Share the public key (starting with something like `ssh-rsa`) with the repository owner(s) listed below so they can add a "Deploy key" to the repository for you.
|
||||
|
||||
**Setting `known_hosts`**
|
||||
|
||||
For GitHub, at this time the contents would be:
|
||||
```
|
||||
|1|hW/UPBCtfR0M/2GejxakBvoqGNY=|DXk4SRaJXzawNdHyBe9mrxvWYvk= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==
|
||||
```
|
||||
|
||||
Don't take my word for it, see: https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints
|
||||
|
||||
#### Install/Update:
|
||||
|
||||
1. Read and follow the prerequisites above and make sure you are ready to install.
|
||||
|
Loading…
x
Reference in New Issue
Block a user