blog/archive/2017/01/index.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2           "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr">
   4   <head>
   5     <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
   6     <title>Petter Reinholdtsen: entries from January 2017</title>
   7     <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/style.css" />
   8     <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/vim.css" />
   9     <link rel="alternate" title="RSS Feed" href="01.rss" type="application/rss+xml" />
  10   </head>
  11   <body>
  12     <!-- XML FEED -->
  13     <div class="title">
  14  <h1>
  15      <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
  16
  17  </h1>
  18
  19 </div>
  20
  21
  22     <h3>Entries from January 2017.</h3>
  23
  24     <div class="entry">
  25       <div class="title">
  26         <a href="http://people.skolelinux.org/pere/blog/Nasjonalbiblioteket_avslutter_sin_ulovlige_bruk_av_Google_Skjemaer.html">Nasjonalbiblioteket avslutter sin ulovlige bruk av Google Skjemaer</a>
  27       </div>
  28       <div class="date">
  29         12th January 2017
  30       </div>
  31       <div class="body">
  32         <p>I dag fikk jeg en skikkelig gladmelding.  Bakgrunnen er at før jul
  33 arrangerte Nasjonalbiblioteket
  34 <a href="http://www.nb.no/Bibliotekutvikling/Kunnskapsorganisering/Nasjonalt-verksregister/Seminar-om-verksregister">et
  35 seminar om sitt knakende gode tiltak «verksregister»</a>.  Eneste
  36 måten å melde seg på dette seminaret var å sende personopplysninger
  37 til Google via Google Skjemaer.  Dette syntes jeg var tvilsom praksis,
  38 da det bør være mulig å delta på seminarer arrangert av det offentlige
  39 uten å måtte dele sine interesser, posisjon og andre
  40 personopplysninger med Google.  Jeg ba derfor om innsyn via
  41 <a href="https://www.mimesbronn.no/">Mimes brønn</a> i
  42 <a href="https://www.mimesbronn.no/request/personopplysninger_til_google_sk">avtaler
  43 og vurderinger Nasjonalbiblioteket hadde rundt dette</a>.
  44 Personopplysningsloven legger klare rammer for hva som må være på
  45 plass før en kan be tredjeparter, spesielt i utlandet, behandle
  46 personopplysninger på sine vegne, så det burde eksistere grundig
  47 dokumentasjon før noe slikt kan bli lovlig.  To jurister hos
  48 Nasjonalbiblioteket mente først dette var helt i orden, og at Googles
  49 standardavtale kunne brukes som databehandlingsavtale.  Det syntes jeg
  50 var merkelig, men har ikke hatt kapasitet til å følge opp saken før
  51 for to dager siden.</p>
  52
  53 <p>Gladnyheten i dag, som kom etter at jeg tipset Nasjonalbiblioteket
  54 om at Datatilsynet underkjente Googles standardavtaler som
  55 databehandleravtaler i 2011, er at Nasjonalbiblioteket har bestemt seg
  56 for å avslutte bruken av Googles Skjemaer/Apps og gå i dialog med DIFI
  57 for å finne bedre måter å håndtere påmeldinger i tråd med
  58 personopplysningsloven.  Det er fantastisk å se at av og til hjelper
  59 det å spørre hva i alle dager det offentlige holder på med.</p>
  60
  61       </div>
  62       <div class="tags">
  63
  64
  65         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
  66
  67
  68       </div>
  69     </div>
  70     <div class="padding"></div>
  71
  72     <div class="entry">
  73       <div class="title">
  74         <a href="http://people.skolelinux.org/pere/blog/Bryter_NAV_sin_egen_personvernerkl_ring_.html">Bryter NAV sin egen personvernerklæring?</a>
  75       </div>
  76       <div class="date">
  77         11th January 2017
  78       </div>
  79       <div class="body">
  80         <p>Jeg leste med interesse en nyhetssak hos
  81 <a href="http://www.digi.no/artikler/nav-avslorer-trygdemisbruk-ved-a-spore-ip-adresser/367394">digi.no</a>
  82 og
  83 <a href="https://www.nrk.no/buskerud/trygdesvindlere-avslores-av-utenlandske-ip-adresser-1.13313461">NRK</a>
  84 om at det ikke bare er meg, men at også NAV bedriver geolokalisering
  85 av IP-adresser, og at det gjøres analyse av IP-adressene til de som
  86 sendes inn meldekort for å se om meldekortet sendes inn fra
  87 utenlandske IP-adresser.  Politiadvokat i Drammen, Hans Lyder Haare,
  88 er sitert i NRK på at «De to er jo blant annet avslørt av
  89 IP-adresser. At man ser at meldekortet kommer fra utlandet.»</p>
  90
  91 <p>Jeg synes det er fint at det blir bedre kjent at IP-adresser
  92 knyttes til enkeltpersoner og at innsamlet informasjon brukes til å
  93 stedsbestemme personer også av aktører her i Norge.  Jeg ser det som
  94 nok et argument for å bruke
  95 <a href="https://www.torproject.org/">Tor</a> så mye som mulig for å
  96 gjøre gjøre IP-lokalisering vanskeligere, slik at en kan beskytte sin
  97 privatsfære og unngå å dele sin fysiske plassering med
  98 uvedkommede.</p>
  99
 100 <P>Men det er en ting som bekymrer meg rundt denne nyheten.  Jeg ble
 101 tipset (takk #nuug) om
 102 <a href="https://www.nav.no/no/NAV+og+samfunn/Kontakt+NAV/Teknisk+brukerstotte/Snarveier/personvernerkl%C3%A6ring-for-arbeids-og-velferdsetaten">NAVs
 103 personvernerklæring</a>, som under punktet «Personvern og statistikk»
 104 lyder:</p>
 105
 106 <p><blockquote>
 107
 108 <p>«Når du besøker nav.no, etterlater du deg elektroniske spor. Sporene
 109 dannes fordi din nettleser automatisk sender en rekke opplysninger til
 110 NAVs tjener (server-maskin) hver gang du ber om å få vist en side. Det
 111 er eksempelvis opplysninger om hvilken nettleser og -versjon du
 112 bruker, og din internettadresse (ip-adresse). For hver side som vises,
 113 lagres følgende opplysninger:</p>
 114
 115 <ul>
 116 <li>hvilken side du ser på</li>
 117 <li>dato og tid</li>
 118 <li>hvilken nettleser du bruker</li>
 119 <li>din ip-adresse</li>
 120 </ul>
 121
 122 <p>Ingen av opplysningene vil bli brukt til å identifisere
 123 enkeltpersoner. NAV bruker disse opplysningene til å generere en
 124 samlet statistikk som blant annet viser hvilke sider som er mest
 125 populære. Statistikken er et redskap til å forbedre våre
 126 tjenester.»</p>
 127
 128 </blockquote></p>
 129
 130 <p>Jeg klarer ikke helt å se hvordan analyse av de besøkendes
 131 IP-adresser for å se hvem som sender inn meldekort via web fra en
 132 IP-adresse i utlandet kan gjøres uten å komme i strid med påstanden om
 133 at «ingen av opplysningene vil bli brukt til å identifisere
 134 enkeltpersoner».  Det virker dermed for meg som at NAV bryter sine
 135 egen personvernerklæring, hvilket
 136 <a href="http://people.skolelinux.org/pere/blog/Er_lover_brutt_n_r_personvernpolicy_ikke_stemmer_med_praksis_.html">Datatilsynet
 137 fortalte meg i starten av desember antagelig er brudd på
 138 personopplysningsloven</a>.
 139
 140 <p>I tillegg er personvernerklæringen ganske misvisende i og med at
 141 NAVs nettsider ikke bare forsyner NAV med personopplysninger, men i
 142 tillegg ber brukernes nettleser kontakte fem andre nettjenere
 143 (script.hotjar.com, static.hotjar.com, vars.hotjar.com,
 144 www.google-analytics.com og www.googletagmanager.com), slik at
 145 personopplysninger blir gjort tilgjengelig for selskapene Hotjar og
 146 Google , og alle som kan lytte på trafikken på veien (som FRA, GCHQ og
 147 NSA).  Jeg klarer heller ikke se hvordan slikt spredning av
 148 personopplysninger kan være i tråd med kravene i
 149 personopplysningloven, eller i tråd med NAVs personvernerklæring.</p>
 150
 151 <p>Kanskje NAV bør ta en nøye titt på sin personvernerklæring?  Eller
 152 kanskje Datatilsynet bør gjøre det?</p>
 153
 154       </div>
 155       <div class="tags">
 156
 157
 158         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
 159
 160
 161       </div>
 162     </div>
 163     <div class="padding"></div>
 164
 165     <div class="entry">
 166       <div class="title">
 167         <a href="http://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html">Where did that package go? &mdash; geolocated IP traceroute</a>
 168       </div>
 169       <div class="date">
 170          9th January 2017
 171       </div>
 172       <div class="body">
 173         <p>Did you ever wonder where the web trafic really flow to reach the
 174 web servers, and who own the network equipment it is flowing through?
 175 It is possible to get a glimpse of this from using traceroute, but it
 176 is hard to find all the details.  Many years ago, I wrote a system to
 177 map the Norwegian Internet (trying to figure out if our plans for a
 178 network game service would get low enough latency, and who we needed
 179 to talk to about setting up game servers close to the users.  Back
 180 then I used traceroute output from many locations (I asked my friends
 181 to run a script and send me their traceroute output) to create the
 182 graph and the map.  The output from traceroute typically look like
 183 this:
 184
 185 <p><pre>
 186 traceroute to www.stortinget.no (85.88.67.10), 30 hops max, 60 byte packets
 187  1  uio-gw10.uio.no (129.240.202.1)  0.447 ms  0.486 ms  0.621 ms
 188  2  uio-gw8.uio.no (129.240.24.229)  0.467 ms  0.578 ms  0.675 ms
 189  3  oslo-gw1.uninett.no (128.39.65.17)  0.385 ms  0.373 ms  0.358 ms
 190  4  te3-1-2.br1.fn3.as2116.net (193.156.90.3)  1.174 ms  1.172 ms  1.153 ms
 191  5  he16-1-1.cr1.san110.as2116.net (195.0.244.234)  2.627 ms he16-1-1.cr2.oslosda310.as2116.net (195.0.244.48)  3.172 ms he16-1-1.cr1.san110.as2116.net (195.0.244.234)  2.857 ms
 192  6  ae1.ar8.oslosda310.as2116.net (195.0.242.39)  0.662 ms  0.637 ms ae0.ar8.oslosda310.as2116.net (195.0.242.23)  0.622 ms
 193  7  89.191.10.146 (89.191.10.146)  0.931 ms  0.917 ms  0.955 ms
 194  8  * * *
 195  9  * * *
 196 [...]
 197 </pre></p>
 198
 199 <p>This show the DNS names and IP addresses of (at least some of the)
 200 network equipment involved in getting the data traffic from me to the
 201 www.stortinget.no server, and how long it took in milliseconds for a
 202 package to reach the equipment and return to me.  Three packages are
 203 sent, and some times the packages do not follow the same path.  This
 204 is shown for hop 5, where three different IP addresses replied to the
 205 traceroute request.</p>
 206
 207 <p>There are many ways to measure trace routes.  Other good traceroute
 208 implementations I use are traceroute (using ICMP packages) mtr (can do
 209 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
 210 traceroute and a lot of other capabilities).  All of them are easily
 211 available in <a href="https://www.debian.org/">Debian</a>.</p>
 212
 213 <p>This time around, I wanted to know the geographic location of
 214 different route points, to visualize how visiting a web page spread
 215 information about the visit to a lot of servers around the globe.  The
 216 background is that a web site today often will ask the browser to get
 217 from many servers the parts (for example HTML, JSON, fonts,
 218 JavaScript, CSS, video) required to display the content.  This will
 219 leak information about the visit to those controlling these servers
 220 and anyone able to peek at the data traffic passing by (like your ISP,
 221 the ISPs backbone provider, FRA, GCHQ, NSA and others).</p>
 222
 223 <p>Lets pick an example, the Norwegian parliament web site
 224 www.stortinget.no.  It is read daily by all members of parliament and
 225 their staff, as well as political journalists, activits and many other
 226 citizens of Norway.  A visit to the www.stortinget.no web site will
 227 ask your browser to contact 8 other servers: ajax.googleapis.com,
 228 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
 229 stats.g.doubleclick.net, www.google-analytics.com,
 230 www.googletagmanager.com and www.netigate.se.  I extracted this by
 231 asking <a href="http://phantomjs.org/">PhantomJS</a> to visit the
 232 Stortinget web page and tell me all the URLs PhantomJS downloaded to
 233 render the page (in HAR format using
 234 <a href="https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js">their
 235 netsniff example</a>.  I am very grateful to Gorm for showing me how
 236 to do this).  My goal is to visualize network traces to all IP
 237 addresses behind these DNS names, do show where visitors personal
 238 information is spread when visiting the page.</p>
 239
 240 <p align="center"><a href="www.stortinget.no-geoip.kml"><img
 241 src="http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-geoip-small.png" alt="map of combined traces for URLs used by www.stortinget.no using GeoIP"/></a></p>
 242
 243 <p>When I had a look around for options, I could not find any good
 244 free software tools to do this, and decided I needed my own traceroute
 245 wrapper outputting KML based on locations looked up using GeoIP.  KML
 246 is easy to work with and easy to generate, and understood by several
 247 of the GIS tools I have available.  I got good help from by NUUG
 248 colleague Anders Einar with this, and the result can be seen in
 249 <a href="https://github.com/petterreinholdtsen/kmltraceroute">my
 250 kmltraceroute git repository</a>.  Unfortunately, the quality of the
 251 free GeoIP databases I could find (and the for-pay databases my
 252 friends had access to) is not up to the task.  The IP addresses of
 253 central Internet infrastructure would typically be placed near the
 254 controlling companies main office, and not where the router is really
 255 located, as you can see from <a href="www.stortinget.no-geoip.kml">the
 256 KML file I created</a> using the GeoLite City dataset from MaxMind.
 257
 258 <p align="center"><a href="http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy.svg"><img
 259 src="http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy-small.png" alt="scapy traceroute graph for URLs used by www.stortinget.no"/></a></p>
 260
 261 <p>I also had a look at the visual traceroute graph created by
 262 <a href="http://www.secdev.org/projects/scapy/">the scrapy project</a>,
 263 showing IP network ownership (aka AS owner) for the IP address in
 264 question.
 265 <a href="http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy.svg">The
 266 graph display a lot of useful information about the traceroute in SVG
 267 format</a>, and give a good indication on who control the network
 268 equipment involved, but it do not include geolocation.  This graph
 269 make it possible to see the information is made available at least for
 270 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
 271 3 Communications and NetDNA.</p>
 272
 273 <p align="center"><a href="https://geotraceroute.com/index.php?node=4&host=www.stortinget.no"><img
 274 src="http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-geotraceroute-small.png" alt="example geotraceroute view for www.stortinget.no"/></a></p>
 275
 276 <p>In the process, I came across the
 277 <a href="https://geotraceroute.com/">web service GeoTraceroute</a> by
 278 Salim Gasmi.  Its methology of combining guesses based on DNS names,
 279 various location databases and finally use latecy times to rule out
 280 candidate locations seemed to do a very good job of guessing correct
 281 geolocation.  But it could only do one trace at the time, did not have
 282 a sensor in Norway and did not make the geolocations easily available
 283 for postprocessing.  So I contacted the developer and asked if he
 284 would be willing to share the code (he refused until he had time to
 285 clean it up), but he was interested in providing the geolocations in a
 286 machine readable format, and willing to set up a sensor in Norway.  So
 287 since yesterday, it is possible to run traces from Norway in this
 288 service thanks to a sensor node set up by
 289 <a href="https://www.nuug.no/">the NUUG assosiation</a>, and get the
 290 trace in KML format for further processing.</p>
 291
 292 <p align="center"><a href="http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-geotraceroute-kml-join.kml"><img
 293 src="http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-geotraceroute-kml-join.png" alt="map of combined traces for URLs used by www.stortinget.no using geotraceroute"/></a></p>
 294
 295 <p>Here we can see a lot of trafic passes Sweden on its way to
 296 Denmark, Germany, Holland and Ireland.  Plenty of places where the
 297 Snowden confirmations verified the traffic is read by various actors
 298 without your best interest as their top priority.</p>
 299
 300 <p>Combining KML files is trivial using a text editor, so I could loop
 301 over all the hosts behind the urls imported by www.stortinget.no and
 302 ask for the KML file from GeoTraceroute, and create a combined KML
 303 file with all the traces (unfortunately only one of the IP addresses
 304 behind the DNS name is traced this time.  To get them all, one would
 305 have to request traces using IP number instead of DNS names from
 306 GeoTraceroute).  That might be the next step in this project.</p>
 307
 308 <p>Armed with these tools, I find it a lot easier to figure out where
 309 the IP traffic moves and who control the boxes involved in moving it.
 310 And every time the link crosses for example the Swedish border, we can
 311 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
 312 Britain and NSA in USA and cables around the globe.  (Hm, what should
 313 we tell them? :) Keep that in mind if you ever send anything
 314 unencrypted over the Internet.</p>
 315
 316 <p>PS: KML files are drawn using
 317 <a href="http://ivanrublev.me/kml/">the KML viewer from Ivan
 318 Rublev<a/>, as it was less cluttered than the local Linux application
 319 Marble.  There are heaps of other options too.</p>
 320
 321 <p>As usual, if you use Bitcoin and want to show your support of my
 322 activities, please send Bitcoin donations to my address
 323 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 324
 325       </div>
 326       <div class="tags">
 327
 328
 329         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/kart">kart</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
 330
 331
 332       </div>
 333     </div>
 334     <div class="padding"></div>
 335
 336     <div class="entry">
 337       <div class="title">
 338         <a href="http://people.skolelinux.org/pere/blog/Introducing_ical_archiver_to_split_out_old_iCalendar_entries.html">Introducing ical-archiver to split out old iCalendar entries</a>
 339       </div>
 340       <div class="date">
 341          4th January 2017
 342       </div>
 343       <div class="body">
 344         <p>Do you have a large <a href="https://icalendar.org/">iCalendar</a>
 345 file with lots of old entries, and would like to archive them to save
 346 space and resources?  At least those of us using KOrganizer know that
 347 turning on and off an event set become slower and slower the more
 348 entries are in the set.  While working on migrating our calendars to a
 349 <a href="http://radicale.org/">Radicale CalDAV server</a> on our
 350 <a href="https://freedomboxfoundation.org/">Freedombox server</a/>, my
 351 loved one wondered if I could find a way to split up the calendar file
 352 she had in KOrganizer, and I set out to write a tool.  I spent a few
 353 days writing and polishing the system, and it is now ready for general
 354 consumption.  The
 355 <a href="https://github.com/petterreinholdtsen/ical-archiver">code for
 356 ical-archiver</a> is publicly available from a git repository on
 357 github.  The system is written in Python and depend on
 358 <a href="http://eventable.github.io/vobject/">the vobject Python
 359 module</a>.</p>
 360
 361 <p>To use it, locate the iCalendar file you want to operate on and
 362 give it as an argument to the ical-archiver script.  This will
 363 generate a set of new files, one file per component type per year for
 364 all components expiring more than two years in the past.  The vevent,
 365 vtodo and vjournal entries are handled by the script.  The remaining
 366 entries are stored in a 'remaining' file.</p>
 367
 368 <p>This is what a test run can look like:
 369
 370 <p><pre>
 371 % ical-archiver t/2004-2016.ics
 372 Found 3612 vevents
 373 Found 6 vtodos
 374 Found 2 vjournals
 375 Writing t/2004-2016.ics-subset-vevent-2004.ics
 376 Writing t/2004-2016.ics-subset-vevent-2005.ics
 377 Writing t/2004-2016.ics-subset-vevent-2006.ics
 378 Writing t/2004-2016.ics-subset-vevent-2007.ics
 379 Writing t/2004-2016.ics-subset-vevent-2008.ics
 380 Writing t/2004-2016.ics-subset-vevent-2009.ics
 381 Writing t/2004-2016.ics-subset-vevent-2010.ics
 382 Writing t/2004-2016.ics-subset-vevent-2011.ics
 383 Writing t/2004-2016.ics-subset-vevent-2012.ics
 384 Writing t/2004-2016.ics-subset-vevent-2013.ics
 385 Writing t/2004-2016.ics-subset-vevent-2014.ics
 386 Writing t/2004-2016.ics-subset-vjournal-2007.ics
 387 Writing t/2004-2016.ics-subset-vjournal-2011.ics
 388 Writing t/2004-2016.ics-subset-vtodo-2012.ics
 389 Writing t/2004-2016.ics-remaining.ics
 390 %
 391 </pre></p>
 392
 393 <p>As you can see, the original file is untouched and new files are
 394 written with names derived from the original file.  If you are happy
 395 with their content, the *-remaining.ics file can replace the original
 396 the the others can be archived or imported as historical calendar
 397 collections.</p>
 398
 399 <p>The script should probably be improved a bit.  The error handling
 400 when discovering broken entries is not good, and I am not sure yet if
 401 it make sense to split different entry types into separate files or
 402 not.  The program is thus likely to change.  If you find it
 403 interesting, please get in touch. :)</p>
 404
 405 <p>As usual, if you use Bitcoin and want to show your support of my
 406 activities, please send Bitcoin donations to my address
 407 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 408
 409       </div>
 410       <div class="tags">
 411
 412
 413         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 414
 415
 416       </div>
 417     </div>
 418     <div class="padding"></div>
 419
 420     <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>
 421     <div id="sidebar">
 422
 423
 424
 425 <h2>Archive</h2>
 426 <ul>
 427
 428 <li>2021
 429 <ul>
 430
 431 <li><a href="http://people.skolelinux.org/pere/blog/archive/2021/01/">January (2)</a></li>
 432
 433 <li><a href="http://people.skolelinux.org/pere/blog/archive/2021/02/">February (1)</a></li>
 434
 435 <li><a href="http://people.skolelinux.org/pere/blog/archive/2021/05/">May (1)</a></li>
 436
 437 <li><a href="http://people.skolelinux.org/pere/blog/archive/2021/06/">June (1)</a></li>
 438
 439 <li><a href="http://people.skolelinux.org/pere/blog/archive/2021/07/">July (3)</a></li>
 440
 441 <li><a href="http://people.skolelinux.org/pere/blog/archive/2021/08/">August (1)</a></li>
 442
 443 </ul></li>
 444
 445 <li>2020
 446 <ul>
 447
 448 <li><a href="http://people.skolelinux.org/pere/blog/archive/2020/02/">February (2)</a></li>
 449
 450 <li><a href="http://people.skolelinux.org/pere/blog/archive/2020/03/">March (2)</a></li>
 451
 452 <li><a href="http://people.skolelinux.org/pere/blog/archive/2020/04/">April (2)</a></li>
 453
 454 <li><a href="http://people.skolelinux.org/pere/blog/archive/2020/05/">May (3)</a></li>
 455
 456 <li><a href="http://people.skolelinux.org/pere/blog/archive/2020/06/">June (2)</a></li>
 457
 458 <li><a href="http://people.skolelinux.org/pere/blog/archive/2020/07/">July (1)</a></li>
 459
 460 <li><a href="http://people.skolelinux.org/pere/blog/archive/2020/09/">September (1)</a></li>
 461
 462 <li><a href="http://people.skolelinux.org/pere/blog/archive/2020/10/">October (1)</a></li>
 463
 464 <li><a href="http://people.skolelinux.org/pere/blog/archive/2020/11/">November (1)</a></li>
 465
 466 </ul></li>
 467
 468 <li>2019
 469 <ul>
 470
 471 <li><a href="http://people.skolelinux.org/pere/blog/archive/2019/01/">January (4)</a></li>
 472
 473 <li><a href="http://people.skolelinux.org/pere/blog/archive/2019/02/">February (3)</a></li>
 474
 475 <li><a href="http://people.skolelinux.org/pere/blog/archive/2019/03/">March (3)</a></li>
 476
 477 <li><a href="http://people.skolelinux.org/pere/blog/archive/2019/05/">May (2)</a></li>
 478
 479 <li><a href="http://people.skolelinux.org/pere/blog/archive/2019/06/">June (5)</a></li>
 480
 481 <li><a href="http://people.skolelinux.org/pere/blog/archive/2019/07/">July (2)</a></li>
 482
 483 <li><a href="http://people.skolelinux.org/pere/blog/archive/2019/08/">August (1)</a></li>
 484
 485 <li><a href="http://people.skolelinux.org/pere/blog/archive/2019/09/">September (1)</a></li>
 486
 487 <li><a href="http://people.skolelinux.org/pere/blog/archive/2019/11/">November (1)</a></li>
 488
 489 <li><a href="http://people.skolelinux.org/pere/blog/archive/2019/12/">December (4)</a></li>
 490
 491 </ul></li>
 492
 493 <li>2018
 494 <ul>
 495
 496 <li><a href="http://people.skolelinux.org/pere/blog/archive/2018/01/">January (1)</a></li>
 497
 498 <li><a href="http://people.skolelinux.org/pere/blog/archive/2018/02/">February (5)</a></li>
 499
 500 <li><a href="http://people.skolelinux.org/pere/blog/archive/2018/03/">March (5)</a></li>
 501
 502 <li><a href="http://people.skolelinux.org/pere/blog/archive/2018/04/">April (3)</a></li>
 503
 504 <li><a href="http://people.skolelinux.org/pere/blog/archive/2018/06/">June (2)</a></li>
 505
 506 <li><a href="http://people.skolelinux.org/pere/blog/archive/2018/07/">July (5)</a></li>
 507
 508 <li><a href="http://people.skolelinux.org/pere/blog/archive/2018/08/">August (3)</a></li>
 509
 510 <li><a href="http://people.skolelinux.org/pere/blog/archive/2018/09/">September (3)</a></li>
 511
 512 <li><a href="http://people.skolelinux.org/pere/blog/archive/2018/10/">October (5)</a></li>
 513
 514 <li><a href="http://people.skolelinux.org/pere/blog/archive/2018/11/">November (2)</a></li>
 515
 516 <li><a href="http://people.skolelinux.org/pere/blog/archive/2018/12/">December (4)</a></li>
 517
 518 </ul></li>
 519
 520 <li>2017
 521 <ul>
 522
 523 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/01/">January (4)</a></li>
 524
 525 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/02/">February (3)</a></li>
 526
 527 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/03/">March (5)</a></li>
 528
 529 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/04/">April (2)</a></li>
 530
 531 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/06/">June (5)</a></li>
 532
 533 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/07/">July (1)</a></li>
 534
 535 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/08/">August (1)</a></li>
 536
 537 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/09/">September (3)</a></li>
 538
 539 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/10/">October (5)</a></li>
 540
 541 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/11/">November (3)</a></li>
 542
 543 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/12/">December (4)</a></li>
 544
 545 </ul></li>
 546
 547 <li>2016
 548 <ul>
 549
 550 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/01/">January (3)</a></li>
 551
 552 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/02/">February (2)</a></li>
 553
 554 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/03/">March (3)</a></li>
 555
 556 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/04/">April (8)</a></li>
 557
 558 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/05/">May (8)</a></li>
 559
 560 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/06/">June (2)</a></li>
 561
 562 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/07/">July (2)</a></li>
 563
 564 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/08/">August (5)</a></li>
 565
 566 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/09/">September (2)</a></li>
 567
 568 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/10/">October (3)</a></li>
 569
 570 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/11/">November (8)</a></li>
 571
 572 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/12/">December (5)</a></li>
 573
 574 </ul></li>
 575
 576 <li>2015
 577 <ul>
 578
 579 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/01/">January (7)</a></li>
 580
 581 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/02/">February (6)</a></li>
 582
 583 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/03/">March (1)</a></li>
 584
 585 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/04/">April (4)</a></li>
 586
 587 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/05/">May (3)</a></li>
 588
 589 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/06/">June (4)</a></li>
 590
 591 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/07/">July (6)</a></li>
 592
 593 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/08/">August (2)</a></li>
 594
 595 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/09/">September (2)</a></li>
 596
 597 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/10/">October (9)</a></li>
 598
 599 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/11/">November (6)</a></li>
 600
 601 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/12/">December (3)</a></li>
 602
 603 </ul></li>
 604
 605 <li>2014
 606 <ul>
 607
 608 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
 609
 610 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
 611
 612 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
 613
 614 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/04/">April (7)</a></li>
 615
 616 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/05/">May (1)</a></li>
 617
 618 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/06/">June (2)</a></li>
 619
 620 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/07/">July (2)</a></li>
 621
 622 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/08/">August (2)</a></li>
 623
 624 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/09/">September (5)</a></li>
 625
 626 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/10/">October (6)</a></li>
 627
 628 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/11/">November (3)</a></li>
 629
 630 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/12/">December (5)</a></li>
 631
 632 </ul></li>
 633
 634 <li>2013
 635 <ul>
 636
 637 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
 638
 639 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
 640
 641 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
 642
 643 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
 644
 645 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
 646
 647 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
 648
 649 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
 650
 651 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
 652
 653 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
 654
 655 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
 656
 657 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
 658
 659 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
 660
 661 </ul></li>
 662
 663 <li>2012
 664 <ul>
 665
 666 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
 667
 668 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
 669
 670 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
 671
 672 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
 673
 674 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
 675
 676 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
 677
 678 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
 679
 680 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
 681
 682 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
 683
 684 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
 685
 686 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
 687
 688 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
 689
 690 </ul></li>
 691
 692 <li>2011
 693 <ul>
 694
 695 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
 696
 697 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
 698
 699 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
 700
 701 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
 702
 703 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
 704
 705 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
 706
 707 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
 708
 709 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
 710
 711 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
 712
 713 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
 714
 715 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
 716
 717 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
 718
 719 </ul></li>
 720
 721 <li>2010
 722 <ul>
 723
 724 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
 725
 726 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
 727
 728 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
 729
 730 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
 731
 732 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
 733
 734 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
 735
 736 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
 737
 738 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
 739
 740 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
 741
 742 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
 743
 744 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
 745
 746 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
 747
 748 </ul></li>
 749
 750 <li>2009
 751 <ul>
 752
 753 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
 754
 755 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
 756
 757 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
 758
 759 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
 760
 761 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
 762
 763 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
 764
 765 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
 766
 767 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
 768
 769 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
 770
 771 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
 772
 773 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
 774
 775 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
 776
 777 </ul></li>
 778
 779 <li>2008
 780 <ul>
 781
 782 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
 783
 784 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
 785
 786 </ul></li>
 787
 788 </ul>
 789
 790
 791
 792 <h2>Tags</h2>
 793 <ul>
 794
 795  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (16)</a></li>
 796
 797  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
 798
 799  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
 800
 801  <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
 802
 803  <li><a href="http://people.skolelinux.org/pere/blog/tags/betalkontant">betalkontant (9)</a></li>
 804
 805  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (12)</a></li>
 806
 807  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (17)</a></li>
 808
 809  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
 810
 811  <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
 812
 813  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (176)</a></li>
 814
 815  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (159)</a></li>
 816
 817  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian-handbook">debian-handbook (8)</a></li>
 818
 819  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (11)</a></li>
 820
 821  <li><a href="http://people.skolelinux.org/pere/blog/tags/dld">dld (17)</a></li>
 822
 823  <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (29)</a></li>
 824
 825  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
 826
 827  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (427)</a></li>
 828
 829  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
 830
 831  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (14)</a></li>
 832
 833  <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (34)</a></li>
 834
 835  <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
 836
 837  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (20)</a></li>
 838
 839  <li><a href="http://people.skolelinux.org/pere/blog/tags/h264">h264 (20)</a></li>
 840
 841  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (43)</a></li>
 842
 843  <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (16)</a></li>
 844
 845  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (23)</a></li>
 846
 847  <li><a href="http://people.skolelinux.org/pere/blog/tags/kodi">kodi (4)</a></li>
 848
 849  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
 850
 851  <li><a href="http://people.skolelinux.org/pere/blog/tags/lego">lego (4)</a></li>
 852
 853  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (8)</a></li>
 854
 855  <li><a href="http://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd (2)</a></li>
 856
 857  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
 858
 859  <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
 860
 861  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (42)</a></li>
 862
 863  <li><a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (13)</a></li>
 864
 865  <li><a href="http://people.skolelinux.org/pere/blog/tags/noark5">noark5 (23)</a></li>
 866
 867  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (318)</a></li>
 868
 869  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (198)</a></li>
 870
 871  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (40)</a></li>
 872
 873  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
 874
 875  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (75)</a></li>
 876
 877  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (112)</a></li>
 878
 879  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (2)</a></li>
 880
 881  <li><a href="http://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
 882
 883  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
 884
 885  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
 886
 887  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (12)</a></li>
 888
 889  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
 890
 891  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (7)</a></li>
 892
 893  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
 894
 895  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (59)</a></li>
 896
 897  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
 898
 899  <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (5)</a></li>
 900
 901  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (71)</a></li>
 902
 903  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (7)</a></li>
 904
 905  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (13)</a></li>
 906
 907  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (61)</a></li>
 908
 909  <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (5)</a></li>
 910
 911  <li><a href="http://people.skolelinux.org/pere/blog/tags/usenix">usenix (2)</a></li>
 912
 913  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (9)</a></li>
 914
 915  <li><a href="http://people.skolelinux.org/pere/blog/tags/verkidetfri">verkidetfri (19)</a></li>
 916
 917  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (75)</a></li>
 918
 919  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
 920
 921  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (42)</a></li>
 922
 923 </ul>
 924
 925
 926     </div>
 927     <p style="text-align: right">
 928  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
 929 </p>
 930
 931   </body>
 932 </html>