Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.security

linux.debian.security

2228 articles, 741 threads (numbers 4277 – 6533) — flat view

| Advanced

Subject Author Date
Feasibility to patch libskia moving forward (2 replies — unroll) Filip Strömbäck <fstromback@debian.org> 2026-09-24 09:10 +0200
   → Re: Feasibility to patch libskia moving forward Sylvain Beucler <beuc@beuc.net> 2026-10-01 10:50 +0200
   → Re: Feasibility to patch libskia moving forward Filip Strömbäck <fstromback@debian.org> 2026-10-10 18:00 +0200
 
Re: Re: Reporting CVE as fixed back to authority (1 reply — unroll) Alexandru Mihail <alexandru2897@gmail.com> 2026-09-15 15:40 +0200
   → Re: Reporting CVE as fixed back to authority Alexandru Mihail <alexandru.mihail2897@gmail.com> 2026-09-21 12:10 +0200
 
Reporting CVE as fixed back to authority (2 replies — unroll) Alexandru Mihail <alexandru.mihail2897@gmail.com> 2026-09-09 11:00 +0200
   → Re: Reporting CVE as fixed back to authority Salvatore Bonaccorso <carnil@debian.org> 2026-09-10 06:40 +0200
     → Re: Reporting CVE as fixed back to authority Daniel Leidert <daniel.leidert@wgdd.de> 2026-09-10 07:40 +0200
 
bullseye-security is not archived (1 reply — unroll) Navaneetha Krishnan <nkr1729@gmail.com> 2026-09-09 06:30 +0200
   → Re: bullseye-security is not archived Salvatore Bonaccorso <carnil@debian.org> 2026-09-10 06:40 +0200
 
Responsible disclosure — security issues in apt, >= 3.0 (3 replies — unroll) Badr Azeez <pronajaf@gmail.com> 2026-08-25 13:40 +0200
   → Re: Responsible disclosure — security issues in apt, >= 3.0 Thomas Williams <thomas@newport.wales> 2026-08-25 14:30 +0200
     → Re: Responsible disclosure — security issues in apt, >= 3.0 Pierre-Elliott Bécue <peb@debian.org> 2026-08-25 19:30 +0200
   → Re: Responsible disclosure — security issues in apt, >= 3.0 Florent Rougon <f.rougon@frougon.net> 2026-08-25 14:40 +0200
 
Bug#1144086: trixie-pu: package redmine/6.0.10 Soren Stoutner <soren@debian.org> 2026-08-11 06:00 +0200
 
CVE-2026-60137 wordpress vulnerability Richard van den Berg <richard@vdberg.org> 2026-07-20 11:30 +0200
 
SE Linux userspace local DOS attack Russell Coker <russell@coker.com.au> 2026-07-19 09:50 +0200
 
Bug#1142349: ca-certificates: certdata2pem.py drops S/MIME-trusted-but-TLS-distrusted CAs, breaking S/MIME verification for chains Mozilla still trusts David Woodhouse <dwmw2@infradead.org> 2026-07-18 12:20 +0200
 
Re: Upcoming stable point release (13.6) "Adam D. Barratt" <adam@adam-barratt.org.uk> 2026-07-11 12:30 +0200
 
Re: Upcoming oldstable point release (12.15) "Adam D. Barratt" <adam@adam-barratt.org.uk> 2026-07-11 12:30 +0200
 
Size of the security-tracker repository (4 replies — unroll) Christoph Biedl <debian.axhn@manchmal.in-ulm.de> 2026-06-04 19:40 +0200
   → Re: Size of the security-tracker repository Sylvain Beucler <beuc@beuc.net> 2026-06-06 09:10 +0200
     → Re: Size of the security-tracker repository Christoph Biedl <debian.axhn@manchmal.in-ulm.de> 2026-06-07 21:30 +0200
       → Re: Size of the security-tracker repository Sylvain Beucler <beuc@beuc.net> 2026-06-11 07:30 +0200
         → Re: Size of the security-tracker repository Sylvain Beucler <beuc@beuc.net> 2026-06-12 07:40 +0200
 
Offering help with atril/trixie,bookworm security update Andreas Henriksson <andreas@fatal.se> 2026-05-27 10:20 +0200
 
Re: Backporting caddy 2.11.2 Andrew Lee <ajqlee@debian.org> 2026-05-20 11:00 +0200
 
Re: Upcoming oldstable point release (12.14) "Adam D. Barratt" <adam@adam-barratt.org.uk> 2026-05-16 13:20 +0200
 
Re: Upcoming stable point release (13.5) "Adam D. Barratt" <adam@adam-barratt.org.uk> 2026-05-16 13:20 +0200
 
Questions re: modprobe mitigations and auditing (from: CVE-2026-31431) James Addison <jay@jp-hosting.net> 2026-05-13 13:10 +0200
 
[nghttp2] request for review of Debian CVE-2023-44487 backports Lukas Märdian <slyon@debian.org> 2026-04-29 16:40 +0200
 
Re: DSA Urgency Critical Salvatore Bonaccorso <carnil@debian.org> 2026-04-26 21:20 +0200
 
harbian-audit v0.8.0 for Debian 13 is released Samson <sccxboy@gmail.com> 2026-04-11 18:20 +0200
 
Re: Upcoming stable point release (13.4) "Adam D. Barratt" <adam@adam-barratt.org.uk> 2026-03-14 12:50 +0100
 
Request for Sponsorship Toward Debian Maintainer Status — Security Team Focus Meso Security <MesoSecurity@protonmail.ch> 2026-02-04 00:20 +0100
 
Re: Next Event- Sponsor, Exhibitor & Delegates Acquisition Strategy! Caralin wilson <caralin@p2bservices.com> 2026-02-03 10:20 +0100
 
Re: Upcoming oldstable point release (12.13) Jonathan Wiltshire <jmw@debian.org> 2026-01-10 13:50 +0100
 
Re: Upcoming stable point release (13.3) Jonathan Wiltshire <jmw@debian.org> 2026-01-10 13:50 +0100
 
経営者の8割が誤解する「教育市場」 石島 紗希/教育フランチャイズセミナー事務局 <info@fc-seminar-online.jp> 2025-12-17 07:40 +0100
 
Re: Errands task manager upstream unconditionally disables TLS certificate verification for CalDAV; does this need to be addressed? Russell Coker <russell@coker.com.au> 2025-12-10 08:20 +0100
 
Keyserver for gpg.conf ? (13 replies — unroll) Francesco Poli <invernomuto@paranoici.org> 2025-11-15 10:40 +0100
   → Re: Keyserver for gpg.conf ? Gunnar Wolf <gwolf@debian.org> 2025-11-15 19:10 +0100
     → Re: Keyserver for gpg.conf ? Holger Levsen <holger@layer-acht.org> 2025-11-15 21:50 +0100
       → Re: Keyserver for gpg.conf ? debianmailinglists.hz5zm@simplelogin.com 2025-11-16 04:10 +0100
         → Re: Keyserver for gpg.conf ? Gunnar Wolf <gwolf@debian.org> 2025-11-16 17:10 +0100
         → Re: Keyserver for gpg.conf ? Jeremy Stanley <fungi@yuggoth.org> 2025-11-17 16:30 +0100
           → Re: Keyserver for gpg.conf ? Jeffrey Walton <noloader@gmail.com> 2025-11-17 16:40 +0100
       → Re: Keyserver for gpg.conf ? Gunnar Wolf <gwolf@debian.org> 2025-11-16 17:10 +0100
     → Re: Keyserver for gpg.conf ? Francesco Poli <invernomuto@paranoici.org> 2025-11-16 13:40 +0100
       → Re: Keyserver for gpg.conf ? Gunnar Wolf <gwolf@debian.org> 2025-11-16 17:10 +0100
   → Re: Keyserver for gpg.conf ? Jeffrey Walton <noloader@gmail.com> 2025-11-17 17:00 +0100
     → Re: Keyserver for gpg.conf ? Francesco Poli <invernomuto@paranoici.org> 2025-11-17 18:40 +0100
       → Re: Keyserver for gpg.conf ? Jeremy Stanley <fungi@yuggoth.org> 2025-11-17 18:50 +0100
       → Re: Keyserver for gpg.conf ? debianmailinglists.hz5zm@simplelogin.com 2025-11-18 01:50 +0100
 
Re: Upcoming stable point release (13.2) "Adam D. Barratt" <adam@adam-barratt.org.uk> 2025-11-15 12:00 +0100
 
Fips Module Config (1 reply — unroll) Robert A Wooldridge <bob.wooldridge@edm-inc.com> 2025-10-28 22:50 +0100
   → Re: Fips Module Config bhaskarvilles@duck.com 2025-10-29 08:00 +0100
 
Status of Intel CET in Debian (2 replies — unroll) Stephan Verbücheln <verbuecheln@posteo.de> 2025-10-15 09:40 +0200
   → Re: Status of Intel CET in Debian Stephan Verbücheln <verbuecheln@posteo.de> 2025-10-15 15:50 +0200
   → Re: Status of Intel CET in Debian Emanuele Rocca <ema@debian.org> 2025-10-16 09:40 +0200
 
Re: Re: BerkeleyDB CVEs Jeffrey Walton <noloader@gmail.com> 2025-10-15 15:50 +0200
 
Re: ftp.debian.org: remove armel from forky and unstable (5 replies — unroll) Thorsten Glaser <tg@debian.org> 2025-09-25 23:50 +0200
   → Re: ftp.debian.org: remove armel from forky and unstable Thorsten Glaser <tg@debian.org> 2025-09-27 17:20 +0200
   → Re: ftp.debian.org: remove armel from forky and unstable Sylvain Beucler <beuc@beuc.net> 2025-09-26 16:50 +0200
     → Re: ftp.debian.org: remove armel from forky and unstable Thorsten Glaser <tg@debian.org> 2025-09-27 01:20 +0200
       → Re: ftp.debian.org: remove armel from forky and unstable Sylvain Beucler <beuc@beuc.net> 2025-09-27 13:10 +0200
     → Re: ftp.debian.org: remove armel from forky and unstable Jochen Sprickerhof <jspricke@debian.org> 2025-09-26 18:50 +0200
 
Re: BerkeleyDB CVEs Jeremy Stanley <fungi@yuggoth.org> 2025-09-26 17:30 +0200
 
On the status of rust/go packages (1 reply — unroll) Sly <slycelot@yandex.ru> 2025-09-27 04:50 +0200
   → Re: On the status of rust/go packages Fabian Grünbichler <debian@fabian.gruenbichler.email> 2025-09-27 10:20 +0200
 
Re: BerkeleyDB CVEs (1 reply — unroll) Carlos Henrique Lima Melara <charles@debian.org> 2025-09-26 17:40 +0200
   → Re: BerkeleyDB CVEs Sylvain Beucler <beuc@beuc.net> 2025-09-26 18:00 +0200
 
Re: BerkeleyDB CVEs debianmailinglists.hz5zm@simplelogin.com 2025-09-26 15:50 +0200
 
Re: Upcoming (old)stable point releases: 13.1 and 12.12 "Adam D. Barratt" <adam@adam-barratt.org.uk> 2025-09-06 13:20 +0200
 
Re: [SECURITY] [DSA 5973-1] linux security update (3 replies — unroll) Stephan Seitz <stse+debian@rootsland.net> 2025-08-14 11:10 +0200
   → Re: [SECURITY] [DSA 5973-1] linux security update Salvatore Bonaccorso <carnil@debian.org> 2025-08-16 20:50 +0200
     → Re: [SECURITY] [DSA 5973-1] linux security update Stephan Seitz <stse+debian@rootsland.net> 2025-08-18 20:20 +0200
       → Re: [SECURITY] [DSA 5973-1] linux security update Salvatore Bonaccorso <carnil@debian.org> 2025-08-19 05:50 +0200
 
Why Does Debian Use PGP to Sign Packages (4 replies — unroll) fosres@posteo.de 2025-08-16 03:40 +0200
   → Re: Why Does Debian Use PGP to Sign Packages Jeffrey Walton <noloader@gmail.com> 2025-08-16 11:20 +0200
     → Re: Why Does Debian Use PGP to Sign Packages Simon Josefsson <simon@josefsson.org> 2025-08-16 11:40 +0200
   → Re: Why Does Debian Use PGP to Sign Packages Simon Josefsson <simon@josefsson.org> 2025-08-16 11:30 +0200
   → Re: Why Does Debian Use PGP to Sign Packages kpcyrd <kpcyrd@archlinux.org> 2025-08-16 16:30 +0200
 
Why Do Developers Continue to Sign with GNUPG (5 replies — unroll) fosres@posteo.de 2025-08-10 17:00 +0200
   → Re: Why Do Developers Continue to Sign with GNUPG "Adam D. Barratt" <adam@adam-barratt.org.uk> 2025-08-10 17:50 +0200
   → Re: Why Do Developers Continue to Sign with GNUPG Jeremy Stanley <fungi@yuggoth.org> 2025-08-10 20:30 +0200
     → Re: Why Do Developers Continue to Sign with GNUPG Simon Josefsson <simon@josefsson.org> 2025-08-12 00:10 +0200
   → Re: Why Do Developers Continue to Sign with GNUPG Malte <ml@enteig.net> 2025-08-10 20:40 +0200
   → Re: Why Do Developers Continue to Sign with GNUPG Gunnar Wolf <gwolf@debian.org> 2025-08-11 07:00 +0200
 
should the Release Notes be updated concerning trixie security (2 replies — unroll) Paul Gevers <elbrus@debian.org> 2025-07-12 22:10 +0200
   → Re: should the Release Notes be updated concerning trixie security Santiago Ruano Rincón <santiagorr@riseup.net> 2025-07-13 01:20 +0200
     → Re: should the Release Notes be updated concerning trixie security Holger Levsen <holger@layer-acht.org> 2025-07-13 10:30 +0200
 
Security tracker suggestions (1 reply — unroll) Adrian Bunk <bunk@debian.org> 2025-06-26 02:20 +0200
   → Re: Security tracker suggestions Roberto C. Sánchez <roberto@debian.org> 2025-06-27 23:50 +0200
 
Resurrecting the Securing Debian Manual (14 replies — unroll) Noah Meyerhans <noahm@debian.org> 2025-06-09 18:30 +0200
   → Re: Resurrecting the Securing Debian Manual Michael Lazin <microlaser@gmail.com> 2025-06-09 18:40 +0200
   → Re: Resurrecting the Securing Debian Manual Holger Levsen <holger@layer-acht.org> 2025-06-09 18:50 +0200
     → Re: Resurrecting the Securing Debian Manual Holger Levsen <holger@layer-acht.org> 2025-06-11 12:10 +0200
       → Re: Resurrecting the Securing Debian Manual Holger Levsen <holger@layer-acht.org> 2025-06-11 18:50 +0200
   → Re: Resurrecting the Securing Debian Manual Jeffrey Chimene <jeff@systasis.co> 2025-06-09 19:10 +0200
   → Re: Resurrecting the Securing Debian Manual Rob Ward <pocketapocketa@protonmail.com> 2025-06-09 19:20 +0200
   → Re: Resurrecting the Securing Debian Manual Vladislav Kurz <vladislav.kurz@webstep.net> 2025-06-09 22:10 +0200
   → Re: Resurrecting the Securing Debian Manual "Dave P." <dprowseus@gmail.com> 2025-06-10 15:20 +0200
     → Re: Resurrecting the Securing Debian Manual Javier Fernandez-Sanguino <jfs@debian.org> 2025-06-10 22:10 +0200
       → Re: Resurrecting the Securing Debian Manual Noah Meyerhans <noahm@debian.org> 2025-06-10 23:00 +0200
         → Re: Resurrecting the Securing Debian Manual Javier Fernandez-Sanguino <jfs@debian.org> 2025-06-11 00:00 +0200
           → Re: Resurrecting the Securing Debian Manual debianmailinglists.hz5zm@simplelogin.com 2025-06-11 08:30 +0200
           → Re: Resurrecting the Securing Debian Manual "Dave P." <dprowseus@gmail.com> 2025-06-11 16:50 +0200
   → Re: Resurrecting the Securing Debian Manual debianmailinglists.hz5zm@simplelogin.com 2025-06-10 19:50 +0200
 
Re: security-tracker: A proposal to significantly reduce reported false-positives (no affected-code shipped) (10 replies — unroll) Samuel Henrique <samueloph@debian.org> 2024-11-28 00:50 +0100
   → Re: security-tracker: A proposal to significantly reduce reported false-positives (no affected-code shipped) Salvatore Bonaccorso <carnil@debian.org> 2024-12-01 15:10 +0100
     → Re: security-tracker: A proposal to significantly reduce reported false-positives (no affected-code shipped) Samuel Henrique <samueloph@debian.org> 2025-03-02 21:50 +0100
       → Re: security-tracker: A proposal to significantly reduce reported false-positives (no affected-code shipped) Samuel Henrique <samueloph@debian.org> 2025-04-13 17:30 +0200
         → Re: security-tracker: A proposal to significantly reduce reported false-positives (no affected-code shipped) Salvatore Bonaccorso <carnil@debian.org> 2025-04-13 17:40 +0200
       → Re: security-tracker: A proposal to significantly reduce reported false-positives (no affected-code shipped) Samuel Henrique <samueloph@debian.org> 2025-04-13 18:10 +0200
         → Re: security-tracker: A proposal to significantly reduce reported false-positives (no affected-code shipped) Salvatore Bonaccorso <carnil@debian.org> 2025-05-01 11:30 +0200
           → Re: security-tracker: A proposal to significantly reduce reported false-positives (no affected-code shipped) Samuel Henrique <samueloph@debian.org> 2025-05-10 21:40 +0200
             → Re: security-tracker: A proposal to significantly reduce reported false-positives (no affected-code shipped) Santiago Ruano Rincón <santiagorr@riseup.net> 2025-05-16 20:30 +0200
               → Re: security-tracker: A proposal to significantly reduce reported false-positives (no affected-code shipped) Salvatore Bonaccorso <carnil@debian.org> 2025-05-18 18:50 +0200
                 → Re: security-tracker: A proposal to significantly reduce reported false-positives (no affected-code shipped) Roberto C. Sánchez <roberto@debian.org> 2025-06-03 23:30 +0200
 
DebCamp 25 Security Tracker sprint - planning announcement Roberto C. Sánchez <roberto@debian.org> 2025-05-22 15:30 +0200
 
Re: Clarification Request: Acceptable Scenarios for Submitting CVE Fixes to Debian Salvatore Bonaccorso <carnil@debian.org> 2025-05-17 22:20 +0200
 
Re: Upcoming stable point release: 12.11 Jonathan Wiltshire <jmw@debian.org> 2025-05-17 11:30 +0200
 
eiärkmýčaež moullereau.rosalina@gmail.com 2025-05-15 07:10 +0200
 
SHH Cipher recommendations and "prohibitions" from Debian? (3 replies — unroll) c.buhtz@posteo.jp 2025-05-13 11:40 +0200
   → Re: SHH Cipher recommendations and "prohibitions" from Debian? Bartosz Fenski <bartosz@fenski.pl> 2025-05-13 12:50 +0200
   → Re: SHH Cipher recommendations and "prohibitions" from Debian? c.buhtz@posteo.jp 2025-05-13 13:20 +0200
   → Use ~/.ssh/config Stephan Verbücheln <verbuecheln@posteo.de> 2025-05-13 14:20 +0200

~Page 1 of ~15 (articles 6417–6533) Older →


csiph-web