Skip to content

Update dev/device-ids to ed25519 (default since v2.0.0) #1029

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
girlfangs wants to merge 2 commits into
base: main
Choose a base branch
from
+6 −6
Open

Update dev/device-ids to ed25519 (default since v2.0.0) #1029

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3c4a0f9
chore(docs): update dev/device-ids to show that since v2.0.0 the defa…
girlfangs Aug 15, 2026
f92e95a
chore(docs): ed25519 is not an acronym
girlfangs Aug 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions dev/device-ids.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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``::
Expand Down