feat: import pre-existing signing key from Synapse #195
Labels
No labels
Bug
Cherry-picking
Database
Dependencies
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/MSC
Matrix/Media
Meta
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Wont fix
old/ci/cd
old/rust
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: continuwuation/continuwuity#195
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
At least I want to support outputting the homeserver signing key from the database because I seriously doubt this is hard lol. It's generated upon creation of the database.
Will maybe try looking into seeing if we can change it too. Not sure how it will be done, maybe what Synapse does and reads it from a file with a check on the file permissions. Or a commandline argument to change it?
This ended up being unfortunately a lot more complex than I thought. I would like to be able to extract the key into Synapse's homeserver signing key format, but it doesn't appear to be as simple as I thought (cryptography is hard)
An unfinished branch is here if someone wants to pick it up: https://github.com/girlbossceo/conduwuit/tree/bad-attempt-at-extracting-homeserver-signing-key
I know a few people have expressed interest in being able to import their keys at least, might be worth taking a look at this eventually
Homeserver signing key stuffto feat: import pre-existing signing key from Synapse