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


Groups > linux.debian.security > #5664

Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to dla-needed.txt with comments.

From Moritz Mühlenhoff <jmm@inutil.org>
Newsgroups linux.debian.security
Subject Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to dla-needed.txt with comments.
Date 2019-08-29 09:40 +0200
Message-ID <yAncd-2NT-3@gated-at.bofh.it> (permalink)
References <yvRkB-8kK-3@gated-at.bofh.it> <yvRkB-8kK-1@gated-at.bofh.it> <yvRXj-mJ-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Adding the radare2 uploaders to CC.

On Fri, Aug 16, 2019 at 11:23:05PM +0200, Markus Koschany wrote:
> >> +  NOTE: 20190816: Affected by CVE-2019-14745. Vulnerable code is in
> >> +  NOTE: libr/core/bin.c. Many no-dsa issues in Jessie and Stretch. Should we
> >> +  NOTE: continue the current approach, update to a newer upstream version or mark
> >> +  NOTE: radare2 as unsupported? Also note that there is a r2-pwnDebian challenge...
> >> +  NOTE: https://bananamafia.dev/post/r2-pwndebian/ (apo)
> > 
> > I'd be in favor of marking radare2 as unsupported, probably even for stable,
> > but definitly for oldstable and older.
> > 
> > I'd be happy to do these changes in src:debian-security-tracker and
> > uploading this to sid.
> 
> +1
> 
> I just noticed that we are not consistent with fixing CVE in radare2 and
> I would also be in favor of marking it as unsupported. Another option
> would be to package always the latest upstream release and backport that
> to stable and oldstable but it seems we already lag behind a few
> versions in unstable, so I'd rather choose the first option.

The upstream link makes it sound as if they are one of those upstreams
which reject the idea of distributions shipping an older release to
a stable distro. For a tool like radare2 that seems fair enough, so
how about simply excluding it from stable releases (and retroactively
drop it from Buster/Stretch in the forthcoming point releases)?

Cheers,
         Moritz

Back to linux.debian.security | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Re: [Git][security-tracker-team/security-tracker][master] Add  radare2 to dla-needed.txt with comments. Holger Levsen <holger@layer-acht.org> - 2019-08-16 22:50 +0200
  Re: [Git][security-tracker-team/security-tracker][master] Add radare2  to dla-needed.txt with comments. Markus Koschany <apo@debian.org> - 2019-08-16 23:30 +0200
    Re: [Git][security-tracker-team/security-tracker][master] Add  radare2 to dla-needed.txt with comments. Moritz Mühlenhoff <jmm@inutil.org> - 2019-08-29 09:40 +0200
      Re: [Git][security-tracker-team/security-tracker][master] Add  radare2 to dla-needed.txt with comments. Raphael Hertzog <hertzog@debian.org> - 2019-08-29 13:50 +0200
        how to deal with widely used packages unsuitable for stable (was Re:  [Git][security-tracker-team/security-tracker][master] Add radare2 to  dla-needed.txt with comments.) Holger Levsen <holger@layer-acht.org> - 2019-08-29 14:20 +0200
          Re: how to deal with widely used packages unsuitable for stable (was  Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to  dla-needed.txt with comments.) Raphael Hertzog <hertzog@debian.org> - 2019-08-29 14:30 +0200
            Re: how to deal with widely used packages unsuitable for stable (was  Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to  dla-needed.txt with comments.) Paul Gevers <elbrus@debian.org> - 2019-08-29 15:20 +0200
              Re: how to deal with widely used packages unsuitable for stable (was  Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to  dla-needed.txt with comments.) Dan Clery <dan@savevsgeek.com> - 2019-08-29 16:40 +0200
                Re: how to deal with widely used packages unsuitable for stable (was  Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to  dla-needed.txt with comments.) Raphael Hertzog <hertzog@debian.org> - 2019-08-30 09:20 +0200
                Re: how to deal with widely used packages unsuitable for stable (was  Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to  dla-needed.txt with comments.) Alexander Wirt <formorer@formorer.de> - 2019-08-30 09:40 +0200
                Re: how to deal with widely used packages unsuitable for stable (was  Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to  dla-needed.txt with comments.) Raphael Hertzog <hertzog@debian.org> - 2019-08-30 11:00 +0200
                Re: how to deal with widely used packages unsuitable for stable (was  Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to  dla-needed.txt with comments.) Alexander Wirt <formorer@formorer.de> - 2019-08-30 11:10 +0200
                Re: how to deal with widely used packages unsuitable for stable (was  Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to  dla-needed.txt with comments.) Raphael Hertzog <hertzog@debian.org> - 2019-08-30 16:50 +0200
                Side issue/question -- {Re: how to deal with widely used packages  ...} Richard Owlett <rowlett@cloud85.net> - 2019-08-30 17:20 +0200
                Re: how to deal with widely used packages unsuitable for stable (was  Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to  dla-needed.txt with comments.) Alexander Wirt <formorer@formorer.de> - 2019-08-30 22:10 +0200
                Re: how to deal with widely used packages unsuitable for stable (was  Re: [Git][security-tracker-team/security-tracker][master] Add radare2 to  dla-needed.txt with comments.) Moritz Mühlenhoff <jmm@inutil.org> - 2019-08-30 10:20 +0200
      Re: [Git][security-tracker-team/security-tracker][master] Add  radare2 to dla-needed.txt with comments. Moritz Mühlenhoff <jmm@inutil.org> - 2019-09-04 21:40 +0200

csiph-web