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
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
 
Latent bugs in armel, armhf packages built before t64 transition (3 replies — unroll) Chris Hofstaedtler <zeha@debian.org> 2024-08-16 00:30 +0200
   → Re: Latent bugs in armel, armhf packages built before t64 transition Emanuele Rocca <ema@debian.org> 2024-08-16 10:30 +0200
     → Re: Latent bugs in armel, armhf packages built before t64 transition Martin <debacle@debian.org> 2024-11-27 23:50 +0100
   → Re: Latent bugs in armel, armhf packages built before t64 transition Leandro Cunha <leandrocunha016@gmail.com> 2024-11-28 00:30 +0100
 
Securing Debian Manual, Out of Date? debianmailinglists.hz5zm@simplelogin.com 2024-11-17 03:20 +0100
 
Fwd: gnome-settings-daemon breaks existing usbguard rules, allowing all usb device by default jan kapoli <jankapoli@proton.me> 2024-11-16 00:10 +0100
 
Re: Bug#539352: /etc/init.d/mountkernfs.sh: Please mount debugfs when available in the kernel Mark Hindley <mark@hindley.org.uk> 2024-11-11 19:50 +0100
 
Upcoming stable point releases: 12.8 and 12.9 (1 reply — unroll) Jonathan Wiltshire <jmw@debian.org> 2024-10-13 12:50 +0200
   → Re: Upcoming stable point releases: 12.8 and 12.9 "Adam D. Barratt" <adam@adam-barratt.org.uk> 2024-11-09 11:40 +0100
 
dpkg MD5 (13 replies — unroll) David Campbell <dcampbell24@gmail.com> 2024-11-07 23:10 +0100
   → Re: dpkg MD5 Jonathan Hutchins <hutchins@tarcanfel.org> 2024-11-07 23:20 +0100
     → Re: dpkg MD5 David Campbell <dcampbell24@gmail.com> 2024-11-07 23:40 +0100
   → Re: dpkg MD5 Jeremy Stanley <fungi@yuggoth.org> 2024-11-08 01:30 +0100
     → Re: dpkg MD5 Jeffrey Walton <noloader@gmail.com> 2024-11-08 03:40 +0100
       → Re: dpkg MD5 Jeremy Stanley <fungi@yuggoth.org> 2024-11-08 04:20 +0100
         → Re: dpkg MD5 debianmailinglists.hz5zm@simplelogin.com 2024-11-08 05:20 +0100
           → Re: dpkg MD5 Jeremy Stanley <fungi@yuggoth.org> 2024-11-08 16:50 +0100
             → Re: dpkg MD5 SZÉPE Viktor <viktor@szepe.net> 2024-11-08 17:00 +0100
               → Re: dpkg MD5 Jeremy Stanley <fungi@yuggoth.org> 2024-11-08 18:30 +0100
         → Re: dpkg MD5 Jeffrey Walton <noloader@gmail.com> 2024-11-08 06:20 +0100
         → Re: dpkg MD5 Jeffrey Walton <noloader@gmail.com> 2024-11-08 20:40 +0100
   → Re: dpkg MD5 Jeffrey Walton <noloader@gmail.com> 2024-11-08 06:30 +0100
   → Re: dpkg MD5 Simon Josefsson <simon@josefsson.org> 2024-11-08 10:10 +0100
 
I Joined This List (1 reply — unroll) David Campbell <dcampbell24@gmail.com> 2024-11-08 02:30 +0100
   → Re: I Joined This List Jeffrey Walton <noloader@gmail.com> 2024-11-08 06:10 +0100
 
Re: security-tracker: A proposal to significantly reduce reported false-positives (no affected-code shipped) Samuel Henrique <samueloph@debian.org> 2024-11-02 21:20 +0100
 
Re: security-tracker: A proposal to significantly reduce reported false-positives (no affected-code shipped) (1 reply — unroll) Samuel Henrique <samueloph@debian.org> 2024-10-29 20:30 +0100
   → Re: security-tracker: A proposal to significantly reduce reported false-positives (no affected-code shipped) Salvatore Bonaccorso <carnil@debian.org> 2024-10-29 20:50 +0100
 
Re: security-tracker: A proposal to significantly reduce reported false-positives (no affected-code shipped) Samuel Henrique <samueloph@debian.org> 2024-08-31 20:30 +0200
 
Upcoming stable point release (12.7) (1 reply — unroll) Jonathan Wiltshire <jmw@debian.org> 2024-07-16 22:30 +0200
   → Re: Upcoming stable point release (12.7) "Adam D. Barratt" <adam@adam-barratt.org.uk> 2024-08-31 13:40 +0200
 
Re: Upcoming oldstable point release (11.11) "Adam D. Barratt" <adam@adam-barratt.org.uk> 2024-08-31 13:40 +0200
 
Recording for my DebConf talk about CVEs (2 replies — unroll) Samuel Henrique <samueloph@debian.org> 2024-08-27 23:40 +0200
   → Re: Recording for my DebConf talk about CVEs Sylvain Beucler <beuc@beuc.net> 2024-08-30 12:20 +0200
     → Re: Recording for my DebConf talk about CVEs "Darren S." <phatbuckett@gmail.com> 2024-08-31 08:30 +0200
 
Bug#1075786: znc.service restarts without warning on upgrade Jesse Rhodes <jesse@sney.ca> 2024-07-05 07:30 +0200
 
Re: Upcoming oldstable point release (11.10) (1 reply — unroll) Jonathan Wiltshire <jmw@debian.org> 2024-06-12 22:20 +0200
   → Re: Upcoming oldstable point release (11.10) "Adam D. Barratt" <adam@adam-barratt.org.uk> 2024-06-29 13:00 +0200
 
Re: Upcoming stable point release (12.6) "Adam D. Barratt" <adam@adam-barratt.org.uk> 2024-06-29 13:00 +0200
 
Bug#1074468: RM: salt/oldstable-security -- RoSRM; removed from oldstable Jonathan Wiltshire <jmw@debian.org> 2024-06-29 10:30 +0200
 
Bug#1074467: RM: snort/oldstable-security -- RoSRM; removed from oldstable Jonathan Wiltshire <jmw@debian.org> 2024-06-29 10:30 +0200
 
CVE applicability (2 replies — unroll) Arul Anand MM <arulanandkk1@gmail.com> 2024-06-18 21:00 +0200
   → Re: CVE applicability Salvatore Bonaccorso <carnil@debian.org> 2024-06-19 08:00 +0200
   → Re: CVE applicability Thomas Hochstein <thh@thh.name> 2024-06-19 23:50 +0200
 
Re: security-tracker: A proposal to significantly reduce reported false-positives (no affected-code shipped) Samuel Henrique <samueloph@debian.org> 2024-05-19 03:50 +0200
 
Bug#1069062: golang-github-disintegration-imaging: CVE-2023-36308 Nilesh Patra <nilesh@debian.org> 2024-04-24 21:20 +0200
 
Re: security-tracker: A proposal to significantly reduce reported false-positives (no affected-code shipped) Samuel Henrique <samueloph@debian.org> 2024-04-22 23:50 +0200
 
Workaround for the GSM privilege escalation vulnerability Stephan Verbücheln <verbuecheln@posteo.de> 2024-04-13 00:00 +0200
 
Re: RFS: paramspider package Samuel Henrique <samueloph@debian.org> 2024-04-07 00:10 +0200
 
Re: RFS: assetfinder package Samuel Henrique <samueloph@debian.org> 2024-04-06 22:00 +0200
 
Re: security-tracker: A proposal to significantly reduce reported false-positives (no affected-code shipped) Samuel Henrique <samueloph@debian.org> 2024-04-06 09:52 +0200
 
security-tracker: A proposal to significantly reduce reported false-positives (no affected-code shipped) (1 reply — unroll) Samuel Henrique <samueloph@debian.org> 2024-04-06 09:50 +0200
   → Re: security-tracker: A proposal to significantly reduce reported false-positives (no affected-code shipped) Gian Piero Carrubba <gpiero@rm-rf.it> 2024-04-06 09:51 +0200
 
Re: security-tracker: A proposal to significantly reduce reported false-positives (no affected-code shipped) Gian Piero Carrubba <gpiero@rm-rf.it> 2024-04-06 09:51 +0200
 
xz backdoor prevention and hosts.deny? (1 reply — unroll) Nick Sal <specialroumpa@proton.me> 2024-03-31 23:50 +0200
   → Re: xz backdoor prevention and hosts.deny? Gian Piero Carrubba <gpiero@rm-rf.it> 2024-04-01 11:50 +0200
 
Re: Upcoming stable point release (12.6) (1 reply — unroll) Gian Piero Carrubba <gpiero@rm-rf.it> 2024-03-30 09:50 +0100
   → Re: Upcoming stable point release (12.6) Joerg Jaspert <joerg@debian.org> 2024-03-30 14:50 +0100
 
CVE-2023-41105 not fixed in bookworm (3 replies — unroll) Richard van den Berg <richard@vdberg.org> 2024-03-01 09:20 +0100
   → Re: CVE-2023-41105 not fixed in bookworm Salvatore Bonaccorso <carnil@debian.org> 2024-03-10 15:00 +0100
     → Re: CVE-2023-41105 not fixed in bookworm StealthMode Hu <stealthmode1975@gmail.com> 2024-03-10 22:30 +0100
       → Re: CVE-2023-41105 not fixed in bookworm piorunz <piorunz@gmx.com> 2024-03-17 14:30 +0100
 
Re: Upcoming oldstable point release (11.9) "Adam D. Barratt" <adam@adam-barratt.org.uk> 2024-02-10 14:10 +0100
 
Re: Upcoming stable point release (12.5) "Adam D. Barratt" <adam@adam-barratt.org.uk> 2024-02-10 14:10 +0100
 
How do I help the project? Tiago Zaniquelli <zani0x03@gmail.com> 2024-01-14 02:50 +0100
 
please help with python3-future removal Alexandre Detiste <alexandre.detiste@gmail.com> 2024-01-12 17:00 +0100
 
new redirects for www.d.o/security and www.d.o/lts/security (1 reply — unroll) Thomas Lange <lange@cs.uni-koeln.de> 2024-01-05 00:20 +0100
   → Re: new redirects for www.d.o/security and www.d.o/lts/security Salvatore Bonaccorso <carnil@debian.org> 2024-01-05 09:30 +0100
 
Reaction to potential PGP schism (11 replies — unroll) Stephan Verbücheln <verbuecheln@posteo.de> 2023-12-14 11:40 +0100
   → Re: Reaction to potential PGP schism Pierre-Elliott Bécue <peb@debian.org> 2023-12-14 17:00 +0100
   → Re: Reaction to potential PGP schism Joerg Jaspert <joerg@debian.org> 2023-12-14 23:10 +0100
   → Re: Reaction to potential PGP schism Daniel Kahn Gillmor <dkg@fifthhorseman.net> 2023-12-21 04:30 +0100
     → Re: Reaction to potential PGP schism Christoph Biedl <debian.axhn@manchmal.in-ulm.de> 2023-12-21 09:30 +0100
       → Re: Reaction to potential PGP schism Meso Security <MesoSecurity@protonmail.ch> 2023-12-21 10:00 +0100
       → Re: Reaction to potential PGP schism Stephan Verbücheln <verbuecheln@posteo.de> 2023-12-21 14:00 +0100
     → Re: Reaction to potential PGP schism Gioele Barabucci <gioele@svario.it> 2023-12-21 11:20 +0100
       → Re: Reaction to potential PGP schism Daniel Kahn Gillmor <dkg@fifthhorseman.net> 2023-12-22 00:50 +0100
     → Re: Reaction to potential PGP schism Enrico Zini <enrico@enricozini.org> 2023-12-21 11:40 +0100
     → Re: Reaction to potential PGP schism Cyril Brulebois <kibi@debian.org> 2023-12-22 02:30 +0100
     → SOP migration (was Re: Reaction to potential PGP schism) Guillem Jover <guillem@debian.org> 2024-01-03 20:00 +0100
 
Performance of security.debian.org? наб <nabijaczleweli@nabijaczleweli.xyz> 2023-12-25 16:30 +0100
 
libssh CVE-2023-6004, CVE-2023-6918, CVE-2023-48795 Sean Whitton <spwhitton@spwhitton.name> 2023-12-24 10:30 +0100
 
Handle jq CVE-2023-49355, which is equal to CVE-2023-50246 (1 reply — unroll) ChangZhuo Chen (陳昌倬) <czchen@debian.org> 2023-12-16 11:20 +0100
   → Re: Handle jq CVE-2023-49355, which is equal to CVE-2023-50246 ChangZhuo Chen (陳昌倬) <czchen@debian.org> 2023-12-20 03:40 +0100

← Newer ~Page 1 of ~15 (articles 6291–6411) Older →


csiph-web