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

Hi there, How can I verify HMAC signatures, using [ns_crypto::hmac ...]? For example, one has sent an encrypted message: set secret_message [ns_crypto::hmac string -digest sha256 "Abracadabra" "What is the magic word?"] ... and another wants to verify integrity and authenticity of that

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

> What do you mean its not encoded correctly? item (2) is not encoded correctly using base64url (https://tools.ietf.org/html/rfc4648#section-5 ). Note that padding ("=") must be omitted as per https://tools.ietf.org/html/rfc7515#section-2

Re: [naviserver-devel] Registering/Allowing request method HTTP PUT

Right on! Thanks Gustaf! The error was in the registration call. I had assigned the virtual OACS url as the path to the file, instead of the physical path. As you brightly described in > ns_register_tcl PUT /REST2/ /usr/local/oacs-5-10/openacs-4/www/ and regarding “unfriendly” behavior >

Re: [naviserver-devel] Registering/Allowing request method HTTP PUT

On 25.05.20 01:17, Maksym Zinchenko wrote: Sorry, actually I don't know about OpenACS, because Im just running NS with custom made app, so I assume it may be an OpenACS question. So I suggest  you to ask on OpenACS forum. The problem is here a not really OpenACS, but related to typical OpenACS

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

NaviServer has native support for base64 and base64url encoding/decoding See: https://naviserver.sourceforge.io/n/naviserver/files/ns_base64.html -gn On 25.05.20 03:23, Maksym Zinchenko wrote: As I understood, you want to send data to your REST API in url, so you cant use ns_base64encodin.