Skip to content

"Validation of incoming decrypted events" section contains manifest nonsense #2363

@richvdh

Description

@richvdh

Link to problem area:

https://spec.matrix.org/v1.17/client-server-api/#validation-of-incoming-decrypted-events

Issue

This says:

The keys.ed25519 property in the decrypted content must match the sender_key property in the cleartext m.room.encrypted event body.

But keys.ed25519 is an ed25519 key, and sender_key is a curve25519 key, so they are never going to match.

This seems to have been mangled during #2122, due to some brainfart on my part.

Metadata

Metadata

Assignees

No one assigned

    Labels

    clarificationAn area where the expected behaviour is understood, but the spec could do with being more explicit

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions