blog/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</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="http://people.skolelinux.org/pere/blog/index.rss" type="application/rss+xml" />
  10   </head>
  11   <body>
  12     <div class="title">
  13  <h1>
  14      <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
  15
  16  </h1>
  17
  18 </div>
  19
  20
  21
  22     <div class="entry">
  23       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Offentlig_elektronisk_postjournal_blokkerer_tilgang_for_utvalgte_webklienter.html">Offentlig elektronisk postjournal blokkerer tilgang for utvalgte webklienter</a></div>
  24       <div class="date">20th April 2017</div>
  25       <div class="body"><p>Jeg oppdaget i dag at <a href="https://www.oep.no/">nettstedet som
  26 publiserer offentlige postjournaler fra statlige etater</a>, OEP, har
  27 begynt å blokkerer enkelte typer webklienter fra å få tilgang.  Vet
  28 ikke hvor mange det gjelder, men det gjelder i hvert fall libwww-perl
  29 og curl.  For å teste selv, kjør følgende:</p>
  30
  31 <blockquote><pre>
  32 % curl -v -s https://www.oep.no/pub/report.xhtml?reportId=3 2>&1 |grep '< HTTP'
  33 < HTTP/1.1 404 Not Found
  34 % curl -v -s --header 'User-Agent:Opera/12.0' https://www.oep.no/pub/report.xhtml?reportId=3 2>&1 |grep '< HTTP'
  35 < HTTP/1.1 200 OK
  36 %
  37 </pre></blockquote>
  38
  39 <p>Her kan en se at tjenesten gir «404 Not Found» for curl i
  40 standardoppsettet, mens den gir «200 OK» hvis curl hevder å være Opera
  41 versjon 12.0.  Offentlig elektronisk postjournal startet blokkeringen
  42 2017-03-02.</p>
  43
  44 <p>Blokkeringen vil gjøre det litt vanskeligere å maskinelt hente
  45 informasjon fra oep.no.  Kan blokkeringen være gjort for å hindre
  46 automatisert innsamling av informasjon fra OEP, slik Pressens
  47 Offentlighetsutvalg gjorde for å dokumentere hvordan departementene
  48 hindrer innsyn i
  49 <a href="http://presse.no/dette-mener-np/undergraver-offentlighetsloven/">rapporten
  50 «Slik hindrer departementer innsyn» som ble publiserte i januar
  51 2017</a>.  Det virker usannsynlig, da det jo er trivielt å bytte
  52 User-Agent til noe nytt.</p>
  53
  54 <p>Finnes det juridisk grunnlag for det offentlige å diskriminere
  55 webklienter slik det gjøres her?  Der tilgang gis eller ikke alt etter
  56 hva klienten sier at den heter?  Da OEP eies av DIFI og driftes av
  57 Basefarm, finnes det kanskje noen dokumenter sendt mellom disse to
  58 aktørene man kan be om innsyn i for å forstå hva som har skjedd.  Men
  59 <a href="https://www.oep.no/search/result.html?period=dateRange&fromDate=01.01.2016&toDate=01.04.2017&dateType=documentDate&caseDescription=&descType=both&caseNumber=&documentNumber=&sender=basefarm&senderType=both&documentType=all&legalAuthority=&archiveCode=&list2=196&searchType=advanced&Search=Search+in+records">postjournalen
  60 til DIFI viser kun to dokumenter</a> det siste året mellom DIFI og
  61 Basefarm.
  62 <a href="https://www.mimesbronn.no/request/blokkering_av_tilgang_til_oep_fo">Mimes brønn neste</a>,
  63 tenker jeg.</p>
  64 </div>
  65       <div class="tags">
  66
  67
  68         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>.
  69
  70
  71       </div>
  72     </div>
  73     <div class="padding"></div>
  74
  75     <div class="entry">
  76       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Free_software_archive_system_Nikita_now_able_to_store_documents.html">Free software archive system Nikita now able to store documents</a></div>
  77       <div class="date">19th March 2017</div>
  78       <div class="body"><p>The <a href="https://github.com/hiOA-ABI/nikita-noark5-core">Nikita
  79 Noark 5 core project</a> is implementing the Norwegian standard for
  80 keeping an electronic archive of government documents.
  81 <a href="http://www.arkivverket.no/arkivverket/Offentlig-forvaltning/Noark/Noark-5/English-version">The
  82 Noark 5 standard</a> document the requirement for data systems used by
  83 the archives in the Norwegian government, and the Noark 5 web interface
  84 specification document a REST web service for storing, searching and
  85 retrieving documents and metadata in such archive.  I've been involved
  86 in the project since a few weeks before Christmas, when the Norwegian
  87 Unix User Group
  88 <a href="https://www.nuug.no/news/NOARK5_kjerne_som_fri_programvare_f_r_epostliste_hos_NUUG.shtml">announced
  89 it supported the project</a>.  I believe this is an important project,
  90 and hope it can make it possible for the government archives in the
  91 future to use free software to keep the archives we citizens depend
  92 on.  But as I do not hold such archive myself, personally my first use
  93 case is to store and analyse public mail journal metadata published
  94 from the government.  I find it useful to have a clear use case in
  95 mind when developing, to make sure the system scratches one of my
  96 itches.</p>
  97
  98 <p>If you would like to help make sure there is a free software
  99 alternatives for the archives, please join our IRC channel
 100 (<a href="irc://irc.freenode.net/%23nikita"">#nikita on
 101 irc.freenode.net</a>) and
 102 <a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">the
 103 project mailing list</a>.</p>
 104
 105 <p>When I got involved, the web service could store metadata about
 106 documents.  But a few weeks ago, a new milestone was reached when it
 107 became possible to store full text documents too.  Yesterday, I
 108 completed an implementation of a command line tool
 109 <tt>archive-pdf</tt> to upload a PDF file to the archive using this
 110 API.  The tool is very simple at the moment, and find existing
 111 <a href="https://en.wikipedia.org/wiki/Fonds">fonds</a>, series and
 112 files while asking the user to select which one to use if more than
 113 one exist.  Once a file is identified, the PDF is associated with the
 114 file and uploaded, using the title extracted from the PDF itself.  The
 115 process is fairly similar to visiting the archive, opening a cabinet,
 116 locating a file and storing a piece of paper in the archive.  Here is
 117 a test run directly after populating the database with test data using
 118 our API tester:</p>
 119
 120 <p><blockquote><pre>
 121 ~/src//noark5-tester$ ./archive-pdf mangelmelding/mangler.pdf
 122 using arkiv: Title of the test fonds created 2017-03-18T23:49:32.103446
 123 using arkivdel: Title of the test series created 2017-03-18T23:49:32.103446
 124
 125  0 - Title of the test case file created 2017-03-18T23:49:32.103446
 126  1 - Title of the test file created 2017-03-18T23:49:32.103446
 127 Select which mappe you want (or search term): 0
 128 Uploading mangelmelding/mangler.pdf
 129   PDF title: Mangler i spesifikasjonsdokumentet for NOARK 5 Tjenestegrensesnitt
 130   File 2017/1: Title of the test case file created 2017-03-18T23:49:32.103446
 131 ~/src//noark5-tester$
 132 </pre></blockquote></p>
 133
 134 <p>You can see here how the fonds (arkiv) and serie (arkivdel) only had
 135 one option, while the user need to choose which file (mappe) to use
 136 among the two created by the API tester.  The <tt>archive-pdf</tt>
 137 tool can be found in the git repository for the API tester.</p>
 138
 139 <p>In the project, I have been mostly working on
 140 <a href="https://github.com/petterreinholdtsen/noark5-tester">the API
 141 tester</a> so far, while getting to know the code base.  The API
 142 tester currently use
 143 <a href="https://en.wikipedia.org/wiki/HATEOAS">the HATEOAS links</a>
 144 to traverse the entire exposed service API and verify that the exposed
 145 operations and objects match the specification, as well as trying to
 146 create objects holding metadata and uploading a simple XML file to
 147 store.  The tester has proved very useful for finding flaws in our
 148 implementation, as well as flaws in the reference site and the
 149 specification.</p>
 150
 151 <p>The test document I uploaded is a summary of all the specification
 152 defects we have collected so far while implementing the web service.
 153 There are several unclear and conflicting parts of the specification,
 154 and we have
 155 <a href="https://github.com/petterreinholdtsen/noark5-tester/tree/master/mangelmelding">started
 156 writing down</a> the questions we get from implementing it.  We use a
 157 format inspired by how <a href="http://www.opengroup.org/austin/">The
 158 Austin Group</a> collect defect reports for the POSIX standard with
 159 <a href="http://www.opengroup.org/austin/mantis.html">their
 160 instructions for the MANTIS defect tracker system</a>, in lack of an official way to structure defect reports for Noark 5 (our first submitted defect report was a <a href="https://github.com/petterreinholdtsen/noark5-tester/blob/master/mangelmelding/sendt/2017-03-15-mangel-prosess.md">request for a procedure for submitting defect reports</a> :).
 161
 162 <p>The Nikita project is implemented using Java and Spring, and is
 163 fairly easy to get up and running using Docker containers for those
 164 that want to test the current code base.  The API tester is
 165 implemented in Python.</p>
 166 </div>
 167       <div class="tags">
 168
 169
 170         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 171
 172
 173       </div>
 174     </div>
 175     <div class="padding"></div>
 176
 177     <div class="entry">
 178       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html">Detecting NFS hangs on Linux without hanging yourself...</a></div>
 179       <div class="date"> 9th March 2017</div>
 180       <div class="body"><p>Over the years, administrating thousand of NFS mounting linux
 181 computers at the time, I often needed a way to detect if the machine
 182 was experiencing NFS hang.  If you try to use <tt>df</tt> or look at a
 183 file or directory affected by the hang, the process (and possibly the
 184 shell) will hang too.  So you want to be able to detect this without
 185 risking the detection process getting stuck too.  It has not been
 186 obvious how to do this.  When the hang has lasted a while, it is
 187 possible to find messages like these in dmesg:</p>
 188
 189 <p><blockquote>
 190 nfs: server nfsserver not responding, still trying
 191 <br>nfs: server nfsserver OK
 192 </blockquote></p>
 193
 194 <p>It is hard to know if the hang is still going on, and it is hard to
 195 be sure looking in dmesg is going to work.  If there are lots of other
 196 messages in dmesg the lines might have rotated out of site before they
 197 are noticed.</p>
 198
 199 <p>While reading through the nfs client implementation in linux kernel
 200 code, I came across some statistics that seem to give a way to detect
 201 it.  The om_timeouts sunrpc value in the kernel will increase every
 202 time the above log entry is inserted into dmesg.  And after digging a
 203 bit further, I discovered that this value show up in
 204 /proc/self/mountstats on Linux.</p>
 205
 206 <p>The mountstats content seem to be shared between files using the
 207 same file system context, so it is enough to check one of the
 208 mountstats files to get the state of the mount point for the machine.
 209 I assume this will not show lazy umounted NFS points, nor NFS mount
 210 points in a different process context (ie with a different filesystem
 211 view), but that does not worry me.</p>
 212
 213 <p>The content for a NFS mount point look similar to this:</p>
 214
 215 <p><blockquote><pre>
 216 [...]
 217 device /dev/mapper/Debian-var mounted on /var with fstype ext3
 218 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
 219         opts:   rw,vers=3,rsize=65536,wsize=65536,namlen=255,acregmin=3,acregmax=60,acdirmin=30,acdirmax=60,soft,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=129.240.3.145,mountvers=3,mountport=4048,mountproto=udp,local_lock=all
 220         age:    7863311
 221         caps:   caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
 222         sec:    flavor=1,pseudoflavor=1
 223         events: 61063112 732346265 1028140 35486205 16220064 8162542 761447191 71714012 37189 3891185 45561809 110486139 4850138 420353 15449177 296502 52736725 13523379 0 52182 9016896 1231 0 0 0 0 0
 224         bytes:  166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
 225         RPC iostats version: 1.0  p/v: 100003/3 (nfs)
 226         xprt:   tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
 227         per-op statistics
 228                 NULL: 0 0 0 0 0 0 0 0
 229              GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
 230              SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
 231               LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
 232               ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
 233             READLINK: 125 125 0 20472 18620 0 1112 1118
 234                 READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
 235                WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
 236               CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
 237                MKDIR: 3680 3680 0 773980 993920 26 23990 24245
 238              SYMLINK: 903 903 0 233428 245488 6 5865 5917
 239                MKNOD: 80 80 0 20148 21760 0 299 304
 240               REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
 241                RMDIR: 3367 3367 0 645112 484848 22 5782 6002
 242               RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
 243                 LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
 244              READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
 245          READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
 246               FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
 247               FSINFO: 2 2 0 232 328 0 1 1
 248             PATHCONF: 1 1 0 116 140 0 0 0
 249               COMMIT: 0 0 0 0 0 0 0 0
 250
 251 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
 252 [...]
 253 </pre></blockquote></p>
 254
 255 <p>The key number to look at is the third number in the per-op list.
 256 It is the number of NFS timeouts experiences per file system
 257 operation.  Here 22 write timeouts and 5 access timeouts.  If these
 258 numbers are increasing, I believe the machine is experiencing NFS
 259 hang.  Unfortunately the timeout value do not start to increase right
 260 away.  The NFS operations need to time out first, and this can take a
 261 while.  The exact timeout value depend on the setup.  For example the
 262 defaults for TCP and UDP mount points are quite different, and the
 263 timeout value is affected by the soft, hard, timeo and retrans NFS
 264 mount options.</p>
 265
 266 <p>The only way I have been able to get working on Debian and RedHat
 267 Enterprise Linux for getting the timeout count is to peek in /proc/.
 268 But according to
 269 <ahref="http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html">Solaris
 270 10 System Administration Guide: Network Services</a>, the 'nfsstat -c'
 271 command can be used to get these timeout values.  But this do not work
 272 on Linux, as far as I can tell.  I
 273 <ahref="http://bugs.debian.org/857043">asked Debian about this</a>,
 274 but have not seen any replies yet.</p>
 275
 276 <p>Is there a better way to figure out if a Linux NFS client is
 277 experiencing NFS hangs?  Is there a way to detect which processes are
 278 affected?  Is there a way to get the NFS mount going quickly once the
 279 network problem causing the NFS hang has been cleared?  I would very
 280 much welcome some clues, as we regularly run into NFS hangs.</p>
 281 </div>
 282       <div class="tags">
 283
 284
 285         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/sysadmin">sysadmin</a>.
 286
 287
 288       </div>
 289     </div>
 290     <div class="padding"></div>
 291
 292     <div class="entry">
 293       <div class="title"><a href="http://people.skolelinux.org/pere/blog/How_does_it_feel_to_be_wiretapped__when_you_should_be_doing_the_wiretapping___.html">How does it feel to be wiretapped, when you should be doing the wiretapping...</a></div>
 294       <div class="date"> 8th March 2017</div>
 295       <div class="body"><p>So the new president in the United States of America claim to be
 296 surprised to discover that he was wiretapped during the election
 297 before he was elected president.  He even claim this must be illegal.
 298 Well, doh, if it is one thing the confirmations from Snowden
 299 documented, it is that the entire population in USA is wiretapped, one
 300 way or another.  Of course the president candidates were wiretapped,
 301 alongside the senators, judges and the rest of the people in USA.</p>
 302
 303 <p>Next, the Federal Bureau of Investigation ask the Department of
 304 Justice to go public rejecting the claims that Donald Trump was
 305 wiretapped illegally.  I fail to see the relevance, given that I am
 306 sure the surveillance industry in USA believe they have all the legal
 307 backing they need to conduct mass surveillance on the entire
 308 world.</p>
 309
 310 <p>There is even the director of the FBI stating that he never saw an
 311 order requesting wiretapping of Donald Trump.  That is not very
 312 surprising, given how the FISA court work, with all its activity being
 313 secret.  Perhaps he only heard about it?</p>
 314
 315 <p>What I find most sad in this story is how Norwegian journalists
 316 present it.  In a news reports the other day in the radio from the
 317 Norwegian National broadcasting Company (NRK), I heard the journalist
 318 claim that 'the FBI denies any wiretapping', while the reality is that
 319 'the FBI denies any illegal wiretapping'.  There is a fundamental and
 320 important difference, and it make me sad that the journalists are
 321 unable to grasp it.</p>
 322
 323 <p><strong>Update 2017-03-13:</strong> Look like
 324 <a href="https://theintercept.com/2017/03/13/rand-paul-is-right-nsa-routinely-monitors-americans-communications-without-warrants/">The
 325 Intercept report that US Senator Rand Paul confirm what I state above</a>.</p>
 326 </div>
 327       <div class="tags">
 328
 329
 330         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
 331
 332
 333       </div>
 334     </div>
 335     <div class="padding"></div>
 336
 337     <div class="entry">
 338       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html">Norwegian Bokmål translation of The Debian Administrator's Handbook complete, proofreading in progress</a></div>
 339       <div class="date"> 3rd March 2017</div>
 340       <div class="body"><p>For almost a year now, we have been working on making a Norwegian
 341 Bokmål edition of <a href="https://debian-handbook.info/">The Debian
 342 Administrator's Handbook</a>.  Now, thanks to the tireless effort of
 343 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
 344 we are working on the proof reading to ensure consistent language and
 345 use of correct computer science terms.  The plan is to make the book
 346 available on paper, as well as in electronic form.  For that to
 347 happen, the proof reading must be completed and all the figures need
 348 to be translated.  If you want to help out, get in touch.</p>
 349
 350 <p><a href="http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf">A
 351
 352 fresh PDF edition</a> in A4 format (the final book will have smaller
 353 pages) of the book created every morning is available for
 354 proofreading.  If you find any errors, please
 355 <a href="https://hosted.weblate.org/projects/debian-handbook/">visit
 356 Weblate and correct the error</a>.  The
 357 <a href="http://l.github.io/debian-handbook/stat/nb-NO/index.html">state
 358 of the translation including figures</a> is a useful source for those
 359 provide Norwegian bokmål screen shots and figures.</p>
 360 </div>
 361       <div class="tags">
 362
 363
 364         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian-handbook">debian-handbook</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
 365
 366
 367       </div>
 368     </div>
 369     <div class="padding"></div>
 370
 371     <div class="entry">
 372       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html">Unlimited randomness with the ChaosKey?</a></div>
 373       <div class="date"> 1st March 2017</div>
 374       <div class="body"><p>A few days ago I ordered a small batch of
 375 <a href="http://altusmetrum.org/ChaosKey/">the ChaosKey</a>, a small
 376 USB dongle for generating entropy created by Bdale Garbee and Keith
 377 Packard.  Yesterday it arrived, and I am very happy to report that it
 378 work great!  According to its designers, to get it to work out of the
 379 box, you need the Linux kernel version 4.1 or later.  I tested on a
 380 Debian Stretch machine (kernel version 4.9), and there it worked just
 381 fine, increasing the available entropy very quickly.  I wrote a small
 382 test oneliner to test.  It first print the current entropy level,
 383 drain /dev/random, and then print the entropy level for five seconds.
 384 Here is the situation without the ChaosKey inserted:</p>
 385
 386 <blockquote><pre>
 387 % cat /proc/sys/kernel/random/entropy_avail; \
 388   dd bs=1M if=/dev/random of=/dev/null count=1; \
 389   for n in $(seq 1 5); do \
 390      cat /proc/sys/kernel/random/entropy_avail; \
 391      sleep 1; \
 392   done
 393 300
 394 0+1 oppføringer inn
 395 0+1 oppføringer ut
 396 28 byte kopiert, 0,000264565 s, 106 kB/s
 397 4
 398 8
 399 12
 400 17
 401 21
 402 %
 403 </pre></blockquote>
 404
 405 <p>The entropy level increases by 3-4 every second.  In such case any
 406 application requiring random bits (like a HTTPS enabled web server)
 407 will halt and wait for more entrpy.  And here is the situation with
 408 the ChaosKey inserted:</p>
 409
 410 <blockquote><pre>
 411 % cat /proc/sys/kernel/random/entropy_avail; \
 412   dd bs=1M if=/dev/random of=/dev/null count=1; \
 413   for n in $(seq 1 5); do \
 414      cat /proc/sys/kernel/random/entropy_avail; \
 415      sleep 1; \
 416   done
 417 1079
 418 0+1 oppføringer inn
 419 0+1 oppføringer ut
 420 104 byte kopiert, 0,000487647 s, 213 kB/s
 421 433
 422 1028
 423 1031
 424 1035
 425 1038
 426 %
 427 </pre></blockquote>
 428
 429 <p>Quite the difference. :) I bought a few more than I need, in case
 430 someone want to buy one here in Norway. :)</p>
 431
 432 <p>Update: The dongle was presented at Debconf last year.  You might
 433 find <a href="https://debconf16.debconf.org/talks/94/">the talk
 434 recording illuminating</a>.  It explains exactly what the source of
 435 randomness is, if you are unable to spot it from the schema drawing
 436 available from the ChaosKey web site linked at the start of this blog
 437 post.</p>
 438 </div>
 439       <div class="tags">
 440
 441
 442         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>.
 443
 444
 445       </div>
 446     </div>
 447     <div class="padding"></div>
 448
 449     <div class="entry">
 450       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Detect_OOXML_files_with_undefined_behaviour_.html">Detect OOXML files with undefined behaviour?</a></div>
 451       <div class="date">21st February 2017</div>
 452       <div class="body"><p>I just noticed
 453 <a href="http://www.arkivrad.no/aktuelt/riksarkivarens-forskrift-pa-horing">the
 454 new Norwegian proposal for archiving rules in the goverment</a> list
 455 <a href="http://www.ecma-international.org/publications/standards/Ecma-376.htm">ECMA-376</a>
 456 / ISO/IEC 29500 (aka OOXML) as valid formats to put in long term
 457 storage.  Luckily such files will only be accepted based on
 458 pre-approval from the National Archive.  Allowing OOXML files to be
 459 used for long term storage might seem like a good idea as long as we
 460 forget that there are plenty of ways for a "valid" OOXML document to
 461 have content with no defined interpretation in the standard, which
 462 lead to a question and an idea.</p>
 463
 464 <p>Is there any tool to detect if a OOXML document depend on such
 465 undefined behaviour?  It would be useful for the National Archive (and
 466 anyone else interested in verifying that a document is well defined)
 467 to have such tool available when considering to approve the use of
 468 OOXML.  I'm aware of the
 469 <a href="https://github.com/arlm/officeotron/">officeotron OOXML
 470 validator</a>, but do not know how complete it is nor if it will
 471 report use of undefined behaviour.  Are there other similar tools
 472 available?  Please send me an email if you know of any such tool.</p>
 473 </div>
 474       <div class="tags">
 475
 476
 477         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 478
 479
 480       </div>
 481     </div>
 482     <div class="padding"></div>
 483
 484     <div class="entry">
 485       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Ruling_ignored_our_objections_to_the_seizure_of_popcorn_time_no___domstolkontroll_.html">Ruling ignored our objections to the seizure of popcorn-time.no (#domstolkontroll)</a></div>
 486       <div class="date">13th February 2017</div>
 487       <div class="body"><p>A few days ago, we received the ruling from
 488 <a href="http://people.skolelinux.org/pere/blog/A_day_in_court_challenging_seizure_of_popcorn_time_no_for__domstolkontroll.html">my
 489 day in court</a>.  The case in question is a challenge of the seizure
 490 of the DNS domain popcorn-time.no.  The ruling simply did not mention
 491 most of our arguments, and seemed to take everything ØKOKRIM said at
 492 face value, ignoring our demonstration and explanations.  But it is
 493 hard to tell for sure, as we still have not seen most of the documents
 494 in the case and thus were unprepared and unable to contradict several
 495 of the claims made in court by the opposition.  We are considering an
 496 appeal, but it is partly a question of funding, as it is costing us
 497 quite a bit to pay for our lawyer.  If you want to help, please
 498 <a href="http://www.nuug.no/dns-beslag-donasjon.shtml">donate to the
 499 NUUG defense fund</a>.</p>
 500
 501 <p>The details of the case, as far as we know it, is available in
 502 Norwegian from
 503 <a href="https://www.nuug.no/news/tags/dns-domenebeslag/">the NUUG
 504 blog</a>.  This also include
 505 <a href="https://www.nuug.no/news/Avslag_etter_rettslig_h_ring_om_DNS_beslaget___vurderer_veien_videre.shtml">the
 506 ruling itself</a>.</p>
 507 </div>
 508       <div class="tags">
 509
 510
 511         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>.
 512
 513
 514       </div>
 515     </div>
 516     <div class="padding"></div>
 517
 518     <div class="entry">
 519       <div class="title"><a href="http://people.skolelinux.org/pere/blog/A_day_in_court_challenging_seizure_of_popcorn_time_no_for__domstolkontroll.html">A day in court challenging seizure of popcorn-time.no for #domstolkontroll</a></div>
 520       <div class="date"> 3rd February 2017</div>
 521       <div class="body"><p align="center"><img width="70%" src="http://people.skolelinux.org/pere/blog/images/2017-02-01-popcorn-time-in-court.jpeg"></p>
 522
 523 <p>On Wednesday, I spent the entire day in court in Follo Tingrett
 524 representing <a href="https://www.nuug.no/">the member association
 525 NUUG</a>, alongside <a href="https://www.efn.no/">the member
 526 association EFN</a> and <a href="http://www.imc.no">the DNS registrar
 527 IMC</a>, challenging the seizure of the DNS name popcorn-time.no.  It
 528 was interesting to sit in a court of law for the first time in my
 529 life.  Our team can be seen in the picture above: attorney Ola
 530 Tellesbø, EFN board member Tom Fredrik Blenning, IMC CEO Morten Emil
 531 Eriksen and NUUG board member Petter Reinholdtsen.</p>
 532
 533 <p><a href="http://www.domstol.no/no/Enkelt-domstol/follo-tingrett/Nar-gar-rettssaken/Beramming/?cid=AAAA1701301512081262234UJFBVEZZZZZEJBAvtale">The
 534 case at hand</a> is that the Norwegian National Authority for
 535 Investigation and Prosecution of Economic and Environmental Crime (aka
 536 Økokrim) decided on their own, to seize a DNS domain early last
 537 year, without following
 538 <a href="https://www.norid.no/no/regelverk/navnepolitikk/#link12">the
 539 official policy of the Norwegian DNS authority</a> which require a
 540 court decision.  The web site in question was a site covering Popcorn
 541 Time.  And Popcorn Time is the name of a technology with both legal
 542 and illegal applications.  Popcorn Time is a client combining
 543 searching a Bittorrent directory available on the Internet with
 544 downloading/distribute content via Bittorrent and playing the
 545 downloaded content on screen.  It can be used illegally if it is used
 546 to distribute content against the will of the right holder, but it can
 547 also be used legally to play a lot of content, for example the
 548 millions of movies
 549 <a href="https://archive.org/details/movies">available from the
 550 Internet Archive</a> or the collection
 551 <a href="http://vodo.net/films/">available from Vodo</a>.  We created
 552 <a href="magnet:?xt=urn:btih:86c1802af5a667ca56d3918aecb7d3c0f7173084&dn=PresentasjonFolloTingrett.mov&tr=udp%3A%2F%2Fpublic.popcorn-tracker.org%3A6969%2Fannounce">a
 553 video demonstrating legally use of Popcorn Time</a> and played it in
 554 Court.  It can of course be downloaded using Bittorrent.</p>
 555
 556 <p>I did not quite know what to expect from a day in court.  The
 557 government held on to their version of the story and we held on to
 558 ours, and I hope the judge is able to make sense of it all.  We will
 559 know in two weeks time.  Unfortunately I do not have high hopes, as
 560 the Government have the upper hand here with more knowledge about the
 561 case, better training in handling criminal law and in general higher
 562 standing in the courts than fairly unknown DNS registrar and member
 563 associations.  It is expensive to be right also in Norway.  So far the
 564 case have cost more than NOK 70 000,-.  To help fund the case, NUUG
 565 and EFN have asked for donations, and managed to collect around NOK 25
 566 000,- so far.  Given the presentation from the Government, I expect
 567 the government to appeal if the case go our way.  And if the case do
 568 not go our way, I hope we have enough funding to appeal.</p>
 569
 570 <p>From the other side came two people from Økokrim.  On the benches,
 571 appearing to be part of the group from the government were two people
 572 from the Simonsen Vogt Wiik lawyer office, and three others I am not
 573 quite sure who was.  Økokrim had proposed to present two witnesses
 574 from The Motion Picture Association, but this was rejected because
 575 they did not speak Norwegian and it was a bit late to bring in a
 576 translator, but perhaps the two from MPA were present anyway.  All
 577 seven appeared to know each other.  Good to see the case is take
 578 seriously.</p>
 579
 580 <p>If you, like me, believe the courts should be involved before a DNS
 581 domain is hijacked by the government, or you believe the Popcorn Time
 582 technology have a lot of useful and legal applications, I suggest you
 583 too <a href="http://www.nuug.no/dns-beslag-donasjon.shtml">donate to
 584 the NUUG defense fund</a>.  Both Bitcoin and bank transfer are
 585 available. If NUUG get more than we need for the legal action (very
 586 unlikely), the rest will be spend promoting free software, open
 587 standards and unix-like operating systems in Norway, so no matter what
 588 happens the money will be put to good use.</p>
 589
 590 <p>If you want to lean more about the case, I recommend you check out
 591 <a href="https://www.nuug.no/news/tags/dns-domenebeslag/">the blog
 592 posts from NUUG covering the case</a>.  They cover the legal arguments
 593 on both sides.</p>
 594 </div>
 595       <div class="tags">
 596
 597
 598         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>.
 599
 600
 601       </div>
 602     </div>
 603     <div class="padding"></div>
 604
 605     <div class="entry">
 606       <div class="title"><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></div>
 607       <div class="date">12th January 2017</div>
 608       <div class="body"><p>I dag fikk jeg en skikkelig gladmelding.  Bakgrunnen er at før jul
 609 arrangerte Nasjonalbiblioteket
 610 <a href="http://www.nb.no/Bibliotekutvikling/Kunnskapsorganisering/Nasjonalt-verksregister/Seminar-om-verksregister">et
 611 seminar om sitt knakende gode tiltak «verksregister»</a>.  Eneste
 612 måten å melde seg på dette seminaret var å sende personopplysninger
 613 til Google via Google Skjemaer.  Dette syntes jeg var tvilsom praksis,
 614 da det bør være mulig å delta på seminarer arrangert av det offentlige
 615 uten å måtte dele sine interesser, posisjon og andre
 616 personopplysninger med Google.  Jeg ba derfor om innsyn via
 617 <a href="https://www.mimesbronn.no/">Mimes brønn</a> i
 618 <a href="https://www.mimesbronn.no/request/personopplysninger_til_google_sk">avtaler
 619 og vurderinger Nasjonalbiblioteket hadde rundt dette</a>.
 620 Personopplysningsloven legger klare rammer for hva som må være på
 621 plass før en kan be tredjeparter, spesielt i utlandet, behandle
 622 personopplysninger på sine vegne, så det burde eksistere grundig
 623 dokumentasjon før noe slikt kan bli lovlig.  To jurister hos
 624 Nasjonalbiblioteket mente først dette var helt i orden, og at Googles
 625 standardavtale kunne brukes som databehandlingsavtale.  Det syntes jeg
 626 var merkelig, men har ikke hatt kapasitet til å følge opp saken før
 627 for to dager siden.</p>
 628
 629 <p>Gladnyheten i dag, som kom etter at jeg tipset Nasjonalbiblioteket
 630 om at Datatilsynet underkjente Googles standardavtaler som
 631 databehandleravtaler i 2011, er at Nasjonalbiblioteket har bestemt seg
 632 for å avslutte bruken av Googles Skjemaer/Apps og gå i dialog med DIFI
 633 for å finne bedre måter å håndtere påmeldinger i tråd med
 634 personopplysningsloven.  Det er fantastisk å se at av og til hjelper
 635 det å spørre hva i alle dager det offentlige holder på med.</p>
 636 </div>
 637       <div class="tags">
 638
 639
 640         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>.
 641
 642
 643       </div>
 644     </div>
 645     <div class="padding"></div>
 646
 647     <p style="text-align: right;"><a href="index.rss"><img src="http://people.skolelinux.org/pere/blog/xml.gif" alt="RSS feed" width="36" height="14" /></a></p>
 648     <div id="sidebar">
 649
 650
 651
 652 <h2>Archive</h2>
 653 <ul>
 654
 655 <li>2017
 656 <ul>
 657
 658 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/01/">January (4)</a></li>
 659
 660 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/02/">February (3)</a></li>
 661
 662 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/03/">March (5)</a></li>
 663
 664 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/04/">April (1)</a></li>
 665
 666 </ul></li>
 667
 668 <li>2016
 669 <ul>
 670
 671 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/01/">January (3)</a></li>
 672
 673 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/02/">February (2)</a></li>
 674
 675 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/03/">March (3)</a></li>
 676
 677 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/04/">April (8)</a></li>
 678
 679 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/05/">May (8)</a></li>
 680
 681 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/06/">June (2)</a></li>
 682
 683 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/07/">July (2)</a></li>
 684
 685 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/08/">August (5)</a></li>
 686
 687 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/09/">September (2)</a></li>
 688
 689 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/10/">October (3)</a></li>
 690
 691 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/11/">November (8)</a></li>
 692
 693 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/12/">December (5)</a></li>
 694
 695 </ul></li>
 696
 697 <li>2015
 698 <ul>
 699
 700 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/01/">January (7)</a></li>
 701
 702 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/02/">February (6)</a></li>
 703
 704 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/03/">March (1)</a></li>
 705
 706 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/04/">April (4)</a></li>
 707
 708 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/05/">May (3)</a></li>
 709
 710 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/06/">June (4)</a></li>
 711
 712 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/07/">July (6)</a></li>
 713
 714 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/08/">August (2)</a></li>
 715
 716 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/09/">September (2)</a></li>
 717
 718 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/10/">October (9)</a></li>
 719
 720 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/11/">November (6)</a></li>
 721
 722 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/12/">December (3)</a></li>
 723
 724 </ul></li>
 725
 726 <li>2014
 727 <ul>
 728
 729 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
 730
 731 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
 732
 733 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
 734
 735 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/04/">April (7)</a></li>
 736
 737 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/05/">May (1)</a></li>
 738
 739 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/06/">June (2)</a></li>
 740
 741 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/07/">July (2)</a></li>
 742
 743 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/08/">August (2)</a></li>
 744
 745 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/09/">September (5)</a></li>
 746
 747 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/10/">October (6)</a></li>
 748
 749 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/11/">November (3)</a></li>
 750
 751 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/12/">December (5)</a></li>
 752
 753 </ul></li>
 754
 755 <li>2013
 756 <ul>
 757
 758 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
 759
 760 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
 761
 762 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
 763
 764 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
 765
 766 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
 767
 768 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
 769
 770 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
 771
 772 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
 773
 774 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
 775
 776 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
 777
 778 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
 779
 780 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
 781
 782 </ul></li>
 783
 784 <li>2012
 785 <ul>
 786
 787 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
 788
 789 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
 790
 791 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
 792
 793 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
 794
 795 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
 796
 797 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
 798
 799 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
 800
 801 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
 802
 803 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
 804
 805 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
 806
 807 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
 808
 809 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
 810
 811 </ul></li>
 812
 813 <li>2011
 814 <ul>
 815
 816 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
 817
 818 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
 819
 820 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
 821
 822 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
 823
 824 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
 825
 826 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
 827
 828 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
 829
 830 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
 831
 832 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
 833
 834 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
 835
 836 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
 837
 838 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
 839
 840 </ul></li>
 841
 842 <li>2010
 843 <ul>
 844
 845 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
 846
 847 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
 848
 849 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
 850
 851 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
 852
 853 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
 854
 855 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
 856
 857 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
 858
 859 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
 860
 861 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
 862
 863 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
 864
 865 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
 866
 867 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
 868
 869 </ul></li>
 870
 871 <li>2009
 872 <ul>
 873
 874 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
 875
 876 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
 877
 878 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
 879
 880 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
 881
 882 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
 883
 884 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
 885
 886 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
 887
 888 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
 889
 890 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
 891
 892 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
 893
 894 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
 895
 896 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
 897
 898 </ul></li>
 899
 900 <li>2008
 901 <ul>
 902
 903 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
 904
 905 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
 906
 907 </ul></li>
 908
 909 </ul>
 910
 911
 912
 913 <h2>Tags</h2>
 914 <ul>
 915
 916  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
 917
 918  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
 919
 920  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
 921
 922  <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
 923
 924  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (9)</a></li>
 925
 926  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (16)</a></li>
 927
 928  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
 929
 930  <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
 931
 932  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (148)</a></li>
 933
 934  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (158)</a></li>
 935
 936  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian-handbook">debian-handbook (3)</a></li>
 937
 938  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
 939
 940  <li><a href="http://people.skolelinux.org/pere/blog/tags/dld">dld (16)</a></li>
 941
 942  <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (23)</a></li>
 943
 944  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
 945
 946  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (346)</a></li>
 947
 948  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
 949
 950  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
 951
 952  <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (29)</a></li>
 953
 954  <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
 955
 956  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (18)</a></li>
 957
 958  <li><a href="http://people.skolelinux.org/pere/blog/tags/h264">h264 (20)</a></li>
 959
 960  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (42)</a></li>
 961
 962  <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (15)</a></li>
 963
 964  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (20)</a></li>
 965
 966  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
 967
 968  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (8)</a></li>
 969
 970  <li><a href="http://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd (2)</a></li>
 971
 972  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
 973
 974  <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
 975
 976  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (39)</a></li>
 977
 978  <li><a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (9)</a></li>
 979
 980  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (288)</a></li>
 981
 982  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (188)</a></li>
 983
 984  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (30)</a></li>
 985
 986  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
 987
 988  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (64)</a></li>
 989
 990  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (99)</a></li>
 991
 992  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
 993
 994  <li><a href="http://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
 995
 996  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
 997
 998  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
 999
1000  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (10)</a></li>
1001
1002  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1003
1004  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (5)</a></li>
1005
1006  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1007
1008  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (52)</a></li>
1009
1010  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1011
1012  <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (5)</a></li>
1013
1014  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (52)</a></li>
1015
1016  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (5)</a></li>
1017
1018  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (11)</a></li>
1019
1020  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (48)</a></li>
1021
1022  <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (3)</a></li>
1023
1024  <li><a href="http://people.skolelinux.org/pere/blog/tags/usenix">usenix (2)</a></li>
1025
1026  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
1027
1028  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (59)</a></li>
1029
1030  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
1031
1032  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (40)</a></li>
1033
1034 </ul>
1035
1036
1037     </div>
1038     <p style="text-align: right">
1039  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
1040 </p>
1041
1042   </body>
1043 </html>