summary refs log tree commit diff
path: root/synapse/federation/federation_base.py
diff options
context:
space:
mode:
authorErik Johnston <erik@matrix.org>2019-01-29 22:35:36 +0000
committerErik Johnston <erik@matrix.org>2019-01-29 22:35:36 +0000
commitff2f65d737b3d36e2aef8c296d1ce731156d3847 (patch)
treeda9b47c540081a3da8b8aa8ff33f1bc2cb142901 /synapse/federation/federation_base.py
parentcheck event format version not room version (diff)
downloadsynapse-ff2f65d737b3d36e2aef8c296d1ce731156d3847.tar.xz
Update comment
Diffstat (limited to 'synapse/federation/federation_base.py')
-rw-r--r--synapse/federation/federation_base.py6
1 files changed, 3 insertions, 3 deletions
diff --git a/synapse/federation/federation_base.py b/synapse/federation/federation_base.py
index 0bff8686e0..a400091db7 100644
--- a/synapse/federation/federation_base.py
+++ b/synapse/federation/federation_base.py
@@ -227,9 +227,7 @@ def _check_sigs_on_pdus(keyring, room_version, pdus):
 
     # we want to check that the event is signed by:
     #
-    # (a) the server which created the event_id
-    #
-    # (b) the sender's server.
+    # (a) the sender's server
     #
     #     - except in the case of invites created from a 3pid invite, which are exempt
     #     from this check, because the sender has to match that of the original 3pid
@@ -243,6 +241,8 @@ def _check_sigs_on_pdus(keyring, room_version, pdus):
     #     and signatures are *supposed* to be valid whether or not an event has been
     #     redacted. But this isn't the worst of the ways that 3pid invites are broken.
     #
+    # (b) for V1 and V2 rooms, the server which created the event_id
+    #
     # let's start by getting the domain for each pdu, and flattening the event back
     # to JSON.