archive
/
matrix-spec-proposals
mirror of https://github.com/matrix-org/matrix-spec-proposals
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update proposals/1442-state-resolution.md

Browse Source 
Co-Authored-By: erikjohnston <erikj@jki.re>
erikj/state_res_rejections
Richard van der Hoff 7 years ago committed by GitHub
parent eaaf36edf7
commit c581c6132e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File

2
proposals/1442-state-resolution.md
Unescape Escape View File

@ -469,7 +469,7 @@ Intuitively using rejected events feels dangerous, however:
2. For a previously rejected event to pass auth there must be a set of state 2. For a previously rejected event to pass auth there must be a set of state
that allows said event. A malicious server could therefore produce a that allows said event. A malicious server could therefore produce a
fork where it claims the state is that particular set of state, duplicate the fork where it claims the state is that particular set of state, duplicate the
rejected event to point to that fork, and send the event. At which point the rejected event to point to that fork, and send the event. The
duplicated event will pass auth. Therefore ignoring rejected events wouldn't duplicated event will pass auth. Therefore ignoring rejected events wouldn't
reduce any potential attack vectors reduce any potential attack vectors

Write Preview
Loading…
Cancel
Save