All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Call for volunteer(s): cups security bump
Date: Fri, 23 May 2014 11:04:21 -0300	[thread overview]
Message-ID: <537F5565.1010903@zacarias.com.ar> (raw)

Hi all.

I'm one of the people who is regularly involved in patching/bumping
packages when security bugs are discovered and i've got a list of
packages in need of love.
This is a call for volunteers because i think it's important to keep the
package base clean regarding security vulnerabilities.

Right now i have one outstanding package that is in dire need of a
version bump: cups.
If you're a regular cups user for your buildroot project(s) then this
might be of benefit/interest to you.
Normally i'd love to do it myself but my free time availability isn't
that great and my test bed consists of a lonely printer so it isn't much
to talk home about.

It ain't simple since a lot of things changed from our current 1.3.x
branch to the latest 1.7.x, most notably it talks to usb printers via
libusb rather than the kernel and foomatic-filters is deprecated in
favour of cups-filter, among a bunch of new deps (packages) needed to
build it.
If you need to know what bugs afflict it just look at:
http://www.cvedetails.com/vulnerability-list/vendor_id-49/product_id-14145/Apple-Cups.html
Cups 1.3.11 was released on 2 july 2009, so at least any CVE-2010*+
probably(1) affects it, and some of the CVE-2009* entries too.

Any takers for this?
Regards.

Note 1: if it's new functionality from a newer branch it may not,
optionally part of bumping is looking at those details to quote them in
the commit log.

             reply	other threads:[~2014-05-23 14:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 14:04 Gustavo Zacarias [this message]
2014-05-23 14:09 ` [Buildroot] Call for volunteer(s): cups security bump Vicente Olivert Riera

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=537F5565.1010903@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.