</div>
<div class="padding"></div>
+<div class="entry">
+ <div class="title">
+ <a href="http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html">Which module is loaded for a given PCI and USB device?</a>
+ </div>
+ <div class="date">
+ 2011-01-23 00:20
+ </div>
+
+ <div class="body">
+
+<p>In the
+<a href="http://packages.qa.debian.org/discover-data">discover-data</a>
+package in Debian, there is a script to report useful information
+about the running hardware for use when people report missing
+information. One part of this script that I find very useful when
+debugging hardware problems, is the part mapping loaded kernel module
+to the PCI device it claims. It allow me to quickly see if the kernel
+module I expect is driving the hardware I am struggling with. To see
+the output, make sure discover-data is installed and run
+<tt>/usr/share/bug/discover-data 3>&1</tt>. The relevant output on
+one of my machines like this:</p>
+
+<pre>
+loaded modules:
+10de:03eb i2c_nforce2
+10de:03f1 ohci_hcd
+10de:03f2 ehci_hcd
+10de:03f0 snd_hda_intel
+10de:03ec pata_amd
+10de:03f6 sata_nv
+1022:1103 k8temp
+109e:036e bttv
+109e:0878 snd_bt87x
+11ab:4364 sky2
+</pre>
+
+<p>The code in question look like this, slightly modified for
+readability and to drop the output to file descriptor 3:</p>
+
+<pre>
+if [ -d /sys/bus/pci/devices/ ] ; then
+ echo loaded pci modules:
+ (
+ cd /sys/bus/pci/devices/
+ for address in * ; do
+ if [ -d "$address/driver/module" ] ; then
+ module=`cd $address/driver/module ; pwd -P | xargs basename`
+ if grep -q "^$module " /proc/modules ; then
+ address=$(echo $address |sed s/0000://)
+ id=`lspci -n -s $address | tail -n 1 | awk '{print $3}'`
+ echo "$id $module"
+ fi
+ fi
+ done
+ )
+ echo
+fi
+</pre>
+
+<p>Similar code could be used to extract USB device module
+mappings:</p>
+
+<pre>
+if [ -d /sys/bus/usb/devices/ ] ; then
+ echo loaded usb modules:
+ (
+ cd /sys/bus/usb/devices/
+ for address in * ; do
+ if [ -d "$address/driver/module" ] ; then
+ module=`cd $address/driver/module ; pwd -P | xargs basename`
+ if grep -q "^$module " /proc/modules ; then
+ address=$(echo $address |sed s/0000://)
+ id=$(lsusb -s $address | tail -n 1 | awk '{print $6}')
+ if [ "$id" ] ; then
+ echo "$id $module"
+ fi
+ fi
+ fi
+ done
+ )
+ echo
+fi
+</pre>
+
+<p>This might perhaps be something to include in other tools as
+well.</p>
+
+ </div>
+ <div class="tags">
+
+
+
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
+
+ </div>
+</div>
+ <div class="padding"></div>
+
+<div class="entry">
+ <div class="title">
+ <a href="http://people.skolelinux.org/pere/blog/Skolelinux_intervju__Morten_Amundsen.html">Skolelinux-intervju: Morten Amundsen</a>
+ </div>
+ <div class="date">
+ 2011-01-23 12:00
+ </div>
+
+ <div class="body">
+
+<p>Denne gangen er det Tromsøkontoret til Friprog-senteret, og nyvalgt
+styremedlem i <a href="http://www.friprogramvareiskolen.no/">foreningen
+FRISK</a> jeg har fått i tale i min intervjuserie med
+<a href="http://www.skolelinux.org/">Skolelinux</a>-folk.</p>
+
+<p><strong>Hvem er du, og hva driver du med til daglig?</strong></p>
+
+<p>Jeg heter Morten Amundsen og jobber i
+<a href="http://www.friprog.no/">Friprog.no</a>, men er for tiden leid
+ut til <a href="http://www.bredbandsfylket.no/">Bredbåndsfylket
+Troms</a> der jeg jobber med ett prosjekt som heter
+"<a href="http://www.bredbandsfylket.no/skolefjoela.157417.no.html">Skolefjøla</a>"
+Vi ser på en åpen løsning som integrerer eksisterende lukkete
+løsninger sammen med fri programvare. Målet er å gi elever og lærere
+en plattform som de kan tilpasse utfra behov.</p>
+
+<p><strong>Hvordan kom du i kontakt med Skolelinux-prosjektet?</strong></p>
+
+<p>Skolelinux har jeg møtt ved flere anledninger opp gjennom åra, både gjennom
+entusiastiske skolelinuxbrukere og skeptiske "forståsegpåere" :-)</p>
+
+<p>Jeg husker en leverandør av et stort OS for noen år siden mente at
+Skolelinux var kun for hackere og nerder og at ingen seriøse skoler
+kunne ta dette i bruk. Heldigvis er kunnskapen større nå og
+skikkelige "IT-folk" søker alltid å utvide sin kunnskap.
+
+<p><strong>Hva er fordelene med Skolelinux slik du ser det?</strong></p>
+
+<p>Ja det er mange fordeler. Uavhengighet, stabilitet, åpenhet, standarder
+osv. Tror det er viktig at man ikke begrenser mulighetene på den plattformen
+elevene skal jobbe.</p>
+
+<p><strong>Hva er ulempene med Skolelinux slik du ser det?</strong></p>
+
+<p>Det største hinderet er det vi opplever på andre områder rundt
+fri programvare, nemlig kunnskap. For mange er det trygt å velge det vi
+alltid har valgt. Fordi leverandørene rundt oss sitter på den kunnskapen og
+de vi støtter oss på har den samme. Hvis vi klarer å riste løs litt og
+glemme gamle kriger mellom operativsystemer og leverandører, men sette ned
+hva som er viktig og velge ut fra det, så hadde man kanskje kommet ut med
+litt andre resultat. Jeg tror IT-folk er konservative og velger tradisjonelt
+og det er synd.</p>
+
+<p><strong>Hvilken fri programvare bruker du til daglig?</strong></p>
+
+<p>Jeg bruker Ubuntu, Android, Jolicloud, Open Office, Zimbra, Picasa
+og Firefox samt en bråte med tjenester som er webbasert. Det eneste
+som er betalingslisens for er OSX. Ser at jeg jobber mer og mer i
+skyen og setter pris på alt jeg slipper egen klient til. Derfor er
+jeg veldig sjarmert av små kjappe operativsystemer som krever minimalt
+av maskinvaren.</p>
+
+<p><strong>Hvilken strategi tror du er den rette å bruke for å få
+skoler til å ta i bruk fri programvare?</strong></p>
+
+<p>Tror en blanding av krav og informasjon er veien å gå. Krav om
+sikkerhet, oppetid og åpne standarder. Informasjon om muligheter og
+alternativer. Her har leverandører, IT-avdelinger og pedagoger en vei
+å gå sammen. Det er til slutt LÆRING det dreier seg om, og da må man
+få mest mulig læring for pengene man har.</p>
+
+ </div>
+ <div class="tags">
+
+
+
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>.
+
+ </div>
+</div>
+ <div class="padding"></div>
+
+<div class="entry">
+ <div class="title">
+ <a href="http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html">Using NVD and CPE to track CVEs in locally maintained software</a>
+ </div>
+ <div class="date">
+ 2011-01-28 15:40
+ </div>
+
+ <div class="body">
+
+<p>The last few days I have looked at ways to track open security
+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 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 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
+to project home pages or URLs to the Freshmeat entries, or using some
+existing naming scheme. And it seem like I am not the first one to
+come across this problem, as MITRE already proposed and implemented a
+solution. Enter the <a href="http://cpe.mitre.org/index.html">Common
+Platform Enumeration</a> dictionary, a vocabulary for referring to
+software, hardware and other platform components. The CPE ids are
+mapped to CVEs in the <a href="http://web.nvd.nist.gov/">National
+Vulnerability Database</a>, allowing me to look up know security
+issues for any CPE name. With this in place, all I need to do is to
+locate the CPE id for the software packages we use at the university.
+This is fairly trivial (I google for 'cve cpe $package' and check the
+NVD entry if a CVE for the package exist).</p>
+
+<p>To give you an example. The GNU gzip source package have the CPE
+name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
+check out, one could look up
+<a href="http://web.nvd.nist.gov/view/vuln/search?cpe=cpe%3A%2Fa%3Agnu%3Agzip:1.3.3">cpe:/a:gnu:gzip:1.3.3
+in NVD</a> and get a list of 6 security holes with public CVE entries.
+The most recent one is
+<a href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001">CVE-2010-0001</a>,
+and at the bottom of the NVD page for this vulnerability the complete
+list of affected versions is provided.</p>
+
+<p>The NVD database of CVEs is also available as a XML dump, allowing
+for offline processing of issues. Using this dump, I've written a
+small script taking a list of CPEs as input and list all CVEs
+affecting the packages represented by these CPEs. One give it CPEs
+with version numbers as specified above and get a list of open
+security issues out.</p>
+
+<p>Of course for this approach to be useful, the quality of the NVD
+information need to be high. For that to happen, I believe as many as
+possible need to use and contribute to the NVD database. I notice
+RHEL is providing
+<a href="https://www.redhat.com/security/data/metrics/rhsamapcpe.txt">a
+map from CVE to CPE</a>, indicating that they are using the CPE
+information. I'm not aware of Debian and Ubuntu doing the same.</p>
+
+<p>To get an idea about the quality for free software, I spent some
+time making it possible to compare the CVE database from Debian with
+the CVE database in NVD. The result look fairly good, but there are
+some inconsistencies in NVD (same software package having several
+CPEs), and some inaccuracies (NVD not mentioning buggy packages that
+Debian believe are affected by a CVE). Hope to find time to improve
+the quality of NVD, but that require being able to get in touch with
+someone maintaining it. So far my three emails with questions and
+corrections have not seen any reply, but I hope contact can be
+established soon.</p>
+
+<p>An interesting application for CPEs is cross platform package
+mapping. It would be useful to know which packages in for example
+RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
+this would be trivial if all linux distributions provided CPE entries
+for their packages.</p>
+
+ </div>
+ <div class="tags">
+
+
+
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>.
+
+ </div>
+</div>
+ <div class="padding"></div>
+
<p style="text-align: right;"><a href="01.rss"><img src="http://people.skolelinux.org/pere/blog/xml.gif" alt="RSS Feed" width="36" height="14"></a></p>
<li>2011
<ul>
-<li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (13)</a></li>
+<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><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (10)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (46)</a></li>
+ <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 (58)</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 (84)</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 (4)</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 (105)</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/rss">rss (1)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (22)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (23)</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>
projects / homepage.git / blobdiff