Update proposals/1442-state-resolution.md

Co-Authored-By: erikjohnston <erikj@jki.re>
pull/977/head
Richard van der Hoff 6 years ago committed by GitHub
parent 6c9a433805
commit eaaf36edf7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

@ -467,7 +467,7 @@ Intuitively using rejected events feels dangerous, however:
auth checks based on the events auth chain (e.g. they can't grant themselves
power levels if they didn't have them before).
2. For a previously rejected event to pass auth there must be a set of state
that allows said event. At which point, a malicious server could 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
rejected event to point to that fork, and send the event. At which point the
duplicated event will pass auth. Therefore ignoring rejected events wouldn't

Loading…
Cancel
Save