Debian Patches
Status for wolfssl/5.9.0-0.2
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| multi-arch.patch | Make header files multi-arch compatible Exclude architecture dependent option HAVE___UINT128 from config.h | Felix Lechner | no | debian | ||
| dfsg.patch | Strike references to removed non-DFSG sources from build files=================================================================== | Felix Lechner <felix.lechner@lease-up.com> | not-needed | |||
| fix-hurd-i386-flags.patch | Fix type definition for socklen_t on hurd-i386 Based on http://bugs.mysql.com/bug.php?id=22326 | Felix Lechner <felix.lechner@lease-up.com> | not-needed | 2017-04-22 | ||
| handle-debian-files.patch | Handling existing debian directory=================================================================== | Jacob Barthelmeh | no | other | ||
| configure-ac-rules.patch | =================================================================== | no | ||||
| pkcs7-verification.patch | wolfcrypt/src/pkcs7.c: Fix PKCS#7 verification for digestAlgorithm.parameters = NULL RFC 8017 hardcodes DER serialization samples of DigestInfo, where the parameter part is always NULL (05 00) for any hash algorithm. This value does therefore *not* depend on SignerInfo.digestAlgorithm.parameters. WolfSSL wrongly assumed and implemented such a dependency. This non-conformance caused an interoperability bug with OpenSSL: A signature created with openssl cms (SHA-2) could not be verified in WolfSSL. OpenSSL leaves SignerInfo.digestAlgorithm.parameters absent, and adds explicit NULL to DigestInfo. WolfSSL saw the absence and wrongly inferred DigestInfo would have no explicit NULL - but it has - leading to size mismatch. |
Tobias Deiminger <tobias.deiminger@posteo.de> | no | https://github.com/haxtibal/wolfssl/commit/7af95eecfa56155cafa15ee45b0ff02877eee1e8 | 2026-03-27 |
All known versions for source package 'wolfssl'
- 5.9.0-0.2 (forky, sid)
- 5.7.2-0.1+deb13u1 (trixie)
- 5.5.4-2+deb12u2 (bookworm)
