From 3c4a0f9fe1b18a4d1d7a0cb01bb0aee4bc2ddf9a Mon Sep 17 00:00:00 2001 From: girlfangs Date: Sat, 15 Aug 2026 12:42:28 -0400 Subject: [PATCH 1/2] chore(docs): update dev/device-ids to show that since v2.0.0 the default signing algo is ed25519 --- dev/device-ids.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/dev/device-ids.rst b/dev/device-ids.rst index cb987db1..990882dc 100644 --- a/dev/device-ids.rst +++ b/dev/device-ids.rst @@ -14,12 +14,12 @@ Keys To understand device IDs we need to look at the underlying mechanisms. At first startup, Syncthing will create a public/private keypair. -Currently this is a 384 bit ECDSA key (3072 bit RSA prior to v0.12.5, -which is what is used as an example in this article). The keys are saved in -the form of the private key (``key.pem``) and a self signed certificate -(``cert.pem``). The self signing part doesn't actually add any security or -functionality as far as Syncthing is concerned but it enables the use of the -keys in a standard TLS exchange. +Currently this is a 256 bit ED25519 key (384 bit ECDSA prior to v2.0.0 and +3072 bit RSA prior to v0.12.5, which is what is used as an example in this +article). The keys are saved in the form of the private key (``key.pem``) and a +self signed certificate (``cert.pem``). The self signing part doesn't actually +add any security or functionality as far as Syncthing is concerned but it enables +the use of the keys in a standard TLS exchange. The typical certificate will look something like this, inspected with ``openssl x509``:: From f92e95aca7e471a6f93cce81e1fe906a81b32cc7 Mon Sep 17 00:00:00 2001 From: girlfangs Date: Sun, 16 Aug 2026 12:33:25 -0400 Subject: [PATCH 2/2] chore(docs): ed25519 is not an acronym --- dev/device-ids.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dev/device-ids.rst b/dev/device-ids.rst index 990882dc..3b648c4c 100644 --- a/dev/device-ids.rst +++ b/dev/device-ids.rst @@ -14,7 +14,7 @@ Keys To understand device IDs we need to look at the underlying mechanisms. At first startup, Syncthing will create a public/private keypair. -Currently this is a 256 bit ED25519 key (384 bit ECDSA prior to v2.0.0 and +Currently this is a 256 bit Ed25519 key (384 bit ECDSA prior to v2.0.0 and 3072 bit RSA prior to v0.12.5, which is what is used as an example in this article). The keys are saved in the form of the private key (``key.pem``) and a self signed certificate (``cert.pem``). The self signing part doesn't actually