e2net/iceshrimp-legacy
2
0
Fork 0
Code Issues Pull requests Packages Projects Releases Activity

fix: relay signature handling

Browse source 
A change sometime ago moved to setting some signature fields in the incoming
object to undefined as opposed to deleting them. The trouble is that downstream
code checks against existence, not undefinedness and rejects the message.

Resolves: #9665
This commit is contained in:
amy bones 2023-01-18 20:16:41 -08:00
parent d05ab9bf46
commit c5de597079
No known key found for this signature in database
GPG key ID: 819528B765A64B82
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
packages/backend/src/remote/activitypub/misc/ld-signature.ts
View file

@ -70,13 +70,13 @@ export class LdSignature {
...options,
"@context": "https://w3id.org/identity/v1",
};
transformedOptions["type"] = undefined;
transformedOptions["id"] = undefined;
transformedOptions["signatureValue"] = undefined;
delete transformedOptions["type"];
delete transformedOptions["id"];
delete transformedOptions["signatureValue"];
const canonizedOptions = await this.normalize(transformedOptions);
const optionsHash = this.sha256(canonizedOptions);
const transformedData = { ...data };
transformedData["signature"] = undefined;
delete transformedData["signature"];
const cannonidedData = await this.normalize(transformedData);
if (this.debug) console.debug(`cannonidedData: ${cannonidedData}`);
const documentHash = this.sha256(cannonidedData);