| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-Use-stdbool.h-instead-of-config.h-in-published-heade.patch | Use <stdbool.h> instead of "config.h" in published header file We don't want to publish our "config.h" as that name is rather too generic to put in /usr/include. Instead, assume the compiler has stdbool.h, which debian systems should always have. |
Keith Packard <keithp@keithp.com> | no | 2020-09-02 | ||
| 0002-man-Switch-safe-option-for-unsafe-in-man-page.patch | man: Switch --safe option for --unsafe in man page The old --safe option is now the default, to get the previous default behavior, use the --unsafe flag. |
Keith Packard <keithp@keithp.com> | no | 2022-01-17 | ||
| 0003-Install-all-headers-in-include-cmark-gfm.patch | Install all headers in include/cmark-gfm These are needed to actually use the library it seems. |
Keith Packard <keithp@keithp.com> | no | 2022-10-25 | ||
| 0004-Fix-out-of-bounds-read-in-autolink.patch | [PATCH] autolink: avoid out-of-bounds read in validate_protocol If validate_protocol runs with the "protocol:..." string starting exactly at the underlying memory buffer used in postprocess_text, prev_char will point to a byte _before_ that memory buffer, and the check will essentially be random. Apparently this works "fine" on little endian architectures, but on big-endian (like s390x, hppa, ppc, ppc64, ...) this fails. And for good reason! Avoid the prev_char check by forwarding the underlying buffer as "start" into validate_protocol. Fixes build failure in Debian on s390x. Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023020 |
Chris Hofstaedtler <chris@hofstaedtler.name> | no | 2022-11-29 |