diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/006100.html')
-rw-r--r-- | zarb-ml/mageia-dev/2011-June/006100.html | 147 |
1 files changed, 147 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/006100.html b/zarb-ml/mageia-dev/2011-June/006100.html new file mode 100644 index 000000000..f41d8b1c8 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/006100.html @@ -0,0 +1,147 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Mageia Advisories Database + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mageia%20Advisories%20Database&In-Reply-To=%3C20110628144946.GR21938%40mars-attacks.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="006096.html"> + <LINK REL="Next" HREF="006095.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Mageia Advisories Database</H1> + <B>nicolas vigier</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mageia%20Advisories%20Database&In-Reply-To=%3C20110628144946.GR21938%40mars-attacks.org%3E" + TITLE="[Mageia-dev] Mageia Advisories Database">boklm at mars-attacks.org + </A><BR> + <I>Tue Jun 28 16:49:46 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="006096.html">[Mageia-dev] Mageia Advisories Database +</A></li> + <LI>Next message: <A HREF="006095.html">[Mageia-dev] Mageia Advisories Database +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6100">[ date ]</a> + <a href="thread.html#6100">[ thread ]</a> + <a href="subject.html#6100">[ subject ]</a> + <a href="author.html#6100">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Tue, 28 Jun 2011, Romain d'Alverny wrote: + +><i> Hi, +</I>><i> +</I>><i> On Tue, Jun 28, 2011 at 15:34, Samuel Verschelde <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">stormi at laposte.net</A>> wrote: +</I>><i> > Le mardi 28 juin 2011 15:20:33, nicolas vigier a écrit : +</I>><i> >> In order to send updates advisories, and have a web page listing all +</I>><i> >> previous advisories, we need to create a database to store them. +</I>><i> >> +</I>><i> >> So I think it should have the following info for each advisory : +</I>><i> >> +</I>><i> >>  - advisory ID: something like MGA-[NUMBER] ? +</I>><i> >>  - advisory date +</I>><i> >>  - affected source packages +</I>><i> >>  - affected distribution versions +</I>><i> >>  - CVE numbers +</I>><i> >>  - list of binary packages with sha1sum +</I>><i> >>  - Mageia Bug # +</I>><i> >>  - Reference URLs +</I>><i> >>  - advisory text +</I>><i> >> +</I>><i> >> Anything else ? +</I>><i> +</I>><i> If using SQL, make sure to normalize the db schema a bit (that is, for +</I>><i> instance, an advisory table, with a distributions table, and a +</I>><i> relationship). MDV security advisory web app had a single table, with +</I>><i> new columns added each time a new release was published and that was +</I>><i> really not good, neither safe to maintain. +</I>><i> +</I>><i> In this perspective, there could be the following tables: +</I>><i> - advisories (id, date, text, list of URLs, list of bug #) +</I>><i> - distributions (id, name) +</I>><i> - source packages (id, name, version) +</I>><i> - CVE numbers +</I> +I am thinking about the following tables : + + - advisories : id, published, publish-date, update-date, text, severity + - source-packages : packagename, filename, sha1, distribution, repository, version, advisory-id + - binary-packages : packagename, filename, sha1, source-package-id + - cve-numbers : cve-number, advisory-id + - bugzilla-numbers : bugzilla-number, advisory-id + - reference-urls : url, advisory-id + +><i> +</I>><i> Not sure about the rest; depends on the data details and what type of +</I>><i> queries would be expected: +</I>><i> - do we only query after the advisory id or do we plan to have stats +</I>><i> per distribution, source package? +</I> +We can query by advisory id, source package, cve number, bugzilla +number. And we can do stats. + +><i> - what screens do you expect? +</I>><i> - are there several CVE numbers for a single advisory? +</I> +Yes. We can have several CVE numbers, source packages, bugzilla numbers, +URLs, distributions, for one advisory. + +><i> - is there a link from source packages and binary packages? +</I> +Yes. + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="006096.html">[Mageia-dev] Mageia Advisories Database +</A></li> + <LI>Next message: <A HREF="006095.html">[Mageia-dev] Mageia Advisories Database +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6100">[ date ]</a> + <a href="thread.html#6100">[ thread ]</a> + <a href="subject.html#6100">[ subject ]</a> + <a href="author.html#6100">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |