Bug#738199: 738199

2015-09-29 Thread Luedtke, Nicholas S
Finally, got a chance to look at this and confirm what the others have been saying. The simplest way would be to add an affected version line to the DSA. But that may complicate other systems. That being said, I could just parse from the security tracker unless there is another list somewhere that

Bug#738199: 738199

2015-10-05 Thread Luedtke, Nicholas S
On Tue, 29 Sep 2015 23:20:54 +0200 =?utf-8?Q?S=C3=A9bastien?= Delafond wrote: > The URL is https://security-tracker.debian.org/tracker/data/json (listed > from https://security-tracker.debian.org/tracker), and using any script > language against this JSON data it's quite trivial to get the versio

Bug#738199: 738199 - Working Solution

2015-11-13 Thread Luedtke, Nicholas S
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Attached is a working solution to this bug. Right now parsing the JSON Security Tracker Information results in a one definition per CVE. I hope to reduce this to one definition per package. (Shouldn't be too much work) Also included in the tar is are m

Bug#738199: 738199

2015-11-06 Thread Luedtke, Nicholas S
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Looking at the JSON file we may just be able to get all the data from there and generate a set of definitions just based off the security tracker. Either way now that the split is over with I have some extra time to start working on this again. - --