Re: [naviserver-devel] Verifying HMAC signature [ns_crypto::hmac ...]

Thanks Gustaf, Yes, it works fine! I was not capable to understand the verification part. I was trying to learn it by repeating the method of base64* with encode/decode. Then, after decrypting, to verify if secret and data were both the same from the original request Best wishes, I On May

Re: [naviserver-devel] What to do when [ns_base64encode] doesn't encrypt properly after the 63rd char?

Thanks Gustaf,It works now.p.s. I don't understand why the subject of this thread got replaced with a previous thread that I opened.The original email that I sent has the subject: "Verifying HMAC signature [ns_crypto::hmac ...]" Original Message Subject: Re: [naviserver-devel]

Re: [naviserver-devel] What to do when [ns_base64encode] doesn't encrypt properly after the 63rd char?

Iuri, The nsc_crypto::hmac performs the HMAC  (Keyed-Hashing for Message Authentication) as specified in RFC 2104, using a symmetric key provided via argument. The HMAC can be verified the same way as a plain digest (without a secret): If a received HMAC (or digest) should be verified, it must

Re: [naviserver-devel] What to do when [ns_base64encode] doesn't encrypt properly after the 63rd char?

On 25.05.20 23:17, Iuri de Araujo Sampaio wrote: On May 25, 2020, at 08:55, Gustaf Neumann > wrote: NaviServer has native support for base64 and base64url encoding/decoding See: https://naviserver.sourceforge.io/n/naviserver/files/ns_base64.html Okay, and what about