Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
synapse
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Monitor
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Maunium
synapse
Commits
ff2f65d7
Commit
ff2f65d7
authored
6 years ago
by
Erik Johnston
Browse files
Options
Downloads
Patches
Plain Diff
Update comment
parent
655ce037
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
synapse/federation/federation_base.py
+3
-3
3 additions, 3 deletions
synapse/federation/federation_base.py
with
3 additions
and
3 deletions
synapse/federation/federation_base.py
+
3
−
3
View file @
ff2f65d7
...
@@ -227,9 +227,7 @@ def _check_sigs_on_pdus(keyring, room_version, pdus):
...
@@ -227,9 +227,7 @@ def _check_sigs_on_pdus(keyring, room_version, pdus):
# we want to check that the event is signed by:
# we want to check that the event is signed by:
#
#
# (a) the server which created the event_id
# (a) the sender's server
#
# (b) the sender's server.
#
#
# - except in the case of invites created from a 3pid invite, which are exempt
# - 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
# 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):
...
@@ -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
# 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.
# 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
# let's start by getting the domain for each pdu, and flattening the event back
# to JSON.
# to JSON.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment