Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Documentation how fill old_signing_keys after changing homeserver.signing.key #5958

Open
MurzNN opened this issue Sep 1, 2019 · 3 comments
Labels
A-Docs things relating to the documentation O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Major functionality / product severely impaired, no satisfactory workaround. T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues. z-p2 (Deprecated Label)

Comments

@MurzNN
Copy link

MurzNN commented Sep 1, 2019

Please add documentation with examples how to fill old_signing_keys values, when we have new homeserver.signing.key and old one.

In homeserver.yaml file there are description:

# The keys that the server used to sign messages with but won't use
# to sign new messages. E.g. it has lost its private key
#
#old_signing_keys:
#  "ed25519:auto":
#    # Base64 encoded public key
#    key: "The public part of your old signing key."
#    # Millisecond POSIX timestamp when the key expired.
#    expired_ts: 123456789123

So users must place in this file only public part of your old signing key, but there are no description how to generate public part, having full old key file? Can you please describe how to do this in description text?

@MurzNN
Copy link
Author

MurzNN commented Sep 1, 2019

As workaround I have found the way to get key via pgsql query:

select encode(verify_key, 'base64') from server_signature_keys where server_name='example.com';

But how to get this string from homeserver.signing.key file is still the question.

@richvdh
Copy link
Member

richvdh commented Sep 2, 2019

Interesting. I guess getting it from the database (or the REST api) is the easiest way. There should really be a script to do it though.

@JochenFriedrich
Copy link

It's really important for an instance to keep track of all old keys. In particular if an instance don't trust any notary servers.

@neilisfragile neilisfragile added z-p2 (Deprecated Label) A-Docs things relating to the documentation labels Sep 13, 2019
@reivilibre reivilibre added S-Major Major functionality / product severely impaired, no satisfactory workaround. T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues. O-Uncommon Most users are unlikely to come across this or unexpected workflow labels May 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-Docs things relating to the documentation O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Major functionality / product severely impaired, no satisfactory workaround. T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues. z-p2 (Deprecated Label)
Projects
None yet
Development

No branches or pull requests

5 participants