aboutsummaryrefslogtreecommitdiffhomepage
path: root/README.md
diff options
context:
space:
mode:
authorPaolo Asperti <[email protected]>2022-07-21 16:45:21 +0200
committerPaolo Asperti <[email protected]>2022-07-22 10:18:50 +0200
commitfab70ce8e73a4f3bd82dd25177a507e15db4d117 (patch)
treee028c11597d5428aef14f186250afd47e701ec6b /README.md
parent06bd1117f6e789bc9cc44db38a1dadaeeb427568 (diff)
downloadrustdesk-server-fab70ce8e73a4f3bd82dd25177a507e15db4d117.tar.gz
rustdesk-server-fab70ce8e73a4f3bd82dd25177a507e15db4d117.zip
keypair verification before container startup
Diffstat (limited to 'README.md')
-rw-r--r--README.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/README.md b/README.md
index 7dbad2d..1aed514 100644
--- a/README.md
+++ b/README.md
@@ -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