From: Klavs Klavsen <kl@vsen.dk>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] RFC: security updates only? (security-1.0.ebuild)
Date: 16 Aug 2003 17:56:13 +0200 [thread overview]
Message-ID: <1061049373.3338.4.camel@amd.vsen.dk> (raw)
In-Reply-To: <200308161631.47162.pauldv@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
How about starting with putting the GLSA's in the tree?
That would be step 1.
Then an emerge sync would give you new security information too.
or perhaps an glsa-ebuild?
After this, I agree it would be best to add a --security option.
IMHO this should work, so emerge -u world --security (or -S - or is that
too close to -s?) would look at all the upgrades suggested by the world
- and then check against the glsa's and see if any of them have are
mentioned here. The glsa's should be named after the package version
that fixes this issue, that way it would be easy to check and upgrade if
the currently installed is older.
Better solutions are welcome - but are they as easy to implement as
this?
--
Regards,
Klavs Klavsen, GSEC - kl@vsen.dk - http://www.vsen.dk
PGP: 7E063C62/2873 188C 968E 600D D8F8 B8DA 3D3A 0B79 7E06 3C62
See my new CMS Hosting Service at http://www.VirkPaaNettet.dk
Working with Unix is like wrestling a worthy opponent.
Working with windows is like attacking a small whining child
who is carrying a .38.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-08-16 15:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-16 9:46 [gentoo-dev] RFC: security updates only? (security-1.0.ebuild) Karsten Schulz
2003-08-16 10:20 ` Paul de Vrieze
2003-08-16 11:03 ` Karsten Schulz
2003-08-16 11:19 ` Karsten Schulz
2003-08-16 14:31 ` Paul de Vrieze
2003-08-16 15:56 ` Klavs Klavsen [this message]
2003-08-16 16:18 ` Karsten Schulz
2003-08-16 15:59 ` Karsten Schulz
2003-08-16 17:11 ` Paul de Vrieze
2003-08-16 19:38 ` Marius Mauch
2003-08-18 10:29 ` Karsten Schulz
2003-08-18 19:17 ` Marius Mauch
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=1061049373.3338.4.camel@amd.vsen.dk \
--to=kl@vsen.dk \
--cc=gentoo-dev@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