Skip to content
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.

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

identifiers: Add signature-id compat mode for KeyId #1812

Closed
wants to merge 1 commit into from

Conversation

zecakeh
Copy link
Contributor

@zecakeh zecakeh commented May 12, 2024

Allows to replace split_id in ruma-signatures with KeyId::parse while having the exact same behavior.

Allows to replace split_id in ruma-signatures with KeyId::parse
while having the exact same behavior.
@zecakeh zecakeh requested a review from a team May 12, 2024 18:57
Comment on lines +32 to +33
#[cfg(feature = "compat-signature-id")]
let is_valid = is_valid || c == '+' || c = '/';
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where in the spec does it mention these "compat" signature ids anyways?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The point of the compat features is to conditionally improve compatibility with other Matrix software that fails to follow the spec properly.

@zecakeh
Copy link
Contributor Author

zecakeh commented Jun 5, 2024

Let's close this. Given the discussion in #1813, we should get rid of KeyId and replace it with its a type only for server signatures.

@zecakeh zecakeh closed this Jun 5, 2024
@zecakeh zecakeh deleted the zecakeh/key-id-signature-compat branch June 5, 2024 09:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants