From: Marius Mauch <genone@genone.homeip.net>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] automatic security updates based on GLSA
Date: Mon, 28 Jul 2003 13:06:45 +0200 [thread overview]
Message-ID: <20030728130645.1afb58bb.genone@genone.homeip.net> (raw)
Hi,
I've started to work on a tool to apply security updates to a gentoo
system by checking the GLSA. It uses a XML format of the GLSA and
updates the affected packages to the fixed versions (well, not at the
moment as I've started this only yesterday). Currently the GLSA are only
sent to a mailinglist in plaintext AFAIK and posted on the forums/GWN.
I've put together a DTD for the XML format by looking through a few GLSA
and xml-fied the latest GLSA for nfs-utils. Both documents are available
at http://gentoo.devel-net.org/glsa/ . This is just a draft, any
suggestions for improvements are welcome as are all comments on this
mini-project.
I'll put some code on the site as soon as it is useful, the current
implemention is still in a very early development state and most work
has gone to the backend by now.
Marius
--
gentoo-dev@gentoo.org mailing list
reply other threads:[~2003-07-28 11:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030728130645.1afb58bb.genone@genone.homeip.net \
--to=genone@genone.homeip.net \
--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