Hi,
On Tue, Jun 28, 2011 at 15:34, Samuel Verschelde sto...@laposte.net wrote:
Le mardi 28 juin 2011 15:20:33, nicolas vigier a écrit :
In order to send updates advisories, and have a web page listing all
previous advisories, we need to create a database to store them.
So I think it should
On 06/28/2011 09:50 AM, Romain d'Alverny wrote:
If using SQL, make sure to normalize the db schema a bit (that is, for
- are there several CVE numbers for a single advisory?
Yes, there could be
--
Stew Benedict
On Tue, 28 Jun 2011, nicolas vigier wrote:
In order to send updates advisories, and have a web page listing all
previous advisories, we need to create a database to store them.
So I think it should have the following info for each advisory :
- advisory ID: something like MGA-[NUMBER] ?
-
On Tue, 28 Jun 2011, Romain d'Alverny wrote:
Hi,
On Tue, Jun 28, 2011 at 15:34, Samuel Verschelde sto...@laposte.net wrote:
Le mardi 28 juin 2011 15:20:33, nicolas vigier a écrit :
In order to send updates advisories, and have a web page listing all
previous advisories, we need to
On Tue, 28 Jun 2011, Christiaan Welvaart wrote:
On Tue, 28 Jun 2011, nicolas vigier wrote:
In order to send updates advisories, and have a web page listing all
previous advisories, we need to create a database to store them.
So I think it should have the following info for each advisory :
Le mardi 28 juin 2011 à 16:23 +0200, Christiaan Welvaart a écrit :
On Tue, 28 Jun 2011, nicolas vigier wrote:
In order to send updates advisories, and have a web page listing all
previous advisories, we need to create a database to store them.
So I think it should have the following
On Tue, 28 Jun 2011, Michael Scherer wrote:
Le mardi 28 juin 2011 à 16:23 +0200, Christiaan Welvaart a écrit :
On Tue, 28 Jun 2011, nicolas vigier wrote:
In order to send updates advisories, and have a web page listing all
previous advisories, we need to create a database to store
