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