endpoint and http processor signature #1742
amitu
started this conversation in
Ideas & RFCs
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The endpoint and http processors may be written with the assumption that they should only accept requests from fastn. One way for them to verify this is if we pass a signature. We already have a FASTN_SECRET_KEY available to
fastn
, so fastn can include an extra headerX-FASTN-PROCESSOR-SIGNATURE
orX-FASTN-ENDPOINT-SIGNATURE
. We will also ship withfastn.django
middleware that will check if these headers are set and signature is verified. To avoid possible replay attack, we will include the content of the header and a one time nonce in the signature as well.Also to make matters simple, we can do encryption of payload as well, so your services can safely run on http, without worrying about client data getting leaked to snoofers.
Beta Was this translation helpful? Give feedback.
All reactions