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
6876b1a2
"README.md" did not exist on "814b4be08e49a2bc92a7b18e172b57c564127009"
Commit
6876b1a2
authored
10 years ago
by
Matthew Hodgson
Browse files
Options
Downloads
Patches
Plain Diff
fix grammatics
parent
107e7d5d
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
docs/server-server/signing.rst
+4
-4
4 additions, 4 deletions
docs/server-server/signing.rst
with
4 additions
and
4 deletions
docs/server-server/signing.rst
+
4
−
4
View file @
6876b1a2
...
...
@@ -130,13 +130,13 @@ Signing events is a more complicated process since servers can choose to redact
non-essential event contents. Before signing the event it is encoded as
Canonical JSON and hashed using SHA-256. The resulting hash is then stored
in the event JSON in a ``hash`` object under a ``sha256`` key. Then all
non-essential keys are striped from the event object and the resulting object
non-essential keys are strip
p
ed from the event object
,
and the resulting object
which included the ``hash`` key is signed using the JSON signing algorithm.
Servers can then transmit the entire event or the event with the non-essential
keys removed. Rec
i
eving servers can then check the entire event if it is
present by computing the SHA-256 of the event excluding the ``hash`` object or
by using the ``hash`` object includ
ing
in the event if keys have been redacted.
keys removed. Rece
i
ving servers can then check the entire event if it is
present by computing the SHA-256 of the event excluding the ``hash`` object
,
or
by using the ``hash`` object includ
ed
in the event if keys have been redacted.
New hash functions can be introduced by adding additional keys to the ``hash``
object. Since the ``hash`` object cannot be redacted a server shouldn't allow
...
...
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