Up to [cvs.NetBSD.org] / pkgsrc / security / libjwt
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
libjwt: fix PLIST for doxygen 1.18 and depend on it Bump PKGREVISION.
libjwt: updated to 3.6.1 LibJWT 3.6.1 is a small test-portability patch release. The in-process HTTP server used by the cached-JWKS test cast write() to (void) to ignore its result. glibc marks write() warn_unused_result, and the (void) cast does not suppress that warning on newer glibc, so the -Werror test build failed. The result is now asserted with ck_assert_int_gt(write(...), 0). This is ABI-compatible with 3.6.0: no library source changed, so the exported symbol set is identical and per the libtool rules only the SONAME revision advances (18:0:4 → 18:1:4). The SONAME stays libjwt.so.14 and existing binaries keep working.
libjwt: fix PLIST for doxygen 1.17
libjwt: updated to 3.3.3 3.3.3 Bug fixes
libjwt: updated to 3.3.2 3.3.2 Patch release to fix symbol visibility for the JSON abstraction layer. Build fix: Mark all JSON abstraction functions with JWT_NO_EXPORT to prevent them from being exported in the shared library's public symbol table. These are internal implementation details of the JSON backend abstraction (Jansson/json-c) and should not be visible to library consumers.
libjwt: updated to 3.2.3 3.2.3 Fix case-sensitive check for Content-Length jwt-cli.bats: Better comparison for all.json doxygen: Updates for cleaner gen of docs
libjwt: bash also needed for building
libjwt: updated to 3.2.2 3.2.2 Various small fixes
libjwt: updated to 3.2.1 3.2.1 Memory leak fixes
libjwt: requires openssl 3
libjwt: updated to 3.2.0 3.2.0 libcurl for jwks and other things 3.1.0 Windows Build and a few fixes + coverage 3.0.0 A new way This is a major overhaul of LibJWT. The previous version was clumsy in that a jwt_t object could be used for creating a new token, or be the result of verifying. The ambiguity led to a lot of possible errors. The key handling was not very well done and was confusing. The new methods has a factory paradigm in that you create either a builder or checker object, configure it for your purposes, and then either generate tokens (builder) or verify tokens (checker) based on the rules you've established. This means you don't have to create an instance for every time you want to perform one of these actions. One of the other new features is a complete JWK and JWKS backend for keys. It is now the only method with which you can load and use keys in LibJWT. There are command line tools for converting PEM type keys into JWK(S) JSON files (and back again). There are also two convenient command line tools for generating and verifying JWT tokens.
libjwt: updated to 2.1.1 2.1.1 jwt_decode_2(): Security vulnerability This function had faulty logic based on some assumptions that it could trust the JWT in that if it was alg:none, it would not run the callback. The assumption would allow an attacker to modify the JWT header and body and trick the function into returning without having retrieved a key from the cb, meaning no verification of the signature was done, and it retuned as if everything was successful. The caller of jwt_decode_2 has no real way to know that their cb was never run. As an aside, it was found that some of the test cases were assuming that you could call jwt_decode_2 with key_provider == NULL. This doesn't make much sense, considering there's no way to pass a key without a key_provider. In this instance, if passed a JWT with alg:none, this was fine. If called with any other alg type, the code would attempt to run the NULL ``key_provider` and produce a SEGV. RESOLUTION jwt_decode_2 will always run the key_provider if passed, assuming there was not a previous error. Always check key_provider for NULL before using it If no key_provider, but JWT had alg != none, processing fails NOTES: jwt_decode() and jwt_decode_2() are being deprecated in favor more robust functionality.
libjwt: added version 1.17.2 JWT C Library.