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.</p>
-<p>After reading up on the issue, it became obvious that the first
+<p>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
<li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (5)</a></li>
+
</ul></li>
<li>2010
<li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (48)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (59)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (62)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (7)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (86)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (1)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (6)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (11)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (5)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (8)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (5)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (12)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (8)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (11)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (106)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (117)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (116)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (18)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (20)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (35)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (36)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (3)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (23)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (24)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (1)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (7)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (8)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (19)</a></li>