Miroirs/slackware-current
1
0
Fork 0
mirror of git://slackware.nl/current.git synced 2024-12-31 10:28:29 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
slackware-current/patches/packages/popa3d-1.0.3-x86_64-7_slack15.0.txt

12 lines
543 B
Text
Raw Normal View History

Thu May 16 02:31:40 UTC 2024 patches/packages/gdk-pixbuf2-2.42.12-x86_64-1_slack15.0.txz: Upgraded. ani: Reject files with multiple INA or IART chunks. ani: Reject files with multiple anih chunks. ani: validate chunk size. Thanks to 0xvhp, pedrib, and Benjamin Gilbert. For more information, see: https://www.cve.org/CVERecord?id=CVE-2022-48622 (* Security fix *) patches/packages/git-2.39.4-x86_64-1_slack15.0.txz: Upgraded. This update fixes security issues: Recursive clones on case-insensitive filesystems that support symbolic links are susceptible to case confusion that can be exploited to execute just-cloned code during the clone operation. Repositories can be configured to execute arbitrary code during local clones. To address this, the ownership checks introduced in v2.30.3 are now extended to cover cloning local repositories. Local clones may end up hardlinking files into the target repository's object database when source and target repository reside on the same disk. If the source repository is owned by a different user, then those hardlinked files may be rewritten at any point in time by the untrusted user. When cloning a local source repository that contains symlinks via the filesystem, Git may create hardlinks to arbitrary user-readable files on the same filesystem as the target repository in the objects/ directory. It is supposed to be safe to clone untrusted repositories, even those unpacked from zip archives or tarballs originating from untrusted sources, but Git can be tricked to run arbitrary code as part of the clone. For more information, see: https://www.cve.org/CVERecord?id=CVE-2024-32002 https://www.cve.org/CVERecord?id=CVE-2024-32004 https://www.cve.org/CVERecord?id=CVE-2024-32020 https://www.cve.org/CVERecord?id=CVE-2024-32021 https://www.cve.org/CVERecord?id=CVE-2024-32465 (* Security fix *) patches/packages/popa3d-1.0.3-x86_64-7_slack15.0.txz: Rebuilt. This is a bugfix release: Build with AUTH_PAM, not AUTH_SHADOW. Thanks to jayjwa. testing/packages/bind-9.18.27-x86_64-1_slack15.0.txz: Upgraded. This is a bugfix release.
2024-05-16 04:31:40 +02:00
popa3d: popa3d (a POP3 daemon)
popa3d:
popa3d: popa3d is a Post Office Protocol version 3 (POP3) server. A POP3
popa3d: server operates on local mailboxes on behalf of its remote users.
popa3d: Users can connect at any time to check their mailbox and fetch the
popa3d: mail that has accumulated. The design goals of this POP3 server are
popa3d: security, reliability, RFC compliance (slightly relaxed to work with
popa3d: real-world POP3 clients), and high performance.
popa3d:
popa3d: The popa3d daemon was written by Solar Designer.
popa3d:
Reference in a new issue Copy permalink