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