public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Urs Schutz <u.schutz@bluewin.ch>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] GLSA management
Date: Tue, 6 Mar 2012 20:13:39 -0300	[thread overview]
Message-ID: <20120306201339.3a0bf160@bluewin.ch> (raw)
In-Reply-To: <CAN0CFw1uKPHb0_BKzvncjozJcH_nRB7rNyXUCdTS3z-zhFKCSA@mail.gmail.com>

On Tue, 6 Mar 2012 10:32:35 -0800
Grant <emailgrant@gmail.com> wrote:

> I've been checking this daily for a while:
> 
> http://www.gentoo.org/security/en/glsa/index.xml
> 
> but every time there's a vulnerability in a package I
> know I have installed, my installed version is
> unaffected.  If I emerge world daily, do I need to check
> on GLSA's?
> 
> - Grant
> 

I run a cron job that does glsa-check -t all daily, and had
one glsa showing up lately (201201-09). This was an old
slot of media-libs/freetype, pulled in by emerge because of
obscure useflags in luatex. This was with stable packages.
Another one showed up because of app-text/acroread, and
was resolved by replacing acroread with evince.

So in my opinion it is necessary to run glsa-check
regularly to show the detected problems within the system.
Run as a cron job there is little work to do, checking the
mail takes less than 10 seconds.

And: A big thanks to the people who invest their time and
use their brains to write the Gentoo Linux Security Advices!

Urs



      parent reply	other threads:[~2012-03-06 23:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06 18:32 [gentoo-user] GLSA management Grant
2012-03-06 18:57 ` Michael Orlitzky
2012-03-06 19:06 ` Neil Bothwick
2012-03-06 19:22   ` Grant
2012-03-07  1:48   ` [gentoo-user] " »Q«
2012-03-07  1:58     ` »Q«
2012-03-06 19:07 ` [gentoo-user] " Florian Philipp
2012-03-06 19:22   ` Grant
2012-03-06 23:13 ` Urs Schutz [this message]

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=20120306201339.3a0bf160@bluewin.ch \
    --to=u.schutz@bluewin.ch \
    --cc=gentoo-user@lists.gentoo.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox