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/_Rapporten_ser_ikke_p__informasjonssikkerhet_knyttet_til_personlig_integritet_.html">«Rapporten ser ikke på informasjonssikkerhet knyttet til personlig integritet»</a></div>
  24       <div class="date">27th June 2017</div>
  25       <div class="body"><p>Jeg kom over teksten
  26 «<a href="https://freedom-to-tinker.com/2017/06/21/killing-car-privacy-by-federal-mandate/">Killing
  27 car privacy by federal mandate</a>» av Leonid Reyzin på Freedom to
  28 Tinker i dag, og det gleder meg å se en god gjennomgang om hvorfor det
  29 er et urimelig inngrep i privatsfæren å la alle biler kringkaste sin
  30 posisjon og bevegelse via radio.  Det omtalte forslaget basert på
  31 Dedicated Short Range Communication (DSRC) kalles Basic Safety Message
  32 (BSM) i USA og Cooperative Awareness Message (CAM) i Europa, og det
  33 norske Vegvesenet er en av de som ser ut til å kunne tenke seg å
  34 pålegge alle biler å fjerne nok en bit av innbyggernes privatsfære.
  35 Anbefaler alle å lese det som står der.
  36
  37 <p>Mens jeg tittet litt på DSRC på biler i Norge kom jeg over et sitat
  38 jeg synes er illustrativt for hvordan det offentlige Norge håndterer
  39 problemstillinger rundt innbyggernes privatsfære i SINTEF-rapporten
  40 «<a href="https://www.sintef.no/publikasjoner/publikasjon/Download/?pubid=SINTEF+A23933">Informasjonssikkerhet
  41 i AutoPASS-brikker</a>» av Trond Foss:</p>
  42
  43 <p><blockquote>
  44 «Rapporten ser ikke på informasjonssikkerhet knyttet til personlig
  45   integritet.»
  46 </blockquote></p>
  47
  48 <p>Så enkelt kan det tydeligvis gjøres når en vurderer
  49 informasjonssikkerheten.  Det holder vel at folkene på toppen kan si
  50 at «Personvernet er ivaretatt», som jo er den populære intetsigende
  51 frasen som gjør at mange tror enkeltindividers integritet tas vare på.
  52 Sitatet fikk meg til å undres på hvor ofte samme tilnærming, å bare se
  53 bort fra behovet for personlig itegritet, blir valgt når en velger å
  54 legge til rette for nok et inngrep i privatsfæren til personer i
  55 Norge.  Det er jo sjelden det får reaksjoner.  Historien om
  56 reaksjonene på Helse Sør-Østs tjenesteutsetting er jo sørgelig nok et
  57 unntak og toppen av isfjellet, desverre.  Tror jeg fortsatt takker nei
  58 til både AutoPASS og holder meg så langt unna det norske helsevesenet
  59 som jeg kan, inntil de har demonstrert og dokumentert at de verdsetter
  60 individets privatsfære og personlige integritet høyere enn kortsiktig
  61 gevist og samfunnsnytte.</p>
  62 </div>
  63       <div class="tags">
  64
  65
  66         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/sikkerhet">sikkerhet</a>.
  67
  68
  69       </div>
  70     </div>
  71     <div class="padding"></div>
  72
  73     <div class="entry">
  74       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Updated_sales_number_for_my_Free_Culture_paper_editions.html">Updated sales number for my Free Culture paper editions</a></div>
  75       <div class="date">12th June 2017</div>
  76       <div class="body"><p>It is pleasing to see that the work we put down in publishing new
  77 editions of the classic <a href="http://www.free-culture.cc/">Free
  78 Culture book</a> by the founder of the Creative Commons movement,
  79 Lawrence Lessig, is still being appreciated.  I had a look at the
  80 latest sales numbers for the paper edition today.  Not too impressive,
  81 but happy to see some buyers still exist.  All the revenue from the
  82 books is sent to the <a href="https://creativecommons.org/">Creative
  83 Commons Corporation</a>, and they receive the largest cut if you buy
  84 directly from Lulu.  Most books are sold via Amazon, with Ingram
  85 second and only a small fraction directly from Lulu.  The ebook
  86 edition is available for free from
  87 <a href="https://github.com/petterreinholdtsen/free-culture-lessig">Github</a>.</p>
  88
  89 <table border="0">
  90 <tr><th rowspan="2" valign="bottom">Title / language</th><th colspan="3">Quantity</th></tr>
  91 <tr><th>2016 jan-jun</th><th>2016 jul-dec</th><th>2017 jan-may</th></tr>
  92
  93 <tr>
  94   <td><a href="http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html">Culture Libre / French</a></td>
  95   <td align="right">3</td>
  96   <td align="right">6</td>
  97   <td align="right">15</td>
  98 </tr>
  99
 100 <tr>
 101   <td><a href="http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">Fri kultur / Norwegian</a></td>
 102   <td align="right">7</td>
 103   <td align="right">1</td>
 104   <td align="right">0</td>
 105 </tr>
 106
 107 <tr>
 108   <td><a href="http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html">Free Culture / English</a></td>
 109   <td align="right">14</td>
 110   <td align="right">27</td>
 111   <td align="right">16</td>
 112 </tr>
 113
 114 <tr>
 115   <td>Total</td>
 116   <td align="right">24</td>
 117   <td align="right">34</td>
 118   <td align="right">31</td>
 119 </tr>
 120
 121 </table>
 122
 123 <p>A bit sad to see the low sales number on the Norwegian edition, and
 124 a bit surprising the English edition still selling so well.</p>
 125
 126 <p>If you would like to translate and publish the book in your native
 127 language, I would be happy to help make it happen.  Please get in
 128 touch.</p>
 129 </div>
 130       <div class="tags">
 131
 132
 133         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>.
 134
 135
 136       </div>
 137     </div>
 138     <div class="padding"></div>
 139
 140     <div class="entry">
 141       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html">Release 0.1.1 of free software archive system Nikita announced</a></div>
 142       <div class="date">10th June 2017</div>
 143       <div class="body"><p>I am very happy to report that the
 144 <a href="https://github.com/hiOA-ABI/nikita-noark5-core">Nikita Noark 5
 145 core project</a> tagged its second release today.  The free software
 146 solution is an implementation of the Norwegian archive standard Noark
 147 5 used by government offices in Norway.  These were the changes in
 148 version 0.1.1 since version 0.1.0 (from NEWS.md):
 149
 150 <ul>
 151
 152  <li>Continued work on the angularjs GUI, including document upload.</li>
 153  <li>Implemented correspondencepartPerson, correspondencepartUnit and
 154    correspondencepartInternal</li>
 155  <li>Applied for coverity coverage and started submitting code on
 156    regualr basis.</li>
 157  <li>Started fixing bugs reported by coverity</li>
 158  <li>Corrected and completed HATEOAS links to make sure entire API is
 159    available via URLs in _links.</li>
 160  <li>Corrected all relation URLs to use trailing slash.</li>
 161  <li>Add initial support for storing data in ElasticSearch.</li>
 162  <li>Now able to receive and store uploaded files in the archive.</li>
 163  <li>Changed JSON output for object lists to have relations in _links.</li>
 164  <li>Improve JSON output for empty object lists.</li>
 165  <li>Now uses correct MIME type application/vnd.noark5-v4+json.</li>
 166  <li>Added support for docker container images.</li>
 167  <li>Added simple API browser implemented in JavaScript/Angular.</li>
 168  <li>Started on archive client implemented in JavaScript/Angular.</li>
 169  <li>Started on prototype to show the public mail journal.</li>
 170  <li>Improved performance by disabling Sprint FileWatcher.</li>
 171  <li>Added support for 'arkivskaper', 'saksmappe' and 'journalpost'.</li>
 172  <li>Added support for some metadata codelists.</li>
 173  <li>Added support for Cross-origin resource sharing (CORS).</li>
 174  <li>Changed login method from Basic Auth to JSON Web Token (RFC 7519)
 175    style.</li>
 176  <li>Added support for GET-ing ny-* URLs.</li>
 177  <li>Added support for modifying entities using PUT and eTag.</li>
 178  <li>Added support for returning XML output on request.</li>
 179  <li>Removed support for English field and class names, limiting ourself
 180    to the official names.</li>
 181  <li>...</li>
 182
 183 </ul>
 184
 185 <p>If this sound interesting to you, please contact us on IRC (#nikita
 186 on irc.freenode.net) or email
 187 (<a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">nikita-noark
 188 mailing list).</p>
 189 </div>
 190       <div class="tags">
 191
 192
 193         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>.
 194
 195
 196       </div>
 197     </div>
 198     <div class="padding"></div>
 199
 200     <div class="entry">
 201       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html">Idea for storing trusted timestamps in a Noark 5 archive</a></div>
 202       <div class="date"> 7th June 2017</div>
 203       <div class="body"><p><em>This is a copy of
 204 <a href="https://lists.nuug.no/pipermail/nikita-noark/2017-June/000297.html">an
 205 email I posted to the nikita-noark mailing list</a>.  Please follow up
 206 there if you would like to discuss this topic.  The background is that
 207 we are making a free software archive system based on the Norwegian
 208 <a href="https://www.arkivverket.no/forvaltning-og-utvikling/regelverk-og-standarder/noark-standarden">Noark
 209 5 standard</a> for government archives.</em></p>
 210
 211 <p>I've been wondering a bit lately how trusted timestamps could be
 212 stored in Noark 5.
 213 <a href="https://en.wikipedia.org/wiki/Trusted_timestamping">Trusted
 214 timestamps</a> can be used to verify that some information
 215 (document/file/checksum/metadata) have not been changed since a
 216 specific time in the past.  This is useful to verify the integrity of
 217 the documents in the archive.</p>
 218
 219 <p>Then it occured to me, perhaps the trusted timestamps could be
 220 stored as dokument variants (ie dokumentobjekt referered to from
 221 dokumentbeskrivelse) with the filename set to the hash it is
 222 stamping?</p>
 223
 224 <p>Given a "dokumentbeskrivelse" with an associated "dokumentobjekt",
 225 a new dokumentobjekt is associated with "dokumentbeskrivelse" with the
 226 same attributes as the stamped dokumentobjekt except these
 227 attributes:</p>
 228
 229 <ul>
 230
 231 <li>format -> "RFC3161"
 232 <li>mimeType -> "application/timestamp-reply"
 233 <li>formatDetaljer -> "&lt;source URL for timestamp service&gt;"
 234 <li>filenavn -> "&lt;sjekksum&gt;.tsr"
 235
 236 </ul>
 237
 238 <p>This assume a service following
 239 <a href="https://tools.ietf.org/html/rfc3161">IETF RFC 3161</a> is
 240 used, which specifiy the given MIME type for replies and the .tsr file
 241 ending for the content of such trusted timestamp.  As far as I can
 242 tell from the Noark 5 specifications, it is OK to have several
 243 variants/renderings of a dokument attached to a given
 244 dokumentbeskrivelse objekt.  It might be stretching it a bit to make
 245 some of these variants represent crypto-signatures useful for
 246 verifying the document integrity instead of representing the dokument
 247 itself.</p>
 248
 249 <p>Using the source of the service in formatDetaljer allow several
 250 timestamping services to be used.  This is useful to spread the risk
 251 of key compromise over several organisations.  It would only be a
 252 problem to trust the timestamps if all of the organisations are
 253 compromised.</p>
 254
 255 <p>The following oneliner on Linux can be used to generate the tsr
 256 file.  $input is the path to the file to checksum, and $sha256 is the
 257 SHA-256 checksum of the file (ie the "<sjekksum>.tsr" value mentioned
 258 above).</p>
 259
 260 <p><blockquote><pre>
 261 openssl ts -query -data "$inputfile" -cert -sha256 -no_nonce \
 262   | curl -s -H "Content-Type: application/timestamp-query" \
 263       --data-binary "@-" http://zeitstempel.dfn.de > $sha256.tsr
 264 </pre></blockquote></p>
 265
 266 <p>To verify the timestamp, you first need to download the public key
 267 of the trusted timestamp service, for example using this command:</p>
 268
 269 <p><blockquote><pre>
 270 wget -O ca-cert.txt \
 271   https://pki.pca.dfn.de/global-services-ca/pub/cacert/chain.txt
 272 </pre></blockquote></p>
 273
 274 <p>Note, the public key should be stored alongside the timestamps in
 275 the archive to make sure it is also available 100 years from now.  It
 276 is probably a good idea to standardise how and were to store such
 277 public keys, to make it easier to find for those trying to verify
 278 documents 100 or 1000 years from now. :)</p>
 279
 280 <p>The verification itself is a simple openssl command:</p>
 281
 282 <p><blockquote><pre>
 283 openssl ts -verify -data $inputfile -in $sha256.tsr \
 284   -CAfile ca-cert.txt -text
 285 </pre></blockquote></p>
 286
 287 <p>Is there any reason this approach would not work?  Is it somehow against
 288 the Noark 5 specification?</p>
 289 </div>
 290       <div class="tags">
 291
 292
 293         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</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>.
 294
 295
 296       </div>
 297     </div>
 298     <div class="padding"></div>
 299
 300     <div class="entry">
 301       <div class="title"><a href="http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html">Når nynorskoversettelsen svikter til eksamen...</a></div>
 302       <div class="date"> 3rd June 2017</div>
 303       <div class="body"><p><a href="http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-622459b.html">Aftenposten
 304 melder i dag</a> om feil i eksamensoppgavene for eksamen i politikk og
 305 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
 306 like.  Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
 307 på om den fri oversetterløsningen
 308 <a href="https://www.apertium.org/">Apertium</a> ville gjort en bedre
 309 jobb enn Utdanningsdirektoratet.  Det kan se slik ut.</p>
 310
 311 <p>Her er bokmålsoppgaven fra eksamenen:</p>
 312
 313 <blockquote>
 314 <p>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
 315 rolle og muligheter til å håndtere internasjonale utfordringer, som
 316 for eksempel flykningekrisen.</p>
 317
 318 <p>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
 319 på temaet:</p>
 320 <ol>
 321 <li>Flykningeregnskapet 2016, UNHCR og IDMC
 322 <li>«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
 323 </ol>
 324
 325 </blockquote>
 326
 327 <p>Dette oversetter Apertium slik:</p>
 328
 329 <blockquote>
 330 <p>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
 331 andre aktørar og høve til å handtera internasjonale utfordringar, som
 332 til dømes *flykningekrisen.</p>
 333
 334 <p>Vedleggja er døme på tekster som kan gje relevante perspektiv på
 335 temaet:</p>
 336
 337 <ol>
 338 <li>*Flykningeregnskapet 2016, *UNHCR og *IDMC</li>
 339 <li>«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015</li>
 340 </ol>
 341
 342 </blockquote>
 343
 344 <p>Ord som ikke ble forstått er markert med stjerne (*), og trenger
 345 ekstra språksjekk.  Men ingen ord er forsvunnet, slik det var i
 346 oppgaven elevene fikk presentert på eksamen.  Jeg mistenker dog at
 347 "andre aktørers rolle og muligheter til ..." burde vært oversatt til
 348 "rolla til andre aktørar og deira høve til ..." eller noe slikt, men
 349 det er kanskje flisespikking.  Det understreker vel bare at det alltid
 350 trengs korrekturlesning etter automatisk oversettelse.</p>
 351 </div>
 352       <div class="tags">
 353
 354
 355         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll</a>.
 356
 357
 358       </div>
 359     </div>
 360     <div class="padding"></div>
 361
 362     <div class="entry">
 363       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Epost_inn_som_arkivformat_i_Riksarkivarens_forskrift_.html">Epost inn som arkivformat i Riksarkivarens forskrift?</a></div>
 364       <div class="date">27th April 2017</div>
 365       <div class="body"><p>I disse dager, med frist 1. mai, har Riksarkivaren ute en høring på
 366 sin forskrift.  Som en kan se er det ikke mye tid igjen før fristen
 367 som går ut på søndag.  Denne forskriften er det som lister opp hvilke
 368 formater det er greit å arkivere i
 369 <a href="http://www.arkivverket.no/arkivverket/Offentleg-forvalting/Noark/Noark-5">Noark
 370 5-løsninger</a> i Norge.</p>
 371
 372 <p>Jeg fant høringsdokumentene hos
 373 <a href="https://www.arkivrad.no/aktuelt/riksarkivarens-forskrift-pa-horing">Norsk
 374 Arkivråd</a> etter å ha blitt tipset på epostlisten til
 375 <a href="https://github.com/hiOA-ABI/nikita-noark5-core">fri
 376 programvareprosjektet Nikita Noark5-Core</a>, som lager et Noark 5
 377 Tjenestegresesnitt.  Jeg er involvert i Nikita-prosjektet og takket
 378 være min interesse for tjenestegrensesnittsprosjektet har jeg lest en
 379 god del Noark 5-relaterte dokumenter, og til min overraskelse oppdaget
 380 at standard epost ikke er på listen over godkjente formater som kan
 381 arkiveres.  Høringen med frist søndag er en glimrende mulighet til å
 382 forsøke å gjøre noe med det.  Jeg holder på med
 383 <a href="https://github.com/petterreinholdtsen/noark5-tester/blob/master/docs/hoering-arkivforskrift.tex">egen
 384 høringsuttalelse</a>, og lurer på om andre er interessert i å støtte
 385 forslaget om å tillate arkivering av epost som epost i arkivet.</p>
 386
 387 <p>Er du igang med å skrive egen høringsuttalelse allerede?  I så fall
 388 kan du jo vurdere å ta med en formulering om epost-lagring. Jeg tror
 389 ikke det trengs så mye.  Her et kort forslag til tekst:</p>
 390
 391 <p><blockquote>
 392
 393   <p>Viser til høring sendt ut 2017-02-17 (Riksarkivarens referanse
 394   2016/9840 HELHJO), og tillater oss å sende inn noen innspill om
 395   revisjon av Forskrift om utfyllende tekniske og arkivfaglige
 396   bestemmelser om behandling av offentlige arkiver (Riksarkivarens
 397   forskrift).</p>
 398
 399   <p>Svært mye av vår kommuikasjon foregår i dag på e-post.  Vi
 400   foreslår derfor at Internett-e-post, slik det er beskrevet i IETF
 401   RFC 5322,
 402   <a href="https://tools.ietf.org/html/rfc5322">https://tools.ietf.org/html/rfc5322</a>. bør
 403   inn som godkjent dokumentformat.  Vi foreslår at forskriftens
 404   oversikt over godkjente dokumentformater ved innlevering i § 5-16
 405   endres til å ta med Internett-e-post.</p>
 406
 407 </blockquote></p>
 408
 409 <p>Som del av arbeidet med tjenestegrensesnitt har vi testet hvordan
 410 epost kan lagres i en Noark 5-struktur, og holder på å skrive et
 411 forslag om hvordan dette kan gjøres som vil bli sendt over til
 412 arkivverket så snart det er ferdig.  De som er interesserte kan
 413 <a href="https://github.com/petterreinholdtsen/noark5-tester/blob/master/docs/epostlagring.md">følge
 414 fremdriften på web</a>.</p>
 415
 416 <p>Oppdatering 2017-04-28: I dag ble høringuttalelsen jeg skrev
 417   <a href="https://www.nuug.no/news/NUUGs_h_ringuttalelse_til_Riksarkivarens_forskrift.shtml">sendt
 418   inn av foreningen NUUG</a>.</p>
 419 </div>
 420       <div class="tags">
 421
 422
 423         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>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 424
 425
 426       </div>
 427     </div>
 428     <div class="padding"></div>
 429
 430     <div class="entry">
 431       <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>
 432       <div class="date">20th April 2017</div>
 433       <div class="body"><p>Jeg oppdaget i dag at <a href="https://www.oep.no/">nettstedet som
 434 publiserer offentlige postjournaler fra statlige etater</a>, OEP, har
 435 begynt å blokkerer enkelte typer webklienter fra å få tilgang.  Vet
 436 ikke hvor mange det gjelder, men det gjelder i hvert fall libwww-perl
 437 og curl.  For å teste selv, kjør følgende:</p>
 438
 439 <blockquote><pre>
 440 % curl -v -s https://www.oep.no/pub/report.xhtml?reportId=3 2>&1 |grep '< HTTP'
 441 < HTTP/1.1 404 Not Found
 442 % curl -v -s --header 'User-Agent:Opera/12.0' https://www.oep.no/pub/report.xhtml?reportId=3 2>&1 |grep '< HTTP'
 443 < HTTP/1.1 200 OK
 444 %
 445 </pre></blockquote>
 446
 447 <p>Her kan en se at tjenesten gir «404 Not Found» for curl i
 448 standardoppsettet, mens den gir «200 OK» hvis curl hevder å være Opera
 449 versjon 12.0.  Offentlig elektronisk postjournal startet blokkeringen
 450 2017-03-02.</p>
 451
 452 <p>Blokkeringen vil gjøre det litt vanskeligere å maskinelt hente
 453 informasjon fra oep.no.  Kan blokkeringen være gjort for å hindre
 454 automatisert innsamling av informasjon fra OEP, slik Pressens
 455 Offentlighetsutvalg gjorde for å dokumentere hvordan departementene
 456 hindrer innsyn i
 457 <a href="http://presse.no/dette-mener-np/undergraver-offentlighetsloven/">rapporten
 458 «Slik hindrer departementer innsyn» som ble publiserte i januar
 459 2017</a>.  Det virker usannsynlig, da det jo er trivielt å bytte
 460 User-Agent til noe nytt.</p>
 461
 462 <p>Finnes det juridisk grunnlag for det offentlige å diskriminere
 463 webklienter slik det gjøres her?  Der tilgang gis eller ikke alt etter
 464 hva klienten sier at den heter?  Da OEP eies av DIFI og driftes av
 465 Basefarm, finnes det kanskje noen dokumenter sendt mellom disse to
 466 aktørene man kan be om innsyn i for å forstå hva som har skjedd.  Men
 467 <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
 468 til DIFI viser kun to dokumenter</a> det siste året mellom DIFI og
 469 Basefarm.
 470 <a href="https://www.mimesbronn.no/request/blokkering_av_tilgang_til_oep_fo">Mimes brønn neste</a>,
 471 tenker jeg.</p>
 472 </div>
 473       <div class="tags">
 474
 475
 476         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>.
 477
 478
 479       </div>
 480     </div>
 481     <div class="padding"></div>
 482
 483     <div class="entry">
 484       <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>
 485       <div class="date">19th March 2017</div>
 486       <div class="body"><p>The <a href="https://github.com/hiOA-ABI/nikita-noark5-core">Nikita
 487 Noark 5 core project</a> is implementing the Norwegian standard for
 488 keeping an electronic archive of government documents.
 489 <a href="http://www.arkivverket.no/arkivverket/Offentlig-forvaltning/Noark/Noark-5/English-version">The
 490 Noark 5 standard</a> document the requirement for data systems used by
 491 the archives in the Norwegian government, and the Noark 5 web interface
 492 specification document a REST web service for storing, searching and
 493 retrieving documents and metadata in such archive.  I've been involved
 494 in the project since a few weeks before Christmas, when the Norwegian
 495 Unix User Group
 496 <a href="https://www.nuug.no/news/NOARK5_kjerne_som_fri_programvare_f_r_epostliste_hos_NUUG.shtml">announced
 497 it supported the project</a>.  I believe this is an important project,
 498 and hope it can make it possible for the government archives in the
 499 future to use free software to keep the archives we citizens depend
 500 on.  But as I do not hold such archive myself, personally my first use
 501 case is to store and analyse public mail journal metadata published
 502 from the government.  I find it useful to have a clear use case in
 503 mind when developing, to make sure the system scratches one of my
 504 itches.</p>
 505
 506 <p>If you would like to help make sure there is a free software
 507 alternatives for the archives, please join our IRC channel
 508 (<a href="irc://irc.freenode.net/%23nikita"">#nikita on
 509 irc.freenode.net</a>) and
 510 <a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">the
 511 project mailing list</a>.</p>
 512
 513 <p>When I got involved, the web service could store metadata about
 514 documents.  But a few weeks ago, a new milestone was reached when it
 515 became possible to store full text documents too.  Yesterday, I
 516 completed an implementation of a command line tool
 517 <tt>archive-pdf</tt> to upload a PDF file to the archive using this
 518 API.  The tool is very simple at the moment, and find existing
 519 <a href="https://en.wikipedia.org/wiki/Fonds">fonds</a>, series and
 520 files while asking the user to select which one to use if more than
 521 one exist.  Once a file is identified, the PDF is associated with the
 522 file and uploaded, using the title extracted from the PDF itself.  The
 523 process is fairly similar to visiting the archive, opening a cabinet,
 524 locating a file and storing a piece of paper in the archive.  Here is
 525 a test run directly after populating the database with test data using
 526 our API tester:</p>
 527
 528 <p><blockquote><pre>
 529 ~/src//noark5-tester$ ./archive-pdf mangelmelding/mangler.pdf
 530 using arkiv: Title of the test fonds created 2017-03-18T23:49:32.103446
 531 using arkivdel: Title of the test series created 2017-03-18T23:49:32.103446
 532
 533  0 - Title of the test case file created 2017-03-18T23:49:32.103446
 534  1 - Title of the test file created 2017-03-18T23:49:32.103446
 535 Select which mappe you want (or search term): 0
 536 Uploading mangelmelding/mangler.pdf
 537   PDF title: Mangler i spesifikasjonsdokumentet for NOARK 5 Tjenestegrensesnitt
 538   File 2017/1: Title of the test case file created 2017-03-18T23:49:32.103446
 539 ~/src//noark5-tester$
 540 </pre></blockquote></p>
 541
 542 <p>You can see here how the fonds (arkiv) and serie (arkivdel) only had
 543 one option, while the user need to choose which file (mappe) to use
 544 among the two created by the API tester.  The <tt>archive-pdf</tt>
 545 tool can be found in the git repository for the API tester.</p>
 546
 547 <p>In the project, I have been mostly working on
 548 <a href="https://github.com/petterreinholdtsen/noark5-tester">the API
 549 tester</a> so far, while getting to know the code base.  The API
 550 tester currently use
 551 <a href="https://en.wikipedia.org/wiki/HATEOAS">the HATEOAS links</a>
 552 to traverse the entire exposed service API and verify that the exposed
 553 operations and objects match the specification, as well as trying to
 554 create objects holding metadata and uploading a simple XML file to
 555 store.  The tester has proved very useful for finding flaws in our
 556 implementation, as well as flaws in the reference site and the
 557 specification.</p>
 558
 559 <p>The test document I uploaded is a summary of all the specification
 560 defects we have collected so far while implementing the web service.
 561 There are several unclear and conflicting parts of the specification,
 562 and we have
 563 <a href="https://github.com/petterreinholdtsen/noark5-tester/tree/master/mangelmelding">started
 564 writing down</a> the questions we get from implementing it.  We use a
 565 format inspired by how <a href="http://www.opengroup.org/austin/">The
 566 Austin Group</a> collect defect reports for the POSIX standard with
 567 <a href="http://www.opengroup.org/austin/mantis.html">their
 568 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> :).
 569
 570 <p>The Nikita project is implemented using Java and Spring, and is
 571 fairly easy to get up and running using Docker containers for those
 572 that want to test the current code base.  The API tester is
 573 implemented in Python.</p>
 574 </div>
 575       <div class="tags">
 576
 577
 578         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>.
 579
 580
 581       </div>
 582     </div>
 583     <div class="padding"></div>
 584
 585     <div class="entry">
 586       <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>
 587       <div class="date"> 9th March 2017</div>
 588       <div class="body"><p>Over the years, administrating thousand of NFS mounting linux
 589 computers at the time, I often needed a way to detect if the machine
 590 was experiencing NFS hang.  If you try to use <tt>df</tt> or look at a
 591 file or directory affected by the hang, the process (and possibly the
 592 shell) will hang too.  So you want to be able to detect this without
 593 risking the detection process getting stuck too.  It has not been
 594 obvious how to do this.  When the hang has lasted a while, it is
 595 possible to find messages like these in dmesg:</p>
 596
 597 <p><blockquote>
 598 nfs: server nfsserver not responding, still trying
 599 <br>nfs: server nfsserver OK
 600 </blockquote></p>
 601
 602 <p>It is hard to know if the hang is still going on, and it is hard to
 603 be sure looking in dmesg is going to work.  If there are lots of other
 604 messages in dmesg the lines might have rotated out of site before they
 605 are noticed.</p>
 606
 607 <p>While reading through the nfs client implementation in linux kernel
 608 code, I came across some statistics that seem to give a way to detect
 609 it.  The om_timeouts sunrpc value in the kernel will increase every
 610 time the above log entry is inserted into dmesg.  And after digging a
 611 bit further, I discovered that this value show up in
 612 /proc/self/mountstats on Linux.</p>
 613
 614 <p>The mountstats content seem to be shared between files using the
 615 same file system context, so it is enough to check one of the
 616 mountstats files to get the state of the mount point for the machine.
 617 I assume this will not show lazy umounted NFS points, nor NFS mount
 618 points in a different process context (ie with a different filesystem
 619 view), but that does not worry me.</p>
 620
 621 <p>The content for a NFS mount point look similar to this:</p>
 622
 623 <p><blockquote><pre>
 624 [...]
 625 device /dev/mapper/Debian-var mounted on /var with fstype ext3
 626 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
 627         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
 628         age:    7863311
 629         caps:   caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
 630         sec:    flavor=1,pseudoflavor=1
 631         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
 632         bytes:  166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
 633         RPC iostats version: 1.0  p/v: 100003/3 (nfs)
 634         xprt:   tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
 635         per-op statistics
 636                 NULL: 0 0 0 0 0 0 0 0
 637              GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
 638              SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
 639               LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
 640               ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
 641             READLINK: 125 125 0 20472 18620 0 1112 1118
 642                 READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
 643                WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
 644               CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
 645                MKDIR: 3680 3680 0 773980 993920 26 23990 24245
 646              SYMLINK: 903 903 0 233428 245488 6 5865 5917
 647                MKNOD: 80 80 0 20148 21760 0 299 304
 648               REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
 649                RMDIR: 3367 3367 0 645112 484848 22 5782 6002
 650               RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
 651                 LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
 652              READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
 653          READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
 654               FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
 655               FSINFO: 2 2 0 232 328 0 1 1
 656             PATHCONF: 1 1 0 116 140 0 0 0
 657               COMMIT: 0 0 0 0 0 0 0 0
 658
 659 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
 660 [...]
 661 </pre></blockquote></p>
 662
 663 <p>The key number to look at is the third number in the per-op list.
 664 It is the number of NFS timeouts experiences per file system
 665 operation.  Here 22 write timeouts and 5 access timeouts.  If these
 666 numbers are increasing, I believe the machine is experiencing NFS
 667 hang.  Unfortunately the timeout value do not start to increase right
 668 away.  The NFS operations need to time out first, and this can take a
 669 while.  The exact timeout value depend on the setup.  For example the
 670 defaults for TCP and UDP mount points are quite different, and the
 671 timeout value is affected by the soft, hard, timeo and retrans NFS
 672 mount options.</p>
 673
 674 <p>The only way I have been able to get working on Debian and RedHat
 675 Enterprise Linux for getting the timeout count is to peek in /proc/.
 676 But according to
 677 <ahref="http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html">Solaris
 678 10 System Administration Guide: Network Services</a>, the 'nfsstat -c'
 679 command can be used to get these timeout values.  But this do not work
 680 on Linux, as far as I can tell.  I
 681 <ahref="http://bugs.debian.org/857043">asked Debian about this</a>,
 682 but have not seen any replies yet.</p>
 683
 684 <p>Is there a better way to figure out if a Linux NFS client is
 685 experiencing NFS hangs?  Is there a way to detect which processes are
 686 affected?  Is there a way to get the NFS mount going quickly once the
 687 network problem causing the NFS hang has been cleared?  I would very
 688 much welcome some clues, as we regularly run into NFS hangs.</p>
 689 </div>
 690       <div class="tags">
 691
 692
 693         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>.
 694
 695
 696       </div>
 697     </div>
 698     <div class="padding"></div>
 699
 700     <div class="entry">
 701       <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>
 702       <div class="date"> 8th March 2017</div>
 703       <div class="body"><p>So the new president in the United States of America claim to be
 704 surprised to discover that he was wiretapped during the election
 705 before he was elected president.  He even claim this must be illegal.
 706 Well, doh, if it is one thing the confirmations from Snowden
 707 documented, it is that the entire population in USA is wiretapped, one
 708 way or another.  Of course the president candidates were wiretapped,
 709 alongside the senators, judges and the rest of the people in USA.</p>
 710
 711 <p>Next, the Federal Bureau of Investigation ask the Department of
 712 Justice to go public rejecting the claims that Donald Trump was
 713 wiretapped illegally.  I fail to see the relevance, given that I am
 714 sure the surveillance industry in USA believe they have all the legal
 715 backing they need to conduct mass surveillance on the entire
 716 world.</p>
 717
 718 <p>There is even the director of the FBI stating that he never saw an
 719 order requesting wiretapping of Donald Trump.  That is not very
 720 surprising, given how the FISA court work, with all its activity being
 721 secret.  Perhaps he only heard about it?</p>
 722
 723 <p>What I find most sad in this story is how Norwegian journalists
 724 present it.  In a news reports the other day in the radio from the
 725 Norwegian National broadcasting Company (NRK), I heard the journalist
 726 claim that 'the FBI denies any wiretapping', while the reality is that
 727 'the FBI denies any illegal wiretapping'.  There is a fundamental and
 728 important difference, and it make me sad that the journalists are
 729 unable to grasp it.</p>
 730
 731 <p><strong>Update 2017-03-13:</strong> Look like
 732 <a href="https://theintercept.com/2017/03/13/rand-paul-is-right-nsa-routinely-monitors-americans-communications-without-warrants/">The
 733 Intercept report that US Senator Rand Paul confirm what I state above</a>.</p>
 734 </div>
 735       <div class="tags">
 736
 737
 738         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>.
 739
 740
 741       </div>
 742     </div>
 743     <div class="padding"></div>
 744
 745     <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>
 746     <div id="sidebar">
 747
 748
 749
 750 <h2>Archive</h2>
 751 <ul>
 752
 753 <li>2017
 754 <ul>
 755
 756 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/01/">January (4)</a></li>
 757
 758 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/02/">February (3)</a></li>
 759
 760 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/03/">March (5)</a></li>
 761
 762 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/04/">April (2)</a></li>
 763
 764 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/06/">June (5)</a></li>
 765
 766 </ul></li>
 767
 768 <li>2016
 769 <ul>
 770
 771 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/01/">January (3)</a></li>
 772
 773 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/02/">February (2)</a></li>
 774
 775 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/03/">March (3)</a></li>
 776
 777 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/04/">April (8)</a></li>
 778
 779 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/05/">May (8)</a></li>
 780
 781 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/06/">June (2)</a></li>
 782
 783 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/07/">July (2)</a></li>
 784
 785 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/08/">August (5)</a></li>
 786
 787 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/09/">September (2)</a></li>
 788
 789 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/10/">October (3)</a></li>
 790
 791 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/11/">November (8)</a></li>
 792
 793 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/12/">December (5)</a></li>
 794
 795 </ul></li>
 796
 797 <li>2015
 798 <ul>
 799
 800 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/01/">January (7)</a></li>
 801
 802 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/02/">February (6)</a></li>
 803
 804 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/03/">March (1)</a></li>
 805
 806 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/04/">April (4)</a></li>
 807
 808 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/05/">May (3)</a></li>
 809
 810 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/06/">June (4)</a></li>
 811
 812 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/07/">July (6)</a></li>
 813
 814 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/08/">August (2)</a></li>
 815
 816 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/09/">September (2)</a></li>
 817
 818 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/10/">October (9)</a></li>
 819
 820 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/11/">November (6)</a></li>
 821
 822 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/12/">December (3)</a></li>
 823
 824 </ul></li>
 825
 826 <li>2014
 827 <ul>
 828
 829 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
 830
 831 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
 832
 833 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
 834
 835 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/04/">April (7)</a></li>
 836
 837 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/05/">May (1)</a></li>
 838
 839 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/06/">June (2)</a></li>
 840
 841 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/07/">July (2)</a></li>
 842
 843 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/08/">August (2)</a></li>
 844
 845 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/09/">September (5)</a></li>
 846
 847 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/10/">October (6)</a></li>
 848
 849 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/11/">November (3)</a></li>
 850
 851 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/12/">December (5)</a></li>
 852
 853 </ul></li>
 854
 855 <li>2013
 856 <ul>
 857
 858 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
 859
 860 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
 861
 862 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
 863
 864 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
 865
 866 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
 867
 868 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
 869
 870 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
 871
 872 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
 873
 874 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
 875
 876 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
 877
 878 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
 879
 880 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
 881
 882 </ul></li>
 883
 884 <li>2012
 885 <ul>
 886
 887 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
 888
 889 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
 890
 891 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
 892
 893 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
 894
 895 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
 896
 897 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
 898
 899 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
 900
 901 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
 902
 903 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
 904
 905 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
 906
 907 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
 908
 909 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
 910
 911 </ul></li>
 912
 913 <li>2011
 914 <ul>
 915
 916 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
 917
 918 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
 919
 920 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
 921
 922 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
 923
 924 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
 925
 926 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
 927
 928 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
 929
 930 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
 931
 932 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
 933
 934 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
 935
 936 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
 937
 938 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
 939
 940 </ul></li>
 941
 942 <li>2010
 943 <ul>
 944
 945 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
 946
 947 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
 948
 949 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
 950
 951 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
 952
 953 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
 954
 955 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
 956
 957 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
 958
 959 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
 960
 961 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
 962
 963 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
 964
 965 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
 966
 967 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
 968
 969 </ul></li>
 970
 971 <li>2009
 972 <ul>
 973
 974 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
 975
 976 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
 977
 978 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
 979
 980 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
 981
 982 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
 983
 984 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
 985
 986 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
 987
 988 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
 989
 990 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
 991
 992 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
 993
 994 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
 995
 996 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
 997
 998 </ul></li>
 999
1000 <li>2008
1001 <ul>
1002
1003 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
1004
1005 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
1006
1007 </ul></li>
1008
1009 </ul>
1010
1011
1012
1013 <h2>Tags</h2>
1014 <ul>
1015
1016  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
1017
1018  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
1019
1020  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
1021
1022  <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
1023
1024  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (9)</a></li>
1025
1026  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (16)</a></li>
1027
1028  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
1029
1030  <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
1031
1032  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (149)</a></li>
1033
1034  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (158)</a></li>
1035
1036  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian-handbook">debian-handbook (3)</a></li>
1037
1038  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
1039
1040  <li><a href="http://people.skolelinux.org/pere/blog/tags/dld">dld (16)</a></li>
1041
1042  <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (24)</a></li>
1043
1044  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
1045
1046  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (349)</a></li>
1047
1048  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
1049
1050  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
1051
1052  <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (30)</a></li>
1053
1054  <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
1055
1056  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (18)</a></li>
1057
1058  <li><a href="http://people.skolelinux.org/pere/blog/tags/h264">h264 (20)</a></li>
1059
1060  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (42)</a></li>
1061
1062  <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (15)</a></li>
1063
1064  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (20)</a></li>
1065
1066  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
1067
1068  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (8)</a></li>
1069
1070  <li><a href="http://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd (2)</a></li>
1071
1072  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1073
1074  <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
1075
1076  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (39)</a></li>
1077
1078  <li><a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (9)</a></li>
1079
1080  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (291)</a></li>
1081
1082  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (189)</a></li>
1083
1084  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (33)</a></li>
1085
1086  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1087
1088  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (64)</a></li>
1089
1090  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (100)</a></li>
1091
1092  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
1093
1094  <li><a href="http://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
1095
1096  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1097
1098  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
1099
1100  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (10)</a></li>
1101
1102  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1103
1104  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (5)</a></li>
1105
1106  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1107
1108  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (53)</a></li>
1109
1110  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1111
1112  <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (5)</a></li>
1113
1114  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (55)</a></li>
1115
1116  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (6)</a></li>
1117
1118  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (11)</a></li>
1119
1120  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (48)</a></li>
1121
1122  <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (3)</a></li>
1123
1124  <li><a href="http://people.skolelinux.org/pere/blog/tags/usenix">usenix (2)</a></li>
1125
1126  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
1127
1128  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (59)</a></li>
1129
1130  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
1131
1132  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (40)</a></li>
1133
1134 </ul>
1135
1136
1137     </div>
1138     <p style="text-align: right">
1139  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
1140 </p>
1141
1142   </body>
1143 </html>