diff options
| author | Wang Mingyu <wangmy@fujitsu.com> | 2026-05-13 12:05:20 +0800 |
|---|---|---|
| committer | Khem Raj <khem.raj@oss.qualcomm.com> | 2026-05-13 20:46:39 -0700 |
| commit | 76e632e2c922fd881158f6b46dcab8c396fcc920 (patch) | |
| tree | c51853d1cec97f7a8231c30a2089dd21eb35bc87 /meta-python | |
| parent | 3d6590618990080eb6cfc615992914054bd25694 (diff) | |
| download | meta-openembedded-76e632e2c922fd881158f6b46dcab8c396fcc920.tar.gz | |
pure-ftpd: upgrade 1.0.53 -> 1.0.54
Changelog:
===========
- Multiple hardening fixes across PureDB, the IP access checker, PAM, LDAP,
quota handling, and pure-pwconvert.
- IP access rules now support IPv6 patterns. Hostname rules are resolved
using the client's address family, so AAAA records can match IPv6 clients;
previously this path was IPv4-only.
- Malformed CIDR widths in PureDB allow/deny lists now fail closed and a
warning is logged identifying the offending pattern.
- LDAP searches that return more than one entry are now rejected as
ambiguous and a warning is logged identifying the offending uid.
- Malformed quota files no longer reset usage to zero; the failure
surfaces during quota checks instead.
- PureDB virtual users with a non-numeric or partially numeric uid or
gid field are now rejected. Records with uid or gid 0 continue to require
ACCEPT_ROOT_VIRTUAL_USERS at build time, as documented.
- Anonymous LDAP binds work again after a regression introduced in 1.0.53.
- Pure-pwconvert skips entries whose fields contain ':' or newline
characters rather than emitting corrupted records.
igned-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Diffstat (limited to 'meta-python')
0 files changed, 0 insertions, 0 deletions
