Mateusz Dukat

+1 Looks like it's still unresolved. yt-dlp on Windows 10: ``` $ ../Download/yt-dlp.exe -vU "https://www.instagram.com/python_is_trash/" [debug] Command-line config: ['-vU', 'https://www.instagram.com/python_is_trash/'] [debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out cp1252...

Hi, From my testing, everything looks fine. Website you linked:  My modified example code: ```c #include "hmac_sha256/hmac_sha256.h" #include #include #include #define SHA256_HASH_SIZE 32 #define DATA_LEN 4 #define KEY_LEN 16...

Are you sure you're not handling your key as string, or using `strlen()` on your key? This way, C/C++ interprets it as [null-terminated string](https://en.wikipedia.org/wiki/Null-terminated_string), and might show different results than...

To be completely sure, here's a quick implementation in OpenSSL EVP: ```c #include #include #define DATA_LEN 4 #define KEY_LEN 16 void handleErrors(void) { ERR_print_errors_fp(stderr); abort(); } int main(void) { EVP_MD_CTX*...

Please upload your code with key and message you're experiencing problems with. I believe there might be an error on your side, with key or message length definition. In the...

I see. Something, somewhere, ignores anything after '\x00' byte in key, but only in this C++ test case. For example, same result exists for keys `010002030405060708090a0b0c0d0e0f` and `01000000000000000000000000000000`. I might...

Found the problem, `std::string` ignores any data after null termination, when variable value is defined as C-string. I'll work on a fix for repo's test. Here's an example of this...

As for your case, I would suggest to use `std::vector`, as defined in `out` container for test cases. https://github.com/h5p9sl/hmac_sha256/blob/9445307885b86fb997b10f49ada5bee47496950a/tests/tests.cpp#L32 **Keep in mind, you have to know the sizes of your...