| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 1001_fix-select.patch | Fix multiple Listen statements on IPv4 and IPv6 addresses. =================================================================== |
Tim Düsterhus <public+debian.org@bastelstu.be> | no | |||
| 1002_fix-ftbfs-on-Hurd.patch | Fix FTBFS on hurd-i386: run_tests.sh duplicates build path. | Aaron M. Ucko <ucko@debian.org> | no | |||
| 1003_fix-rereading-filter-conf-when-unprivileged.patch | If dropping privileges, read the filter config always as unprivileged user and report an error, if that fails. | Heiko Schlittermann <hs@schlittermann.de> | no | |||
| 0001_fix-segfault-with-socks4.patch | [PATCH] fix segfault in socks4 upstream with unresolvable hostname using a socks4 tor upstream with an .onion url resulted in gethostbyname() returning NULL and a subsequent segfault. not only did the code not check the return value of gethostbyname(), that resolver API itself isn't threadsafe. as pure SOCKS4 supports only IPv4 addresses, and the main SOCKS4 user to this date is tor, we just use SOCKS4a unconditionally and pass the hostname to the proxy without trying to do any local name resolving. i suspect in 2021 almost all SOCKS4 proxy servers in existence use SOCKS4a extension, but should i be wrong on this, i prefer issue reports to show up and implement plain SOCKS4 fallback only when i see it is actually used in practice. |
rofl0r <rofl0r@users.noreply.github.com> | no | 2021-06-25 |