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/Video_DVD_reader_library___python_dvdvideo___nice_free_software.html">Video DVD reader library / python-dvdvideo - nice free software
</a></div>
24 <div class=
"date">21st March
2014</div>
25 <div class=
"body"><p>Keeping your DVD collection safe from scratches and curious
26 children fingers while still having it available when you want to see a
27 movie is not straight forward. My preferred method at the moment is
28 to store a full copy of the ISO on a hard drive, and use VLC, Popcorn
29 Hour or other useful players to view the resulting file. This way the
30 subtitles and bonus material are still available and using the ISO is
31 just like inserting the original DVD record in the DVD player.
</p>
33 <p>Earlier I used dd for taking security copies, but it do not handle
34 DVDs giving read errors (which are quite a few of them). I've also
36 <a href=
"http://people.skolelinux.org/pere/blog/Ripping_problematic_DVDs_using_dvdbackup_and_genisoimage.html">dvdbackup
37 and genisoimage
</a>, but these days I use the marvellous python library
39 <a href=
"http://bblank.thinkmo.de/blog/new-software-python-dvdvideo">python-dvdvideo
</a>
40 written by Bastian Blank. It is
41 <a href
"http://packages.qa.debian.org/p/python-dvdvideo.html">in Debian
42 already
</a> and the binary package name is python3-dvdvideo. Instead
43 of trying to read every block from the DVD, it parses the file
44 structure and figure out which block on the DVD is actually in used,
45 and only read those blocks from the DVD. This work surprisingly well,
46 and I have been able to almost backup my entire DVD collection using
47 this method.
</p> So far, python-dvdvideo have failed on between
10 and
48 20 DVDs, which is a small fraction of my collection. The most common
50 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720831">DVDs
51 using UTF-
16 instead of UTF-
8 characters
</a>, which according to
52 Bastian is against the DVD specification (and seem to cause some
53 players to fail too). A rarer problem is what seem to be inconsistent
54 DVD structures, as the python library
55 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723079">claim
56 there is a overlap between objects
</a>. An equally rare problem claim
57 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741878">some
58 value is out of range
</a>. No idea what is going on there. I wish I
59 knew enough about the DVD format to fix these, to ensure my movie
60 collection will stay with me in the future.
</p>
62 <p>So, if you need to keep your DVDs safe, back them up using
63 python-dvdvideo. :)
</p>
68 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>.
73 <div class=
"padding"></div>
76 <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>
77 <div class=
"date">16th March
2014</div>
78 <div class=
"body"><p>Det offentlige Norge har mye kunnskap og informasjon. Men hvordan
79 kan en få tilgang til den på en enkel måte? Takket være et lite
80 knippe lover og tilhørende forskrifter, blant annet
81 <a href=
"http://lovdata.no/dokument/NL/lov/2006-05-19-16">offentlighetsloven
</a>,
82 <a href=
"http://lovdata.no/dokument/NL/lov/2003-05-09-31">miljøinformasjonsloven
</a>
84 <a href=
"http://lovdata.no/dokument/NL/lov/1967-02-10/">forvaltningsloven
</a>
85 har en rett til å spørre det offentlige og få svar. Men det finnes
86 intet offentlig arkiv over hva andre har spurt om, og dermed risikerer en
87 å måtte forstyrre myndighetene gang på gang for å få tak i samme
88 informasjonen på nytt.
<a href=
"http://www.mysociety.org/">Britiske
89 mySociety
</a> har laget tjenesten
90 <a href=
"http://www.whatdotheyknow.com/">WhatDoTheyKnow
</a> som gjør
91 noe med dette. I Storbritannia blir WhatdoTheyKnow brukt i
92 <a href=
"http://www.mysociety.org/2011/07/01/whatdotheyknows-share-of-central-government-foi-requests-q2-2011/">ca
93 15% av alle innsynsforespørsler mot sentraladministrasjonen
</a>.
94 Prosjektet heter
<a href=
"http://www.alaveteli.org/">Alaveteli
</A>, og
95 er takk i bruk en rekke steder etter at løsningen ble generalisert og
96 gjort mulig å oversette. Den hjelper borgerne med å be om innsyn,
97 rådgir ved purringer og klager og lar alle se hvilke henvendelser som
98 er sendt til det offentlige og hvilke svar som er kommet inn, i et
99 søkpart arkiv. Her i Norge holder vi i foreningen NUUG på å få opp en
100 norsk utgave av Alaveteli, og her trenger vi din hjelp med
103 <p>Så langt er
76 % av Alaveteli oversatt til norsk bokmål, men vi
104 skulle gjerne vært oppe i
100 % før lansering. Oversettelsen gjøres
105 på
<a href=
"https://www.transifex.com/projects/p/alaveteli/">Transifex,
106 der enhver som registrerer seg
</a> og ber om tilgang til
107 bokmålsoversettelsen får bidra. Vi har satt opp en test av tjenesten
108 (som ikke sender epost til det offentlige, kun til oss som holder på å
109 sette opp tjenesten) på maskinen
110 <a href=
"http://alaveteli-dev.nuug.no/">alaveteli-dev.nuug.no
</a>, der
111 en kan se hvordan de oversatte meldingen blir seende ut på nettsiden.
112 Når tjenesten lanseres vil den hete
113 <a href=
"https://www.mimesbrønn.no/">Mimes brønn
</a>, etter
114 visdomskilden som Odin måtte gi øyet sitt for å få drikke i. Den
115 nettsiden er er ennå ikke klar til bruk.
</p>
117 <p>Hvis noen vil oversette til nynorsk også, så skal vi finne ut
118 hvordan vi lager en flerspråklig tjeneste. Men i første omgang er
119 fokus på bokmålsoversettelsen, der vi selv har nok peiling til å ha
120 fått oversatt
76%, men trenger hjelp for å komme helt i mål. :)
</p>
125 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>.
130 <div class=
"padding"></div>
133 <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>
134 <div class=
"date">14th March
2014</div>
135 <div class=
"body"><p>The
<a href=
"https://wiki.debian.org/FreedomBox">Freedombox
136 project
</a> is working on providing the software and hardware for
137 making it easy for non-technical people to host their data and
138 communication at home, and being able to communicate with their
139 friends and family encrypted and away from prying eyes. It has been
140 going on for a while, and is slowly progressing towards a new test
143 <p>And what day could be better than the Pi day to announce that the
144 new version will provide "hard drive" / SD card / USB stick images for
145 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
146 system), and can also be installed using a Debian installer preseed
147 file. The Debian based Freedombox is now based on Debian Jessie,
148 where most of the needed packages used are already present. Only one,
149 the freedombox-setup package, is missing. To try to build your own
150 boot image to test the current status, fetch the freedom-maker scripts
152 <a href=
"http://packages.qa.debian.org/vmdebootstrap">vmdebootstrap
</a>
153 with a user with sudo access to become root:
156 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
158 sudo apt-get install git vmdebootstrap mercurial python-docutils \
159 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
161 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
164 <p>Root access is needed to run debootstrap and mount loopback
165 devices. See the README for more details on the build. If you do not
166 want all three images, trim the make line. But note that thanks to
<a
167 href=
"https://bugs.debian.org/741407">a race condition in
168 vmdebootstrap
</a>, the build might fail without the patch to the
171 <p>If you instead want to install using a Debian CD and the preseed
172 method, boot a Debian Wheezy ISO and use this boot argument to load
173 the preseed values:
</p>
176 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a>
179 <p>But note that due to
<a href=
"https://bugs.debian.org/740673">a
180 recently introduced bug in apt in Jessie
</a>, the installer will
181 currently hang while setting up APT sources. Killing the
182 '
<tt>apt-cdrom ident
</tt>' process when it hang a few times during the
183 installation will get the installation going. This affect all
184 installations in Jessie, and I expect it will be fixed soon.
</p>
186 Give it a go and let us know how it goes on the mailing list, and help
187 us get the new release published. :) Please join us on
188 <a href=
"irc://irc.debian.org:6667/%23freedombox">IRC (#freedombox on
189 irc.debian.org)
</a> and
190 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss">the
191 mailing list
</a> if you want to help make this vision come true.
</p>
196 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>.
201 <div class=
"padding"></div>
204 <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>
205 <div class=
"date">12th March
2014</div>
206 <div class=
"body"><p>On larger sites, it is useful to use a dedicated storage server for
207 storing user home directories and data. The design for handling this
208 in
<a href=
"http://www.skolelinux.org/">Debian Edu / Skolelinux
</a>, is
209 to update the automount rules in LDAP and let the automount daemon on
210 the clients take care of the rest. I was reminded about the need to
211 document this better when one of the customers of
212 <a href=
"http://www.slxdrift.no/">Skolelinux Drift AS
</a>, where I am
213 on the board of directors, asked about how to do this. The steps to
214 get this working are the following:
</p>
218 <li>Add new storage server in DNS. I use nas-server.intern as the
219 example host here.
</li>
221 <li>Add automoun LDAP information about this server in LDAP, to allow
222 all clients to automatically mount it on reqeust.
</li>
224 <li>Add the relevant entries in tjener.intern:/etc/fstab, because
225 tjener.intern do not use automount to avoid mounting loops.
</li>
229 <p>DNS entries are added in GOsa², and not described here. Follow the
230 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/GettingStarted">instructions
231 in the manual
</a> (Machine Management with GOsa² in section Getting
234 <p>Ensure that the NFS export points on the server are exported to the
235 relevant subnets or machines:
</p>
238 root@tjener:~# showmount -e nas-server
239 Export list for nas-server:
242 </pre></blockquote></p>
244 <p>Here everything on the backbone network is granted access to the
245 /storage export. With NFSv3 it is slightly better to limit it to
246 netgroup membership or single IP addresses to have some limits on the
249 <p>The next step is to update LDAP. This can not be done using GOsa²,
250 because it lack a module for automount. Instead, use ldapvi and add
251 the required LDAP objects using an editor.
</p>
254 ldapvi --ldap-conf -ZD '(cn=admin)' -b ou=automount,dc=skole,dc=skolelinux,dc=no
255 </pre></blockquote></p>
257 <p>When the editor show up, add the following LDAP objects at the
258 bottom of the document. The "/&" part in the last LDAP object is a
259 wild card matching everything the nas-server exports, removing the
260 need to list individual mount points in LDAP.
</p>
263 add cn=nas-server,ou=auto.skole,ou=automount,dc=skole,dc=skolelinux,dc=no
264 objectClass: automount
266 automountInformation: -fstype=autofs --timeout=
60 ldap:ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no
268 add ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no
270 objectClass: automountMap
273 add cn=/,ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no
274 objectClass: automount
276 automountInformation: -fstype=nfs,tcp,rsize=
32768,wsize=
32768,rw,intr,hard,nodev,nosuid,noatime nas-server.intern:/&
277 </pre></blockquote></p>
279 <p>The last step to remember is to mount the relevant mount points in
280 tjener.intern by adding them to /etc/fstab, creating the mount
281 directories using mkdir and running "mount -a" to mount them.
</p>
283 <p>When this is done, your users should be able to access the files on
284 the storage server directly by just visiting the
285 /tjener/nas-server/storage/ directory using any application on any
286 workstation, LTSP client or LTSP server.
</p>
291 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>.
296 <div class=
"padding"></div>
299 <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>
300 <div class=
"date"> 7th March
2014</div>
301 <div class=
"body"><p>For noen uker siden ble NXCs fri programvarelisenserte
303 <a href=
"http://www.nuug.no/aktiviteter/20140211-noark/">presentert hos
305 <a href=
"https://www.youtube.com/watch?v=JCb_dNS3MHQ">på youtube
306 foreløbig
</a>), og det fikk meg til å titte litt mer på NOARK5,
307 standarden for arkivhåndtering i det offentlige Norge. Jeg lurer på
308 om denne kjernen kan være nyttig i et par av mine prosjekter, og for ett
309 av dem er det mest aktuelt å lagre epost. Jeg klarte ikke finne noen
310 anbefaling om hvordan RFC
822-formattert epost (aka Internett-epost)
311 burde lagres i NOARK5, selv om jeg vet at noen arkiver tar
312 PDF-utskrift av eposten med sitt epostprogram og så arkiverer PDF-en
313 (eller enda værre, tar papirutskrift og lagrer bildet av eposten som
316 <p>Det er ikke så mange formater som er akseptert av riksarkivet til
317 langtidsoppbevaring av offentlige arkiver, og PDF og XML er de mest
318 aktuelle i så måte. Det slo meg at det måtte da finnes en eller annen
319 egnet XML-representasjon og at det kanskje var enighet om hvilken som
320 burde brukes, så jeg tok mot til meg og spurte
321 <a href=
"http://samdok.com/">SAMDOK
</a>, en gruppe tilknyttet
322 arkivverket som ser ut til å jobbe med NOARK-samhandling, om de hadde
328 <p>Usikker på om dette er riktig forum å ta opp mitt spørsmål, men jeg
329 lurer på om det er definert en anbefaling om hvordan RFC
330 822-formatterte epost (aka vanlig Internet-epost) bør lages håndteres
331 i NOARK5, slik at en bevarer all informasjon i eposten
332 (f.eks. Received-linjer). Finnes det en anbefalt XML-mapping ala den
334 <URL:
<a href=
"https://www.informit.com/articles/article.aspx?p=32074">https://www.informit.com/articles/article.aspx?p=
32074</a> >? Mitt
335 mål er at det skal være mulig å lagre eposten i en NOARK5-kjerne og
336 kunne få ut en identisk formattert kopi av opprinnelig epost ved
340 <p>Postmottaker hos SAMDOK mente spørsmålet heller burde stilles
341 direkte til riksarkivet, og jeg fikk i dag svar derfra formulert av
342 seniorrådgiver Geir Ivar Tungesvik:
</p>
345 <p>Riksarkivet har ingen anbefalinger når det gjelder konvertering fra
346 e-post til XML. Det står arkivskaper fritt å eventuelt definere/bruke
347 eget format. Inklusive da - som det spørres om - et format der det er
348 mulig å re-etablere e-post format ut fra XML-en. XML (e-post)
349 dokumenter må være referert i arkivstrukturen, og det må vedlegges et
350 gyldig XML skjema (.xsd) for XML-filene. Arkivskaper står altså fritt
351 til å gjøre hva de vil, bare det dokumenteres og det kan dannes et
352 utrekk ved avlevering til depot.
</p>
354 <p>De obligatoriske kravene i Noark
5 standarden må altså oppfylles -
355 etter dialog med Riksarkivet i forbindelse med godkjenning. For
356 offentlige arkiv er det særlig viktig med filene loependeJournal.xml
357 og offentligJournal.xml. Private arkiv som vil forholde seg til Noark
358 5 standarden er selvsagt frie til å bruke det som er relevant for dem
359 av obligatoriske krav.
</p>
362 <p>Det ser dermed ut for meg som om det er et lite behov for å
363 standardisere XML-lagring av RFC-
822-formatterte meldinger. Noen som
364 vet om god spesifikasjon i så måte? I tillegg til den omtalt over,
365 har jeg kommet over flere aktuelle beskrivelser (søk på "rfc
822
366 xml", så finner du aktuelle alternativer).
</p>
370 <li><a href=
"http://www.openhealth.org/xmtp/">XML MIME Transformation
371 protocol (XMTP)
</a> fra OpenHealth, sist oppdatert
2001.
</li>
373 <li><a href=
"https://tools.ietf.org/html/draft-klyne-message-rfc822-xml-03">An
374 XML format for mail and other messages
</a> utkast fra IETF datert
377 <li><a href=
"http://www.informit.com/articles/article.aspx?p=32074">xMail:
378 E-mail as XML
</a> en artikkel fra
2003 som beskriver python-modulen
379 rfc822 som gir ut XML-representasjon av en RFC
822-formattert epost.
</li>
383 <p>Finnes det andre og bedre spesifikasjoner for slik lagring? Send
384 meg en epost hvis du har innspill.
</p>
389 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>.
394 <div class=
"padding"></div>
397 <div class=
"title"><a href=
"http://people.skolelinux.org/pere/blog/Lenker_for_2014_02_28.html">Lenker for
2014-
02-
28</a></div>
398 <div class=
"date">28th February
2014</div>
399 <div class=
"body"><p>Her er noen lenker til tekster jeg har satt pris på å lese de siste
400 månedene. Det er mye om varsleren Edward Snowden, som burde få all
401 hjelp, støtte og beskyttelse Norge kan stille opp med for å ha satt
402 totalitær overvåkning på sakskartet, men også endel annet
403 tankevekkende og interessant.
</p>
408 <a href=
"http://www.dagbladet.no/2013/12/21/nyheter/thomas_drake/nsa/overvakning/snowden/30925886/">-
409 NSA tenker som Stasi
</a> - Dagbladet.no
</li>
411 <li>2013-
12-
19 <a href=
"http://www.dagensit.no/article2732734.ece">-
412 Staten har ikke rett til å vite alt om deg
</a> - DN.no
</li>
415 <a href=
"http://www.dagbladet.no/2013/12/21/nyheter/krig_og_konflikter/politikk/utenriks/30961126/">Nye
416 mål for NSAs spionasje avslørt
</a> - Dagbladet.no
</li>
419 <a href=
"http://www.dagbladet.no/2013/12/19/nyheter/nsa/usa/politikk/barack_obama/30918684/">«NSA
420 bør fjernes fra sin makt til å samle inn metadata fra amerikanske
421 telefonsamtaler»
</a> - Dagbladet.no
</li>
424 <a href=
"http://www.dagbladet.no/2013/12/18/kultur/meninger/hovedkronikk/debatt/snowden/30901089/">Etterretning,
425 overvåking, frihet og sikkerhet
</a> - Dagbladet.no
</li>
428 <a href=
"http://www.nrk.no/verden/snowden-vil-ha-asyl-i-brasil-1.11423444">Snowden
429 angriper USA i åpent brev
</a> - nrk.no
</li>
432 <a href=
"http://www.digi.no/925820/rettslig-nederlag-for-etterretning">Rettslig
433 nederlag for etterretning
</a> - digi.no
</li>
436 <a href=
"http://www.dagbladet.no/2013/12/21/kultur/meninger/hovedkommentar/kommentar/etterretning/30963284/">Truende
437 nedkjøling
</a> - dagbladet.no
</li>
440 <a href=
"http://www.aftenposten.no/viten/Matematikk-og-forstaelse-7411849.html">Matematikk
441 og forståelse
</a> - aftenposten.no
</li>
444 <a href=
"http://www.nrk.no/viten/ny-studie_sovn-reinser-hjernen-var-1.11306106">Vi
445 søv for å reinse hjernen vår, ifølgje ny studie
</a> - nrk.no
</li>
448 <a href=
"http://www.nrk.no/buskerud/julebaksten-i-vasken-1.11410033">Rotterace
449 i kloakken
</a> - nrk.no
</li>
452 <a href=
"http://www.aftenposten.no/viten/Apne-brev-og-frie-tanker-7413734.html">Åpne
453 brev og frie tanker
</a> - aftenposten.no
</li>
456 <a href=
"http://www.aftenposten.no/viten/Stopp-kunnskapsapartheidet-7428229.html">Stopp dagens kunnskapsapartheid!
</a> - aftenposten.no
</li>
459 <a href=
"http://www.aftenposten.no/nyheter/uriks/EU-rapport-Britisk-og-amerikansk-overvaking-ser-ut-til-a-vare-ulovlig-7428933.html">EU-rapport:
460 Britisk og amerikansk overvåking ser ut til å være ulovlig
</a> -
463 <li>2013-
10-
23 Professor Jan Arild Audestad
464 <a href=
"http://www.digi.no/924008/advarer-mot-konspirasjonsteori">Advarer
465 mot konspirasjonsteori
</a> i digi.no og sier han ikke tror NSA kan
466 avlytte mobiltelefoner, mens han noen måneder senere forteller:
</li>
469 <a href=
"http://www.aftenposten.no/nyheter/iriks/--Vi-ble-presset-til-a-svekke-mobilsikkerheten-pa-80-tallet-7410467.html">-
470 Vi ble presset til å svekke mobilsikkerheten på
80-tallet
</a> -
474 <a href=
"http://tv.nrk.no/program/koid20005814/et-moete-med-edward-snowden">Et
475 møte med Edward Snowden
</a> - intervju sendt av nrk, tilgjengelig til
479 <a href=
"http://politiken.dk/debat/profiler/jessteinpedersen/ECE2210356/litteraturredaktoeren-helle-thornings-tavshed-om-snowden-er-en-skandale/">Litteraturredaktøren:
480 Helle Thornings tavshed om Snowden er en skandale
</a> -
484 <a href=
"http://www.aftenposten.no/meninger/kronikker/Bra-a-ha-en-Storebror-7476734.html">Bra å ha en «Storebror»
</a> - aftenposten.no
</li>
487 <a href=
"http://johnchristianelden.blogg.no/1393536806_narkotikasiktet_stort.html">"Narkotikasiktet
488 Stortingsmann" - Spillet bak kulissene
</a> - John Christian Eldens
492 <a href=
"http://www.aftenposten.no/meninger/Heksejakt-pa-hasjbrukere-7486283.html">Heksejakt
493 på hasjbrukere
</a> - aftenposten.no
</li>
500 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>.
505 <div class=
"padding"></div>
508 <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>
509 <div class=
"date">22nd February
2014</div>
510 <div class=
"body"><p>Many years ago, I wrote a GPL licensed version of the netgroup and
511 innetgr tools, because I needed them in
512 <a href=
"http://www.skolelinux.org/">Skolelinux
</a>. I called the project
513 ng-utils, and it has served me well. I placed the project under the
514 <a href=
"http://www.hungry.com/">Hungry Programmer
</a> umbrella, and it was maintained in our CVS
515 repository. But many years ago, the CVS repository was dropped (lost,
516 not migrated to new hardware, not sure), and the project have lacked a
517 proper home since then.
</p>
519 <p>Last summer, I had a look at the package and made a new release
520 fixing a irritating crash bug, but was unable to store the changes in
521 a proper source control system. I applied for a project on
522 <a href=
"https://alioth.debian.org/">Alioth
</a>, but did not have time
523 to follow up on it. Until today. :)
</p>
525 <p>After many hours of cleaning and migration, the ng-utils project
526 now have a new home, and a git repository with the highlight of the
527 history of the project. I published all release tarballs and imported
528 them into the git repository. As the project is really stable and not
529 expected to gain new features any time soon, I decided to make a new
530 release and call it
1.0. Visit the new project home on
531 <a href=
"https://alioth.debian.org/projects/ng-utils/">https://alioth.debian.org/projects/ng-utils/
</a>
532 if you want to check it out. The new version is also uploaded into
533 <a href=
"http://packages.qa.debian.org/n/ng-utils.html">Debian Unstable
</a>.
</p>
538 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>.
543 <div class=
"padding"></div>
546 <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>
547 <div class=
"date"> 3rd February
2014</div>
548 <div class=
"body"><p>A few days ago I decided to try to help the Hurd people to get
549 their changes into sysvinit, to allow them to use the normal sysvinit
550 boot system instead of their old one. This follow up on the
551 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html">great
552 Google Summer of Code work
</a> done last summer by Justus Winter to
553 get Debian on Hurd working more like Debian on Linux. To get started,
554 I downloaded a prebuilt hard disk image from
555 <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>,
556 and started it using virt-manager.
</p>
558 <p>The first think I had to do after logging in (root without any
559 password) was to get the network operational. I followed
560 <a href=
"https://www.debian.org/ports/hurd/hurd-install">the
561 instructions on the Debian GNU/Hurd ports page
</a> and ran these
562 commands as root to get the machine to accept a IP address from the
563 kvm internal DHCP server:
</p>
566 settrans -fgap /dev/netdde /hurd/netdde
567 kill $(ps -ef|awk '/[p]finet/ { print $
2}')
568 kill $(ps -ef|awk '/[d]evnode/ { print $
2}')
570 </pre></blockquote></p>
572 <p>After this, the machine had internet connectivity, and I could
573 upgrade it and install the sysvinit packages from experimental and
574 enable it as the default boot system in Hurd.
</p>
576 <p>But before I did that, I set a password on the root user, as ssh is
577 running on the machine it for ssh login to work a password need to be
578 set. Also, note that a bug somewhere in openssh on Hurd block
579 compression from working. Remember to turn that off on the client
582 <p>Run these commands as root to upgrade and test the new sysvinit
586 cat
> /etc/apt/sources.list.d/experimental.list
<<EOF
587 deb http://http.debian.net/debian/ experimental main
591 apt-get install -t experimental initscripts sysv-rc sysvinit \
592 sysvinit-core sysvinit-utils
593 update-alternatives --config runsystem
594 </pre></blockquote></p>
596 <p>To reboot after switching boot system, you have to use
597 <tt>reboot-hurd
</tt> instead of just
<tt>reboot
</tt>, as there is not
598 yet a sysvinit process able to receive the signals from the normal
599 'reboot' command. After switching to sysvinit as the boot system,
600 upgrading every package and rebooting, the network come up with DHCP
601 after boot as it should, and the settrans/pkill hack mentioned at the
602 start is no longer needed. But for some strange reason, there are no
603 longer any login prompt in the virtual console, so I logged in using
606 <p>Note that there are some race conditions in Hurd making the boot
607 fail some times. No idea what the cause is, but hope the Hurd porters
608 figure it out. At least Justus said on IRC (#debian-hurd on
609 irc.debian.org) that they are aware of the problem. A way to reduce
610 the impact is to upgrade to the Hurd packages built by Justus by
611 adding this repository to the machine:
</p>
614 cat
> /etc/apt/sources.list.d/hurd-ci.list
<<EOF
615 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
617 </pre></blockquote></p>
619 <p>At the moment the prebuilt virtual machine get some packages from
620 http://ftp.debian-ports.org/debian, because some of the packages in
621 unstable do not yet include the required patches that are lingering in
622 BTS. This is the completely list of "unofficial" packages installed:
</p>
625 # aptitude search '?narrow(?version(CURRENT),?origin(Debian Ports))'
626 i emacs - GNU Emacs editor (metapackage)
628 i hurd-recommended - Miscellaneous translators
629 i isc-dhcp-client - ISC DHCP client
630 i isc-dhcp-common - common files used by all the isc-dhcp* packages
631 i libc-bin - Embedded GNU C Library: Binaries
632 i libc-dev-bin - Embedded GNU C Library: Development binaries
633 i libc0.3 - Embedded GNU C Library: Shared libraries
634 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
635 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
636 i multiarch-support - Transitional package to ensure multiarch compatibilit
637 i A x11-common - X Window System (X.Org) infrastructure
638 i xorg - X.Org X Window System
639 i A xserver-xorg - X.Org X server
640 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
642 </pre></blockquote></p>
644 <p>All in all, testing hurd has been an interesting experience. :)
645 X.org did not work out of the box and I never took the time to follow
646 the porters instructions to fix it. This time I was interested in the
647 command line stuff.
<p>
652 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>.
657 <div class=
"padding"></div>
660 <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>
661 <div class=
"date">29th January
2014</div>
662 <div class=
"body"><p>Bitcoin is a incredible use of peer to peer communication and
663 encryption, allowing direct and immediate money transfer without any
664 central control. It is sometimes claimed to be ideal for illegal
665 activity, which I believe is quite a long way from the truth. At least
666 I would not conduct illegal money transfers using a system where the
667 details of every transaction are kept forever. This point is
669 <a href=
"https://www.usenix.org/publications/login">USENIX ;login:
</a>
670 from December
2013, in the article
671 "
<a href=
"https://www.usenix.org/system/files/login/articles/03_meiklejohn-online.pdf">A
672 Fistful of Bitcoins - Characterizing Payments Among Men with No
673 Names
</a>" by Sarah Meiklejohn, Marjori Pomarole,Grant Jordan, Kirill
674 Levchenko, Damon McCoy, Geoffrey M. Voelker, and Stefan Savage. They
675 analyse the transaction log in the Bitcoin system, using it to find
676 addresses belong to individuals and organisations and follow the flow
677 of money from both Bitcoin theft and trades on Silk Road to where the
678 money end up. This is how they wrap up their article:</p>
681 <p>"To demonstrate the usefulness of this type of analysis, we turned
682 our attention to criminal activity. In the Bitcoin economy, criminal
683 activity can appear in a number of forms, such as dealing drugs on
684 Silk Road or simply stealing someone else’s bitcoins. We followed the
685 flow of bitcoins out of Silk Road (in particular, from one notorious
686 address) and from a number of highly publicized thefts to see whether
687 we could track the bitcoins to known services. Although some of the
688 thieves attempted to use sophisticated mixing techniques (or possibly
689 mix services) to obscure the flow of bitcoins, for the most part
690 tracking the bitcoins was quite straightforward, and we ultimately saw
691 large quantities of bitcoins flow to a variety of exchanges directly
692 from the point of theft (or the withdrawal from Silk Road).
</p>
694 <p>As acknowledged above, following stolen bitcoins to the point at
695 which they are deposited into an exchange does not in itself identify
696 the thief; however, it does enable further de-anonymization in the
697 case in which certain agencies can determine (through, for example,
698 subpoena power) the real-world owner of the account into which the
699 stolen bitcoins were deposited. Because such exchanges seem to serve
700 as chokepoints into and out of the Bitcoin economy (i.e., there are
701 few alternative ways to cash out), we conclude that using Bitcoin for
702 money laundering or other illicit purposes does not (at least at
703 present) seem to be particularly attractive."
</p>
706 <p>These researches are not the first to analyse the Bitcoin
707 transaction log. The
2011 paper
708 "
<a href=
"http://arxiv.org/abs/1107.4524">An Analysis of Anonymity in
709 the Bitcoin System
</A>" by Fergal Reid and Martin Harrigan is
710 summarized like this:</p>
713 "Anonymity in Bitcoin, a peer-to-peer electronic currency system, is a
714 complicated issue. Within the system, users are identified by
715 public-keys only. An attacker wishing to de-anonymize its users will
716 attempt to construct the one-to-many mapping between users and
717 public-keys and associate information external to the system with the
718 users. Bitcoin tries to prevent this attack by storing the mapping of
719 a user to his or her public-keys on that user's node only and by
720 allowing each user to generate as many public-keys as required. In
721 this chapter we consider the topological structure of two networks
722 derived from Bitcoin's public transaction history. We show that the
723 two networks have a non-trivial topological structure, provide
724 complementary views of the Bitcoin system and have implications for
725 anonymity. We combine these structures with external information and
726 techniques such as context discovery and flow analysis to investigate
727 an alleged theft of Bitcoins, which, at the time of the theft, had a
728 market value of approximately half a million U.S. dollars.
"
731 <p>I hope these references can help kill the urban myth that Bitcoin
732 is anonymous. It isn't really a good fit for illegal activites. Use
733 cash if you need to stay anonymous, at least until regular DNA
734 sampling of notes and coins become the norm. :)</p>
736 <p>As usual, if you use Bitcoin and want to show your support of my
737 activities, please send Bitcoin donations to my address
738 <b><a href="bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
743 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>.
748 <div class="padding
"></div>
751 <div class="title
"><a href="http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
">New chrpath release 0.16</a></div>
752 <div class="date
">14th January 2014</div>
753 <div class="body
"><p><a href="http://www.coverity.com/
">Coverity</a> is a nice tool to
754 find problems in C, C++ and Java code using static source code
755 analysis. It can detect a lot of different problems, and is very
756 useful to find memory and locking bugs in the error handling part of
757 the source. The company behind it provide
758 <a href="https://scan.coverity.com/
">check of free software projects as
759 a community service</a>, and many hundred free software projects are
760 already checked. A few days ago I decided to have a closer look at
761 the Coverity system, and discovered that the
762 <a href="http://www.gnu.org/software/gnash/
">gnash</a> and
763 <a href="http://sourceforge.net/projects/ipmitool/
">ipmitool</a>
764 projects I am involved with was already registered. But these are
765 fairly big, and I would also like to have a small and easy project to
766 check, and decided to <a href="http://scan.coverity.com/projects/
1179">request
767 checking of the chrpath project</a>. It was
768 added to the checker and discovered seven potential defects. Six of
769 these were real, mostly resource "leak" when the program detected an
770 error. Nothing serious, as the resources would be released a fraction
771 of a second later when the program exited because of the error, but it
772 is nice to do it right in case the source of the program some time in
773 the future end up in a library. Having fixed all defects and added
774 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel">a
775 mailing list for the chrpath developers
</a>, I decided it was time to
776 publish a new release. These are the release notes:
</p>
778 <p>New in
0.16 released
2014-
01-
14:
</p>
782 <li>Fixed all minor bugs discovered by Coverity.
</li>
783 <li>Updated config.sub and config.guess from the GNU project.
</li>
784 <li>Mention new project mailing list in the documentation.
</li>
789 <a href=
"https://alioth.debian.org/frs/?group_id=31052">download the
790 new version
0.16 from alioth
</a>. Please let us know via the Alioth
791 project if something is wrong with the new release. The test suite
792 did not discover any old errors, so if you find a new one, please also
793 include a test suite check.
</p>
798 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath
</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>.
803 <div class=
"padding"></div>
805 <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>
816 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/01/">January (
2)
</a></li>
818 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/02/">February (
3)
</a></li>
820 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/03/">March (
5)
</a></li>
827 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/01/">January (
11)
</a></li>
829 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/02/">February (
9)
</a></li>
831 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/03/">March (
9)
</a></li>
833 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/04/">April (
6)
</a></li>
835 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/05/">May (
9)
</a></li>
837 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/06/">June (
10)
</a></li>
839 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/07/">July (
7)
</a></li>
841 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/08/">August (
3)
</a></li>
843 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/09/">September (
5)
</a></li>
845 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/10/">October (
7)
</a></li>
847 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/11/">November (
9)
</a></li>
849 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/12/">December (
3)
</a></li>
856 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/01/">January (
7)
</a></li>
858 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/02/">February (
10)
</a></li>
860 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/03/">March (
17)
</a></li>
862 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/04/">April (
12)
</a></li>
864 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/05/">May (
12)
</a></li>
866 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/06/">June (
20)
</a></li>
868 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/07/">July (
17)
</a></li>
870 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/08/">August (
6)
</a></li>
872 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/09/">September (
9)
</a></li>
874 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/10/">October (
17)
</a></li>
876 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/11/">November (
10)
</a></li>
878 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/12/">December (
7)
</a></li>
885 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/01/">January (
16)
</a></li>
887 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/02/">February (
6)
</a></li>
889 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/03/">March (
6)
</a></li>
891 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/04/">April (
7)
</a></li>
893 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/05/">May (
3)
</a></li>
895 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/06/">June (
2)
</a></li>
897 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/07/">July (
7)
</a></li>
899 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/08/">August (
6)
</a></li>
901 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/09/">September (
4)
</a></li>
903 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/10/">October (
2)
</a></li>
905 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/11/">November (
3)
</a></li>
907 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/12/">December (
1)
</a></li>
914 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/01/">January (
2)
</a></li>
916 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/02/">February (
1)
</a></li>
918 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/03/">March (
3)
</a></li>
920 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/04/">April (
3)
</a></li>
922 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/05/">May (
9)
</a></li>
924 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/06/">June (
14)
</a></li>
926 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/07/">July (
12)
</a></li>
928 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/08/">August (
13)
</a></li>
930 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/09/">September (
7)
</a></li>
932 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/10/">October (
9)
</a></li>
934 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/11/">November (
13)
</a></li>
936 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/12/">December (
12)
</a></li>
943 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/01/">January (
8)
</a></li>
945 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/02/">February (
8)
</a></li>
947 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/03/">March (
12)
</a></li>
949 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/04/">April (
10)
</a></li>
951 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/05/">May (
9)
</a></li>
953 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/06/">June (
3)
</a></li>
955 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/07/">July (
4)
</a></li>
957 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/08/">August (
3)
</a></li>
959 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/09/">September (
1)
</a></li>
961 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/10/">October (
2)
</a></li>
963 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/11/">November (
3)
</a></li>
965 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/12/">December (
3)
</a></li>
972 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2008/11/">November (
5)
</a></li>
974 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2008/12/">December (
7)
</a></li>
985 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (
13)
</a></li>
987 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/amiga">amiga (
1)
</a></li>
989 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/aros">aros (
1)
</a></li>
991 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bankid">bankid (
4)
</a></li>
993 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (
8)
</a></li>
995 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (
14)
</a></li>
997 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bsa">bsa (
2)
</a></li>
999 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (
2)
</a></li>
1001 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian (
95)
</a></li>
1003 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (
145)
</a></li>
1005 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/digistan">digistan (
10)
</a></li>
1007 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/docbook">docbook (
10)
</a></li>
1009 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (
4)
</a></li>
1011 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/english">english (
239)
</a></li>
1013 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (
21)
</a></li>
1015 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (
12)
</a></li>
1017 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (
12)
</a></li>
1019 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (
6)
</a></li>
1021 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (
11)
</a></li>
1023 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/intervju">intervju (
39)
</a></li>
1025 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (
7)
</a></li>
1027 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/kart">kart (
18)
</a></li>
1029 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/ldap">ldap (
9)
</a></li>
1031 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/lenker">lenker (
7)
</a></li>
1033 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (
1)
</a></li>
1035 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (
7)
</a></li>
1037 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (
26)
</a></li>
1039 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/norsk">norsk (
242)
</a></li>
1041 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/nuug">nuug (
162)
</a></li>
1043 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (
11)
</a></li>
1045 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/open311">open311 (
2)
</a></li>
1047 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (
46)
</a></li>
1049 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/personvern">personvern (
69)
</a></li>
1051 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/raid">raid (
1)
</a></li>
1053 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/reprap">reprap (
11)
</a></li>
1055 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/rfid">rfid (
2)
</a></li>
1057 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/robot">robot (
9)
</a></li>
1059 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/rss">rss (
1)
</a></li>
1061 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/ruter">ruter (
4)
</a></li>
1063 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (
2)
</a></li>
1065 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (
35)
</a></li>
1067 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (
4)
</a></li>
1069 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (
4)
</a></li>
1071 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/standard">standard (
44)
</a></li>
1073 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (
3)
</a></li>
1075 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (
9)
</a></li>
1077 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (
22)
</a></li>
1079 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (
1)
</a></li>
1081 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/valg">valg (
8)
</a></li>
1083 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/video">video (
40)
</a></li>
1085 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (
4)
</a></li>
1087 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/web">web (
29)
</a></li>
1093 <p style=
"text-align: right">
1094 Created by
<a href=
"http://steve.org.uk/Software/chronicle">Chronicle v4.6
</a>