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
Integrate FASP signature handling with existing system.
- Add `activitypub_pre_get_public_key` filter to Remote_Actors::get_public_key()
allowing custom key resolution for non-URL keyIds (like FASP serverIds)
- Add Ed25519 signature verification using WordPress's sodium_compat:
- Http_Message_Signature now handles Ed25519 keys via sodium_crypto_sign_verify_detached()
- Ed25519 keys are passed as arrays: ['type' => 'ed25519', 'key' => $raw_bytes]
- FASP integration:
- Fasp::init() registers filter to provide Ed25519 public keys for serverId lookups
- Fasp::get_registration_by_server_id() added for server_id based lookups
- FASP now uses the same signature verification code path as ActivityPub
- Reuse Application actor's RSA keypair for signing FASP responses (already in place)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
0 commit comments