You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Misskey integration: support custom signer/verifier and async key resolver #21
Updating misskey#16250 to current develop exposed a mismatch with misskey#17322, which moved RSA signing from synchronous node:crypto to slacc (a managed thread pool). This library currently calls crypto.subtle.sign/verify directly, leaving no hook for callers to substitute their own signing or verification backend.
Problems
1. No custom signer hook
signAsDraftToRequest() and signAsRFC9421ToRequestOrResponse() call Web Crypto internally. Misskey needs to delegate RSA signing to slacc while keeping Ed25519 on Web Crypto. There is currently no way to inject a custom signer without forking.
2. No async key resolver for verification
verifyParsedSignature() accepts a pre-loaded CryptoKey | Map. Misskey resolves keys from its ActivityPub actor resolver (network + cache), keyed by keyId, label, algorithm, and signature version. A synchronous pre-load doesn't fit this flow.
Activity
tamaina commentedon May 22, 2026
↑Codexに書かせました
要は、slaccの高速なRSA署名をサポートするためにsigner/verifierを関数で導入できるようにしようということです