From: QA Team Robot <qa@altlinux.org> To: sisyphus-cybertalk@lists.altlinux.org Subject: [cyber] I: p8/branch packages: +3 (18240) Date: Fri, 10 Apr 2020 04:46:51 +0000 Message-ID: <20200410044651.GA32651@gyle.altlinux.org> (raw) 3 UPDATED packages apache2 - The most widely used Web server on the Internet * Mon Apr 06 2020 Anton Farygin <rider@altlinux> 1:2.4.43-alt1 - 2.4.43 (Fixes: CVE-2020-1927, CVE-2020-1934) * Thu Mar 19 2020 Stanislav Levin <slev@altlinux> 1:2.4.41-alt3 - fixed TLS 1.3 client cert authentication for POST requests * Wed Mar 18 2020 Stanislav Levin <slev@altlinux> 1:2.4.41-alt2 - mod_proxy_ajp: added "secret" parameter to proxy workers * Wed Aug 14 2019 Anton Farygin <rider@altlinux> 1:2.4.41-alt1 - 2.4.41 * Tue Apr 02 2019 Anton Farygin <rider@altlinux> 1:2.4.39-alt1 chrooted - The chrooted environment helper * Fri Apr 03 2020 Dmitry V. Levin <ldv@altlinux> 0.3.11-alt1 - Copy: always dereference symbolic links in SOURCE (by Alexey Shabalin; closes: #33591). * Wed Mar 11 2020 Ivan Zakharyaschev <imz@altlinux> 0.3.10-alt1 - Fixes: + OVE-20200311-0001 Normal update operations by root can corrupt/crash running processes through modifying libraries (Normally, the processes that can be affected are only the services already running in the chrooted environment being updated, if it is on a different filesystem than the system libraries, and hence they can't be hardlinked. Extraordinarily, if a file in a chrooted environment has been a hardlink to a system library, but ln hasn't succeeded this time for some reason, the affected processes are any already running processes system-wide. This could happen only as a result of actions initiated by root: for example, a package upgrade which included the old version of chrooted, or a package upgrade which included libraries in a system with the old version of chrooted, or an invocation of /sbin/update_chrooted.) * Tue Apr 10 2018 Maxim Voronov <mvoronov@altlinux> 0.3.9-alt1 - copy_resolv_conf: added support for symlinked /etc/localtime (see #32346). * Fri Aug 24 2012 Dmitry V. Levin <ldv@altlinux> 0.3.8-alt1 Note: changelog entry for 0.3.8-alt1.M80P.1 not found. kernel-image-std-debug - The Linux kernel (the core of the Linux operating system) * Thu Apr 02 2020 Kernel Bot <kernelbot@altlinux> 1:4.9.218-alt0.M80P.1 - v4.9.218 * Sat Mar 21 2020 Kernel Bot <kernelbot@altlinux> 1:4.9.217-alt0.M80P.1 Total 18240 source packages.
reply other threads:[~2020-04-10 4:46 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20200410044651.GA32651@gyle.altlinux.org \ --to=qa@altlinux.org \ --cc=devel@lists.altlinux.org \ --cc=sisyphus-cybertalk@lists.altlinux.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
ALT Linux Sisyphus cybertalk This inbox may be cloned and mirrored by anyone: git clone --mirror http://lore.altlinux.org/sisyphus-cybertalk/0 sisyphus-cybertalk/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 sisyphus-cybertalk sisyphus-cybertalk/ http://lore.altlinux.org/sisyphus-cybertalk \ sisyphus-cybertalk@lists.altlinux.org sisyphus-cybertalk@lists.altlinux.ru sisyphus-cybertalk@lists.altlinux.com public-inbox-index sisyphus-cybertalk Example config snippet for mirrors. Newsgroup available over NNTP: nntp://lore.altlinux.org/org.altlinux.lists.sisyphus-cybertalk AGPL code for this site: git clone https://public-inbox.org/public-inbox.git