diff options
| author |  tobi <31960611+tsmethurst@users.noreply.github.com> | 2024-06-06 13:50:56 +0200 |
|---|---|---|
| committer |  GitHub <noreply@github.com> | 2024-06-06 12:50:56 +0100 |
| commit | 131020faeb4c65e9a787ac61debc4c2142b103b4 (patch) | |
| tree | 9ea29f2834e4ec258bdc67e86ed23c824fa55cc5 /docs | |
| parent | [feature] do not uncache status / emoji media if attached status is bookmarke... (diff) | |
| download | gotosocial-131020faeb4c65e9a787ac61debc4c2142b103b4.tar.xz | |
drop date (#2969)
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/federation/federating_with_gotosocial.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/federation/federating_with_gotosocial.md b/docs/federation/federating_with_gotosocial.md index 947a03f9b..0fd4580ce 100644 --- a/docs/federation/federating_with_gotosocial.md +++ b/docs/federation/federating_with_gotosocial.md @@ -44,8 +44,8 @@ GoToSocial request signing is implemented in [internal/transport](https://github When assembling signatures: -- outgoing `GET` requests use `(request-target) host date` -- outgoing `POST` requests use `(request-target) host date digest` +- outgoing `GET` requests use `(request-target) (created) host` +- outgoing `POST` requests use `(request-target) (created) host digest` GoToSocial sets the "algorithm" field in signatures to the value `hs2019`, which essentially means "derive the algorithm from metadata associated with the keyId". The *actual* algorithm used for generating signatures is `RSA_SHA256`, which is in line with other ActivityPub implementations. When validating a GoToSocial HTTP signature, remote servers can safely assume that the signature is generated using `sha256`. |