archive
/
matrix-spec
mirror of https://github.com/matrix-org/matrix-spec
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>
pull/977/head
Richard van der Hoff 6 years ago committed by GitHub
parent 539ca4cf15
commit f06455479d
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

@ -471,7 +471,7 @@ Intuitively using rejected events feels dangerous, however:
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. The rejected event to point to that fork, and send the event. The
duplicated event would then pass the auth checks. Ignoring rejected events would therefore not duplicated event would then pass the auth checks. Ignoring rejected events would therefore not
reduce any potential attack vectors eliminate any potential attack vectors.
We specifically don't use rejected auth events in the iterative auth checks, as We specifically don't use rejected auth events in the iterative auth checks, as
in that case the auth events aren't re-authed like the rest of the events in the in that case the auth events aren't re-authed like the rest of the events in the

Write Preview
Loading…
Cancel
Save