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/Free_software_archive_system_Nikita_now_able_to_store_documents.html">Free software archive system Nikita now able to store documents
</a></div>
24 <div class=
"date">19th March
2017</div>
25 <div class=
"body"><p>The
<a href=
"https://github.com/hiOA-ABI/nikita-noark5-core">Nikita
26 Noark
5 core project
</a> is implementing the Norwegian standard for
27 keeping an electronic archive of government documents.
28 <a href=
"http://www.arkivverket.no/arkivverket/Offentlig-forvaltning/Noark/Noark-5/English-version">The
29 Noark
5 standard
</a> document the requirement for data systems used by
30 the archives in the Norwegian government, and the Noark
5 web interface
31 specification document a REST web service for storing, searching and
32 retrieving documents and metadata in such archive. I've been involved
33 in the project since a few weeks before Christmas, when the Norwegian
35 <a href=
"https://www.nuug.no/news/NOARK5_kjerne_som_fri_programvare_f_r_epostliste_hos_NUUG.shtml">announced
36 it supported the project
</a>. I believe this is an important project,
37 and hope it can make it possible for the government archives in the
38 future to use free software to keep the archives we citizens depend
39 on. But as I do not hold such archive myself, personally my first use
40 case is to store and analyse public mail journal metadata published
41 from the government. I find it useful to have a clear use case in
42 mind when developing, to make sure the system scratches one of my
45 <p>If you would like to help make sure there is a free software
46 alternatives for the archives, please join our IRC channel
47 (
<a href=
"irc://irc.freenode.net/%23nikita"">#nikita on
48 irc.freenode.net</a>) and
49 <a href="https://lists.nuug.no/mailman/listinfo/nikita-noark
">the
50 project mailing list</a>.</p>
52 <p>When I got involved, the web service could store metadata about
53 documents. But a few weeks ago, a new milestone was reached when it
54 became possible to store full text documents too. Yesterday, I
55 completed an implementation of a command line tool
56 <tt>archive-pdf</tt> to upload a PDF file to the archive using this
57 API. The tool is very simple at the moment, and find existing
58 <a href="https://en.wikipedia.org/wiki/Fonds
">fonds</a>, series and
59 files while asking the user to select which one to use if more than
60 one exist. Once a file is identified, the PDF is associated with the
61 file and uploaded, using the title extracted from the PDF itself. The
62 process is fairly similar to visiting the archive, opening a cabinet,
63 locating a file and storing a piece of paper in the archive. Here is
64 a test run directly after populating the database with test data using
68 ~/src//noark5-tester$ ./archive-pdf mangelmelding/mangler.pdf
69 using arkiv: Title of the test fonds created 2017-03-18T23:49:32.103446
70 using arkivdel: Title of the test series created 2017-03-18T23:49:32.103446
72 0 - Title of the test case file created 2017-03-18T23:49:32.103446
73 1 - Title of the test file created 2017-03-18T23:49:32.103446
74 Select which mappe you want (or search term): 0
75 Uploading mangelmelding/mangler.pdf
76 PDF title: Mangler i spesifikasjonsdokumentet for NOARK 5 Tjenestegrensesnitt
77 File 2017/1: Title of the test case file created 2017-03-18T23:49:32.103446
79 </pre></blockquote></p>
81 <p>You can see here how the fonds (arkiv) and serie (arkivdel) only had
82 one option, while the user need to choose which file (mappe) to use
83 among the two created by the API tester. The <tt>archive-pdf</tt>
84 tool can be found in the git repository for the API tester.</p>
86 <p>In the project, I have been mostly working on
87 <a href="https://github.com/petterreinholdtsen/noark5-tester
">the API
88 tester</a> so far, while getting to know the code base. The API
90 <a href="https://en.wikipedia.org/wiki/HATEOAS
">the HATEOAS links</a>
91 to traverse the entire exposed service API and verify that the exposed
92 operations and objects match the specification, as well as trying to
93 create objects holding metadata and uploading a simple XML file to
94 store. The tester has proved very useful for finding flaws in our
95 implementation, as well as flaws in the reference site and the
98 <p>The test document I uploaded is a summary of all the specification
99 defects we have collected so far while implementing the web service.
100 There are several unclear and conflicting parts of the specification,
102 <a href="https://github.com/petterreinholdtsen/noark5-tester/tree/master/mangelmelding
">started
103 writing down</a> the questions we get from implementing it. We use a
104 format inspired by how <a href="http://www.opengroup.org/austin/
">The
105 Austin Group</a> collect defect reports for the POSIX standard with
106 <a href="http://www.opengroup.org/austin/mantis.html
">their
107 instructions for the MANTIS defect tracker system</a>, in lack of an official way to structure defect reports for Noark 5 (our first submitted defect report was a <a href="https://github.com/petterreinholdtsen/noark5-tester/blob/master/mangelmelding/sendt/
2017-
03-
15-mangel-prosess.md
">request for a procedure for submitting defect reports</a> :).
109 <p>The Nikita project is implemented using Java and Spring, and is
110 fairly easy to get up and running using Docker containers for those
111 that want to test the current code base. The API tester is
112 implemented in Python.</p>
117 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english
">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug
">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn
">offentlig innsyn</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard
">standard</a>.
122 <div class="padding
"></div>
125 <div class="title
"><a href="http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
">Detecting NFS hangs on Linux without hanging yourself...</a></div>
126 <div class="date
"> 9th March 2017</div>
127 <div class="body
"><p>Over the years, administrating thousand of NFS mounting linux
128 computers at the time, I often needed a way to detect if the machine
129 was experiencing NFS hang. If you try to use <tt>df</tt> or look at a
130 file or directory affected by the hang, the process (and possibly the
131 shell) will hang too. So you want to be able to detect this without
132 risking the detection process getting stuck too. It has not been
133 obvious how to do this. When the hang has lasted a while, it is
134 possible to find messages like these in dmesg:</p>
137 nfs: server nfsserver not responding, still trying
138 <br>nfs: server nfsserver OK
141 <p>It is hard to know if the hang is still going on, and it is hard to
142 be sure looking in dmesg is going to work. If there are lots of other
143 messages in dmesg the lines might have rotated out of site before they
146 <p>While reading through the nfs client implementation in linux kernel
147 code, I came across some statistics that seem to give a way to detect
148 it. The om_timeouts sunrpc value in the kernel will increase every
149 time the above log entry is inserted into dmesg. And after digging a
150 bit further, I discovered that this value show up in
151 /proc/self/mountstats on Linux.</p>
153 <p>The mountstats content seem to be shared between files using the
154 same file system context, so it is enough to check one of the
155 mountstats files to get the state of the mount point for the machine.
156 I assume this will not show lazy umounted NFS points, nor NFS mount
157 points in a different process context (ie with a different filesystem
158 view), but that does not worry me.</p>
160 <p>The content for a NFS mount point look similar to this:</p>
164 device /dev/mapper/Debian-var mounted on /var with fstype ext3
165 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
166 opts: rw,vers=3,rsize=65536,wsize=65536,namlen=255,acregmin=3,acregmax=60,acdirmin=30,acdirmax=60,soft,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=129.240.3.145,mountvers=3,mountport=4048,mountproto=udp,local_lock=all
168 caps: caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
169 sec: flavor=1,pseudoflavor=1
170 events: 61063112 732346265 1028140 35486205 16220064 8162542 761447191 71714012 37189 3891185 45561809 110486139 4850138 420353 15449177 296502 52736725 13523379 0 52182 9016896 1231 0 0 0 0 0
171 bytes: 166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
172 RPC iostats version: 1.0 p/v: 100003/3 (nfs)
173 xprt: tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
175 NULL: 0 0 0 0 0 0 0 0
176 GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
177 SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
178 LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
179 ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
180 READLINK: 125 125 0 20472 18620 0 1112 1118
181 READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
182 WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
183 CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
184 MKDIR: 3680 3680 0 773980 993920 26 23990 24245
185 SYMLINK: 903 903 0 233428 245488 6 5865 5917
186 MKNOD: 80 80 0 20148 21760 0 299 304
187 REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
188 RMDIR: 3367 3367 0 645112 484848 22 5782 6002
189 RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
190 LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
191 READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
192 READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
193 FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
194 FSINFO: 2 2 0 232 328 0 1 1
195 PATHCONF: 1 1 0 116 140 0 0 0
196 COMMIT: 0 0 0 0 0 0 0 0
198 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
200 </pre></blockquote></p>
202 <p>The key number to look at is the third number in the per-op list.
203 It is the number of NFS timeouts experiences per file system
204 operation. Here 22 write timeouts and 5 access timeouts. If these
205 numbers are increasing, I believe the machine is experiencing NFS
206 hang. Unfortunately the timeout value do not start to increase right
207 away. The NFS operations need to time out first, and this can take a
208 while. The exact timeout value depend on the setup. For example the
209 defaults for TCP and UDP mount points are quite different, and the
210 timeout value is affected by the soft, hard, timeo and retrans NFS
213 <p>The only way I have been able to get working on Debian and RedHat
214 Enterprise Linux for getting the timeout count is to peek in /proc/.
216 <ahref="http://docs.oracle.com/cd/E19253-
01/
816-
4555/netmonitor-
12/index.html
">Solaris
217 10 System Administration Guide: Network Services</a>, the 'nfsstat -c'
218 command can be used to get these timeout values. But this do not work
219 on Linux, as far as I can tell. I
220 <ahref="http://bugs.debian.org/
857043">asked Debian about this</a>,
221 but have not seen any replies yet.</p>
223 <p>Is there a better way to figure out if a Linux NFS client is
224 experiencing NFS hangs? Is there a way to detect which processes are
225 affected? Is there a way to get the NFS mount going quickly once the
226 network problem causing the NFS hang has been cleared? I would very
227 much welcome some clues, as we regularly run into NFS hangs.</p>
232 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian
">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english
">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sysadmin
">sysadmin</a>.
237 <div class="padding
"></div>
240 <div class="title
"><a href="http://people.skolelinux.org/pere/blog/How_does_it_feel_to_be_wiretapped__when_you_should_be_doing_the_wiretapping___.html
">How does it feel to be wiretapped, when you should be doing the wiretapping...</a></div>
241 <div class="date
"> 8th March 2017</div>
242 <div class="body
"><p>So the new president in the United States of America claim to be
243 surprised to discover that he was wiretapped during the election
244 before he was elected president. He even claim this must be illegal.
245 Well, doh, if it is one thing the confirmations from Snowden
246 documented, it is that the entire population in USA is wiretapped, one
247 way or another. Of course the president candidates were wiretapped,
248 alongside the senators, judges and the rest of the people in USA.</p>
250 <p>Next, the Federal Bureau of Investigation ask the Department of
251 Justice to go public rejecting the claims that Donald Trump was
252 wiretapped illegally. I fail to see the relevance, given that I am
253 sure the surveillance industry in USA believe they have all the legal
254 backing they need to conduct mass surveillance on the entire
257 <p>There is even the director of the FBI stating that he never saw an
258 order requesting wiretapping of Donald Trump. That is not very
259 surprising, given how the FISA court work, with all its activity being
260 secret. Perhaps he only heard about it?</p>
262 <p>What I find most sad in this story is how Norwegian journalists
263 present it. In a news reports the other day in the radio from the
264 Norwegian National broadcasting Company (NRK), I heard the journalist
265 claim that 'the FBI denies any wiretapping', while the reality is that
266 'the FBI denies any illegal wiretapping'. There is a fundamental and
267 important difference, and it make me sad that the journalists are
268 unable to grasp it.</p>
270 <p><strong>Update 2017-03-13:</strong> Look like
271 <a href="https://theintercept.com/
2017/
03/
13/rand-paul-is-right-nsa-routinely-monitors-americans-communications-without-warrants/
">The
272 Intercept report that US Senator Rand Paul confirm what I state above</a>.</p>
277 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english
">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance
">surveillance</a>.
282 <div class="padding
"></div>
285 <div class="title
"><a href="http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
">Norwegian Bokmål translation of The Debian Administrator's Handbook complete, proofreading in progress</a></div>
286 <div class="date
"> 3rd March 2017</div>
287 <div class="body
"><p>For almost a year now, we have been working on making a Norwegian
288 Bokmål edition of <a href="https://debian-handbook.info/
">The Debian
289 Administrator's Handbook</a>. Now, thanks to the tireless effort of
290 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
291 we are working on the proof reading to ensure consistent language and
292 use of correct computer science terms. The plan is to make the book
293 available on paper, as well as in electronic form. For that to
294 happen, the proof reading must be completed and all the figures need
295 to be translated. If you want to help out, get in touch.</p>
297 <p><a href="http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf
">A
299 fresh PDF edition</a> in A4 format (the final book will have smaller
300 pages) of the book created every morning is available for
301 proofreading. If you find any errors, please
302 <a href="https://hosted.weblate.org/projects/debian-handbook/
">visit
303 Weblate and correct the error</a>. The
304 <a href="http://l.github.io/debian-handbook/stat/nb-NO/index.html
">state
305 of the translation including figures</a> is a useful source for those
306 provide Norwegian bokmål screen shots and figures.</p>
311 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian
">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian-handbook
">debian-handbook</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english
">english</a>.
316 <div class="padding
"></div>
319 <div class="title
"><a href="http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
">Unlimited randomness with the ChaosKey?</a></div>
320 <div class="date
"> 1st March 2017</div>
321 <div class="body
"><p>A few days ago I ordered a small batch of
322 <a href="http://altusmetrum.org/ChaosKey/
">the ChaosKey</a>, a small
323 USB dongle for generating entropy created by Bdale Garbee and Keith
324 Packard. Yesterday it arrived, and I am very happy to report that it
325 work great! According to its designers, to get it to work out of the
326 box, you need the Linux kernel version 4.1 or later. I tested on a
327 Debian Stretch machine (kernel version 4.9), and there it worked just
328 fine, increasing the available entropy very quickly. I wrote a small
329 test oneliner to test. It first print the current entropy level,
330 drain /dev/random, and then print the entropy level for five seconds.
331 Here is the situation without the ChaosKey inserted:</p>
334 % cat /proc/sys/kernel/random/entropy_avail; \
335 dd bs=1M if=/dev/random of=/dev/null count=1; \
336 for n in $(seq 1 5); do \
337 cat /proc/sys/kernel/random/entropy_avail; \
343 28 byte kopiert, 0,000264565 s, 106 kB/s
352 <p>The entropy level increases by 3-4 every second. In such case any
353 application requiring random bits (like a HTTPS enabled web server)
354 will halt and wait for more entrpy. And here is the situation with
355 the ChaosKey inserted:</p>
358 % cat /proc/sys/kernel/random/entropy_avail; \
359 dd bs=1M if=/dev/random of=/dev/null count=1; \
360 for n in $(seq 1 5); do \
361 cat /proc/sys/kernel/random/entropy_avail; \
367 104 byte kopiert, 0,000487647 s, 213 kB/s
376 <p>Quite the difference. :) I bought a few more than I need, in case
377 someone want to buy one here in Norway. :)</p>
379 <p>Update: The dongle was presented at Debconf last year. You might
380 find <a href="https://debconf16.debconf.org/talks/
94/
">the talk
381 recording illuminating</a>. It explains exactly what the source of
382 randomness is, if you are unable to spot it from the schema drawing
383 available from the ChaosKey web site linked at the start of this blog
389 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>.
394 <div class="padding
"></div>
397 <div class="title
"><a href="http://people.skolelinux.org/pere/blog/Detect_OOXML_files_with_undefined_behaviour_.html
">Detect OOXML files with undefined behaviour?</a></div>
398 <div class="date
">21st February 2017</div>
399 <div class="body
"><p>I just noticed
400 <a href="http://www.arkivrad.no/aktuelt/riksarkivarens-forskrift-pa-horing
">the
401 new Norwegian proposal for archiving rules in the goverment</a> list
402 <a href="http://www.ecma-international.org/publications/standards/Ecma-
376.htm
">ECMA-376</a>
403 / ISO/IEC 29500 (aka OOXML) as valid formats to put in long term
404 storage. Luckily such files will only be accepted based on
405 pre-approval from the National Archive. Allowing OOXML files to be
406 used for long term storage might seem like a good idea as long as we
407 forget that there are plenty of ways for a "valid" OOXML document to
408 have content with no defined interpretation in the standard, which
409 lead to a question and an idea.
</p>
411 <p>Is there any tool to detect if a OOXML document depend on such
412 undefined behaviour? It would be useful for the National Archive (and
413 anyone else interested in verifying that a document is well defined)
414 to have such tool available when considering to approve the use of
415 OOXML. I'm aware of the
416 <a href=
"https://github.com/arlm/officeotron/">officeotron OOXML
417 validator
</a>, but do not know how complete it is nor if it will
418 report use of undefined behaviour. Are there other similar tools
419 available? Please send me an email if you know of any such tool.
</p>
424 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/nuug">nuug
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/standard">standard
</a>.
429 <div class=
"padding"></div>
432 <div class=
"title"><a href=
"http://people.skolelinux.org/pere/blog/Ruling_ignored_our_objections_to_the_seizure_of_popcorn_time_no___domstolkontroll_.html">Ruling ignored our objections to the seizure of popcorn-time.no (#domstolkontroll)
</a></div>
433 <div class=
"date">13th February
2017</div>
434 <div class=
"body"><p>A few days ago, we received the ruling from
435 <a href=
"http://people.skolelinux.org/pere/blog/A_day_in_court_challenging_seizure_of_popcorn_time_no_for__domstolkontroll.html">my
436 day in court
</a>. The case in question is a challenge of the seizure
437 of the DNS domain popcorn-time.no. The ruling simply did not mention
438 most of our arguments, and seemed to take everything ØKOKRIM said at
439 face value, ignoring our demonstration and explanations. But it is
440 hard to tell for sure, as we still have not seen most of the documents
441 in the case and thus were unprepared and unable to contradict several
442 of the claims made in court by the opposition. We are considering an
443 appeal, but it is partly a question of funding, as it is costing us
444 quite a bit to pay for our lawyer. If you want to help, please
445 <a href=
"http://www.nuug.no/dns-beslag-donasjon.shtml">donate to the
446 NUUG defense fund
</a>.
</p>
448 <p>The details of the case, as far as we know it, is available in
450 <a href=
"https://www.nuug.no/news/tags/dns-domenebeslag/">the NUUG
451 blog
</a>. This also include
452 <a href=
"https://www.nuug.no/news/Avslag_etter_rettslig_h_ring_om_DNS_beslaget___vurderer_veien_videre.shtml">the
453 ruling itself
</a>.
</p>
458 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/nuug">nuug
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett
</a>.
463 <div class=
"padding"></div>
466 <div class=
"title"><a href=
"http://people.skolelinux.org/pere/blog/A_day_in_court_challenging_seizure_of_popcorn_time_no_for__domstolkontroll.html">A day in court challenging seizure of popcorn-time.no for #domstolkontroll
</a></div>
467 <div class=
"date"> 3rd February
2017</div>
468 <div class=
"body"><p align=
"center"><img width=
"70%" src=
"http://people.skolelinux.org/pere/blog/images/2017-02-01-popcorn-time-in-court.jpeg"></p>
470 <p>On Wednesday, I spent the entire day in court in Follo Tingrett
471 representing
<a href=
"https://www.nuug.no/">the member association
472 NUUG
</a>, alongside
<a href=
"https://www.efn.no/">the member
473 association EFN
</a> and
<a href=
"http://www.imc.no">the DNS registrar
474 IMC
</a>, challenging the seizure of the DNS name popcorn-time.no. It
475 was interesting to sit in a court of law for the first time in my
476 life. Our team can be seen in the picture above: attorney Ola
477 Tellesbø, EFN board member Tom Fredrik Blenning, IMC CEO Morten Emil
478 Eriksen and NUUG board member Petter Reinholdtsen.
</p>
480 <p><a href=
"http://www.domstol.no/no/Enkelt-domstol/follo-tingrett/Nar-gar-rettssaken/Beramming/?cid=AAAA1701301512081262234UJFBVEZZZZZEJBAvtale">The
481 case at hand
</a> is that the Norwegian National Authority for
482 Investigation and Prosecution of Economic and Environmental Crime (aka
483 Økokrim) decided on their own, to seize a DNS domain early last
484 year, without following
485 <a href=
"https://www.norid.no/no/regelverk/navnepolitikk/#link12">the
486 official policy of the Norwegian DNS authority
</a> which require a
487 court decision. The web site in question was a site covering Popcorn
488 Time. And Popcorn Time is the name of a technology with both legal
489 and illegal applications. Popcorn Time is a client combining
490 searching a Bittorrent directory available on the Internet with
491 downloading/distribute content via Bittorrent and playing the
492 downloaded content on screen. It can be used illegally if it is used
493 to distribute content against the will of the right holder, but it can
494 also be used legally to play a lot of content, for example the
496 <a href=
"https://archive.org/details/movies">available from the
497 Internet Archive
</a> or the collection
498 <a href=
"http://vodo.net/films/">available from Vodo
</a>. We created
499 <a href=
"magnet:?xt=urn:btih:86c1802af5a667ca56d3918aecb7d3c0f7173084&dn=PresentasjonFolloTingrett.mov&tr=udp%3A%2F%2Fpublic.popcorn-tracker.org%3A6969%2Fannounce">a
500 video demonstrating legally use of Popcorn Time
</a> and played it in
501 Court. It can of course be downloaded using Bittorrent.
</p>
503 <p>I did not quite know what to expect from a day in court. The
504 government held on to their version of the story and we held on to
505 ours, and I hope the judge is able to make sense of it all. We will
506 know in two weeks time. Unfortunately I do not have high hopes, as
507 the Government have the upper hand here with more knowledge about the
508 case, better training in handling criminal law and in general higher
509 standing in the courts than fairly unknown DNS registrar and member
510 associations. It is expensive to be right also in Norway. So far the
511 case have cost more than NOK
70 000,-. To help fund the case, NUUG
512 and EFN have asked for donations, and managed to collect around NOK
25
513 000,- so far. Given the presentation from the Government, I expect
514 the government to appeal if the case go our way. And if the case do
515 not go our way, I hope we have enough funding to appeal.
</p>
517 <p>From the other side came two people from Økokrim. On the benches,
518 appearing to be part of the group from the government were two people
519 from the Simonsen Vogt Wiik lawyer office, and three others I am not
520 quite sure who was. Økokrim had proposed to present two witnesses
521 from The Motion Picture Association, but this was rejected because
522 they did not speak Norwegian and it was a bit late to bring in a
523 translator, but perhaps the two from MPA were present anyway. All
524 seven appeared to know each other. Good to see the case is take
527 <p>If you, like me, believe the courts should be involved before a DNS
528 domain is hijacked by the government, or you believe the Popcorn Time
529 technology have a lot of useful and legal applications, I suggest you
530 too
<a href=
"http://www.nuug.no/dns-beslag-donasjon.shtml">donate to
531 the NUUG defense fund
</a>. Both Bitcoin and bank transfer are
532 available. If NUUG get more than we need for the legal action (very
533 unlikely), the rest will be spend promoting free software, open
534 standards and unix-like operating systems in Norway, so no matter what
535 happens the money will be put to good use.
</p>
537 <p>If you want to lean more about the case, I recommend you check out
538 <a href=
"https://www.nuug.no/news/tags/dns-domenebeslag/">the blog
539 posts from NUUG covering the case
</a>. They cover the legal arguments
545 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/nuug">nuug
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett
</a>.
550 <div class=
"padding"></div>
553 <div class=
"title"><a href=
"http://people.skolelinux.org/pere/blog/Nasjonalbiblioteket_avslutter_sin_ulovlige_bruk_av_Google_Skjemaer.html">Nasjonalbiblioteket avslutter sin ulovlige bruk av Google Skjemaer
</a></div>
554 <div class=
"date">12th January
2017</div>
555 <div class=
"body"><p>I dag fikk jeg en skikkelig gladmelding. Bakgrunnen er at før jul
556 arrangerte Nasjonalbiblioteket
557 <a href=
"http://www.nb.no/Bibliotekutvikling/Kunnskapsorganisering/Nasjonalt-verksregister/Seminar-om-verksregister">et
558 seminar om sitt knakende gode tiltak «verksregister»
</a>. Eneste
559 måten å melde seg på dette seminaret var å sende personopplysninger
560 til Google via Google Skjemaer. Dette syntes jeg var tvilsom praksis,
561 da det bør være mulig å delta på seminarer arrangert av det offentlige
562 uten å måtte dele sine interesser, posisjon og andre
563 personopplysninger med Google. Jeg ba derfor om innsyn via
564 <a href=
"https://www.mimesbronn.no/">Mimes brønn
</a> i
565 <a href=
"https://www.mimesbronn.no/request/personopplysninger_til_google_sk">avtaler
566 og vurderinger Nasjonalbiblioteket hadde rundt dette
</a>.
567 Personopplysningsloven legger klare rammer for hva som må være på
568 plass før en kan be tredjeparter, spesielt i utlandet, behandle
569 personopplysninger på sine vegne, så det burde eksistere grundig
570 dokumentasjon før noe slikt kan bli lovlig. To jurister hos
571 Nasjonalbiblioteket mente først dette var helt i orden, og at Googles
572 standardavtale kunne brukes som databehandlingsavtale. Det syntes jeg
573 var merkelig, men har ikke hatt kapasitet til å følge opp saken før
574 for to dager siden.
</p>
576 <p>Gladnyheten i dag, som kom etter at jeg tipset Nasjonalbiblioteket
577 om at Datatilsynet underkjente Googles standardavtaler som
578 databehandleravtaler i
2011, er at Nasjonalbiblioteket har bestemt seg
579 for å avslutte bruken av Googles Skjemaer/Apps og gå i dialog med DIFI
580 for å finne bedre måter å håndtere påmeldinger i tråd med
581 personopplysningsloven. Det er fantastisk å se at av og til hjelper
582 det å spørre hva i alle dager det offentlige holder på med.
</p>
587 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/norsk">norsk
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/personvern">personvern
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/web">web
</a>.
592 <div class=
"padding"></div>
595 <div class=
"title"><a href=
"http://people.skolelinux.org/pere/blog/Bryter_NAV_sin_egen_personvernerkl_ring_.html">Bryter NAV sin egen personvernerklæring?
</a></div>
596 <div class=
"date">11th January
2017</div>
597 <div class=
"body"><p>Jeg leste med interesse en nyhetssak hos
598 <a href=
"http://www.digi.no/artikler/nav-avslorer-trygdemisbruk-ved-a-spore-ip-adresser/367394">digi.no
</a>
600 <a href=
"https://www.nrk.no/buskerud/trygdesvindlere-avslores-av-utenlandske-ip-adresser-1.13313461">NRK
</a>
601 om at det ikke bare er meg, men at også NAV bedriver geolokalisering
602 av IP-adresser, og at det gjøres analyse av IP-adressene til de som
603 sendes inn meldekort for å se om meldekortet sendes inn fra
604 utenlandske IP-adresser. Politiadvokat i Drammen, Hans Lyder Haare,
605 er sitert i NRK på at «De to er jo blant annet avslørt av
606 IP-adresser. At man ser at meldekortet kommer fra utlandet.»
</p>
608 <p>Jeg synes det er fint at det blir bedre kjent at IP-adresser
609 knyttes til enkeltpersoner og at innsamlet informasjon brukes til å
610 stedsbestemme personer også av aktører her i Norge. Jeg ser det som
611 nok et argument for å bruke
612 <a href=
"https://www.torproject.org/">Tor
</a> så mye som mulig for å
613 gjøre gjøre IP-lokalisering vanskeligere, slik at en kan beskytte sin
614 privatsfære og unngå å dele sin fysiske plassering med
617 <P>Men det er en ting som bekymrer meg rundt denne nyheten. Jeg ble
618 tipset (takk #nuug) om
619 <a href=
"https://www.nav.no/no/NAV+og+samfunn/Kontakt+NAV/Teknisk+brukerstotte/Snarveier/personvernerkl%C3%A6ring-for-arbeids-og-velferdsetaten">NAVs
620 personvernerklæring
</a>, som under punktet «Personvern og statistikk»
625 <p>«Når du besøker nav.no, etterlater du deg elektroniske spor. Sporene
626 dannes fordi din nettleser automatisk sender en rekke opplysninger til
627 NAVs tjener (server-maskin) hver gang du ber om å få vist en side. Det
628 er eksempelvis opplysninger om hvilken nettleser og -versjon du
629 bruker, og din internettadresse (ip-adresse). For hver side som vises,
630 lagres følgende opplysninger:
</p>
633 <li>hvilken side du ser på
</li>
635 <li>hvilken nettleser du bruker
</li>
636 <li>din ip-adresse
</li>
639 <p>Ingen av opplysningene vil bli brukt til å identifisere
640 enkeltpersoner. NAV bruker disse opplysningene til å generere en
641 samlet statistikk som blant annet viser hvilke sider som er mest
642 populære. Statistikken er et redskap til å forbedre våre
647 <p>Jeg klarer ikke helt å se hvordan analyse av de besøkendes
648 IP-adresser for å se hvem som sender inn meldekort via web fra en
649 IP-adresse i utlandet kan gjøres uten å komme i strid med påstanden om
650 at «ingen av opplysningene vil bli brukt til å identifisere
651 enkeltpersoner». Det virker dermed for meg som at NAV bryter sine
652 egen personvernerklæring, hvilket
653 <a href=
"http://people.skolelinux.org/pere/blog/Er_lover_brutt_n_r_personvernpolicy_ikke_stemmer_med_praksis_.html">Datatilsynet
654 fortalte meg i starten av desember antagelig er brudd på
655 personopplysningsloven
</a>.
657 <p>I tillegg er personvernerklæringen ganske misvisende i og med at
658 NAVs nettsider ikke bare forsyner NAV med personopplysninger, men i
659 tillegg ber brukernes nettleser kontakte fem andre nettjenere
660 (script.hotjar.com, static.hotjar.com, vars.hotjar.com,
661 www.google-analytics.com og www.googletagmanager.com), slik at
662 personopplysninger blir gjort tilgjengelig for selskapene Hotjar og
663 Google , og alle som kan lytte på trafikken på veien (som FRA, GCHQ og
664 NSA). Jeg klarer heller ikke se hvordan slikt spredning av
665 personopplysninger kan være i tråd med kravene i
666 personopplysningloven, eller i tråd med NAVs personvernerklæring.
</p>
668 <p>Kanskje NAV bør ta en nøye titt på sin personvernerklæring? Eller
669 kanskje Datatilsynet bør gjøre det?
</p>
674 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/personvern">personvern
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance
</a>.
679 <div class=
"padding"></div>
681 <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>
692 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2017/01/">January (
4)
</a></li>
694 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2017/02/">February (
3)
</a></li>
696 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2017/03/">March (
5)
</a></li>
703 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2016/01/">January (
3)
</a></li>
705 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2016/02/">February (
2)
</a></li>
707 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2016/03/">March (
3)
</a></li>
709 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2016/04/">April (
8)
</a></li>
711 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2016/05/">May (
8)
</a></li>
713 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2016/06/">June (
2)
</a></li>
715 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2016/07/">July (
2)
</a></li>
717 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2016/08/">August (
5)
</a></li>
719 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2016/09/">September (
2)
</a></li>
721 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2016/10/">October (
3)
</a></li>
723 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2016/11/">November (
8)
</a></li>
725 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2016/12/">December (
5)
</a></li>
732 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2015/01/">January (
7)
</a></li>
734 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2015/02/">February (
6)
</a></li>
736 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2015/03/">March (
1)
</a></li>
738 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2015/04/">April (
4)
</a></li>
740 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2015/05/">May (
3)
</a></li>
742 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2015/06/">June (
4)
</a></li>
744 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2015/07/">July (
6)
</a></li>
746 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2015/08/">August (
2)
</a></li>
748 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2015/09/">September (
2)
</a></li>
750 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2015/10/">October (
9)
</a></li>
752 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2015/11/">November (
6)
</a></li>
754 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2015/12/">December (
3)
</a></li>
761 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/01/">January (
2)
</a></li>
763 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/02/">February (
3)
</a></li>
765 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/03/">March (
8)
</a></li>
767 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/04/">April (
7)
</a></li>
769 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/05/">May (
1)
</a></li>
771 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/06/">June (
2)
</a></li>
773 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/07/">July (
2)
</a></li>
775 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/08/">August (
2)
</a></li>
777 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/09/">September (
5)
</a></li>
779 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/10/">October (
6)
</a></li>
781 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/11/">November (
3)
</a></li>
783 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/12/">December (
5)
</a></li>
790 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/01/">January (
11)
</a></li>
792 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/02/">February (
9)
</a></li>
794 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/03/">March (
9)
</a></li>
796 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/04/">April (
6)
</a></li>
798 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/05/">May (
9)
</a></li>
800 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/06/">June (
10)
</a></li>
802 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/07/">July (
7)
</a></li>
804 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/08/">August (
3)
</a></li>
806 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/09/">September (
5)
</a></li>
808 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/10/">October (
7)
</a></li>
810 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/11/">November (
9)
</a></li>
812 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/12/">December (
3)
</a></li>
819 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/01/">January (
7)
</a></li>
821 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/02/">February (
10)
</a></li>
823 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/03/">March (
17)
</a></li>
825 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/04/">April (
12)
</a></li>
827 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/05/">May (
12)
</a></li>
829 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/06/">June (
20)
</a></li>
831 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/07/">July (
17)
</a></li>
833 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/08/">August (
6)
</a></li>
835 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/09/">September (
9)
</a></li>
837 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/10/">October (
17)
</a></li>
839 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/11/">November (
10)
</a></li>
841 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/12/">December (
7)
</a></li>
848 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/01/">January (
16)
</a></li>
850 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/02/">February (
6)
</a></li>
852 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/03/">March (
6)
</a></li>
854 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/04/">April (
7)
</a></li>
856 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/05/">May (
3)
</a></li>
858 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/06/">June (
2)
</a></li>
860 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/07/">July (
7)
</a></li>
862 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/08/">August (
6)
</a></li>
864 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/09/">September (
4)
</a></li>
866 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/10/">October (
2)
</a></li>
868 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/11/">November (
3)
</a></li>
870 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/12/">December (
1)
</a></li>
877 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/01/">January (
2)
</a></li>
879 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/02/">February (
1)
</a></li>
881 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/03/">March (
3)
</a></li>
883 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/04/">April (
3)
</a></li>
885 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/05/">May (
9)
</a></li>
887 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/06/">June (
14)
</a></li>
889 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/07/">July (
12)
</a></li>
891 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/08/">August (
13)
</a></li>
893 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/09/">September (
7)
</a></li>
895 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/10/">October (
9)
</a></li>
897 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/11/">November (
13)
</a></li>
899 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/12/">December (
12)
</a></li>
906 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/01/">January (
8)
</a></li>
908 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/02/">February (
8)
</a></li>
910 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/03/">March (
12)
</a></li>
912 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/04/">April (
10)
</a></li>
914 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/05/">May (
9)
</a></li>
916 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/06/">June (
3)
</a></li>
918 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/07/">July (
4)
</a></li>
920 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/08/">August (
3)
</a></li>
922 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/09/">September (
1)
</a></li>
924 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/10/">October (
2)
</a></li>
926 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/11/">November (
3)
</a></li>
928 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/12/">December (
3)
</a></li>
935 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2008/11/">November (
5)
</a></li>
937 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2008/12/">December (
7)
</a></li>
948 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (
13)
</a></li>
950 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/amiga">amiga (
1)
</a></li>
952 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/aros">aros (
1)
</a></li>
954 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bankid">bankid (
4)
</a></li>
956 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (
9)
</a></li>
958 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (
16)
</a></li>
960 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bsa">bsa (
2)
</a></li>
962 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (
2)
</a></li>
964 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian (
148)
</a></li>
966 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (
158)
</a></li>
968 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/debian-handbook">debian-handbook (
3)
</a></li>
970 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/digistan">digistan (
10)
</a></li>
972 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/dld">dld (
16)
</a></li>
974 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/docbook">docbook (
23)
</a></li>
976 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (
4)
</a></li>
978 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/english">english (
346)
</a></li>
980 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (
23)
</a></li>
982 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (
12)
</a></li>
984 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (
29)
</a></li>
986 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (
9)
</a></li>
988 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (
18)
</a></li>
990 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/h264">h264 (
20)
</a></li>
992 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/intervju">intervju (
42)
</a></li>
994 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (
15)
</a></li>
996 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/kart">kart (
20)
</a></li>
998 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/ldap">ldap (
9)
</a></li>
1000 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/lenker">lenker (
8)
</a></li>
1002 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd (
2)
</a></li>
1004 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (
1)
</a></li>
1006 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (
8)
</a></li>
1008 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (
39)
</a></li>
1010 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (
9)
</a></li>
1012 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/norsk">norsk (
287)
</a></li>
1014 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/nuug">nuug (
188)
</a></li>
1016 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (
29)
</a></li>
1018 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/open311">open311 (
2)
</a></li>
1020 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (
64)
</a></li>
1022 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/personvern">personvern (
99)
</a></li>
1024 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/raid">raid (
1)
</a></li>
1026 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/reactos">reactos (
1)
</a></li>
1028 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/reprap">reprap (
11)
</a></li>
1030 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/rfid">rfid (
3)
</a></li>
1032 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/robot">robot (
10)
</a></li>
1034 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/rss">rss (
1)
</a></li>
1036 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/ruter">ruter (
5)
</a></li>
1038 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (
2)
</a></li>
1040 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (
52)
</a></li>
1042 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (
4)
</a></li>
1044 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (
5)
</a></li>
1046 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/standard">standard (
52)
</a></li>
1048 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (
5)
</a></li>
1050 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (
11)
</a></li>
1052 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (
48)
</a></li>
1054 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (
3)
</a></li>
1056 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/usenix">usenix (
2)
</a></li>
1058 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/valg">valg (
8)
</a></li>
1060 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/video">video (
59)
</a></li>
1062 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (
4)
</a></li>
1064 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/web">web (
40)
</a></li>
1070 <p style=
"text-align: right">
1071 Created by
<a href=
"http://steve.org.uk/Software/chronicle">Chronicle v4.6
</a>