Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.security > #6167
| From | Chris Penalver <christopher.m.penalver@gmail.com> |
|---|---|
| Newsgroups | linux.debian.security |
| Subject | Inquiry on Bullseye and https://security-tracker.debian.org/tracker/CVE-2019-8457 |
| Date | 2022-08-26 11:30 +0200 |
| Message-ID | <EYDP3-3aXL-1@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Hi Debian Security Team, I am inquiring on Debian Bullseye as it relates to: https://security-tracker.debian.org/tracker/CVE-2019-8457 Specifically, it is noted the team has put in a good faith effort in analyzing the feasibility of backporting relevant patches to Bullseye, and classifying the urgency of such effort. My read of this so far is that it's a debug mode only exposure, normally disabled in production (by default). With that said, for those environment who are using Bullseye, outside of the amount of changes required for the backport, is there any technical 'gotchas' or further advice the team could provide for those who are considering a self-maintain of relevant patches from bookworm / sid into Bullseye while the discussion continues on this? Thanks! - Chris Peñalver christopher.m.penalver@gmail.com
Back to linux.debian.security | Previous | Next — Next in thread | Find similar
Inquiry on Bullseye and https://security-tracker.debian.org/tracker/CVE-2019-8457 Chris Penalver <christopher.m.penalver@gmail.com> - 2022-08-26 11:30 +0200 Re: Inquiry on Bullseye and https://security-tracker.debian.org/tracker/CVE-2019-8457 Ángel <debian-security@debian.16bits.net> - 2022-09-04 02:30 +0200
csiph-web