HTTP Message Signatures explained

[@jgoebel]

What do you think about this video? Let me know in the comments below.

[@KellyClowers]

Thanks, found the IETF draft, but didn't feel like wading through the RFC technical language today, wanted a plain English overview, this was great for that.

[@ramunasguobys6809]

Wow, thanks a lot, RFC documentation - a tangled mess of spaghetti. This was extremely helpful.

[@missiontechdk6064]

Super useful information content.Loved it 🏆.Please bring more quality content like this

[@jgoebel]

thx 👍

[@damirdesign]

Fantastic content, always learn something new. Great explanations too.

[@jgoebel]

Much appreciated!

[@yadneshkhode3091]

thanks bro keep on uploading

[@jgoebel]

thx

[@LyanDwiPangestu]

Hi Jan, Your explanation is very clear and helpful, thank you Can you share the diagram you used to explain in this video? Thank you

[@saiaussie]

Great content. Thanks. How can a verifier get the key based on the id? Is there a standard for that? Wouldn't it be more easier and standardised if the key-id was rather a key-uri? Secondly, is this RFC in draft or live?

[@jgoebel]

One option would be JSON Web Key Sets

[@yjhjerry]

How is the signature verified? Is there a common key involved?

[@jgoebel]

If you use an asymmetric algorithm, then the signature is created with a private key and verified with a public key. If you use a MAC (e.g. HMAC) instead of a digital signature, then you have a shared secret.

[@nigelharo6647]

Could you share that diagram pls?