7 commits

Author	SHA1	Message	Date
fr33domlover	e325175a9c	Publish 2 rotating instance-scope keys instead of the one-implicitly-shared-key ... Before, there was a single key used as a personal key for all actors. Now, things work like this: - There are 2 keys, each time one is rotated, this way the old key remains valid and we can freely rotate without a risk of race conditions on other servers and end up with our posts being rejected - The keys are explicitly instance-scope keys, all actors refer to them - We add the ActivityPub-Actor header to all activity POSTs we send, to declare for which specific actor our signature applies. Activities and otherwise different payloads may have varying ways to specify attribution; using this header will be a standard uniform way to specify the actor, regardless of payload format. Of course, servers should make sure the actual activity is attributed to the same actor we specified in the header. (This is important with instance-scope keys; for personal keys it's not critical)	2019-02-07 10:34:33 +00:00
fr33domlover	04e26a911d	In httpGetAP, if we got an unexpected Content-Type, specify it in error message	2019-01-21 22:24:09 +00:00
fr33domlover	1f47ca39eb	Federation test outbox page with form for entering JSON	2019-01-21 15:54:57 +00:00
fr33domlover	2a4dc345f4	Back to using the (updated) YesodHttpSig class	2019-01-19 04:21:56 +00:00
fr33domlover	393cce0ede	When GETing the keyId, set Accept header to JSON-LD/AS2	2019-01-19 02:57:58 +00:00
fr33domlover	93def0dfc8	When doing httpJSON to GET keyId, use appHttpManager, not the silly global one	2019-01-19 02:33:20 +00:00
fr33domlover	e4153fc909	Ugh I forgot *again* to commit a new source file, the actual InboxR handler	2019-01-19 01:56:50 +00:00