From: Joseph Carter <knghtbrd@efn.org>
To: Karl Peters <karl.h.peters@gmx.net>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Does a automatic security package tool exists?
Date: Tue, 11 Mar 2003 10:47:55 -0800 [thread overview]
Message-ID: <20030311184755.GB14253@galen.bluecherry.net> (raw)
In-Reply-To: <200303111842.54584.karl.h.peters@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]
On Tue, Mar 11, 2003 at 06:42:54PM +0100, Karl Peters wrote:
> the GLSAs to the announce mailinglist are really ok, but if you have
> more gentoo systems, manually updating security related packages is not
> so much fun, and quickly you may forget something.
>
> I imagine a GLSA database like the package.mask file, where information
> about package versions is kept, which packages are insecure and prehaps
> which version are suggested for updating.
I support making the information available other methods, but I absolutely
do not want GLSAs to stop being posted to -announce. It's a good list to
post them to and I recommend any Gentoo user be subscribed to it. Its
only traffic is the occasional announcement and of course the GLSAs. Who
can complain about that?
--
Joseph Carter <knghtbrd@efn.org> SCO must cease to exist!
<netgod> heh thats a lost cause, like the correct pronounciation of
"jewelry"
<netgod> give it up :-)
<sage> and the correct spelling of "colour" :)
<BenC> heh
<sage> and aluminium
<BenC> or nuclear weapons
<sage> are you threating me yankee ?
<sage> just cause we don't have the bomb...
<BenC> back off ya yellow belly
[-- Attachment #2: Type: application/pgp-signature, Size: 253 bytes --]
next prev parent reply other threads:[~2003-03-11 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 17:42 [gentoo-dev] Does a automatic security package tool exists? Karl Peters
2003-03-11 18:47 ` Joseph Carter [this message]
2003-03-11 19:32 ` Karl Peters
2003-03-12 15:34 ` Jan Winhuysen
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=20030311184755.GB14253@galen.bluecherry.net \
--to=knghtbrd@efn.org \
--cc=gentoo-dev@gentoo.org \
--cc=karl.h.peters@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox