diff options
| author | RustDesk <[email protected]> | 2022-07-22 16:23:29 +0800 |
|---|---|---|
| committer | GitHub <[email protected]> | 2022-07-22 16:23:29 +0800 |
| commit | dbab22cbbcc51e5c188e76d4bffdcc331fab7e55 (patch) | |
| tree | a394791581f99bf06e536863efd9d49f6367e6f1 /README.md | |
| parent | d11607fb6c2c8430a41c103d378990ac1fc81d30 (diff) | |
| parent | fab70ce8e73a4f3bd82dd25177a507e15db4d117 (diff) | |
| download | rustdesk-server-dbab22cbbcc51e5c188e76d4bffdcc331fab7e55.tar.gz rustdesk-server-dbab22cbbcc51e5c188e76d4bffdcc331fab7e55.zip | |
Merge pull request #70 from paspo/docker_verify_keypair
keypair verification before container startup
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 2 |
1 files changed, 2 insertions, 0 deletions
@@ -185,6 +185,8 @@ We use these environment variables: You can obviously keep the key pair in a docker volume, but the best practices tells you to not write the keys on the filesystem; so we provide a couple of options. On container startup, the presence of the keypair is checked (`/data/id_ed25519.pub` and `/data/id_ed25519`) and if one of these keys doesn't exist, it's recreated from ENV variables or docker secrets. +Then the validity of the keypair is checked: if public and private keys doesn't match, the container will stop. +If you provide no keys, `hbbs` will generate one for you, and it'll place it in the default location. #### Use ENV to store the key pair |