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/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html">Simpler recipe on how to make a simple $7 IMSI Catcher using Debian</a></div>
  24       <div class="date"> 9th August 2017</div>
  25       <div class="body"><p>On friday, I came across an interesting article in the Norwegian
  26 web based ICT news magazine digi.no on
  27 <a href="https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-60-kroner-na-kan-mobiler-kartlegges-av-alle/398588">how
  28 to collect the IMSI numbers of nearby cell phones</a> using the cheap
  29 DVB-T software defined radios.  The article refered to instructions
  30 and <a href="https://www.youtube.com/watch?v=UjwgNd_as30">a recipe by
  31 Keld Norman on Youtube on how to make a simple $7 IMSI Catcher</a>, and I decided to test them out.</p>
  32
  33 <p>The instructions said to use Ubuntu, install pip using apt (to
  34 bypass apt), use pip to install pybombs (to bypass both apt and pip),
  35 and the ask pybombs to fetch and build everything you need from
  36 scratch.  I wanted to see if I could do the same on the most recent
  37 Debian packages, but this did not work because pybombs tried to build
  38 stuff that no longer build with the most recent openssl library or
  39 some other version skew problem.  While trying to get this recipe
  40 working, I learned that the apt->pip->pybombs route was a long detour,
  41 and the only piece of software dependency missing in Debian was the
  42 gr-gsm package.  I also found out that the lead upstream developer of
  43 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
  44 Debian packages provided in an Ubuntu PPA repository.  All I needed to
  45 do was to dget the Debian source package and built it.</p>
  46
  47 <p>The IMSI collector is a python script listening for packages on the
  48 loopback network device and printing to the terminal some specific GSM
  49 packages with IMSI numbers in them.  The code is fairly short and easy
  50 to understand.  The reason this work is because gr-gsm include a tool
  51 to read GSM data from a software defined radio like a DVB-T USB stick
  52 and other software defined radios, decode them and inject them into a
  53 network device on your Linux machine (using the loopback device by
  54 default).  This proved to work just fine, and I've been testing the
  55 collector for a few days now.</p>
  56
  57 <p>The updated and simpler recipe is thus to</p>
  58
  59 <ol>
  60
  61 <li>start with a Debian machine running Stretch or newer,</li>
  62
  63 <li>build and install the gr-gsm package available from
  64 <a href="http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/">http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/</a>,</li>
  65
  66 <li>clone the git repostory from <a href="https://github.com/Oros42/IMSI-catcher">https://github.com/Oros42/IMSI-catcher</a>,</li>
  67
  68 <li>run grgsm_livemon and adjust the frequency until the terminal
  69 where it was started is filled with a stream of text (meaning you
  70 found a GSM station).</li>
  71
  72 <li>go into the IMSI-catcher directory and run 'sudo python simple_IMSI-catcher.py' to extract the IMSI numbers.</li>
  73
  74 </ol>
  75
  76 <p>To make it even easier in the future to get this sniffer up and
  77 running, I decided to package
  78 <a href="https://github.com/ptrkrysik/gr-gsm/">the gr-gsm project</a>
  79 for Debian (<a href="https://bugs.debian.org/871055">WNPP
  80 #871055</a>), and the package was uploaded into the NEW queue today.
  81 Luckily the gnuradio maintainer has promised to help me, as I do not
  82 know much about gnuradio stuff yet.</p>
  83
  84 <p>I doubt this "IMSI cacher" is anywhere near as powerfull as
  85 commercial tools like
  86 <a href="https://www.thespyphone.com/portable-imsi-imei-catcher/">The
  87 Spy Phone Portable IMSI / IMEI Catcher</a> or the
  88 <a href="https://en.wikipedia.org/wiki/Stingray_phone_tracker">Harris
  89 Stingray</a>, but I hope the existance of cheap alternatives can make
  90 more people realise how their whereabouts when carrying a cell phone
  91 is easily tracked.  Seeing the data flow on the screen, realizing that
  92 I live close to a police station and knowing that the police is also
  93 wearing cell phones, I wonder how hard it would be for criminals to
  94 track the position of the police officers to discover when there are
  95 police near by, or for foreign military forces to track the location
  96 of the Norwegian military forces, or for anyone to track the location
  97 of government officials...</p>
  98
  99 <p>It is worth noting that the data reported by the IMSI-catcher
 100 script mentioned above is only a fraction of the data broadcasted on
 101 the GSM network.  It will only collect one frequency at the time,
 102 while a typical phone will be using several frequencies, and not all
 103 phones will be using the frequencies tracked by the grgsm_livemod
 104 program.  Also, there is a lot of radio chatter being ignored by the
 105 simple_IMSI-catcher script, which would be collected by extending the
 106 parser code.  I wonder if gr-gsm can be set up to listen to more than
 107 one frequency?</p>
 108 </div>
 109       <div class="tags">
 110
 111
 112         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/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
 113
 114
 115       </div>
 116     </div>
 117     <div class="padding"></div>
 118
 119     <div class="entry">
 120       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html">Norwegian Bokmål edition of Debian Administrator's Handbook is now available</a></div>
 121       <div class="date">25th July 2017</div>
 122       <div class="body"><p align="center"><img align="center" src="http://people.skolelinux.org/pere/blog/images/2017-07-25-debian-handbook-nb-testprint.png"/></p>
 123
 124 <p>I finally received a copy of the Norwegian Bokmål edition of
 125 "<a href="https://debian-handbook.info/">The Debian Administrator's
 126 Handbook</a>".  This test copy arrived in the mail a few days ago, and
 127 I am very happy to hold the result in my hand.   We spent around one and a half year translating it. This paperbook edition
 128 <a href="https://debian-handbook.info/get/#norwegian">is available
 129 from lulu.com</a>.  If you buy it quickly, you save 25% on the list
 130 price.  The book is also available for download in electronic form as
 131 PDF, EPUB and Mobipocket, as can be
 132 <a href="https://debian-handbook.info/browse/nb-NO/stable/">read online
 133 as a web page</a>.</p>
 134
 135 <p>This is the second book I publish (the first was the book
 136 "<a href="http://free-culture.cc/">Free Culture</a>" by Lawrence Lessig
 137 in
 138 <a href="http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html">English</a>,
 139 <a href="http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html">French</a>
 140 and
 141 <a href="http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">Norwegian
 142 Bokmål</a>), and I am very excited to finally wrap up this
 143 project.  I hope
 144 "<a href="http://www.lulu.com/shop/rapha%C3%ABl-hertzog-and-roland-mas/h%C3%A5ndbok-for-debian-administratoren/paperback/product-23262290.html">Håndbok
 145 for Debian-administratoren</a>" will be well received.</p>
 146 </div>
 147       <div class="tags">
 148
 149
 150         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>.
 151
 152
 153       </div>
 154     </div>
 155     <div class="padding"></div>
 156
 157     <div class="entry">
 158       <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>
 159       <div class="date">27th June 2017</div>
 160       <div class="body"><p>Jeg kom over teksten
 161 «<a href="https://freedom-to-tinker.com/2017/06/21/killing-car-privacy-by-federal-mandate/">Killing
 162 car privacy by federal mandate</a>» av Leonid Reyzin på Freedom to
 163 Tinker i dag, og det gleder meg å se en god gjennomgang om hvorfor det
 164 er et urimelig inngrep i privatsfæren å la alle biler kringkaste sin
 165 posisjon og bevegelse via radio.  Det omtalte forslaget basert på
 166 Dedicated Short Range Communication (DSRC) kalles Basic Safety Message
 167 (BSM) i USA og Cooperative Awareness Message (CAM) i Europa, og det
 168 norske Vegvesenet er en av de som ser ut til å kunne tenke seg å
 169 pålegge alle biler å fjerne nok en bit av innbyggernes privatsfære.
 170 Anbefaler alle å lese det som står der.
 171
 172 <p>Mens jeg tittet litt på DSRC på biler i Norge kom jeg over et sitat
 173 jeg synes er illustrativt for hvordan det offentlige Norge håndterer
 174 problemstillinger rundt innbyggernes privatsfære i SINTEF-rapporten
 175 «<a href="https://www.sintef.no/publikasjoner/publikasjon/Download/?pubid=SINTEF+A23933">Informasjonssikkerhet
 176 i AutoPASS-brikker</a>» av Trond Foss:</p>
 177
 178 <p><blockquote>
 179 «Rapporten ser ikke på informasjonssikkerhet knyttet til personlig
 180   integritet.»
 181 </blockquote></p>
 182
 183 <p>Så enkelt kan det tydeligvis gjøres når en vurderer
 184 informasjonssikkerheten.  Det holder vel at folkene på toppen kan si
 185 at «Personvernet er ivaretatt», som jo er den populære intetsigende
 186 frasen som gjør at mange tror enkeltindividers integritet tas vare på.
 187 Sitatet fikk meg til å undres på hvor ofte samme tilnærming, å bare se
 188 bort fra behovet for personlig itegritet, blir valgt når en velger å
 189 legge til rette for nok et inngrep i privatsfæren til personer i
 190 Norge.  Det er jo sjelden det får reaksjoner.  Historien om
 191 reaksjonene på Helse Sør-Østs tjenesteutsetting er jo sørgelig nok et
 192 unntak og toppen av isfjellet, desverre.  Tror jeg fortsatt takker nei
 193 til både AutoPASS og holder meg så langt unna det norske helsevesenet
 194 som jeg kan, inntil de har demonstrert og dokumentert at de verdsetter
 195 individets privatsfære og personlige integritet høyere enn kortsiktig
 196 gevist og samfunnsnytte.</p>
 197 </div>
 198       <div class="tags">
 199
 200
 201         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>.
 202
 203
 204       </div>
 205     </div>
 206     <div class="padding"></div>
 207
 208     <div class="entry">
 209       <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>
 210       <div class="date">12th June 2017</div>
 211       <div class="body"><p>It is pleasing to see that the work we put down in publishing new
 212 editions of the classic <a href="http://www.free-culture.cc/">Free
 213 Culture book</a> by the founder of the Creative Commons movement,
 214 Lawrence Lessig, is still being appreciated.  I had a look at the
 215 latest sales numbers for the paper edition today.  Not too impressive,
 216 but happy to see some buyers still exist.  All the revenue from the
 217 books is sent to the <a href="https://creativecommons.org/">Creative
 218 Commons Corporation</a>, and they receive the largest cut if you buy
 219 directly from Lulu.  Most books are sold via Amazon, with Ingram
 220 second and only a small fraction directly from Lulu.  The ebook
 221 edition is available for free from
 222 <a href="https://github.com/petterreinholdtsen/free-culture-lessig">Github</a>.</p>
 223
 224 <table border="0">
 225 <tr><th rowspan="2" valign="bottom">Title / language</th><th colspan="3">Quantity</th></tr>
 226 <tr><th>2016 jan-jun</th><th>2016 jul-dec</th><th>2017 jan-may</th></tr>
 227
 228 <tr>
 229   <td><a href="http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html">Culture Libre / French</a></td>
 230   <td align="right">3</td>
 231   <td align="right">6</td>
 232   <td align="right">15</td>
 233 </tr>
 234
 235 <tr>
 236   <td><a href="http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">Fri kultur / Norwegian</a></td>
 237   <td align="right">7</td>
 238   <td align="right">1</td>
 239   <td align="right">0</td>
 240 </tr>
 241
 242 <tr>
 243   <td><a href="http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html">Free Culture / English</a></td>
 244   <td align="right">14</td>
 245   <td align="right">27</td>
 246   <td align="right">16</td>
 247 </tr>
 248
 249 <tr>
 250   <td>Total</td>
 251   <td align="right">24</td>
 252   <td align="right">34</td>
 253   <td align="right">31</td>
 254 </tr>
 255
 256 </table>
 257
 258 <p>A bit sad to see the low sales number on the Norwegian edition, and
 259 a bit surprising the English edition still selling so well.</p>
 260
 261 <p>If you would like to translate and publish the book in your native
 262 language, I would be happy to help make it happen.  Please get in
 263 touch.</p>
 264 </div>
 265       <div class="tags">
 266
 267
 268         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>.
 269
 270
 271       </div>
 272     </div>
 273     <div class="padding"></div>
 274
 275     <div class="entry">
 276       <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>
 277       <div class="date">10th June 2017</div>
 278       <div class="body"><p>I am very happy to report that the
 279 <a href="https://github.com/hiOA-ABI/nikita-noark5-core">Nikita Noark 5
 280 core project</a> tagged its second release today.  The free software
 281 solution is an implementation of the Norwegian archive standard Noark
 282 5 used by government offices in Norway.  These were the changes in
 283 version 0.1.1 since version 0.1.0 (from NEWS.md):
 284
 285 <ul>
 286
 287  <li>Continued work on the angularjs GUI, including document upload.</li>
 288  <li>Implemented correspondencepartPerson, correspondencepartUnit and
 289    correspondencepartInternal</li>
 290  <li>Applied for coverity coverage and started submitting code on
 291    regualr basis.</li>
 292  <li>Started fixing bugs reported by coverity</li>
 293  <li>Corrected and completed HATEOAS links to make sure entire API is
 294    available via URLs in _links.</li>
 295  <li>Corrected all relation URLs to use trailing slash.</li>
 296  <li>Add initial support for storing data in ElasticSearch.</li>
 297  <li>Now able to receive and store uploaded files in the archive.</li>
 298  <li>Changed JSON output for object lists to have relations in _links.</li>
 299  <li>Improve JSON output for empty object lists.</li>
 300  <li>Now uses correct MIME type application/vnd.noark5-v4+json.</li>
 301  <li>Added support for docker container images.</li>
 302  <li>Added simple API browser implemented in JavaScript/Angular.</li>
 303  <li>Started on archive client implemented in JavaScript/Angular.</li>
 304  <li>Started on prototype to show the public mail journal.</li>
 305  <li>Improved performance by disabling Sprint FileWatcher.</li>
 306  <li>Added support for 'arkivskaper', 'saksmappe' and 'journalpost'.</li>
 307  <li>Added support for some metadata codelists.</li>
 308  <li>Added support for Cross-origin resource sharing (CORS).</li>
 309  <li>Changed login method from Basic Auth to JSON Web Token (RFC 7519)
 310    style.</li>
 311  <li>Added support for GET-ing ny-* URLs.</li>
 312  <li>Added support for modifying entities using PUT and eTag.</li>
 313  <li>Added support for returning XML output on request.</li>
 314  <li>Removed support for English field and class names, limiting ourself
 315    to the official names.</li>
 316  <li>...</li>
 317
 318 </ul>
 319
 320 <p>If this sound interesting to you, please contact us on IRC (#nikita
 321 on irc.freenode.net) or email
 322 (<a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">nikita-noark
 323 mailing list).</p>
 324 </div>
 325       <div class="tags">
 326
 327
 328         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>.
 329
 330
 331       </div>
 332     </div>
 333     <div class="padding"></div>
 334
 335     <div class="entry">
 336       <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>
 337       <div class="date"> 7th June 2017</div>
 338       <div class="body"><p><em>This is a copy of
 339 <a href="https://lists.nuug.no/pipermail/nikita-noark/2017-June/000297.html">an
 340 email I posted to the nikita-noark mailing list</a>.  Please follow up
 341 there if you would like to discuss this topic.  The background is that
 342 we are making a free software archive system based on the Norwegian
 343 <a href="https://www.arkivverket.no/forvaltning-og-utvikling/regelverk-og-standarder/noark-standarden">Noark
 344 5 standard</a> for government archives.</em></p>
 345
 346 <p>I've been wondering a bit lately how trusted timestamps could be
 347 stored in Noark 5.
 348 <a href="https://en.wikipedia.org/wiki/Trusted_timestamping">Trusted
 349 timestamps</a> can be used to verify that some information
 350 (document/file/checksum/metadata) have not been changed since a
 351 specific time in the past.  This is useful to verify the integrity of
 352 the documents in the archive.</p>
 353
 354 <p>Then it occured to me, perhaps the trusted timestamps could be
 355 stored as dokument variants (ie dokumentobjekt referered to from
 356 dokumentbeskrivelse) with the filename set to the hash it is
 357 stamping?</p>
 358
 359 <p>Given a "dokumentbeskrivelse" with an associated "dokumentobjekt",
 360 a new dokumentobjekt is associated with "dokumentbeskrivelse" with the
 361 same attributes as the stamped dokumentobjekt except these
 362 attributes:</p>
 363
 364 <ul>
 365
 366 <li>format -> "RFC3161"
 367 <li>mimeType -> "application/timestamp-reply"
 368 <li>formatDetaljer -> "&lt;source URL for timestamp service&gt;"
 369 <li>filenavn -> "&lt;sjekksum&gt;.tsr"
 370
 371 </ul>
 372
 373 <p>This assume a service following
 374 <a href="https://tools.ietf.org/html/rfc3161">IETF RFC 3161</a> is
 375 used, which specifiy the given MIME type for replies and the .tsr file
 376 ending for the content of such trusted timestamp.  As far as I can
 377 tell from the Noark 5 specifications, it is OK to have several
 378 variants/renderings of a dokument attached to a given
 379 dokumentbeskrivelse objekt.  It might be stretching it a bit to make
 380 some of these variants represent crypto-signatures useful for
 381 verifying the document integrity instead of representing the dokument
 382 itself.</p>
 383
 384 <p>Using the source of the service in formatDetaljer allow several
 385 timestamping services to be used.  This is useful to spread the risk
 386 of key compromise over several organisations.  It would only be a
 387 problem to trust the timestamps if all of the organisations are
 388 compromised.</p>
 389
 390 <p>The following oneliner on Linux can be used to generate the tsr
 391 file.  $input is the path to the file to checksum, and $sha256 is the
 392 SHA-256 checksum of the file (ie the "<sjekksum>.tsr" value mentioned
 393 above).</p>
 394
 395 <p><blockquote><pre>
 396 openssl ts -query -data "$inputfile" -cert -sha256 -no_nonce \
 397   | curl -s -H "Content-Type: application/timestamp-query" \
 398       --data-binary "@-" http://zeitstempel.dfn.de > $sha256.tsr
 399 </pre></blockquote></p>
 400
 401 <p>To verify the timestamp, you first need to download the public key
 402 of the trusted timestamp service, for example using this command:</p>
 403
 404 <p><blockquote><pre>
 405 wget -O ca-cert.txt \
 406   https://pki.pca.dfn.de/global-services-ca/pub/cacert/chain.txt
 407 </pre></blockquote></p>
 408
 409 <p>Note, the public key should be stored alongside the timestamps in
 410 the archive to make sure it is also available 100 years from now.  It
 411 is probably a good idea to standardise how and were to store such
 412 public keys, to make it easier to find for those trying to verify
 413 documents 100 or 1000 years from now. :)</p>
 414
 415 <p>The verification itself is a simple openssl command:</p>
 416
 417 <p><blockquote><pre>
 418 openssl ts -verify -data $inputfile -in $sha256.tsr \
 419   -CAfile ca-cert.txt -text
 420 </pre></blockquote></p>
 421
 422 <p>Is there any reason this approach would not work?  Is it somehow against
 423 the Noark 5 specification?</p>
 424 </div>
 425       <div class="tags">
 426
 427
 428         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>.
 429
 430
 431       </div>
 432     </div>
 433     <div class="padding"></div>
 434
 435     <div class="entry">
 436       <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>
 437       <div class="date"> 3rd June 2017</div>
 438       <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
 439 melder i dag</a> om feil i eksamensoppgavene for eksamen i politikk og
 440 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
 441 like.  Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
 442 på om den fri oversetterløsningen
 443 <a href="https://www.apertium.org/">Apertium</a> ville gjort en bedre
 444 jobb enn Utdanningsdirektoratet.  Det kan se slik ut.</p>
 445
 446 <p>Her er bokmålsoppgaven fra eksamenen:</p>
 447
 448 <blockquote>
 449 <p>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
 450 rolle og muligheter til å håndtere internasjonale utfordringer, som
 451 for eksempel flykningekrisen.</p>
 452
 453 <p>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
 454 på temaet:</p>
 455 <ol>
 456 <li>Flykningeregnskapet 2016, UNHCR og IDMC
 457 <li>«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
 458 </ol>
 459
 460 </blockquote>
 461
 462 <p>Dette oversetter Apertium slik:</p>
 463
 464 <blockquote>
 465 <p>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
 466 andre aktørar og høve til å handtera internasjonale utfordringar, som
 467 til dømes *flykningekrisen.</p>
 468
 469 <p>Vedleggja er døme på tekster som kan gje relevante perspektiv på
 470 temaet:</p>
 471
 472 <ol>
 473 <li>*Flykningeregnskapet 2016, *UNHCR og *IDMC</li>
 474 <li>«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015</li>
 475 </ol>
 476
 477 </blockquote>
 478
 479 <p>Ord som ikke ble forstått er markert med stjerne (*), og trenger
 480 ekstra språksjekk.  Men ingen ord er forsvunnet, slik det var i
 481 oppgaven elevene fikk presentert på eksamen.  Jeg mistenker dog at
 482 "andre aktørers rolle og muligheter til ..." burde vært oversatt til
 483 "rolla til andre aktørar og deira høve til ..." eller noe slikt, men
 484 det er kanskje flisespikking.  Det understreker vel bare at det alltid
 485 trengs korrekturlesning etter automatisk oversettelse.</p>
 486 </div>
 487       <div class="tags">
 488
 489
 490         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>.
 491
 492
 493       </div>
 494     </div>
 495     <div class="padding"></div>
 496
 497     <div class="entry">
 498       <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>
 499       <div class="date">27th April 2017</div>
 500       <div class="body"><p>I disse dager, med frist 1. mai, har Riksarkivaren ute en høring på
 501 sin forskrift.  Som en kan se er det ikke mye tid igjen før fristen
 502 som går ut på søndag.  Denne forskriften er det som lister opp hvilke
 503 formater det er greit å arkivere i
 504 <a href="http://www.arkivverket.no/arkivverket/Offentleg-forvalting/Noark/Noark-5">Noark
 505 5-løsninger</a> i Norge.</p>
 506
 507 <p>Jeg fant høringsdokumentene hos
 508 <a href="https://www.arkivrad.no/aktuelt/riksarkivarens-forskrift-pa-horing">Norsk
 509 Arkivråd</a> etter å ha blitt tipset på epostlisten til
 510 <a href="https://github.com/hiOA-ABI/nikita-noark5-core">fri
 511 programvareprosjektet Nikita Noark5-Core</a>, som lager et Noark 5
 512 Tjenestegresesnitt.  Jeg er involvert i Nikita-prosjektet og takket
 513 være min interesse for tjenestegrensesnittsprosjektet har jeg lest en
 514 god del Noark 5-relaterte dokumenter, og til min overraskelse oppdaget
 515 at standard epost ikke er på listen over godkjente formater som kan
 516 arkiveres.  Høringen med frist søndag er en glimrende mulighet til å
 517 forsøke å gjøre noe med det.  Jeg holder på med
 518 <a href="https://github.com/petterreinholdtsen/noark5-tester/blob/master/docs/hoering-arkivforskrift.tex">egen
 519 høringsuttalelse</a>, og lurer på om andre er interessert i å støtte
 520 forslaget om å tillate arkivering av epost som epost i arkivet.</p>
 521
 522 <p>Er du igang med å skrive egen høringsuttalelse allerede?  I så fall
 523 kan du jo vurdere å ta med en formulering om epost-lagring. Jeg tror
 524 ikke det trengs så mye.  Her et kort forslag til tekst:</p>
 525
 526 <p><blockquote>
 527
 528   <p>Viser til høring sendt ut 2017-02-17 (Riksarkivarens referanse
 529   2016/9840 HELHJO), og tillater oss å sende inn noen innspill om
 530   revisjon av Forskrift om utfyllende tekniske og arkivfaglige
 531   bestemmelser om behandling av offentlige arkiver (Riksarkivarens
 532   forskrift).</p>
 533
 534   <p>Svært mye av vår kommuikasjon foregår i dag på e-post.  Vi
 535   foreslår derfor at Internett-e-post, slik det er beskrevet i IETF
 536   RFC 5322,
 537   <a href="https://tools.ietf.org/html/rfc5322">https://tools.ietf.org/html/rfc5322</a>. bør
 538   inn som godkjent dokumentformat.  Vi foreslår at forskriftens
 539   oversikt over godkjente dokumentformater ved innlevering i § 5-16
 540   endres til å ta med Internett-e-post.</p>
 541
 542 </blockquote></p>
 543
 544 <p>Som del av arbeidet med tjenestegrensesnitt har vi testet hvordan
 545 epost kan lagres i en Noark 5-struktur, og holder på å skrive et
 546 forslag om hvordan dette kan gjøres som vil bli sendt over til
 547 arkivverket så snart det er ferdig.  De som er interesserte kan
 548 <a href="https://github.com/petterreinholdtsen/noark5-tester/blob/master/docs/epostlagring.md">følge
 549 fremdriften på web</a>.</p>
 550
 551 <p>Oppdatering 2017-04-28: I dag ble høringuttalelsen jeg skrev
 552   <a href="https://www.nuug.no/news/NUUGs_h_ringuttalelse_til_Riksarkivarens_forskrift.shtml">sendt
 553   inn av foreningen NUUG</a>.</p>
 554 </div>
 555       <div class="tags">
 556
 557
 558         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>.
 559
 560
 561       </div>
 562     </div>
 563     <div class="padding"></div>
 564
 565     <div class="entry">
 566       <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>
 567       <div class="date">20th April 2017</div>
 568       <div class="body"><p>Jeg oppdaget i dag at <a href="https://www.oep.no/">nettstedet som
 569 publiserer offentlige postjournaler fra statlige etater</a>, OEP, har
 570 begynt å blokkerer enkelte typer webklienter fra å få tilgang.  Vet
 571 ikke hvor mange det gjelder, men det gjelder i hvert fall libwww-perl
 572 og curl.  For å teste selv, kjør følgende:</p>
 573
 574 <blockquote><pre>
 575 % curl -v -s https://www.oep.no/pub/report.xhtml?reportId=3 2>&1 |grep '< HTTP'
 576 < HTTP/1.1 404 Not Found
 577 % curl -v -s --header 'User-Agent:Opera/12.0' https://www.oep.no/pub/report.xhtml?reportId=3 2>&1 |grep '< HTTP'
 578 < HTTP/1.1 200 OK
 579 %
 580 </pre></blockquote>
 581
 582 <p>Her kan en se at tjenesten gir «404 Not Found» for curl i
 583 standardoppsettet, mens den gir «200 OK» hvis curl hevder å være Opera
 584 versjon 12.0.  Offentlig elektronisk postjournal startet blokkeringen
 585 2017-03-02.</p>
 586
 587 <p>Blokkeringen vil gjøre det litt vanskeligere å maskinelt hente
 588 informasjon fra oep.no.  Kan blokkeringen være gjort for å hindre
 589 automatisert innsamling av informasjon fra OEP, slik Pressens
 590 Offentlighetsutvalg gjorde for å dokumentere hvordan departementene
 591 hindrer innsyn i
 592 <a href="http://presse.no/dette-mener-np/undergraver-offentlighetsloven/">rapporten
 593 «Slik hindrer departementer innsyn» som ble publiserte i januar
 594 2017</a>.  Det virker usannsynlig, da det jo er trivielt å bytte
 595 User-Agent til noe nytt.</p>
 596
 597 <p>Finnes det juridisk grunnlag for det offentlige å diskriminere
 598 webklienter slik det gjøres her?  Der tilgang gis eller ikke alt etter
 599 hva klienten sier at den heter?  Da OEP eies av DIFI og driftes av
 600 Basefarm, finnes det kanskje noen dokumenter sendt mellom disse to
 601 aktørene man kan be om innsyn i for å forstå hva som har skjedd.  Men
 602 <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
 603 til DIFI viser kun to dokumenter</a> det siste året mellom DIFI og
 604 Basefarm.
 605 <a href="https://www.mimesbronn.no/request/blokkering_av_tilgang_til_oep_fo">Mimes brønn neste</a>,
 606 tenker jeg.</p>
 607 </div>
 608       <div class="tags">
 609
 610
 611         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>.
 612
 613
 614       </div>
 615     </div>
 616     <div class="padding"></div>
 617
 618     <div class="entry">
 619       <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>
 620       <div class="date">19th March 2017</div>
 621       <div class="body"><p>The <a href="https://github.com/hiOA-ABI/nikita-noark5-core">Nikita
 622 Noark 5 core project</a> is implementing the Norwegian standard for
 623 keeping an electronic archive of government documents.
 624 <a href="http://www.arkivverket.no/arkivverket/Offentlig-forvaltning/Noark/Noark-5/English-version">The
 625 Noark 5 standard</a> document the requirement for data systems used by
 626 the archives in the Norwegian government, and the Noark 5 web interface
 627 specification document a REST web service for storing, searching and
 628 retrieving documents and metadata in such archive.  I've been involved
 629 in the project since a few weeks before Christmas, when the Norwegian
 630 Unix User Group
 631 <a href="https://www.nuug.no/news/NOARK5_kjerne_som_fri_programvare_f_r_epostliste_hos_NUUG.shtml">announced
 632 it supported the project</a>.  I believe this is an important project,
 633 and hope it can make it possible for the government archives in the
 634 future to use free software to keep the archives we citizens depend
 635 on.  But as I do not hold such archive myself, personally my first use
 636 case is to store and analyse public mail journal metadata published
 637 from the government.  I find it useful to have a clear use case in
 638 mind when developing, to make sure the system scratches one of my
 639 itches.</p>
 640
 641 <p>If you would like to help make sure there is a free software
 642 alternatives for the archives, please join our IRC channel
 643 (<a href="irc://irc.freenode.net/%23nikita"">#nikita on
 644 irc.freenode.net</a>) and
 645 <a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">the
 646 project mailing list</a>.</p>
 647
 648 <p>When I got involved, the web service could store metadata about
 649 documents.  But a few weeks ago, a new milestone was reached when it
 650 became possible to store full text documents too.  Yesterday, I
 651 completed an implementation of a command line tool
 652 <tt>archive-pdf</tt> to upload a PDF file to the archive using this
 653 API.  The tool is very simple at the moment, and find existing
 654 <a href="https://en.wikipedia.org/wiki/Fonds">fonds</a>, series and
 655 files while asking the user to select which one to use if more than
 656 one exist.  Once a file is identified, the PDF is associated with the
 657 file and uploaded, using the title extracted from the PDF itself.  The
 658 process is fairly similar to visiting the archive, opening a cabinet,
 659 locating a file and storing a piece of paper in the archive.  Here is
 660 a test run directly after populating the database with test data using
 661 our API tester:</p>
 662
 663 <p><blockquote><pre>
 664 ~/src//noark5-tester$ ./archive-pdf mangelmelding/mangler.pdf
 665 using arkiv: Title of the test fonds created 2017-03-18T23:49:32.103446
 666 using arkivdel: Title of the test series created 2017-03-18T23:49:32.103446
 667
 668  0 - Title of the test case file created 2017-03-18T23:49:32.103446
 669  1 - Title of the test file created 2017-03-18T23:49:32.103446
 670 Select which mappe you want (or search term): 0
 671 Uploading mangelmelding/mangler.pdf
 672   PDF title: Mangler i spesifikasjonsdokumentet for NOARK 5 Tjenestegrensesnitt
 673   File 2017/1: Title of the test case file created 2017-03-18T23:49:32.103446
 674 ~/src//noark5-tester$
 675 </pre></blockquote></p>
 676
 677 <p>You can see here how the fonds (arkiv) and serie (arkivdel) only had
 678 one option, while the user need to choose which file (mappe) to use
 679 among the two created by the API tester.  The <tt>archive-pdf</tt>
 680 tool can be found in the git repository for the API tester.</p>
 681
 682 <p>In the project, I have been mostly working on
 683 <a href="https://github.com/petterreinholdtsen/noark5-tester">the API
 684 tester</a> so far, while getting to know the code base.  The API
 685 tester currently use
 686 <a href="https://en.wikipedia.org/wiki/HATEOAS">the HATEOAS links</a>
 687 to traverse the entire exposed service API and verify that the exposed
 688 operations and objects match the specification, as well as trying to
 689 create objects holding metadata and uploading a simple XML file to
 690 store.  The tester has proved very useful for finding flaws in our
 691 implementation, as well as flaws in the reference site and the
 692 specification.</p>
 693
 694 <p>The test document I uploaded is a summary of all the specification
 695 defects we have collected so far while implementing the web service.
 696 There are several unclear and conflicting parts of the specification,
 697 and we have
 698 <a href="https://github.com/petterreinholdtsen/noark5-tester/tree/master/mangelmelding">started
 699 writing down</a> the questions we get from implementing it.  We use a
 700 format inspired by how <a href="http://www.opengroup.org/austin/">The
 701 Austin Group</a> collect defect reports for the POSIX standard with
 702 <a href="http://www.opengroup.org/austin/mantis.html">their
 703 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> :).
 704
 705 <p>The Nikita project is implemented using Java and Spring, and is
 706 fairly easy to get up and running using Docker containers for those
 707 that want to test the current code base.  The API tester is
 708 implemented in Python.</p>
 709 </div>
 710       <div class="tags">
 711
 712
 713         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>.
 714
 715
 716       </div>
 717     </div>
 718     <div class="padding"></div>
 719
 720     <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>
 721     <div id="sidebar">
 722
 723
 724
 725 <h2>Archive</h2>
 726 <ul>
 727
 728 <li>2017
 729 <ul>
 730
 731 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/01/">January (4)</a></li>
 732
 733 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/02/">February (3)</a></li>
 734
 735 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/03/">March (5)</a></li>
 736
 737 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/04/">April (2)</a></li>
 738
 739 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/06/">June (5)</a></li>
 740
 741 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/07/">July (1)</a></li>
 742
 743 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/08/">August (1)</a></li>
 744
 745 </ul></li>
 746
 747 <li>2016
 748 <ul>
 749
 750 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/01/">January (3)</a></li>
 751
 752 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/02/">February (2)</a></li>
 753
 754 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/03/">March (3)</a></li>
 755
 756 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/04/">April (8)</a></li>
 757
 758 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/05/">May (8)</a></li>
 759
 760 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/06/">June (2)</a></li>
 761
 762 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/07/">July (2)</a></li>
 763
 764 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/08/">August (5)</a></li>
 765
 766 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/09/">September (2)</a></li>
 767
 768 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/10/">October (3)</a></li>
 769
 770 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/11/">November (8)</a></li>
 771
 772 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/12/">December (5)</a></li>
 773
 774 </ul></li>
 775
 776 <li>2015
 777 <ul>
 778
 779 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/01/">January (7)</a></li>
 780
 781 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/02/">February (6)</a></li>
 782
 783 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/03/">March (1)</a></li>
 784
 785 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/04/">April (4)</a></li>
 786
 787 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/05/">May (3)</a></li>
 788
 789 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/06/">June (4)</a></li>
 790
 791 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/07/">July (6)</a></li>
 792
 793 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/08/">August (2)</a></li>
 794
 795 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/09/">September (2)</a></li>
 796
 797 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/10/">October (9)</a></li>
 798
 799 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/11/">November (6)</a></li>
 800
 801 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/12/">December (3)</a></li>
 802
 803 </ul></li>
 804
 805 <li>2014
 806 <ul>
 807
 808 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
 809
 810 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
 811
 812 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
 813
 814 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/04/">April (7)</a></li>
 815
 816 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/05/">May (1)</a></li>
 817
 818 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/06/">June (2)</a></li>
 819
 820 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/07/">July (2)</a></li>
 821
 822 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/08/">August (2)</a></li>
 823
 824 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/09/">September (5)</a></li>
 825
 826 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/10/">October (6)</a></li>
 827
 828 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/11/">November (3)</a></li>
 829
 830 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/12/">December (5)</a></li>
 831
 832 </ul></li>
 833
 834 <li>2013
 835 <ul>
 836
 837 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
 838
 839 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
 840
 841 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
 842
 843 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
 844
 845 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
 846
 847 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
 848
 849 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
 850
 851 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
 852
 853 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
 854
 855 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
 856
 857 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
 858
 859 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
 860
 861 </ul></li>
 862
 863 <li>2012
 864 <ul>
 865
 866 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
 867
 868 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
 869
 870 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
 871
 872 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
 873
 874 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
 875
 876 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
 877
 878 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
 879
 880 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
 881
 882 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
 883
 884 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
 885
 886 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
 887
 888 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
 889
 890 </ul></li>
 891
 892 <li>2011
 893 <ul>
 894
 895 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
 896
 897 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
 898
 899 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
 900
 901 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
 902
 903 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
 904
 905 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
 906
 907 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
 908
 909 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
 910
 911 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
 912
 913 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
 914
 915 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
 916
 917 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
 918
 919 </ul></li>
 920
 921 <li>2010
 922 <ul>
 923
 924 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
 925
 926 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
 927
 928 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
 929
 930 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
 931
 932 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
 933
 934 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
 935
 936 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
 937
 938 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
 939
 940 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
 941
 942 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
 943
 944 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
 945
 946 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
 947
 948 </ul></li>
 949
 950 <li>2009
 951 <ul>
 952
 953 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
 954
 955 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
 956
 957 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
 958
 959 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
 960
 961 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
 962
 963 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
 964
 965 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
 966
 967 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
 968
 969 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
 970
 971 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
 972
 973 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
 974
 975 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
 976
 977 </ul></li>
 978
 979 <li>2008
 980 <ul>
 981
 982 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
 983
 984 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
 985
 986 </ul></li>
 987
 988 </ul>
 989
 990
 991
 992 <h2>Tags</h2>
 993 <ul>
 994
 995  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
 996
 997  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
 998
 999  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
1000
1001  <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
1002
1003  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (9)</a></li>
1004
1005  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (16)</a></li>
1006
1007  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
1008
1009  <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
1010
1011  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (151)</a></li>
1012
1013  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (158)</a></li>
1014
1015  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian-handbook">debian-handbook (4)</a></li>
1016
1017  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
1018
1019  <li><a href="http://people.skolelinux.org/pere/blog/tags/dld">dld (16)</a></li>
1020
1021  <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (24)</a></li>
1022
1023  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
1024
1025  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (351)</a></li>
1026
1027  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
1028
1029  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
1030
1031  <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (30)</a></li>
1032
1033  <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
1034
1035  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (18)</a></li>
1036
1037  <li><a href="http://people.skolelinux.org/pere/blog/tags/h264">h264 (20)</a></li>
1038
1039  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (42)</a></li>
1040
1041  <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (15)</a></li>
1042
1043  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (20)</a></li>
1044
1045  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
1046
1047  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (8)</a></li>
1048
1049  <li><a href="http://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd (2)</a></li>
1050
1051  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1052
1053  <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
1054
1055  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (39)</a></li>
1056
1057  <li><a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (9)</a></li>
1058
1059  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (291)</a></li>
1060
1061  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (189)</a></li>
1062
1063  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (33)</a></li>
1064
1065  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1066
1067  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (64)</a></li>
1068
1069  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (101)</a></li>
1070
1071  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
1072
1073  <li><a href="http://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
1074
1075  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1076
1077  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
1078
1079  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (10)</a></li>
1080
1081  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1082
1083  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (5)</a></li>
1084
1085  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1086
1087  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (53)</a></li>
1088
1089  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1090
1091  <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (5)</a></li>
1092
1093  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (55)</a></li>
1094
1095  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (6)</a></li>
1096
1097  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (11)</a></li>
1098
1099  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (49)</a></li>
1100
1101  <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (3)</a></li>
1102
1103  <li><a href="http://people.skolelinux.org/pere/blog/tags/usenix">usenix (2)</a></li>
1104
1105  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
1106
1107  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (59)</a></li>
1108
1109  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
1110
1111  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (40)</a></li>
1112
1113 </ul>
1114
1115
1116     </div>
1117     <p style="text-align: right">
1118  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
1119 </p>
1120
1121   </body>
1122 </html>