Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.security
2228 articles, 741 threads (numbers 4277 – 6533) — flat view
| Advanced| Subject | Author | Date |
|---|---|---|
| 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 |
| Open security issues affecting trixie which are not RC (2025-04-29) (3 replies — unroll) | Moritz Mühlenhoff <jmm@inutil.org> | 2025-04-29 20:30 +0200 |
| → Re: Open security issues affecting trixie which are not RC (2025-04-29) | Jeffrey Walton <noloader@gmail.com> | 2025-04-29 22:20 +0200 |
| → Re: Open security issues affecting trixie which are not RC (2025-04-29) | NoisyCoil <noisycoil@disroot.org> | 2025-04-29 23:40 +0200 |
| → Re: Open security issues affecting trixie which are not RC (2025-04-29) | Sune Vuorela <nospam@vuorela.dk> | 2025-04-30 09:10 +0200 |
| Testmail (12 replies — unroll) | hste@tutamail.com | 2025-03-22 10:10 +0100 |
| → Re: Testmail | sylvain <contact@baal.fr> | 2025-03-22 11:20 +0100 |
| → Testmail | Arne Pisch <old_man999@freenet.de> | 2025-03-22 12:30 +0100 |
| → Re: Testmail | j V <janoval42@gmail.com> | 2025-03-22 15:40 +0100 |
| → Re: Testmail | Álesson Nunes <pinkblez@gmail.com> | 2025-03-22 19:40 +0100 |
| → Re: Testmail | Meso Security <MesoSecurity@protonmail.ch> | 2025-03-22 18:50 +0100 |
| → Re: Testmail | Jeffrey Walton <noloader@gmail.com> | 2025-03-22 18:50 +0100 |
| → FWD: Re: Testmail | hste@tutamail.com | 2025-03-23 08:40 +0100 |
| → Strange welcome after a testmail | hste@tutamail.com | 2025-03-24 10:30 +0100 |
| → Re: Strange welcome after a testmail | Pierre-Elliott Bécue <peb@debian.org> | 2025-03-24 16:40 +0100 |
| → FWD: FWD: FWD: Re: Strange welcome after a testmail | hste@tutamail.com | 2025-03-24 17:10 +0100 |
| → Re: FWD: FWD: FWD: Re: Strange welcome after a testmail | Lupe Christoph <lupe@lupe-christoph.de> | 2025-03-24 17:20 +0100 |
| → FWD: Re: Strange welcome after a testmail | hste@tutamail.com | 2025-03-24 19:50 +0100 |
| Re: sbuscribe | Povl Ole Haarlev Olsen <debian-security@stderr.dk> | 2025-03-19 14:50 +0100 |
| PHISHING ALERT: Re: Email delivery failed | Julien Plissonneau Duquène <sre4ever@free.fr> | 2025-01-27 08:50 +0100 |
| Intel Microcode updates (30 replies — unroll) | Russell Coker <russell@coker.com.au> | 2019-06-10 06:10 +0200 |
| → Re: Intel Microcode updates | Michael Stone <mstone@debian.org> | 2019-06-10 13:20 +0200 |
| → Re: Intel Microcode updates | Davide Prina <davide.prina@gmail.com> | 2019-06-10 19:50 +0200 |
| → Re: Intel Microcode updates | Michael Stone <mstone@debian.org> | 2019-06-10 20:40 +0200 |
| → Re: Intel Microcode updates | Davide Prina <davide.prina@gmail.com> | 2019-06-11 20:10 +0200 |
| → Re: Intel Microcode updates | Michael Stone <mstone@debian.org> | 2019-06-11 22:00 +0200 |
| → Re: Intel Microcode updates | Russell Coker <russell@coker.com.au> | 2019-06-11 14:00 +0200 |
| → Re: Intel Microcode updates | Henrique de Moraes Holschuh <hmh@debian.org> | 2019-06-11 04:20 +0200 |
| → Re: Intel Microcode updates | Russell Coker <russell@coker.com.au> | 2019-06-11 14:00 +0200 |
| → Re: Intel Microcode updates | Moritz Mühlenhoff <jmm@inutil.org> | 2019-06-11 14:30 +0200 |
| → Re: Intel Microcode updates | Henrique de Moraes Holschuh <hmh@debian.org> | 2019-06-12 17:00 +0200 |
| → Re: Intel Microcode updates | Elmar Stellnberger <estellnb@gmail.com> | 2019-06-18 13:00 +0200 |
| → Re: Intel Microcode updates | Henrique de Moraes Holschuh <hmh@debian.org> | 2019-06-23 22:30 +0200 |
| → Re: Intel Microcode updates | Elmar Stellnberger <estellnb@gmail.com> | 2019-06-23 22:40 +0200 |
| → Re: Intel Microcode updates | Henrique de Moraes Holschuh <hmh@debian.org> | 2019-06-24 04:10 +0200 |
| → Re: Intel Microcode updates | Davide Prina <davide.prina@gmail.com> | 2019-06-24 19:40 +0200 |
| → Re: Intel Microcode updates | "Henrique de Moraes Holschuh" <hmh@debian.org> | 2024-12-08 01:20 +0100 |
| → Re: Intel Microcode updates | Elmar Stellnberger <estellnb@gmail.com> | 2019-06-18 22:10 +0200 |
| → Re: Intel Microcode updates | Elmar Stellnberger <estellnb@gmail.com> | 2019-06-22 14:30 +0200 |
| → Re: Intel Microcode updates | Andrew McGlashan <andrew.mcglashan@affinityvision.com.au> | 2019-06-11 19:10 +0200 |
| → Re: Intel Microcode updates | Holger Levsen <holger@layer-acht.org> | 2019-06-11 19:20 +0200 |
| → Re: Intel Microcode updates | Andrew McGlashan <andrew.mcglashan@affinityvision.com.au> | 2019-06-11 21:10 +0200 |
| → Re: Intel Microcode updates | Andrew McGlashan <andrew.mcglashan@affinityvision.com.au> | 2019-06-11 21:20 +0200 |
| → Re: Intel Microcode updates | Elmar Stellnberger <estellnb@gmail.com> | 2019-06-18 11:20 +0200 |
| → Re: Intel Microcode updates | Andrew McGlashan <andrew.mcglashan@affinityvision.com.au> | 2019-06-18 20:30 +0200 |
| → Re: Intel Microcode updates | Rob van der Putten <rob@sput.nl> | 2019-06-20 14:40 +0200 |
| → Re: Intel Microcode updates | Elmar Stellnberger <estellnb@gmail.com> | 2019-06-18 22:10 +0200 |
| → Re: Intel Microcode updates | Elmar Stellnberger <estellnb@gmail.com> | 2019-06-22 14:30 +0200 |
| → Re: Intel Microcode updates | Davide Prina <davide.prina@gmail.com> | 2019-06-23 10:00 +0200 |
| → Re: Intel Microcode updates | Lou Poppler <LouPoppler@cableone.net> | 2019-06-24 02:20 +0200 |
| → Re: Intel Microcode updates | Davide Prina <davide.prina@gmail.com> | 2019-06-24 20:00 +0200 |
| Re: [DSA 5824-1] chromium security update (1 reply — unroll) | Bjørn Mork <bjorn@mork.no> | 2024-12-07 13:10 +0100 |
| → Re: [DSA 5824-1] chromium security update | Santiago Vila <sanvila@debian.org> | 2024-12-07 13:30 +0100 |
| Should Debian ask for a CPE when a CVE in Debian is found? (8 replies — unroll) | "Wheeler, David A" <dwheeler@ida.org> | 2016-02-12 17:30 +0100 |
| → RE: Should Debian ask for a CPE when a CVE in Debian is found? | "Booth, Harold" <harold.booth@nist.gov> | 2016-02-12 19:30 +0100 |
| → Re: Should Debian ask for a CPE when a CVE in Debian is found? | "David A. Wheeler" <dwheeler@linuxfoundation.org> | 2024-12-01 21:50 +0100 |
| → Re: Should Debian ask for a CPE when a CVE in Debian is found? | Paul Wise <pabs@debian.org> | 2016-02-13 22:00 +0100 |
| → Re: Should Debian ask for a CPE when a CVE in Debian is found? | Holger Levsen <holger@layer-acht.org> | 2016-02-15 10:10 +0100 |
| → Re: Should Debian ask for a CPE when a CVE in Debian is found? | Vulchev <v.vulchev@gmail.com> | 2016-02-15 10:30 +0100 |
| → Re: Should Debian ask for a CPE when a CVE in Debian is found? | Elmar Stellnberger <estellnb@gmail.com> | 2016-02-15 10:40 +0100 |
| → Re: Should Debian ask for a CPE when a CVE in Debian is found? | "georg@riseup.net" <georg@riseup.net> | 2016-02-15 18:40 +0100 |
| → Re: Should Debian ask for a CPE when a CVE in Debian is found? | Paul Wise <pabs@debian.org> | 2016-02-16 00:50 +0100 |
| Re: I forgot my password and Debian need password when booting (6 replies — unroll) | Paul Wise <pabs@debian.org> | 2019-10-27 03:30 +0100 |
| → Re: I forgot my password and Debian need password when booting | Mostaf Faridi <mostafafaridi@gmail.com> | 2019-10-27 08:00 +0100 |
| → Re: I forgot my password and Debian need password when booting | Paul Wise <pabs@debian.org> | 2019-10-27 08:30 +0100 |
| → Re: I forgot my password and Debian need password when booting | Craig <chouck@binghamton.edu> | 2019-10-27 22:10 +0100 |
| → Re: I forgot my password and Debian need password when booting | Paul Tagliamonte <paultag@debian.org> | 2019-10-27 22:20 +0100 |
| → Re: I forgot my password and Debian need password when booting | CMH <chouck@binghamton.edu> | 2019-10-28 12:30 +0100 |
| → Re: I forgot my password and Debian need password when booting | CMH <chouck@binghamton.edu> | 2024-11-28 21:40 +0100 |
| (No Subject) (2 replies — unroll) | "Sergey S." <hello@8am.dev> | 2024-11-28 10:30 +0100 |
| → Re: (No Subject) | "Sergey S." <hello@8am.dev> | 2024-11-28 11:00 +0100 |
| → Re: (No Subject) | Povl Ole Haarlev Olsen <debian-security@stderr.dk> | 2024-11-28 11:20 +0100 |
| bind9 update 9.16.50 -- too many record (7 replies — unroll) | Guillaume Bienkowski <guillaume.bienkowski@braincube.com> | 2024-07-26 17:30 +0200 |
| → Re: bind9 update 9.16.50 -- too many record | Lee <ler762@gmail.com> | 2024-07-26 21:50 +0200 |
| → Re: bind9 update 9.16.50 -- too many record | Salvatore Bonaccorso <carnil@debian.org> | 2024-07-28 07:40 +0200 |
| → Re: bind9 update 9.16.50 -- too many record | Ondřej Surý <ondrej@sury.org> | 2024-07-28 10:30 +0200 |
| → Re: bind9 update 9.16.50 -- too many record | Guillaume Bienkowski <guillaume.bienkowski@braincube.com> | 2024-07-28 18:30 +0200 |
| → Re: bind9 update 9.16.50 -- too many record | Ondřej Surý <ondrej@sury.org> | 2024-07-29 12:20 +0200 |
| → Re: bind9 update 9.16.50 -- too many record | Salvatore Bonaccorso <carnil@debian.org> | 2024-07-29 15:30 +0200 |
| → Re: bind9 update 9.16.50 -- too many record | Guillaume Bienkowski <guillaume.bienkowski@braincube.com> | 2024-11-28 10:30 +0100 |
← Newer ~Page 2 of ~38 (articles 6379–6450) Older →
csiph-web