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/Public_Trusted_Timestamping_services_for_everyone.html">Public Trusted Timestamping services for everyone</a></div>
  24       <div class="date">25th March 2014</div>
  25       <div class="body"><p>Did you ever need to store logs or other files in a way that would
  26 allow it to be used as evidence in court, and needed a way to
  27 demonstrate without reasonable doubt that the file had not been
  28 changed since it was created?  Or, did you ever need to document that
  29 a given document was received at some point in time, like some
  30 archived document or the answer to an exam, and not changed after it
  31 was received?  The problem in these settings is to remove the need to
  32 trust yourself and your computers, while still being able to prove
  33 that a file is the same as it was at some given time in the past.</p>
  34
  35 <p>A solution to these problems is to have a trusted third party
  36 "stamp" the document and verify that at some given time the document
  37 looked a given way.  Such
  38 <a href="https://en.wikipedia.org/wiki/Notarius">notarius</a> service
  39 have been around for thousands of years, and its digital equivalent is
  40 called a
  41 <a href="http://en.wikipedia.org/wiki/Trusted_timestamping">trusted
  42 timestamping service</a>.  <a href="http://www.ietf.org/">The Internet
  43 Engineering Task Force</a> standardised how such service could work a
  44 few years ago as <a href="http://tools.ietf.org/html/rfc3161">RFC
  45 3161</a>.  The mechanism is simple.  Create a hash of the file in
  46 question, send it to a trusted third party which add a time stamp to
  47 the hash and sign the result with its private key, and send back the
  48 signed hash + timestamp.  Both email, FTP and HTTP can be used to
  49 request such signature, depending on what is provided by the service
  50 used. Anyone with the document and the signature can then verify that
  51 the document matches the signature by creating their own hash and
  52 checking the signature using the trusted third party public key.
  53 There are several commercial services around providing such
  54 timestamping.  A quick search for
  55 "<a href="https://duckduckgo.com/?q=rfc+3161+service">rfc 3161
  56 service</a>" pointed me to at least
  57 <a href="https://www.digistamp.com/technical/how-a-digital-time-stamp-works/">DigiStamp</a>,
  58 <a href="http://www.quovadisglobal.co.uk/CertificateServices/SigningServices/TimeStamp.aspx">Quo
  59 Vadis</a>,
  60 <a href="https://www.globalsign.com/timestamp-service/">Global Sign</a>
  61 and <a href="http://www.globaltrustfinder.com/TSADefault.aspx">Global
  62 Trust Finder</a>.  The system work as long as the private key of the
  63 trusted third party is not compromised.</p>
  64
  65 <p>But as far as I can tell, there are very few public trusted
  66 timestamp services available for everyone.  I've been looking for one
  67 for a while now. But yesterday I found one over at
  68 <a href="https://www.pki.dfn.de/zeitstempeldienst/">Deutches
  69 Forschungsnetz</a> mentioned in
  70 <a href="http://www.d-mueller.de/blog/dealing-with-trusted-timestamps-in-php-rfc-3161/">a
  71 blog by David Müller</a>.  I then found
  72 <a href="http://www.rz.uni-greifswald.de/support/dfn-pki-zertifikate/zeitstempeldienst.html">a
  73 good recipe on how to use the service</a> over at the University of
  74 Greifswald.</p>
  75
  76 <p><a href="http://www.openssl.org/">The OpenSSL library</a> contain
  77 both server and tools to use and set up your own signing service.  See
  78 the ts(1SSL), tsget(1SSL) manual pages for more details.  The
  79 following shell script demonstrate how to extract a signed timestamp
  80 for any file on the disk in a Debian environment:</p>
  81
  82 <p><blockquote><pre>
  83 #!/bin/sh
  84 set -e
  85 url="http://zeitstempel.dfn.de"
  86 caurl="https://pki.pca.dfn.de/global-services-ca/pub/cacert/chain.txt"
  87 reqfile=$(mktemp -t tmp.XXXXXXXXXX.tsq)
  88 resfile=$(mktemp -t tmp.XXXXXXXXXX.tsr)
  89 cafile=chain.txt
  90 if [ ! -f $cafile ] ; then
  91     wget -O $cafile "$caurl"
  92 fi
  93 openssl ts -query -data "$1" -cert | tee "$reqfile" \
  94     | /usr/lib/ssl/misc/tsget -h "$url" -o "$resfile"
  95 openssl ts -reply -in "$resfile" -text 1>&2
  96 openssl ts -verify -data "$1" -in "$resfile" -CAfile "$cafile" 1>&2
  97 base64 < "$resfile"
  98 rm "$reqfile" "$resfile"
  99 </pre></blockquote></p>
 100
 101 <p>The argument to the script is the file to timestamp, and the output
 102 is a base64 encoded version of the signature to STDOUT and details
 103 about the signature to STDERR.  Note that due to
 104 <a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742553">a bug
 105 in the tsget script</a>, you might need to modify the included script
 106 and remove the last line.  Or just write your own HTTP uploader using
 107 curl. :) Now you too can prove and verify that files have not been
 108 changed.</p>
 109
 110 <p>But the Internet need more public trusted timestamp services.
 111 Perhaps something for <a href="http://www.uninett.no/">Uninett</a> or
 112 my work place the <a href="http://www.uio.no/">University of Oslo</a>
 113 to set up?</p>
 114 </div>
 115       <div class="tags">
 116
 117
 118         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>.
 119
 120
 121       </div>
 122     </div>
 123     <div class="padding"></div>
 124
 125     <div class="entry">
 126       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Video_DVD_reader_library___python_dvdvideo___nice_free_software.html">Video DVD reader library / python-dvdvideo - nice free software</a></div>
 127       <div class="date">21st March 2014</div>
 128       <div class="body"><p>Keeping your DVD collection safe from scratches and curious
 129 children fingers while still having it available when you want to see a
 130 movie is not straight forward.  My preferred method at the moment is
 131 to store a full copy of the ISO on a hard drive, and use VLC, Popcorn
 132 Hour or other useful players to view the resulting file.  This way the
 133 subtitles and bonus material are still available and using the ISO is
 134 just like inserting the original DVD record in the DVD player.</p>
 135
 136 <p>Earlier I used dd for taking security copies, but it do not handle
 137 DVDs giving read errors (which are quite a few of them).  I've also
 138 tried using
 139 <a href="http://people.skolelinux.org/pere/blog/Ripping_problematic_DVDs_using_dvdbackup_and_genisoimage.html">dvdbackup
 140 and genisoimage</a>, but these days I use the marvellous python library
 141 and program
 142 <a href="http://bblank.thinkmo.de/blog/new-software-python-dvdvideo">python-dvdvideo</a>
 143 written by Bastian Blank.  It is
 144 <a href="http://packages.qa.debian.org/p/python-dvdvideo.html">in Debian
 145 already</a> and the binary package name is python3-dvdvideo. Instead
 146 of trying to read every block from the DVD, it parses the file
 147 structure and figure out which block on the DVD is actually in used,
 148 and only read those blocks from the DVD.  This work surprisingly well,
 149 and I have been able to almost backup my entire DVD collection using
 150 this method.</p> So far, python-dvdvideo have failed on between 10 and
 151 20 DVDs, which is a small fraction of my collection.  The most common
 152 problem is
 153 <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720831">DVDs
 154 using UTF-16 instead of UTF-8 characters</a>, which according to
 155 Bastian is against the DVD specification (and seem to cause some
 156 players to fail too).  A rarer problem is what seem to be inconsistent
 157 DVD structures, as the python library
 158 <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723079">claim
 159 there is a overlap between objects</a>.  An equally rare problem claim
 160 <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741878">some
 161 value is out of range</a>.  No idea what is going on there.  I wish I
 162 knew enough about the DVD format to fix these, to ensure my movie
 163 collection will stay with me in the future.</p>
 164
 165 <p>So, if you need to keep your DVDs safe, back them up using
 166 python-dvdvideo. :)</p>
 167 </div>
 168       <div class="tags">
 169
 170
 171         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
 172
 173
 174       </div>
 175     </div>
 176     <div class="padding"></div>
 177
 178     <div class="entry">
 179       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Norsk_utgave_av_Alaveteli___WhatDoTheyKnow_p__trappene.html">Norsk utgave av Alaveteli / WhatDoTheyKnow på trappene</a></div>
 180       <div class="date">16th March 2014</div>
 181       <div class="body"><p>Det offentlige Norge har mye kunnskap og informasjon.  Men hvordan
 182 kan en få tilgang til den på en enkel måte?  Takket være et lite
 183 knippe lover og tilhørende forskrifter, blant annet
 184 <a href="http://lovdata.no/dokument/NL/lov/2006-05-19-16">offentlighetsloven</a>,
 185 <a href="http://lovdata.no/dokument/NL/lov/2003-05-09-31">miljøinformasjonsloven</a>
 186 og
 187 <a href="http://lovdata.no/dokument/NL/lov/1967-02-10/">forvaltningsloven</a>
 188 har en rett til å spørre det offentlige og få svar.  Men det finnes
 189 intet offentlig arkiv over hva andre har spurt om, og dermed risikerer en
 190 å måtte forstyrre myndighetene gang på gang for å få tak i samme
 191 informasjonen på nytt.  <a href="http://www.mysociety.org/">Britiske
 192 mySociety</a> har laget tjenesten
 193 <a href="http://www.whatdotheyknow.com/">WhatDoTheyKnow</a> som gjør
 194 noe med dette.  I Storbritannia blir WhatdoTheyKnow brukt i
 195 <a href="http://www.mysociety.org/2011/07/01/whatdotheyknows-share-of-central-government-foi-requests-q2-2011/">ca
 196 15% av alle innsynsforespørsler mot sentraladministrasjonen</a>.
 197 Prosjektet heter <a href="http://www.alaveteli.org/">Alaveteli</A>, og
 198 er takk i bruk en rekke steder etter at løsningen ble generalisert og
 199 gjort mulig å oversette.  Den hjelper borgerne med å be om innsyn,
 200 rådgir ved purringer og klager og lar alle se hvilke henvendelser som
 201 er sendt til det offentlige og hvilke svar som er kommet inn, i et
 202 søkpart arkiv.  Her i Norge holder vi i foreningen NUUG på å få opp en
 203 norsk utgave av Alaveteli, og her trenger vi din hjelp med
 204 oversettelsen.</p>
 205
 206 <p>Så langt er 76 % av Alaveteli oversatt til norsk bokmål, men vi
 207 skulle gjerne vært oppe i 100 % før lansering.  Oversettelsen gjøres
 208 på <a href="https://www.transifex.com/projects/p/alaveteli/">Transifex,
 209 der enhver som registrerer seg</a> og ber om tilgang til
 210 bokmålsoversettelsen får bidra.  Vi har satt opp en test av tjenesten
 211 (som ikke sender epost til det offentlige, kun til oss som holder på å
 212 sette opp tjenesten) på maskinen
 213 <a href="http://alaveteli-dev.nuug.no/">alaveteli-dev.nuug.no</a>, der
 214 en kan se hvordan de oversatte meldingen blir seende ut på nettsiden.
 215 Når tjenesten lanseres vil den hete
 216 <a href="https://www.mimesbrønn.no/">Mimes brønn</a>, etter
 217 visdomskilden som Odin måtte gi øyet sitt for å få drikke i.  Den
 218 nettsiden er er ennå ikke klar til bruk.</p>
 219
 220 <p>Hvis noen vil oversette til nynorsk også, så skal vi finne ut
 221 hvordan vi lager en flerspråklig tjeneste.  Men i første omgang er
 222 fokus på bokmålsoversettelsen, der vi selv har nok peiling til å ha
 223 fått oversatt 76%, men trenger hjelp for å komme helt i mål. :)</p>
 224 </div>
 225       <div class="tags">
 226
 227
 228         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>.
 229
 230
 231       </div>
 232     </div>
 233     <div class="padding"></div>
 234
 235     <div class="entry">
 236       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html">Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</a></div>
 237       <div class="date">14th March 2014</div>
 238       <div class="body"><p>The <a href="https://wiki.debian.org/FreedomBox">Freedombox
 239 project</a> is working on providing the software and hardware for
 240 making it easy for non-technical people to host their data and
 241 communication at home, and being able to communicate with their
 242 friends and family encrypted and away from prying eyes.  It has been
 243 going on for a while, and is slowly progressing towards a new test
 244 release (0.2).</p>
 245
 246 <p>And what day could be better than the Pi day to announce that the
 247 new version will provide "hard drive" / SD card / USB stick images for
 248 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
 249 system), and can also be installed using a Debian installer preseed
 250 file.  The Debian based Freedombox is now based on Debian Jessie,
 251 where most of the needed packages used are already present.  Only one,
 252 the freedombox-setup package, is missing.  To try to build your own
 253 boot image to test the current status, fetch the freedom-maker scripts
 254 and build using
 255 <a href="http://packages.qa.debian.org/vmdebootstrap">vmdebootstrap</a>
 256 with a user with sudo access to become root:
 257
 258 <pre>
 259 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
 260   freedom-maker
 261 sudo apt-get install git vmdebootstrap mercurial python-docutils \
 262   mktorrent extlinux virtualbox qemu-user-static binfmt-support \
 263   u-boot-tools
 264 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
 265 </pre>
 266
 267 <p>Root access is needed to run debootstrap and mount loopback
 268 devices.  See the README for more details on the build. If you do not
 269 want all three images, trim the make line.  But note that thanks to <a
 270 href="https://bugs.debian.org/741407">a race condition in
 271 vmdebootstrap</a>, the build might fail without the patch to the
 272 kpartx call.</p>
 273
 274 <p>If you instead want to install using a Debian CD and the preseed
 275 method, boot a Debian Wheezy ISO and use this boot argument to load
 276 the preseed values:</p>
 277
 278 <pre>
 279 url=<a href="http://www.reinholdtsen.name/freedombox/preseed-jessie.dat">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat</a>
 280 </pre>
 281
 282 <p>But note that due to <a href="https://bugs.debian.org/740673">a
 283 recently introduced bug in apt in Jessie</a>, the installer will
 284 currently hang while setting up APT sources.  Killing the
 285 '<tt>apt-cdrom ident</tt>' process when it hang a few times during the
 286 installation will get the installation going.  This affect all
 287 installations in Jessie, and I expect it will be fixed soon.</p>
 288
 289 Give it a go and let us know how it goes on the mailing list, and help
 290 us get the new release published. :) Please join us on
 291 <a href="irc://irc.debian.org:6667/%23freedombox">IRC (#freedombox on
 292 irc.debian.org)</a> and
 293 <a href="http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss">the
 294 mailing list</a> if you want to help make this vision come true.</p>
 295 </div>
 296       <div class="tags">
 297
 298
 299         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/freedombox">freedombox</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
 300
 301
 302       </div>
 303     </div>
 304     <div class="padding"></div>
 305
 306     <div class="entry">
 307       <div class="title"><a href="http://people.skolelinux.org/pere/blog/How_to_add_extra_storage_servers_in_Debian_Edu___Skolelinux.html">How to add extra storage servers in Debian Edu / Skolelinux</a></div>
 308       <div class="date">12th March 2014</div>
 309       <div class="body"><p>On larger sites, it is useful to use a dedicated storage server for
 310 storing user home directories and data.  The design for handling this
 311 in <a href="http://www.skolelinux.org/">Debian Edu / Skolelinux</a>, is
 312 to update the automount rules in LDAP and let the automount daemon on
 313 the clients take care of the rest.  I was reminded about the need to
 314 document this better when one of the customers of
 315 <a href="http://www.slxdrift.no/">Skolelinux Drift AS</a>, where I am
 316 on the board of directors, asked about how to do this.  The steps to
 317 get this working are the following:</p>
 318
 319 <p><ol>
 320
 321 <li>Add new storage server in DNS.  I use nas-server.intern as the
 322 example host here.</li>
 323
 324 <li>Add automoun LDAP information about this server in LDAP, to allow
 325 all clients to automatically mount it on reqeust.</li>
 326
 327 <li>Add the relevant entries in tjener.intern:/etc/fstab, because
 328 tjener.intern do not use automount to avoid mounting loops.</li>
 329
 330 </ol></p>
 331
 332 <p>DNS entries are added in GOsa², and not described here.  Follow the
 333 <a href="https://wiki.debian.org/DebianEdu/Documentation/Wheezy/GettingStarted">instructions
 334 in the manual</a> (Machine Management with GOsa² in section Getting
 335 started).</p>
 336
 337 <p>Ensure that the NFS export points on the server are exported to the
 338 relevant subnets or machines:</p>
 339
 340 <p><blockquote><pre>
 341 root@tjener:~# showmount -e nas-server
 342 Export list for nas-server:
 343 /storage         10.0.0.0/8
 344 root@tjener:~#
 345 </pre></blockquote></p>
 346
 347 <p>Here everything on the backbone network is granted access to the
 348 /storage export.  With NFSv3 it is slightly better to limit it to
 349 netgroup membership or single IP addresses to have some limits on the
 350 NFS access.</p>
 351
 352 <p>The next step is to update LDAP.  This can not be done using GOsa²,
 353 because it lack a module for automount.  Instead, use ldapvi and add
 354 the required LDAP objects using an editor.</p>
 355
 356 <p><blockquote><pre>
 357 ldapvi --ldap-conf -ZD '(cn=admin)' -b ou=automount,dc=skole,dc=skolelinux,dc=no
 358 </pre></blockquote></p>
 359
 360 <p>When the editor show up, add the following LDAP objects at the
 361 bottom of the document.  The "/&" part in the last LDAP object is a
 362 wild card matching everything the nas-server exports, removing the
 363 need to list individual mount points in LDAP.</p>
 364
 365 <p><blockquote><pre>
 366 add cn=nas-server,ou=auto.skole,ou=automount,dc=skole,dc=skolelinux,dc=no
 367 objectClass: automount
 368 cn: nas-server
 369 automountInformation: -fstype=autofs --timeout=60 ldap:ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no
 370
 371 add ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no
 372 objectClass: top
 373 objectClass: automountMap
 374 ou: auto.nas-server
 375
 376 add cn=/,ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no
 377 objectClass: automount
 378 cn: /
 379 automountInformation: -fstype=nfs,tcp,rsize=32768,wsize=32768,rw,intr,hard,nodev,nosuid,noatime nas-server.intern:/&
 380 </pre></blockquote></p>
 381
 382 <p>The last step to remember is to mount the relevant mount points in
 383 tjener.intern by adding them to /etc/fstab, creating the mount
 384 directories using mkdir and running "mount -a" to mount them.</p>
 385
 386 <p>When this is done, your users should be able to access the files on
 387 the storage server directly by just visiting the
 388 /tjener/nas-server/storage/ directory using any application on any
 389 workstation, LTSP client or LTSP server.</p>
 390 </div>
 391       <div class="tags">
 392
 393
 394         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap</a>.
 395
 396
 397       </div>
 398     </div>
 399     <div class="padding"></div>
 400
 401     <div class="entry">
 402       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Hvordan_b_r_RFC_822_formattert_epost_lagres_i_en_NOARK5_database_.html">Hvordan bør RFC 822-formattert epost lagres i en NOARK5-database?</a></div>
 403       <div class="date"> 7th March 2014</div>
 404       <div class="body"><p>For noen uker siden ble NXCs fri programvarelisenserte
 405 NOARK5-løsning
 406 <a href="http://www.nuug.no/aktiviteter/20140211-noark/">presentert hos
 407 NUUG</a> (video
 408 <a href="https://www.youtube.com/watch?v=JCb_dNS3MHQ">på youtube
 409 foreløbig</a>), og det fikk meg til å titte litt mer på NOARK5,
 410 standarden for arkivhåndtering i det offentlige Norge.  Jeg lurer på
 411 om denne kjernen kan være nyttig i et par av mine prosjekter, og for ett
 412 av dem er det mest aktuelt å lagre epost.  Jeg klarte ikke finne noen
 413 anbefaling om hvordan RFC 822-formattert epost (aka Internett-epost)
 414 burde lagres i NOARK5, selv om jeg vet at noen arkiver tar
 415 PDF-utskrift av eposten med sitt epostprogram og så arkiverer PDF-en
 416 (eller enda værre, tar papirutskrift og lagrer bildet av eposten som
 417 PDF i arkivet).</p>
 418
 419 <p>Det er ikke så mange formater som er akseptert av riksarkivet til
 420 langtidsoppbevaring av offentlige arkiver, og PDF og XML er de mest
 421 aktuelle i så måte.  Det slo meg at det måtte da finnes en eller annen
 422 egnet XML-representasjon og at det kanskje var enighet om hvilken som
 423 burde brukes, så jeg tok mot til meg og spurte
 424 <a href="http://samdok.com/">SAMDOK</a>, en gruppe tilknyttet
 425 arkivverket som ser ut til å jobbe med NOARK-samhandling, om de hadde
 426 noen anbefalinger:
 427
 428 <p><blockquote>
 429 <p>Hei.</p>
 430
 431 <p>Usikker på om dette er riktig forum å ta opp mitt spørsmål, men jeg
 432 lurer på om det er definert en anbefaling om hvordan RFC
 433 822-formatterte epost (aka vanlig Internet-epost) bør lages håndteres
 434 i NOARK5, slik at en bevarer all informasjon i eposten
 435 (f.eks. Received-linjer).  Finnes det en anbefalt XML-mapping ala den
 436 som beskrives på
 437 &lt;URL: <a href="https://www.informit.com/articles/article.aspx?p=32074">https://www.informit.com/articles/article.aspx?p=32074</a> &gt;?  Mitt
 438 mål er at det skal være mulig å lagre eposten i en NOARK5-kjerne og
 439 kunne få ut en identisk formattert kopi av opprinnelig epost ved
 440 behov.</p>
 441 </blockquote></p>
 442
 443 <p>Postmottaker hos SAMDOK mente spørsmålet heller burde stilles
 444 direkte til riksarkivet, og jeg fikk i dag svar derfra formulert av
 445 seniorrådgiver Geir Ivar Tungesvik:</p>
 446
 447 <p><blockquote>
 448 <p>Riksarkivet har ingen anbefalinger når det gjelder konvertering fra
 449 e-post til XML.  Det står arkivskaper fritt å eventuelt definere/bruke
 450 eget format.  Inklusive da - som det spørres om - et format der det er
 451 mulig å re-etablere e-post format ut fra XML-en.  XML (e-post)
 452 dokumenter må være referert i arkivstrukturen, og det må vedlegges et
 453 gyldig XML skjema (.xsd) for XML-filene. Arkivskaper står altså fritt
 454 til å gjøre hva de vil, bare det dokumenteres og det kan dannes et
 455 utrekk ved avlevering til depot.</p>
 456
 457 <p>De obligatoriske kravene i Noark 5 standarden må altså oppfylles -
 458 etter dialog med Riksarkivet i forbindelse med godkjenning. For
 459 offentlige arkiv er det særlig viktig med filene loependeJournal.xml
 460 og offentligJournal.xml. Private arkiv som vil forholde seg til Noark
 461 5 standarden er selvsagt frie til å bruke det som er relevant for dem
 462 av obligatoriske krav.</p>
 463 </blockquote></p>
 464
 465 <p>Det ser dermed ut for meg som om det er et lite behov for å
 466 standardisere XML-lagring av RFC-822-formatterte meldinger.  Noen som
 467 vet om god spesifikasjon i så måte?  I tillegg til den omtalt over,
 468 har jeg kommet over flere aktuelle beskrivelser (søk på "rfc 822
 469 xml", så finner du aktuelle alternativer).</p>
 470
 471 <ul>
 472
 473 <li><a href="http://www.openhealth.org/xmtp/">XML MIME Transformation
 474 protocol (XMTP)</a> fra OpenHealth, sist oppdatert 2001.</li>
 475
 476 <li><a href="https://tools.ietf.org/html/draft-klyne-message-rfc822-xml-03">An
 477 XML format for mail and other messages</a> utkast fra IETF datert
 478 2001.</li>
 479
 480 <li><a href="http://www.informit.com/articles/article.aspx?p=32074">xMail:
 481 E-mail as XML</a> en artikkel fra 2003 som beskriver python-modulen
 482 rfc822 som gir ut XML-representasjon av en RFC 822-formattert epost.</li>
 483
 484 </ul>
 485
 486 <p>Finnes det andre og bedre spesifikasjoner for slik lagring?  Send
 487 meg en epost hvis du har innspill.</p>
 488 </div>
 489       <div class="tags">
 490
 491
 492         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>.
 493
 494
 495       </div>
 496     </div>
 497     <div class="padding"></div>
 498
 499     <div class="entry">
 500       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Lenker_for_2014_02_28.html">Lenker for 2014-02-28</a></div>
 501       <div class="date">28th February 2014</div>
 502       <div class="body"><p>Her er noen lenker til tekster jeg har satt pris på å lese de siste
 503 månedene.  Det er mye om varsleren Edward Snowden, som burde få all
 504 hjelp, støtte og beskyttelse Norge kan stille opp med for å ha satt
 505 totalitær overvåkning på sakskartet, men også endel annet
 506 tankevekkende og interessant.</p>
 507
 508 <ul>
 509
 510 <li>2013-12-21
 511 <a href="http://www.dagbladet.no/2013/12/21/nyheter/thomas_drake/nsa/overvakning/snowden/30925886/">-
 512 NSA tenker som Stasi</a> - Dagbladet.no</li>
 513
 514 <li>2013-12-19 <a href="http://www.dagensit.no/article2732734.ece">-
 515 Staten har ikke rett til å vite alt om deg</a> - DN.no</li>
 516
 517 <li>2013-12-21
 518 <a href="http://www.dagbladet.no/2013/12/21/nyheter/krig_og_konflikter/politikk/utenriks/30961126/">Nye
 519 mål for NSAs spionasje avslørt</a> - Dagbladet.no</li>
 520
 521 <li>2013-12-19
 522 <a href="http://www.dagbladet.no/2013/12/19/nyheter/nsa/usa/politikk/barack_obama/30918684/">«NSA
 523 bør fjernes fra sin makt til å samle inn metadata fra amerikanske
 524 telefonsamtaler»</a> - Dagbladet.no</li>
 525
 526 <li>2013-12-18
 527 <a href="http://www.dagbladet.no/2013/12/18/kultur/meninger/hovedkronikk/debatt/snowden/30901089/">Etterretning,
 528 overvåking, frihet og sikkerhet</a> - Dagbladet.no</li>
 529
 530 <li>2013-12-17
 531 <a href="http://www.nrk.no/verden/snowden-vil-ha-asyl-i-brasil-1.11423444">Snowden
 532 angriper USA i åpent brev</a> - nrk.no</li>
 533
 534 <li>2013-12-17
 535 <a href="http://www.digi.no/925820/rettslig-nederlag-for-etterretning">Rettslig
 536 nederlag for etterretning</a> - digi.no</li>
 537
 538 <li>2013-12-21
 539 <a href="http://www.dagbladet.no/2013/12/21/kultur/meninger/hovedkommentar/kommentar/etterretning/30963284/">Truende
 540 nedkjøling</a> - dagbladet.no</li>
 541
 542 <li>2013-12-20
 543 <a href="http://www.aftenposten.no/viten/Matematikk-og-forstaelse-7411849.html">Matematikk
 544 og forståelse</a> - aftenposten.no</li>
 545
 546 <li>2013-10-20
 547 <a href="http://www.nrk.no/viten/ny-studie_sovn-reinser-hjernen-var-1.11306106">Vi
 548 søv for å reinse hjernen vår, ifølgje ny studie</a> - nrk.no</li>
 549
 550 <li>2013-12-11
 551 <a href="http://www.nrk.no/buskerud/julebaksten-i-vasken-1.11410033">Rotterace
 552 i kloakken</a> - nrk.no</li>
 553
 554 <li>2013-12-30
 555 <a href="http://www.aftenposten.no/viten/Apne-brev-og-frie-tanker-7413734.html">Åpne
 556 brev og frie tanker</a> - aftenposten.no</li>
 557
 558 <li>2014-01-12
 559 <a href="http://www.aftenposten.no/viten/Stopp-kunnskapsapartheidet-7428229.html">Stopp dagens kunnskapsapartheid!</a> - aftenposten.no</li>
 560
 561 <li>2014-01-09
 562 <a href="http://www.aftenposten.no/nyheter/uriks/EU-rapport-Britisk-og-amerikansk-overvaking-ser-ut-til-a-vare-ulovlig-7428933.html">EU-rapport:
 563 Britisk og amerikansk overvåking ser ut til å være ulovlig</a> -
 564 aftenposten.no</li>
 565
 566 <li>2013-10-23 Professor Jan Arild Audestad
 567 <a href="http://www.digi.no/924008/advarer-mot-konspirasjonsteori">Advarer
 568 mot konspirasjonsteori</a> i digi.no og sier han ikke tror NSA kan
 569 avlytte mobiltelefoner, mens han noen måneder senere forteller:</li>
 570
 571 <li>2014-01-09
 572 <a href="http://www.aftenposten.no/nyheter/iriks/--Vi-ble-presset-til-a-svekke-mobilsikkerheten-pa-80-tallet-7410467.html">-
 573 Vi ble presset til å svekke mobilsikkerheten på 80-tallet</a> -
 574 aftenposten.no</li>
 575
 576 <li>2014-02-12
 577 <a href="http://tv.nrk.no/program/koid20005814/et-moete-med-edward-snowden">Et
 578 møte med Edward Snowden</a> - intervju sendt av nrk, tilgjengelig til
 579 2015-01-31</li>
 580
 581 <li>2014-02-17
 582 <a href="http://politiken.dk/debat/profiler/jessteinpedersen/ECE2210356/litteraturredaktoeren-helle-thornings-tavshed-om-snowden-er-en-skandale/">Litteraturredaktøren:
 583 Helle Thornings tavshed om Snowden er en skandale</a> -
 584 politiken.dk</li>
 585
 586 <li>2014-02-21
 587 <a href="http://www.aftenposten.no/meninger/kronikker/Bra-a-ha-en-Storebror-7476734.html">Bra å ha en «Storebror»</a> - aftenposten.no</li>
 588
 589 <li>2014-02-28
 590 <a href="http://johnchristianelden.blogg.no/1393536806_narkotikasiktet_stort.html">"Narkotikasiktet
 591 Stortingsmann" - Spillet bak kulissene</a> - John Christian Eldens
 592 blogg</li>
 593
 594 <li>2014-02-28
 595 <a href="http://www.aftenposten.no/meninger/Heksejakt-pa-hasjbrukere-7486283.html">Heksejakt
 596 på hasjbrukere</a> - aftenposten.no</li>
 597
 598 </ul>
 599 </div>
 600       <div class="tags">
 601
 602
 603         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>.
 604
 605
 606       </div>
 607     </div>
 608     <div class="padding"></div>
 609
 610     <div class="entry">
 611       <div class="title"><a href="http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html">New home and release 1.0 for netgroup and innetgr (aka ng-utils)</a></div>
 612       <div class="date">22nd February 2014</div>
 613       <div class="body"><p>Many years ago, I wrote a GPL licensed version of the netgroup and
 614 innetgr tools, because I needed them in
 615 <a href="http://www.skolelinux.org/">Skolelinux</a>.  I called the project
 616 ng-utils, and it has served me well.  I placed the project under the
 617 <a href="http://www.hungry.com/">Hungry Programmer</a> umbrella, and it was maintained in our CVS
 618 repository.  But many years ago, the CVS repository was dropped (lost,
 619 not migrated to new hardware, not sure), and the project have lacked a
 620 proper home since then.</p>
 621
 622 <p>Last summer, I had a look at the package and made a new release
 623 fixing a irritating crash bug, but was unable to store the changes in
 624 a proper source control system.  I applied for a project on
 625 <a href="https://alioth.debian.org/">Alioth</a>, but did not have time
 626 to follow up on it.  Until today. :)</p>
 627
 628 <p>After many hours of cleaning and migration, the ng-utils project
 629 now have a new home, and a git repository with the highlight of the
 630 history of the project.  I published all release tarballs and imported
 631 them into the git repository.  As the project is really stable and not
 632 expected to gain new features any time soon, I decided to make a new
 633 release and call it 1.0.  Visit the new project home on
 634 <a href="https://alioth.debian.org/projects/ng-utils/">https://alioth.debian.org/projects/ng-utils/</a>
 635 if you want to check it out.  The new version is also uploaded into
 636 <a href="http://packages.qa.debian.org/n/ng-utils.html">Debian Unstable</a>.</p>
 637 </div>
 638       <div class="tags">
 639
 640
 641         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>.
 642
 643
 644       </div>
 645     </div>
 646     <div class="padding"></div>
 647
 648     <div class="entry">
 649       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html">Testing sysvinit from experimental in Debian Hurd</a></div>
 650       <div class="date"> 3rd February 2014</div>
 651       <div class="body"><p>A few days ago I decided to try to help the Hurd people to get
 652 their changes into sysvinit, to allow them to use the normal sysvinit
 653 boot system instead of their old one.  This follow up on the
 654 <a href="https://teythoon.cryptobitch.de//categories/gsoc.html">great
 655 Google Summer of Code work</a> done last summer by Justus Winter to
 656 get Debian on Hurd working more like Debian on Linux.  To get started,
 657 I downloaded a prebuilt hard disk image from
 658 <a href="http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd.img.tar.gz">http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd.img.tar.gz</a>,
 659 and started it using virt-manager.</p>
 660
 661 <p>The first think I had to do after logging in (root without any
 662 password) was to get the network operational.  I followed
 663 <a href="https://www.debian.org/ports/hurd/hurd-install">the
 664 instructions on the Debian GNU/Hurd ports page</a> and ran these
 665 commands as root to get the machine to accept a IP address from the
 666 kvm internal DHCP server:</p>
 667
 668 <p><blockquote><pre>
 669 settrans -fgap /dev/netdde /hurd/netdde
 670 kill $(ps -ef|awk '/[p]finet/ { print $2}')
 671 kill $(ps -ef|awk '/[d]evnode/ { print $2}')
 672 dhclient /dev/eth0
 673 </pre></blockquote></p>
 674
 675 <p>After this, the machine had internet connectivity, and I could
 676 upgrade it and install the sysvinit packages from experimental and
 677 enable it as the default boot system in Hurd.</p>
 678
 679 <p>But before I did that, I set a password on the root user, as ssh is
 680 running on the machine it for ssh login to work a password need to be
 681 set.  Also, note that a bug somewhere in openssh on Hurd block
 682 compression from working.  Remember to turn that off on the client
 683 side.</p>
 684
 685 <p>Run these commands as root to upgrade and test the new sysvinit
 686 stuff:</p>
 687
 688 <p><blockquote><pre>
 689 cat > /etc/apt/sources.list.d/experimental.list &lt;&lt;EOF
 690 deb http://http.debian.net/debian/ experimental main
 691 EOF
 692 apt-get update
 693 apt-get dist-upgrade
 694 apt-get install -t experimental initscripts sysv-rc sysvinit \
 695     sysvinit-core sysvinit-utils
 696 update-alternatives --config runsystem
 697 </pre></blockquote></p>
 698
 699 <p>To reboot after switching boot system, you have to use
 700 <tt>reboot-hurd</tt> instead of just <tt>reboot</tt>, as there is not
 701 yet a sysvinit process able to receive the signals from the normal
 702 'reboot' command.  After switching to sysvinit as the boot system,
 703 upgrading every package and rebooting, the network come up with DHCP
 704 after boot as it should, and the settrans/pkill hack mentioned at the
 705 start is no longer needed.  But for some strange reason, there are no
 706 longer any login prompt in the virtual console, so I logged in using
 707 ssh instead.
 708
 709 <p>Note that there are some race conditions in Hurd making the boot
 710 fail some times.  No idea what the cause is, but hope the Hurd porters
 711 figure it out.  At least Justus said on IRC (#debian-hurd on
 712 irc.debian.org) that they are aware of the problem.  A way to reduce
 713 the impact is to upgrade to the Hurd packages built by Justus by
 714 adding this repository to the machine:</p>
 715
 716 <p><blockquote><pre>
 717 cat > /etc/apt/sources.list.d/hurd-ci.list &lt;&lt;EOF
 718 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
 719 EOF
 720 </pre></blockquote></p>
 721
 722 <p>At the moment the prebuilt virtual machine get some packages from
 723 http://ftp.debian-ports.org/debian, because some of the packages in
 724 unstable do not yet include the required patches that are lingering in
 725 BTS.  This is the completely list of "unofficial" packages installed:</p>
 726
 727 <p><blockquote><pre>
 728 # aptitude search '?narrow(?version(CURRENT),?origin(Debian Ports))'
 729 i   emacs                   - GNU Emacs editor (metapackage)
 730 i   gdb                     - GNU Debugger
 731 i   hurd-recommended        - Miscellaneous translators
 732 i   isc-dhcp-client         - ISC DHCP client
 733 i   isc-dhcp-common         - common files used by all the isc-dhcp* packages
 734 i   libc-bin                - Embedded GNU C Library: Binaries
 735 i   libc-dev-bin            - Embedded GNU C Library: Development binaries
 736 i   libc0.3                 - Embedded GNU C Library: Shared libraries
 737 i A libc0.3-dbg             - Embedded GNU C Library: detached debugging symbols
 738 i   libc0.3-dev             - Embedded GNU C Library: Development Libraries and Hea
 739 i   multiarch-support       - Transitional package to ensure multiarch compatibilit
 740 i A x11-common              - X Window System (X.Org) infrastructure
 741 i   xorg                    - X.Org X Window System
 742 i A xserver-xorg            - X.Org X server
 743 i A xserver-xorg-input-all  - X.Org X server -- input driver metapackage
 744 #
 745 </pre></blockquote></p>
 746
 747 <p>All in all, testing hurd has been an interesting experience. :)
 748 X.org did not work out of the box and I never took the time to follow
 749 the porters instructions to fix it.  This time I was interested in the
 750 command line stuff.<p>
 751 </div>
 752       <div class="tags">
 753
 754
 755         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
 756
 757
 758       </div>
 759     </div>
 760     <div class="padding"></div>
 761
 762     <div class="entry">
 763       <div class="title"><a href="http://people.skolelinux.org/pere/blog/A_fist_full_of_non_anonymous_Bitcoins.html">A fist full of non-anonymous Bitcoins</a></div>
 764       <div class="date">29th January 2014</div>
 765       <div class="body"><p>Bitcoin is a incredible use of peer to peer communication and
 766 encryption, allowing direct and immediate money transfer without any
 767 central control.  It is sometimes claimed to be ideal for illegal
 768 activity, which I believe is quite a long way from the truth.  At least
 769 I would not conduct illegal money transfers using a system where the
 770 details of every transaction are kept forever.  This point is
 771 investigated in
 772 <a href="https://www.usenix.org/publications/login">USENIX ;login:</a>
 773 from December 2013, in the article
 774 "<a href="https://www.usenix.org/system/files/login/articles/03_meiklejohn-online.pdf">A
 775 Fistful of Bitcoins - Characterizing Payments Among Men with No
 776 Names</a>" by Sarah Meiklejohn, Marjori Pomarole,Grant Jordan, Kirill
 777 Levchenko, Damon McCoy, Geoffrey M. Voelker, and Stefan Savage.  They
 778 analyse the transaction log in the Bitcoin system, using it to find
 779 addresses belong to individuals and organisations and follow the flow
 780 of money from both Bitcoin theft and trades on Silk Road to where the
 781 money end up.  This is how they wrap up their article:</p>
 782
 783 <p><blockquote>
 784 <p>"To demonstrate the usefulness of this type of analysis, we turned
 785 our attention to criminal activity. In the Bitcoin economy, criminal
 786 activity can appear in a number of forms, such as dealing drugs on
 787 Silk Road or simply stealing someone else’s bitcoins. We followed the
 788 flow of bitcoins out of Silk Road (in particular, from one notorious
 789 address) and from a number of highly publicized thefts to see whether
 790 we could track the bitcoins to known services. Although some of the
 791 thieves attempted to use sophisticated mixing techniques (or possibly
 792 mix services) to obscure the flow of bitcoins, for the most part
 793 tracking the bitcoins was quite straightforward, and we ultimately saw
 794 large quantities of bitcoins flow to a variety of exchanges directly
 795 from the point of theft (or the withdrawal from Silk Road).</p>
 796
 797 <p>As acknowledged above, following stolen bitcoins to the point at
 798 which they are deposited into an exchange does not in itself identify
 799 the thief; however, it does enable further de-anonymization in the
 800 case in which certain agencies can determine (through, for example,
 801 subpoena power) the real-world owner of the account into which the
 802 stolen bitcoins were deposited.  Because such exchanges seem to serve
 803 as chokepoints into and out of the Bitcoin economy (i.e., there are
 804 few alternative ways to cash out), we conclude that using Bitcoin for
 805 money laundering or other illicit purposes does not (at least at
 806 present) seem to be particularly attractive."</p>
 807 </blockquote><p>
 808
 809 <p>These researches are not the first to analyse the Bitcoin
 810 transaction log.  The 2011 paper
 811 "<a href="http://arxiv.org/abs/1107.4524">An Analysis of Anonymity in
 812 the Bitcoin System</A>" by Fergal Reid and Martin Harrigan is
 813 summarized like this:</p>
 814
 815 <p><blockquote>
 816 "Anonymity in Bitcoin, a peer-to-peer electronic currency system, is a
 817 complicated issue. Within the system, users are identified by
 818 public-keys only. An attacker wishing to de-anonymize its users will
 819 attempt to construct the one-to-many mapping between users and
 820 public-keys and associate information external to the system with the
 821 users. Bitcoin tries to prevent this attack by storing the mapping of
 822 a user to his or her public-keys on that user's node only and by
 823 allowing each user to generate as many public-keys as required. In
 824 this chapter we consider the topological structure of two networks
 825 derived from Bitcoin's public transaction history. We show that the
 826 two networks have a non-trivial topological structure, provide
 827 complementary views of the Bitcoin system and have implications for
 828 anonymity. We combine these structures with external information and
 829 techniques such as context discovery and flow analysis to investigate
 830 an alleged theft of Bitcoins, which, at the time of the theft, had a
 831 market value of approximately half a million U.S. dollars."
 832 </blockquote></p>
 833
 834 <p>I hope these references can help kill the urban myth that Bitcoin
 835 is anonymous.  It isn't really a good fit for illegal activites.  Use
 836 cash if you need to stay anonymous, at least until regular DNA
 837 sampling of notes and coins become the norm. :)</p>
 838
 839 <p>As usual, if you use Bitcoin and want to show your support of my
 840 activities, please send Bitcoin donations to my address
 841 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&label=PetterReinholdtsenBlog">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 842 </div>
 843       <div class="tags">
 844
 845
 846         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin</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/sikkerhet">sikkerhet</a>.
 847
 848
 849       </div>
 850     </div>
 851     <div class="padding"></div>
 852
 853     <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>
 854     <div id="sidebar">
 855
 856
 857
 858 <h2>Archive</h2>
 859 <ul>
 860
 861 <li>2014
 862 <ul>
 863
 864 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
 865
 866 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
 867
 868 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/03/">March (6)</a></li>
 869
 870 </ul></li>
 871
 872 <li>2013
 873 <ul>
 874
 875 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
 876
 877 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
 878
 879 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
 880
 881 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
 882
 883 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
 884
 885 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
 886
 887 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
 888
 889 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
 890
 891 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
 892
 893 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
 894
 895 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
 896
 897 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
 898
 899 </ul></li>
 900
 901 <li>2012
 902 <ul>
 903
 904 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
 905
 906 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
 907
 908 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
 909
 910 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
 911
 912 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
 913
 914 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
 915
 916 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
 917
 918 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
 919
 920 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
 921
 922 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
 923
 924 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
 925
 926 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
 927
 928 </ul></li>
 929
 930 <li>2011
 931 <ul>
 932
 933 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
 934
 935 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
 936
 937 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
 938
 939 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
 940
 941 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
 942
 943 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
 944
 945 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
 946
 947 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
 948
 949 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
 950
 951 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
 952
 953 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
 954
 955 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
 956
 957 </ul></li>
 958
 959 <li>2010
 960 <ul>
 961
 962 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
 963
 964 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
 965
 966 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
 967
 968 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
 969
 970 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
 971
 972 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
 973
 974 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
 975
 976 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
 977
 978 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
 979
 980 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
 981
 982 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
 983
 984 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
 985
 986 </ul></li>
 987
 988 <li>2009
 989 <ul>
 990
 991 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
 992
 993 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
 994
 995 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
 996
 997 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
 998
 999 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
1000
1001 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
1002
1003 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
1004
1005 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
1006
1007 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
1008
1009 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
1010
1011 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
1012
1013 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
1014
1015 </ul></li>
1016
1017 <li>2008
1018 <ul>
1019
1020 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
1021
1022 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
1023
1024 </ul></li>
1025
1026 </ul>
1027
1028
1029
1030 <h2>Tags</h2>
1031 <ul>
1032
1033  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
1034
1035  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
1036
1037  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
1038
1039  <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
1040
1041  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (8)</a></li>
1042
1043  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (14)</a></li>
1044
1045  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
1046
1047  <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
1048
1049  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (95)</a></li>
1050
1051  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (145)</a></li>
1052
1053  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
1054
1055  <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (10)</a></li>
1056
1057  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
1058
1059  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (240)</a></li>
1060
1061  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (21)</a></li>
1062
1063  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
1064
1065  <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (12)</a></li>
1066
1067  <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (6)</a></li>
1068
1069  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (11)</a></li>
1070
1071  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (39)</a></li>
1072
1073  <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (7)</a></li>
1074
1075  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (18)</a></li>
1076
1077  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
1078
1079  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (7)</a></li>
1080
1081  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1082
1083  <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (7)</a></li>
1084
1085  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (26)</a></li>
1086
1087  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (242)</a></li>
1088
1089  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (162)</a></li>
1090
1091  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (11)</a></li>
1092
1093  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1094
1095  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (46)</a></li>
1096
1097  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (69)</a></li>
1098
1099  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
1100
1101  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1102
1103  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (2)</a></li>
1104
1105  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (9)</a></li>
1106
1107  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1108
1109  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
1110
1111  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1112
1113  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (36)</a></li>
1114
1115  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1116
1117  <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (4)</a></li>
1118
1119  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (44)</a></li>
1120
1121  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (3)</a></li>
1122
1123  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (9)</a></li>
1124
1125  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (22)</a></li>
1126
1127  <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (1)</a></li>
1128
1129  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
1130
1131  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (40)</a></li>
1132
1133  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
1134
1135  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (29)</a></li>
1136
1137 </ul>
1138
1139
1140     </div>
1141     <p style="text-align: right">
1142  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
1143 </p>
1144
1145   </body>
1146 </html>