Skip to content

Conversation

@FragLegs
Copy link
Contributor

@FragLegs FragLegs commented May 23, 2024

To address the attacks proposed in #161 and #160, this PR adda a paragraph indicating that all Stream Management API endpoints must use authorization that associates stream IDs with a specific Receiver, unless some other method of trust is established.

@FragLegs FragLegs requested a review from a team as a code owner May 23, 2024 16:24
@FragLegs
Copy link
Contributor Author

FragLegs commented Jun 4, 2024

Update RFC2818 and RFC7235 to RFC9110

FragLegs added 3 commits June 6, 2024 16:28
…management API endpoints, regardless of whether there is an alternative way of securing the communication. Add language saying the the Transmitter should also tie the 'aud' value to the auth from the Receiver.
@tulshi tulshi merged commit d2607b9 into main Jun 10, 2024
@tulshi tulshi deleted the 161-require-auth branch June 10, 2024 17:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Stream Audience Mix-Up Attacker Stream Subject Insertion

5 participants