From: Petter Reinholdtsen Date: Fri, 28 Jan 2011 16:45:45 +0000 (+0000) Subject: Typos. X-Git-Url: https://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/035c56be8b394ccf0447a09d819603932817f265 Typos. --- diff --git a/blog/data/2011-01-28-cve-cpe.txt b/blog/data/2011-01-28-cve-cpe.txt index b8ffc37e1e..eefc618357 100644 --- a/blog/data/2011-01-28-cve-cpe.txt +++ b/blog/data/2011-01-28-cve-cpe.txt @@ -7,14 +7,14 @@ issues here at my work with the University of Oslo. My idea is that it should be possible to use the information about security issues available on the Internet, and check our locally maintained/distributed software against this information. It should -allow us to verify that no known security issue are forgotten. The +allow us to verify that no known security issues are forgotten. The CVE database listing vulnerabilities seem like a great central point, and by using the package lists from Debian mapped to CVEs provided by the testing security team, I believed it should be possible to figure out which security holes were present in our free software collection.

-

After reading up on the issue, it became obvious that the first +

After reading up on the topic, it became obvious that the first building block is to be able to name software packages in a unique and consistent way across data sources. I considered several ways to do this, for example coming up with my own naming scheme like using URLs