]> pere.pagekite.me Git - homepage.git/blob - blog/index.html
projects / homepage.git / blob
? search:
summary | shortlog | log | commit | commitdiff | tree
blame | history | raw | HEAD
Generated.
[homepage.git] / blog / index.html
1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr">
4 <head>
5 <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
6 <title>Petter Reinholdtsen</title>
7 <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/style.css" />
8 <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/vim.css" />
9 <link rel="alternate" title="RSS Feed" href="http://people.skolelinux.org/pere/blog/index.rss" type="application/rss+xml" />
10 </head>
11 <body>
12 <div class="title">
13 <h1>
14 <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
15
16 </h1>
17
18 </div>
19
20
21
22 <div class="entry">
23 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html">Coz profiler for multi-threaded software is now in Debian</a></div>
24 <div class="date">13th November 2016</div>
25 <div class="body"><p><a href="http://coz-profiler.org/">The Coz profiler</a>, a nice
26 profiler able to run benchmarking experiments on the instrumented
27 multi-threaded program, finally
28 <a href="https://tracker.debian.org/pkg/coz-profiler">made it into
29 Debian unstable yesterday</A>. Lluís Vilanova and I have spent many
30 months since
31 <a href="http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html">I
32 blogged about the coz tool</a> in August working with upstream to make
33 it suitable for Debian. There are still issues with clang
34 compatibility, inline assembly only working x86 and minimized
35 JavaScript libraries.</p>
36
37 <p>To test it, install 'coz-profiler' using apt and run it like this:</p>
38
39 <p><blockquote>
40 <tt>coz run --- /path/to/binary-with-debug-info</tt>
41 </blockquote></p>
42
43 <p>This will produce a profile.coz file in the current working
44 directory with the profiling information. This is then given to a
45 JavaScript application provided in the package and available from
46 <a href="http://plasma-umass.github.io/coz/">a project web page</a>.
47 To start the local copy, invoke it in a browser like this:</p>
48
49 <p><blockquote>
50 <tt>sensible-browser /usr/share/coz-profiler/viewer/index.htm</tt>
51 </blockquote></p>
52
53 <p>See the project home page and the
54 <a href="https://www.usenix.org/publications/login/summer2016/curtsinger">USENIX
55 ;login: article on Coz</a> for more information on how it is
56 working.</p>
57 </div>
58 <div class="tags">
59
60
61 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>.
62
63
64 </div>
65 </div>
66 <div class="padding"></div>
67
68 <div class="entry">
69 <div class="title"><a href="http://people.skolelinux.org/pere/blog/How_to_talk_with_your_loved_ones_in_private.html">How to talk with your loved ones in private</a></div>
70 <div class="date"> 7th November 2016</div>
71 <div class="body"><p>A few days ago I ran a very biased and informal survey to get an
72 idea about what options are being used to communicate with end to end
73 encryption with friends and family. I explicitly asked people not to
74 list options only used in a work setting. The background is the
75 uneasy feeling I get when using Signal, a feeling shared by others as
76 a blog post from Sander Venima about
77 <a href="https://sandervenema.ch/2016/11/why-i-wont-recommend-signal-anymore/">why
78 he do not recommend Signal anymore</a> (with
79 <a href="https://news.ycombinator.com/item?id=12883410">feedback from
80 the Signal author available from ycombinator</a>). I wanted an
81 overview of the options being used, and hope to include those options
82 in a less biased survey later on. So far I have not taken the time to
83 look into the individual proposed systems. They range from text
84 sharing web pages, via file sharing and email to instant messaging,
85 VOIP and video conferencing. For those considering which system to
86 use, it is also useful to have a look at
87 <a href="https://www.eff.org/secure-messaging-scorecard">the EFF Secure
88 messaging scorecard</a> which is slightly out of date but still
89 provide valuable information.</p>
90
91 <p>So, on to the list. There were some used by many, some used by a
92 few, some rarely used ones and a few mentioned but without anyone
93 claiming to use them. Notice the grouping is in reality quite random
94 given the biased self selected set of participants. First the ones
95 used by many:</p>
96
97 <ul>
98
99 <li><a href="https://whispersystems.org/">Signal</a></li>
100 <li>Email w/<a href="http://openpgp.org/">OpenPGP</a> (Enigmail, GPGSuite,etc)</li>
101 <li><a href="https://www.whatsapp.com/">Whatsapp</a></li>
102 <li>IRC w/<a href="https://otr.cypherpunks.ca/">OTR</a></li>
103 <li>XMPP w/<a href="https://otr.cypherpunks.ca/">OTR</a></li>
104
105 </ul>
106
107 <p>Then the ones used by a few.</p>
108
109 <ul>
110
111 <li><a href="https://wiki.mumble.info/wiki/Main_Page">Mumble</a></li>
112 <li>iMessage (included in iOS from Apple)</li>
113 <li><a href="https://telegram.org/">Telegram</a></li>
114 <li><a href="https://jitsi.org/">Jitsi</a></li>
115 <li><a href="https://keybase.io/download">Keybase file</a></li>
116
117 </ul>
118
119 <p>Then the ones used by even fewer people</p>
120
121 <ul>
122
123 <li><a href="https://ring.cx/">Ring</a></li>
124 <li><a href="https://bitmessage.org/">Bitmessage</a></li>
125 <li><a href="https://wire.com/">Wire</a></li>
126 <li>VoIP w/<a href="https://en.wikipedia.org/wiki/ZRTP">ZRTP</a> or controlled <a href="https://en.wikipedia.org/wiki/Secure_Real-time_Transport_Protocol">SRTP</a> (e.g using <a href="https://en.wikipedia.org/wiki/CSipSimple">CSipSimple</a>, <a href="https://en.wikipedia.org/wiki/Linphone">Linphone</a>)</li>
127 <li><a href="https://matrix.org/">Matrix</a></li>
128 <li><a href="https://kontalk.org/">Kontalk</a></li>
129 <li><a href="https://0bin.net/">0bin</a> (encrypted pastebin)</li>
130 <li><a href="https://appear.in">Appear.in</a></li>
131 <li><a href="https://riot.im/">riot</a></li>
132 <li><a href="https://www.wickr.com/">Wickr Me</a></li>
133
134 </ul>
135
136 <p>And finally the ones mentioned by not marked as used by
137 anyone. This might be a mistake, perhaps the person adding the entry
138 forgot to flag it as used?</p>
139
140 <ul>
141
142 <li>Email w/Certificates <a href="https://en.wikipedia.org/wiki/S/MIME">S/MIME</a></li>
143 <li><a href="https://www.crypho.com/">Crypho</a></li>
144 <li><a href="https://cryptpad.fr/">CryptPad</a></li>
145 <li><a href="https://github.com/ricochet-im/ricochet">ricochet</a></li>
146
147 </ul>
148
149 <p>Given the network effect it seem obvious to me that we as a society
150 have been divided and conquered by those interested in keeping
151 encrypted and secure communication away from the masses. The
152 finishing remarks <a href="https://vimeo.com/97505679">from Aral Balkan
153 in his talk "Free is a lie"</a> about the usability of free software
154 really come into effect when you want to communicate in private with
155 your friends and family. We can not expect them to allow the
156 usability of communication tool to block their ability to talk to
157 their loved ones.</p>
158
159 <p>Note for example the option IRC w/OTR. Most IRC clients do not
160 have OTR support, so in most cases OTR would not be an option, even if
161 you wanted to. In my personal experience, about 1 in 20 I talk to
162 have a IRC client with OTR. For private communication to really be
163 available, most people to talk to must have the option in their
164 currently used client. I can not simply ask my family to install an
165 IRC client. I need to guide them through a technical multi-step
166 process of adding extensions to the client to get them going. This is
167 a non-starter for most.</p>
168
169 <p>I would like to be able to do video phone calls, audio phone calls,
170 exchange instant messages and share files with my loved ones, without
171 being forced to share with people I do not know. I do not want to
172 share the content of the conversations, and I do not want to share who
173 I communicate with or the fact that I communicate with someone.
174 Without all these factors in place, my private life is being more or
175 less invaded.</p>
176 </div>
177 <div class="tags">
178
179
180 Tags: <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>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
181
182
183 </div>
184 </div>
185 <div class="padding"></div>
186
187 <div class="entry">
188 <div class="title"><a href="http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html">My own self balancing Lego Segway</a></div>
189 <div class="date"> 4th November 2016</div>
190 <div class="body"><p>A while back I received a Gyro sensor for the NXT
191 <a href="mindstorms.lego.com">Mindstorms</a> controller as a birthday
192 present. It had been on my wishlist for a while, because I wanted to
193 build a Segway like balancing lego robot. I had already built
194 <a href="http://www.nxtprograms.com/NXT2/segway/">a simple balancing
195 robot</a> with the kids, using the light/color sensor included in the
196 NXT kit as the balance sensor, but it was not working very well. It
197 could balance for a while, but was very sensitive to the light
198 condition in the room and the reflective properties of the surface and
199 would fall over after a short while. I wanted something more robust,
200 and had
201 <a href="https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&key=NGY1044">the
202 gyro sensor from HiTechnic</a> I believed would solve it on my
203 wishlist for some years before it suddenly showed up as a gift from my
204 loved ones. :)</p>
205
206 <p>Unfortunately I have not had time to sit down and play with it
207 since then. But that changed some days ago, when I was searching for
208 lego segway information and came across a recipe from HiTechnic for
209 building
210 <a href="http://www.hitechnic.com/blog/gyro-sensor/htway/">the
211 HTWay</a>, a segway like balancing robot. Build instructions and
212 <a href="https://www.hitechnic.com/upload/786-HTWayC.nxc">source
213 code</a> was included, so it was just a question of putting it all
214 together. And thanks to the great work of many Debian developers, the
215 compiler needed to build the source for the NXT is already included in
216 Debian, so I was read to go in less than an hour. The resulting robot
217 do not look very impressive in its simplicity:</p>
218
219 <p align="center"><img width="70%" src="http://people.skolelinux.org/pere/blog/images/2016-11-04-lego-htway-robot.jpeg"></p>
220
221 <p>Because I lack the infrared sensor used to control the robot in the
222 design from HiTechnic, I had to comment out the last task
223 (taskControl). I simply placed /* and */ around it get the program
224 working without that sensor present. Now it balances just fine until
225 the battery status run low:</p>
226
227 <p align="center"><video width="70%" controls="true">
228 <source src="http://people.skolelinux.org/pere/blog/images/2016-11-04-lego-htway-balancing.ogv" type="video/ogg">
229 </video></p>
230
231 <p>Now we would like to teach it how to follow a line and take remote
232 control instructions using the included Bluetooth receiver in the NXT.</p>
233
234 <p>If you, like me, love LEGO and want to make sure we find the tools
235 they need to work with LEGO in Debian and all our derivative
236 distributions like Ubuntu, check out
237 <a href="http://wiki.debian.org/LegoDesigners">the LEGO designers
238 project page</a> and join the Debian LEGO team. Personally I own a
239 RCX and NXT controller (no EV3), and would like to make sure the
240 Debian tools needed to program the systems I own work as they
241 should.</p>
242 </div>
243 <div class="tags">
244
245
246 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/robot">robot</a>.
247
248
249 </div>
250 </div>
251 <div class="padding"></div>
252
253 <div class="entry">
254 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Aktivitetsb_nd_som_beskytter_privatsf_ren.html">Aktivitetsbånd som beskytter privatsfæren</a></div>
255 <div class="date"> 3rd November 2016</div>
256 <div class="body"><p>Jeg ble så imponert over
257 <a href="https://www.nrk.no/norge/forbrukerradet-mener-aktivitetsarmband-strider-mot-norsk-lov-1.13209079">dagens
258 gladnyhet på NRK</a>, om at Forbrukerrådet klager inn vilkårene for
259 bruk av aktivitetsbånd fra Fitbit, Garmin, Jawbone og Mio til
260 Datatilsynet og forbrukerombudet, at jeg sendte følgende brev til
261 forbrukerrådet for å uttrykke min støtte:
262
263 <blockquote>
264
265 <p>Jeg ble veldig glad over å lese at Forbrukerrådet
266 <a href="http://www.forbrukerradet.no/siste-nytt/klager-inn-aktivitetsarmband-for-brudd-pa-norsk-lov/">klager
267 inn flere aktivitetsbånd til Datatilsynet for dårlige vilkår</a>. Jeg
268 har ønsket meg et aktivitetsbånd som kan måle puls, bevegelse og
269 gjerne også andre helserelaterte indikatorer en stund nå. De eneste
270 jeg har funnet i salg gjør, som dere også har oppdaget, graverende
271 inngrep i privatsfæren og sender informasjonen ut av huset til folk og
272 organisasjoner jeg ikke ønsker å dele aktivitets- og helseinformasjon
273 med. Jeg ønsker et alternativ som <em>ikke</em> sender informasjon til
274 skyen, men derimot bruker
275 <a href="http://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html">en
276 fritt og åpent standardisert</a> protokoll (eller i det minste en
277 dokumentert protokoll uten patent- og opphavsrettslige
278 bruksbegrensinger) til å kommunisere med datautstyr jeg kontrollerer.
279 Er jo ikke interessert i å betale noen for å tilrøve seg
280 personopplysninger fra meg. Desverre har jeg ikke funnet noe
281 alternativ så langt.</p>
282
283 <p>Det holder ikke å endre på bruksvilkårene for enhetene, slik
284 Datatilsynet ofte legger opp til i sin behandling, når de gjør slik
285 f.eks. Fitbit (den jeg har sett mest på). Fitbit krypterer
286 informasjonen på enheten og sender den kryptert til leverandøren. Det
287 gjør det i praksis umulig både å sjekke hva slags informasjon som
288 sendes over, og umulig å ta imot informasjonen selv i stedet for
289 Fitbit. Uansett hva slags historie som forteller i bruksvilkårene er
290 en jo både prisgitt leverandørens godvilje og at de ikke tvinges av
291 sitt lands myndigheter til å lyve til sine kunder om hvorvidt
292 personopplysninger spres ut over det bruksvilkårene sier. Det er
293 veldokumentert hvordan f.eks. USA tvinger selskaper vha. såkalte
294 National security letters til å utlevere personopplysninger samtidig
295 som de ikke får lov til å fortelle dette til kundene sine.</p>
296
297 <p>Stå på, jeg er veldig glade for at dere har sett på saken. Vet
298 dere om aktivitetsbånd i salg i dag som ikke tvinger en til å utlevere
299 aktivitets- og helseopplysninger med leverandøren?</p>
300
301 </blockquote>
302
303 <p>Jeg håper en konkurrent som respekterer kundenes privatliv klarer å
304 nå opp i markedet, slik at det finnes et reelt alternativ for oss som
305 har full tillit til at skyleverandører vil prioritere egen inntjening
306 og myndighetspålegg langt foran kundenes rett til privatliv. Jeg har
307 ingen tiltro til at Datatilsynet vil kreve noe mer enn at vilkårene
308 endres slik at de forklarer eksplisitt i hvor stor grad bruk av
309 produktene utraderer privatsfæren til kundene. Det vil nok gjøre de
310 innklagede armbåndene «lovlige», men fortsatt tvinge kundene til å
311 dele sine personopplysninger med leverandøren.</p>
312 </div>
313 <div class="tags">
314
315
316 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
317
318
319 </div>
320 </div>
321 <div class="padding"></div>
322
323 <div class="entry">
324 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html">Experience and updated recipe for using the Signal app without a mobile phone</a></div>
325 <div class="date">10th October 2016</div>
326 <div class="body"><p>In July
327 <a href="http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html">I
328 wrote how to get the Signal Chrome/Chromium app working</a> without
329 the ability to receive SMS messages (aka without a cell phone). It is
330 time to share some experiences and provide an updated setup.</p>
331
332 <p>The Signal app have worked fine for several months now, and I use
333 it regularly to chat with my loved ones. I had a major snag at the
334 end of my summer vacation, when the the app completely forgot my
335 setup, identity and keys. The reason behind this major mess was
336 running out of disk space. To avoid that ever happening again I have
337 started storing everything in <tt>userdata/</tt> in git, to be able to
338 roll back to an earlier version if the files are wiped by mistake. I
339 had to use it once after introducing the git backup. When rolling
340 back to an earlier version, one need to use the 'reset session' option
341 in Signal to get going, and notify the people you talk with about the
342 problem. I assume there is some sequence number tracking in the
343 protocol to detect rollback attacks. The git repository is rather big
344 (674 MiB so far), but I have not tried to figure out if some of the
345 content can be added to a .gitignore file due to lack of spare
346 time.</p>
347
348 <p>I've also hit the 90 days timeout blocking, and noticed that this
349 make it impossible to send messages using Signal. I could still
350 receive them, but had to patch the code with a new timestamp to send.
351 I believe the timeout is added by the developers to force people to
352 upgrade to the latest version of the app, even when there is no
353 protocol changes, to reduce the version skew among the user base and
354 thus try to keep the number of support requests down.</p>
355
356 <p>Since my original recipe, the Signal source code changed slightly,
357 making the old patch fail to apply cleanly. Below is an updated
358 patch, including the shell wrapper I use to start Signal. The
359 original version required a new user to locate the JavaScript console
360 and call a function from there. I got help from a friend with more
361 JavaScript knowledge than me to modify the code to provide a GUI
362 button instead. This mean that to get started you just need to run
363 the wrapper and click the 'Register without mobile phone' to get going
364 now. I've also modified the timeout code to always set it to 90 days
365 in the future, to avoid having to patch the code regularly.</p>
366
367 <p>So, the updated recipe for Debian Jessie:</p>
368
369 <ol>
370
371 <li>First, install required packages to get the source code and the
372 browser you need. Signal only work with Chrome/Chromium, as far as I
373 know, so you need to install it.
374
375 <pre>
376 apt install git tor chromium
377 git clone https://github.com/WhisperSystems/Signal-Desktop.git
378 </pre></li>
379
380 <li>Modify the source code using command listed in the the patch
381 block below.</li>
382
383 <li>Start Signal using the run-signal-app wrapper (for example using
384 <tt>`pwd`/run-signal-app</tt>).
385
386 <li>Click on the 'Register without mobile phone', will in a phone
387 number you can receive calls to the next minute, receive the
388 verification code and enter it into the form field and press
389 'Register'. Note, the phone number you use will be user Signal
390 username, ie the way others can find you on Signal.</li>
391
392 <li>You can now use Signal to contact others. Note, new contacts do
393 not show up in the contact list until you restart Signal, and there is
394 no way to assign names to Contacts. There is also no way to create or
395 update chat groups. I suspect this is because the web app do not have
396 a associated contact database.</li>
397
398 </ol>
399
400 <p>I am still a bit uneasy about using Signal, because of the way its
401 main author moxie0 reject federation and accept dependencies to major
402 corporations like Google (part of the code is fetched from Google) and
403 Amazon (the central coordination point is owned by Amazon). See for
404 example
405 <a href="https://github.com/LibreSignal/LibreSignal/issues/37">the
406 LibreSignal issue tracker</a> for a thread documenting the authors
407 view on these issues. But the network effect is strong in this case,
408 and several of the people I want to communicate with already use
409 Signal. Perhaps we can all move to <a href="https://ring.cx/">Ring</a>
410 once it <a href="https://bugs.debian.org/830265">work on my
411 laptop</a>? It already work on Windows and Android, and is included
412 in <a href="https://tracker.debian.org/pkg/ring">Debian</a> and
413 <a href="https://launchpad.net/ubuntu/+source/ring">Ubuntu</a>, but not
414 working on Debian Stable.</p>
415
416 <p>Anyway, this is the patch I apply to the Signal code to get it
417 working. It switch to the production servers, disable to timeout,
418 make registration easier and add the shell wrapper:</p>
419
420 <pre>
421 cd Signal-Desktop; cat &lt;&lt;EOF | patch -p1
422 diff --git a/js/background.js b/js/background.js
423 index 24b4c1d..579345f 100644
424 --- a/js/background.js
425 +++ b/js/background.js
426 @@ -33,9 +33,9 @@
427 });
428 });
429
430 - var SERVER_URL = 'https://textsecure-service-staging.whispersystems.org';
431 + var SERVER_URL = 'https://textsecure-service-ca.whispersystems.org';
432 var SERVER_PORTS = [80, 4433, 8443];
433 - var ATTACHMENT_SERVER_URL = 'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com';
434 + var ATTACHMENT_SERVER_URL = 'https://whispersystems-textsecure-attachments.s3.amazonaws.com';
435 var messageReceiver;
436 window.getSocketStatus = function() {
437 if (messageReceiver) {
438 diff --git a/js/expire.js b/js/expire.js
439 index 639aeae..beb91c3 100644
440 --- a/js/expire.js
441 +++ b/js/expire.js
442 @@ -1,6 +1,6 @@
443 ;(function() {
444 'use strict';
445 - var BUILD_EXPIRATION = 0;
446 + var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
447
448 window.extension = window.extension || {};
449
450 diff --git a/js/views/install_view.js b/js/views/install_view.js
451 index 7816f4f..1d6233b 100644
452 --- a/js/views/install_view.js
453 +++ b/js/views/install_view.js
454 @@ -38,7 +38,8 @@
455 return {
456 'click .step1': this.selectStep.bind(this, 1),
457 'click .step2': this.selectStep.bind(this, 2),
458 - 'click .step3': this.selectStep.bind(this, 3)
459 + 'click .step3': this.selectStep.bind(this, 3),
460 + 'click .callreg': function() { extension.install('standalone') },
461 };
462 },
463 clearQR: function() {
464 diff --git a/options.html b/options.html
465 index dc0f28e..8d709f6 100644
466 --- a/options.html
467 +++ b/options.html
468 @@ -14,7 +14,10 @@
469 &lt;div class='nav'>
470 &lt;h1>{{ installWelcome }}&lt;/h1>
471 &lt;p>{{ installTagline }}&lt;/p>
472 - &lt;div> &lt;a class='button step2'>{{ installGetStartedButton }}&lt;/a> &lt;/div>
473 + &lt;div> &lt;a class='button step2'>{{ installGetStartedButton }}&lt;/a>
474 + &lt;br> &lt;a class="button callreg">Register without mobile phone&lt;/a>
475 +
476 + &lt;/div>
477 &lt;span class='dot step1 selected'>&lt;/span>
478 &lt;span class='dot step2'>&lt;/span>
479 &lt;span class='dot step3'>&lt;/span>
480 --- /dev/null 2016-10-07 09:55:13.730181472 +0200
481 +++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
482 @@ -0,0 +1,12 @@
483 +#!/bin/sh
484 +set -e
485 +cd $(dirname $0)
486 +mkdir -p userdata
487 +userdata="`pwd`/userdata"
488 +if [ -d "$userdata" ] && [ ! -d "$userdata/.git" ] ; then
489 + (cd $userdata && git init)
490 +fi
491 +(cd $userdata && git add . && git commit -m "Current status." || true)
492 +exec chromium \
493 + --proxy-server="socks://localhost:9050" \
494 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
495 EOF
496 chmod a+rx run-signal-app
497 </pre>
498
499 <p>As usual, if you use Bitcoin and want to show your support of my
500 activities, please send Bitcoin donations to my address
501 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&label=PetterReinholdtsenBlog">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
502 </div>
503 <div class="tags">
504
505
506 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/sikkerhet">sikkerhet</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
507
508
509 </div>
510 </div>
511 <div class="padding"></div>
512
513 <div class="entry">
514 <div class="title"><a href="http://people.skolelinux.org/pere/blog/NRKs_kildevern_n_r_NRK_epost_deles_med_utenlands_etterretning_.html">NRKs kildevern når NRK-epost deles med utenlands etterretning?</a></div>
515 <div class="date"> 8th October 2016</div>
516 <div class="body"><p>NRK
517 <a href="https://nrkbeta.no/2016/09/02/securing-whistleblowers/">lanserte
518 for noen uker siden</a> en ny
519 <a href="https://www.nrk.no/varsle/">varslerportal som bruker
520 SecureDrop til å ta imot tips</a> der det er vesentlig at ingen
521 utenforstående får vite at NRK er tipset. Det er et langt steg
522 fremover for NRK, og når en leser bloggposten om hva de har tenkt på
523 og hvordan løsningen er satt opp virker det som om de har gjort en
524 grundig jobb der. Men det er ganske mye ekstra jobb å motta tips via
525 SecureDrop, så varslersiden skriver "Nyhetstips som ikke krever denne
526 typen ekstra vern vil vi gjerne ha på nrk.no/03030", og 03030-siden
527 foreslår i tillegg til et webskjema å bruke epost, SMS, telefon,
528 personlig oppmøte og brevpost. Denne artikkelen handler disse andre
529 metodene.</p>
530
531 <p>Når en sender epost til en @nrk.no-adresse så vil eposten sendes ut
532 av landet til datamaskiner kontrollert av Microsoft. En kan sjekke
533 dette selv ved å slå opp epostleveringsadresse (MX) i DNS. For NRK er
534 dette i dag "nrk-no.mail.protection.outlook.com". NRK har som en ser
535 valgt å sette bort epostmottaket sitt til de som står bak outlook.com,
536 dvs. Microsoft. En kan sjekke hvor nettverkstrafikken tar veien
537 gjennom Internett til epostmottaket vha. programmet
538 <tt>traceroute</tt>, og finne ut hvem som eier en Internett-adresse
539 vha. whois-systemet. Når en gjør dette for epost-trafikk til @nrk.no
540 ser en at trafikken fra Norge mot nrk-no.mail.protection.outlook.com
541 går via Sverige mot enten Irland eller Tyskland (det varierer fra gang
542 til gang og kan endre seg over tid).</p>
543
544 <p>Vi vet fra
545 <a href="https://no.wikipedia.org/wiki/FRA-loven">introduksjonen av
546 FRA-loven</a> at IP-trafikk som passerer grensen til Sverige avlyttes
547 av Försvarets radioanstalt (FRA). Vi vet videre takket være
548 Snowden-bekreftelsene at trafikk som passerer grensen til
549 Storbritannia avlyttes av Government Communications Headquarters
550 (GCHQ). I tillegg er er det nettopp lansert et forslag i Norge om at
551 forsvarets E-tjeneste skal få avlytte trafikk som krysser grensen til
552 Norge. Jeg er ikke kjent med dokumentasjon på at Irland og Tyskland
553 gjør det samme. Poenget er uansett at utenlandsk etterretning har
554 mulighet til å snappe opp trafikken når en sender epost til @nrk.no.
555 I tillegg er det selvsagt tilgjengelig for Microsoft som er underlagt USAs
556 jurisdiksjon og
557 <a href="https://www.theguardian.com/world/2013/jul/11/microsoft-nsa-collaboration-user-data">samarbeider
558 med USAs etterretning på flere områder</a>. De som tipser NRK om
559 nyheter via epost kan dermed gå ut fra at det blir kjent for mange
560 andre enn NRK at det er gjort.</p>
561
562 <p>Bruk av SMS og telefon registreres av blant annet telefonselskapene
563 og er tilgjengelig i følge lov og forskrift for blant annet Politi,
564 NAV og Finanstilsynet, i tillegg til IT-folkene hos telefonselskapene
565 og deres overordnede. Hvis innringer eller mottaker bruker
566 smarttelefon vil slik kontakt også gjøres tilgjengelig for ulike
567 app-leverandører og de som lytter på trafikken mellom telefon og
568 app-leverandør, alt etter hva som er installert på telefonene som
569 brukes.</p>
570
571 <p>Brevpost kan virke trygt, og jeg vet ikke hvor mye som registreres
572 og lagres av postens datastyrte postsorteringssentraler. Det vil ikke
573 overraske meg om det lagres hvor i landet hver konvolutt kommer fra og
574 hvor den er adressert, i hvert fall for en kortere periode. Jeg vet
575 heller ikke hvem slik informasjon gjøres tilgjengelig for. Det kan
576 være nok til å ringe inn potensielle kilder når det krysses med hvem
577 som kjente til aktuell informasjon og hvor de befant seg (tilgjengelig
578 f.eks. hvis de bærer mobiltelefon eller bor i nærheten).</p>
579
580 <p>Personlig oppmøte hos en NRK-journalist er antagelig det tryggeste,
581 men en bør passe seg for å bruke NRK-kantina. Der bryter de nemlig
582 <a href="http://www.lovdata.no/all/hl-19850524-028.html#14">Sentralbanklovens
583 paragraf 14</a> og nekter folk å betale med kontanter. I stedet
584 krever de at en varsle sin bankkortutsteder om hvor en befinner seg
585 ved å bruke bankkort. Banktransaksjoner er tilgjengelig for
586 bankkortutsteder (det være seg VISA, Mastercard, Nets og/eller en
587 bank) i tillegg til politiet og i hvert fall tidligere med Se & Hør
588 (via utro tjenere, slik det ble avslørt etter utgivelsen av boken
589 «Livet, det forbannede» av Ken B. Rasmussen). Men hvor mange kjenner
590 en NRK-journalist personlig? Besøk på NRK på Marienlyst krever at en
591 registrerer sin ankost elektronisk i besøkssystemet. Jeg vet ikke hva
592 som skjer med det datasettet, men har grunn til å tro at det sendes ut
593 SMS til den en skal besøke med navnet som er oppgitt. Kanskje greit å
594 oppgi falskt navn.</p>
595
596 <p>Når så tipset er kommet frem til NRK skal det behandles
597 redaksjonelt i NRK. Der vet jeg via ulike kilder at de fleste
598 journalistene bruker lokalt installert programvare, men noen bruker
599 Google Docs og andre skytjenester i strid med interne retningslinjer
600 når de skriver. Hvordan vet en hvem det gjelder? Ikke vet jeg, men
601 det kan være greit å spørre for å sjekke at journalisten har tenkt på
602 problemstillingen, før en gir et tips. Og hvis tipset omtales internt
603 på epost, er det jo grunn til å tro at også intern eposten vil deles
604 med Microsoft og utenlands etterretning, slik tidligere nevnt, men det
605 kan hende at det holdes internt i NRKs interne MS Exchange-løsning.
606 Men Microsoft ønsker å få alle Exchange-kunder over "i skyen" (eller
607 andre folks datamaskiner, som det jo innebærer), så jeg vet ikke hvor
608 lenge det i så fall vil vare.</p>
609
610 <p>I tillegg vet en jo at
611 <a href="https://www.nrk.no/ytring/elektronisk-kildevern-i-nrk-1.11941196">NRK
612 har valgt å gi nasjonal sikkerhetsmyndighet (NSM) tilgang til å se på
613 intern og ekstern Internett-trafikk</a> hos NRK ved oppsett av såkalte
614 VDI-noder, på tross av
615 <a href="https://www.nrk.no/ytring/bekymring-for-nrks-kildevern-1.11941584">protester
616 fra NRKs journalistlag</a>. Jeg vet ikke om den vil kunne snappe opp
617 dokumenter som lagres på interne filtjenere eller dokumenter som lages
618 i de interne webbaserte publiseringssystemene, men vet at hva noden
619 ser etter på nettet kontrolleres av NSM og oppdateres automatisk, slik
620 at det ikke gir så mye mening å sjekke hva noden ser etter i dag når
621 det kan endres automatisk i morgen.</p>
622
623 <p>Personlig vet jeg ikke om jeg hadde turt tipse NRK hvis jeg satt på
624 noe som kunne være en trussel mot den bestående makten i Norge eller
625 verden. Til det virker det å være for mange åpninger for
626 utenforstående med andre prioriteter enn NRKs journalistiske fokus.
627 Og den største truslen for en varsler er jo om metainformasjon kommer
628 på avveie, dvs. informasjon om at en har vært i kontakt med en
629 journalist. Det kan være nok til at en kommer i myndighetenes
630 søkelys, og de færreste har nok operasjonell sikkerhet til at vil tåle
631 slik flombelysning på sitt privatliv.</p>
632 </div>
633 <div class="tags">
634
635
636 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/dld">dld</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>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
637
638
639 </div>
640 </div>
641 <div class="padding"></div>
642
643 <div class="entry">
644 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html">Isenkram, Appstream and udev make life as a LEGO builder easier</a></div>
645 <div class="date"> 7th October 2016</div>
646 <div class="body"><p><a href="http://packages.qa.debian.org/isenkram">The Isenkram
647 system</a> provide a practical and easy way to figure out which
648 packages support the hardware in a given machine. The command line
649 tool <tt>isenkram-lookup</tt> and the tasksel options provide a
650 convenient way to list and install packages relevant for the current
651 hardware during system installation, both user space packages and
652 firmware packages. The GUI background daemon on the other hand provide
653 a pop-up proposing to install packages when a new dongle is inserted
654 while using the computer. For example, if you plug in a smart card
655 reader, the system will ask if you want to install <tt>pcscd</tt> if
656 that package isn't already installed, and if you plug in a USB video
657 camera the system will ask if you want to install <tt>cheese</tt> if
658 cheese is currently missing. This already work just fine.</p>
659
660 <p>But Isenkram depend on a database mapping from hardware IDs to
661 package names. When I started no such database existed in Debian, so
662 I made my own data set and included it with the isenkram package and
663 made isenkram fetch the latest version of this database from git using
664 http. This way the isenkram users would get updated package proposals
665 as soon as I learned more about hardware related packages.</p>
666
667 <p>The hardware is identified using modalias strings. The modalias
668 design is from the Linux kernel where most hardware descriptors are
669 made available as a strings that can be matched using filename style
670 globbing. It handle USB, PCI, DMI and a lot of other hardware related
671 identifiers.</p>
672
673 <p>The downside to the Isenkram specific database is that there is no
674 information about relevant distribution / Debian version, making
675 isenkram propose obsolete packages too. But along came AppStream, a
676 cross distribution mechanism to store and collect metadata about
677 software packages. When I heard about the proposal, I contacted the
678 people involved and suggested to add a hardware matching rule using
679 modalias strings in the specification, to be able to use AppStream for
680 mapping hardware to packages. This idea was accepted and AppStream is
681 now a great way for a package to announce the hardware it support in a
682 distribution neutral way. I wrote
683 <a href="http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html">a
684 recipe on how to add such meta-information</a> in a blog post last
685 December. If you have a hardware related package in Debian, please
686 announce the relevant hardware IDs using AppStream.</p>
687
688 <p>In Debian, almost all packages that can talk to a LEGO Mindestorms
689 RCX or NXT unit, announce this support using AppStream. The effect is
690 that when you insert such LEGO robot controller into your Debian
691 machine, Isenkram will propose to install the packages needed to get
692 it working. The intention is that this should allow the local user to
693 start programming his robot controller right away without having to
694 guess what packages to use or which permissions to fix.</p>
695
696 <p>But when I sat down with my son the other day to program our NXT
697 unit using his Debian Stretch computer, I discovered something
698 annoying. The local console user (ie my son) did not get access to
699 the USB device for programming the unit. This used to work, but no
700 longer in Jessie and Stretch. After some investigation and asking
701 around on #debian-devel, I discovered that this was because udev had
702 changed the mechanism used to grant access to local devices. The
703 ConsoleKit mechanism from <tt>/lib/udev/rules.d/70-udev-acl.rules</tt>
704 no longer applied, because LDAP users no longer was added to the
705 plugdev group during login. Michael Biebl told me that this method
706 was obsolete and the new method used ACLs instead. This was good
707 news, as the plugdev mechanism is a mess when using a remote user
708 directory like LDAP. Using ACLs would make sure a user lost device
709 access when she logged out, even if the user left behind a background
710 process which would retain the plugdev membership with the ConsoleKit
711 setup. Armed with this knowledge I moved on to fix the access problem
712 for the LEGO Mindstorms related packages.</p>
713
714 <p>The new system uses a udev tag, 'uaccess'. It can either be
715 applied directly for a device, or is applied in
716 /lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
717 LEGO Mindstorms udev rules did not have a class, I decided to add the
718 tag directly in the udev rules files included in the packages. Here
719 is one example. For the nqc C compiler for the RCX, the
720 <tt>/lib/udev/rules.d/60-nqc.rules</tt> file now look like this:
721
722 <p><pre>
723 SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="0694", ATTR{idProduct}=="0001", \
724 SYMLINK+="rcx-%k", TAG+="uaccess"
725 </pre></p>
726
727 <p>The key part is the 'TAG+="uaccess"' at the end. I suspect all
728 packages using plugdev in their /lib/udev/rules.d/ files should be
729 changed to use this tag (either directly or indirectly via
730 <tt>70-uaccess.rules</tt>). Perhaps a lintian check should be created
731 to detect this?</p>
732
733 <p>I've been unable to find good documentation on the uaccess feature.
734 It is unclear to me if the uaccess tag is an internal implementation
735 detail like the udev-acl tag used by
736 <tt>/lib/udev/rules.d/70-udev-acl.rules</tt>. If it is, I guess the
737 indirect method is the preferred way. Michael
738 <a href="https://github.com/systemd/systemd/issues/4288">asked for more
739 documentation from the systemd project</a> and I hope it will make
740 this clearer. For now I use the generic classes when they exist and
741 is already handled by <tt>70-uaccess.rules</tt>, and add the tag
742 directly if no such class exist.</p>
743
744 <p>To learn more about the isenkram system, please check out
745 <a href="http://people.skolelinux.org/pere/blog/tags/isenkram/">my
746 blog posts tagged isenkram</a>.</p>
747
748 <p>To help out making life for LEGO constructors in Debian easier,
749 please join us on our IRC channel
750 <a href="irc://irc.debian.org/%23debian-lego">#debian-lego</a> and join
751 the <a href="https://alioth.debian.org/projects/debian-lego/">Debian
752 LEGO team</a> in the Alioth project we created yesterday. A mailing
753 list is not yet created, but we are working on it. :)</p>
754
755 <p>As usual, if you use Bitcoin and want to show your support of my
756 activities, please send Bitcoin donations to my address
757 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&label=PetterReinholdtsenBlog">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
758 </div>
759 <div class="tags">
760
761
762 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/isenkram">isenkram</a>.
763
764
765 </div>
766 </div>
767 <div class="padding"></div>
768
769 <div class="entry">
770 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Aftenposten_redakt_ren_med_lua_i_h_nda.html">Aftenposten-redaktøren med lua i hånda</a></div>
771 <div class="date"> 9th September 2016</div>
772 <div class="body"><p>En av dagens nyheter er at Aftenpostens redaktør Espen Egil Hansen
773 bruker
774 <a href="https://www.nrk.no/kultur/aftenposten-brukar-heile-forsida-pa-facebook-kritikk-1.13126918">forsiden
775 av papiravisen på et åpent brev til Facebooks sjef Mark Zuckerberg om
776 Facebooks fjerning av bilder, tekster og sider de ikke liker</a>. Det
777 må være uvant for redaktøren i avisen Aftenposten å stå med lua i
778 handa og håpe på å bli hørt. Spesielt siden Aftenposten har vært med
779 på å gi Facebook makten de nå demonstrerer at de har. Ved å melde seg
780 inn i Facebook-samfunnet har de sagt ja til bruksvilkårene og inngått
781 en antagelig bindende avtale. Kanskje de skulle lest og vurdert
782 vilkårene litt nærmere før de sa ja, i stedet for å klage over at
783 reglende de har valgt å akseptere blir fulgt? Personlig synes jeg
784 vilkårene er uakseptable og det ville ikke falle meg inn å gå inn på
785 en avtale med slike vilkår. I tillegg til uakseptable vilkår er det
786 mange andre grunner til å unngå Facebook. Du kan finne en solid
787 gjennomgang av flere slike argumenter hos
788 <a href="https://stallman.org/facebook.html">Richard Stallmans side om
789 Facebook</a>.
790
791 <p>Jeg håper flere norske redaktører på samme vis må stå med lua i
792 hånden inntil de forstår at de selv er med på å føre samfunnet på
793 ville veier ved å omfavne Facebook slik de gjør når de omtaler og
794 løfter frem saker fra Facebook, og tar i bruk Facebook som
795 distribusjonskanal for sine nyheter. De bidrar til
796 overvåkningssamfunnet og raderer ut lesernes privatsfære når de lenker
797 til Facebook på sine sider, og låser seg selv inne i en omgivelse der
798 det er Facebook, og ikke redaktøren, som sitter med makta.</p>
799
800 <p>Men det vil nok ta tid, i et Norge der de fleste nettredaktører
801 <a href="http://people.skolelinux.org/pere/blog/Snurpenot_overv_kning_av_sensitiv_personinformasjon.html">deler
802 sine leseres personopplysinger med utenlands etterretning</a>.</p>
803
804 <p>For øvrig burde varsleren Edward Snowden få politisk asyl i
805 Norge.</p>
806 </div>
807 <div class="tags">
808
809
810 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
811
812
813 </div>
814 </div>
815 <div class="padding"></div>
816
817 <div class="entry">
818 <div class="title"><a href="http://people.skolelinux.org/pere/blog/E_tjenesten_ber_om_innsyn_i_eposten_til_partiene_p__Stortinget.html">E-tjenesten ber om innsyn i eposten til partiene på Stortinget</a></div>
819 <div class="date"> 6th September 2016</div>
820 <div class="body"><p>I helga kom det et hårreisende forslag fra Lysne II-utvalget satt
821 ned av Forsvarsdepartementet. Lysne II-utvalget var bedt om å vurdere
822 ønskelista til Forsvarets etterretningstjeneste (e-tjenesten), og har
823 kommet med
824 <a href="http://www.aftenposten.no/norge/Utvalg-sier-ja-til-at-E-tjenesten-far-overvake-innholdet-i-all-internett--og-telefontrafikk-som-krysser-riksgrensen-603232b.html">forslag
825 om at e-tjenesten skal få lov til a avlytte all Internett-trafikk</a>
826 som passerer Norges grenser. Få er klar over at dette innebærer at
827 e-tjenesten får tilgang til epost sendt til de fleste politiske
828 partiene på Stortinget. Regjeringspartiet Høyre (@hoyre.no),
829 støttepartiene Venstre (@venstre.no) og Kristelig Folkeparti (@krf.no)
830 samt Sosialistisk Ventreparti (@sv.no) og Miljøpartiet de grønne
831 (@mdg.no) har nemlig alle valgt å ta imot eposten sin via utenlandske
832 tjenester. Det betyr at hvis noen sender epost til noen med en slik
833 adresse vil innholdet i eposten, om dette forslaget blir vedtatt, gjøres
834 tilgjengelig for e-tjenesten. Venstre, Sosialistisk Ventreparti og
835 Miljøpartiet De Grønne har valgt å motta sin epost hos Google,
836 Kristelig Folkeparti har valgt å motta sin epost hos Microsoft, og
837 Høyre har valgt å motta sin epost hos Comendo med mottak i Danmark og
838 Irland. Kun Arbeiderpartiet og Fremskrittspartiet har valgt å motta
839 eposten sin i Norge, hos henholdsvis Intility AS og Telecomputing
840 AS.</p>
841
842 <p>Konsekvensen er at epost inn og ut av de politiske organisasjonene,
843 til og fra partimedlemmer og partiets tillitsvalgte vil gjøres
844 tilgjengelig for e-tjenesten for analyse og sortering. Jeg mistenker
845 at kunnskapen som slik blir tilgjengelig vil være nyttig hvis en
846 ønsker å vite hvilke argumenter som treffer publikum når en ønsker å
847 påvirke Stortingets representanter.</p
848
849 <p>Ved hjelp av MX-oppslag i DNS for epost-domene, tilhørende
850 whois-oppslag av IP-adressene og traceroute for å se hvorvidt
851 trafikken går via utlandet kan enhver få bekreftet at epost sendt til
852 de omtalte partiene vil gjøres tilgjengelig for forsvarets
853 etterretningstjeneste hvis forslaget blir vedtatt. En kan også bruke
854 den kjekke nett-tjenesten <a href="http://ipinfo.io/">ipinfo.io</a>
855 for å få en ide om hvor i verden en IP-adresse hører til.</p>
856
857 <p>På den positive siden vil forslaget gjøre at enda flere blir
858 motivert til å ta grep for å bruke
859 <a href="https://www.torproject.org/">Tor</a> og krypterte
860 kommunikasjonsløsninger for å kommunisere med sine kjære, for å sikre
861 at privatsfæren vernes. Selv bruker jeg blant annet
862 <a href="https://www.freedomboxfoundation.org/">FreedomBox</a> og
863 <a href="https://whispersystems.org/">Signal</a> til slikt. Ingen av
864 dem er optimale, men de fungerer ganske bra allerede og øker kostnaden
865 for dem som ønsker å invadere mitt privatliv.</p>
866
867 <p>For øvrig burde varsleren Edward Snowden få politisk asyl i
868 Norge.</p>
869
870 <!--
871
872 venstre.no
873 venstre.no mail is handled by 10 aspmx.l.google.com.
874 venstre.no mail is handled by 20 alt1.aspmx.l.google.com.
875 venstre.no mail is handled by 20 alt2.aspmx.l.google.com.
876 venstre.no mail is handled by 30 aspmx2.googlemail.com.
877 venstre.no mail is handled by 30 aspmx3.googlemail.com.
878
879 traceroute to aspmx.l.google.com (173.194.222.27), 30 hops max, 60 byte packets
880 1 uio-gw10.uio.no (129.240.6.1) 0.411 ms 0.438 ms 0.536 ms
881 2 uio-gw8.uio.no (129.240.24.229) 0.375 ms 0.452 ms 0.548 ms
882 3 oslo-gw1.uninett.no (128.39.65.17) 1.940 ms 1.950 ms 1.942 ms
883 4 se-tug.nordu.net (109.105.102.108) 6.910 ms 6.949 ms 7.283 ms
884 5 google-gw.nordu.net (109.105.98.6) 6.975 ms 6.967 ms 6.958 ms
885 6 209.85.250.192 (209.85.250.192) 7.337 ms 7.286 ms 10.890 ms
886 7 209.85.254.13 (209.85.254.13) 7.394 ms 209.85.254.31 (209.85.254.31) 7.586 ms 209.85.254.33 (209.85.254.33) 7.570 ms
887 8 209.85.251.255 (209.85.251.255) 15.686 ms 209.85.249.229 (209.85.249.229) 16.118 ms 209.85.251.255 (209.85.251.255) 16.073 ms
888 9 74.125.37.255 (74.125.37.255) 16.794 ms 216.239.40.248 (216.239.40.248) 16.113 ms 74.125.37.44 (74.125.37.44) 16.764 ms
889 10 * * *
890
891 mdg.no
892 mdg.no mail is handled by 1 aspmx.l.google.com.
893 mdg.no mail is handled by 5 alt2.aspmx.l.google.com.
894 mdg.no mail is handled by 5 alt1.aspmx.l.google.com.
895 mdg.no mail is handled by 10 aspmx2.googlemail.com.
896 mdg.no mail is handled by 10 aspmx3.googlemail.com.
897 sv.no
898 sv.no mail is handled by 1 aspmx.l.google.com.
899 sv.no mail is handled by 5 alt1.aspmx.l.google.com.
900 sv.no mail is handled by 5 alt2.aspmx.l.google.com.
901 sv.no mail is handled by 10 aspmx3.googlemail.com.
902 sv.no mail is handled by 10 aspmx2.googlemail.com.
903 hoyre.no
904 hoyre.no mail is handled by 10 hoyre-no.mx1.comendosystems.com.
905 hoyre.no mail is handled by 20 hoyre-no.mx2.comendosystems.net.
906
907 traceroute to hoyre-no.mx1.comendosystems.com (89.104.206.4), 30 hops max, 60 byte packets
908 1 uio-gw10.uio.no (129.240.6.1) 0.450 ms 0.510 ms 0.591 ms
909 2 uio-gw8.uio.no (129.240.24.229) 0.383 ms 0.508 ms 0.596 ms
910 3 oslo-gw1.uninett.no (128.39.65.17) 0.311 ms 0.315 ms 0.300 ms
911 4 se-tug.nordu.net (109.105.102.108) 6.837 ms 6.842 ms 6.834 ms
912 5 dk-uni.nordu.net (109.105.97.10) 26.073 ms 26.085 ms 26.076 ms
913 6 dix.1000m.soeborg.ip.comendo.dk (192.38.7.22) 15.372 ms 15.046 ms 15.123 ms
914 7 89.104.192.65 (89.104.192.65) 15.875 ms 15.990 ms 16.239 ms
915 8 89.104.192.179 (89.104.192.179) 15.676 ms 15.674 ms 15.664 ms
916 9 03dm-com.mx1.staysecuregroup.com (89.104.206.4) 15.637 ms * *
917
918 krf.no
919 krf.no mail is handled by 10 krf-no.mail.protection.outlook.com.
920
921 traceroute to krf-no.mail.protection.outlook.com (213.199.154.42), 30 hops max, 60 byte packets
922 1 uio-gw10.uio.no (129.240.6.1) 0.401 ms 0.438 ms 0.536 ms
923 2 uio-gw8.uio.no (129.240.24.229) 11.076 ms 11.120 ms 11.204 ms
924 3 oslo-gw1.uninett.no (128.39.65.17) 0.232 ms 0.234 ms 0.271 ms
925 4 se-tug.nordu.net (109.105.102.108) 6.811 ms 6.820 ms 6.815 ms
926 5 netnod-ix-ge-a-sth-4470.microsoft.com (195.245.240.181) 7.074 ms 7.013 ms 7.061 ms
927 6 ae1-0.sto-96cbe-1b.ntwk.msn.net (104.44.225.161) 7.227 ms 7.362 ms 7.293 ms
928 7 be-8-0.ibr01.ams.ntwk.msn.net (104.44.5.7) 41.993 ms 43.334 ms 41.939 ms
929 8 be-1-0.ibr02.ams.ntwk.msn.net (104.44.4.214) 43.153 ms 43.507 ms 43.404 ms
930 9 ae3-0.fra-96cbe-1b.ntwk.msn.net (104.44.5.17) 29.897 ms 29.831 ms 29.794 ms
931 10 ae10-0.vie-96cbe-1a.ntwk.msn.net (198.206.164.1) 42.309 ms 42.130 ms 41.808 ms
932 11 * ae8-0.vie-96cbe-1b.ntwk.msn.net (104.44.227.29) 41.425 ms *
933 12 * * *
934
935 arbeiderpartiet.no
936 arbeiderpartiet.no mail is handled by 10 mail.intility.com.
937 arbeiderpartiet.no mail is handled by 20 mail2.intility.com.
938
939 traceroute to mail.intility.com (188.95.245.87), 30 hops max, 60 byte packets
940 1 uio-gw10.uio.no (129.240.6.1) 0.486 ms 0.508 ms 0.649 ms
941 2 uio-gw8.uio.no (129.240.24.229) 0.416 ms 0.508 ms 0.620 ms
942 3 oslo-gw1.uninett.no (128.39.65.17) 0.276 ms 0.278 ms 0.275 ms
943 4 te3-1-2.br1.fn3.as2116.net (193.156.90.3) 0.374 ms 0.371 ms 0.416 ms
944 5 he16-1-1.cr1.san110.as2116.net (195.0.244.234) 3.132 ms he16-1-1.cr2.oslosda310.as2116.net (195.0.244.48) 10.079 ms he16-1-1.cr1.san110.as2116.net (195.0.244.234) 3.353 ms
945 6 te1-2-0.ar2.ulv89.as2116.net (195.0.243.194) 0.569 ms te5-0-0.ar2.ulv89.as2116.net (195.0.243.192) 0.661 ms 0.653 ms
946 7 cD2EC45C1.static.as2116.net (193.69.236.210) 0.654 ms 0.615 ms 0.590 ms
947 8 185.7.132.38 (185.7.132.38) 1.661 ms 1.808 ms 1.695 ms
948 9 185.7.132.100 (185.7.132.100) 1.793 ms 1.943 ms 1.546 ms
949 10 * * *
950
951 frp.no
952 frp.no mail is handled by 10 mx03.telecomputing.no.
953 frp.no mail is handled by 20 mx01.telecomputing.no.
954
955 traceroute to mx03.telecomputing.no (95.128.105.102), 30 hops max, 60 byte packets
956 1 uio-gw10.uio.no (129.240.6.1) 0.378 ms 0.402 ms 0.479 ms
957 2 uio-gw8.uio.no (129.240.24.229) 0.361 ms 0.458 ms 0.548 ms
958 3 oslo-gw1.uninett.no (128.39.65.17) 0.361 ms 0.352 ms 0.336 ms
959 4 xe-2-2-0-0.san-peer2.osl.no.ip.tdc.net (193.156.90.16) 0.375 ms 0.366 ms 0.346 ms
960 5 xe-2-0-2-0.ost-pe1.osl.no.ip.tdc.net (85.19.121.97) 0.780 ms xe-2-0-0-0.ost-pe1.osl.no.ip.tdc.net (85.19.121.101) 0.713 ms xe-2-0-2-0.ost-pe1.osl.no.ip.tdc.net (85.19.121.97) 0.759 ms
961 6 cpe.xe-0-2-0-100.ost-pe1.osl.no.customer.tdc.net (85.19.26.46) 0.837 ms 0.755 ms 0.759 ms
962 7 95.128.105.3 (95.128.105.3) 1.050 ms 1.288 ms 1.182 ms
963 8 mx03.telecomputing.no (95.128.105.102) 0.717 ms 0.703 ms 0.692 ms
964
965 -->
966 </div>
967 <div class="tags">
968
969
970 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
971
972
973 </div>
974 </div>
975 <div class="padding"></div>
976
977 <div class="entry">
978 <div class="title"><a href="http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html">First draft Norwegian Bokmål edition of The Debian Administrator's Handbook now public</a></div>
979 <div class="date">30th August 2016</div>
980 <div class="body"><p>In April we
981 <a href="http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html">started
982 to work</a> on a Norwegian Bokmål edition of the "open access" book on
983 how to set up and administrate a Debian system. Today I am happy to
984 report that the first draft is now publicly available. You can find
985 it on <a href="https://debian-handbook.info/get/">get the Debian
986 Administrator's Handbook page</a> (under Other languages). The first
987 eight chapters have a first draft translation, and we are working on
988 proofreading the content. If you want to help out, please start
989 contributing using
990 <a href="https://hosted.weblate.org/projects/debian-handbook/">the
991 hosted weblate project page</a>, and get in touch using
992 <a href="http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators">the
993 translators mailing list</a>. Please also check out
994 <a href="https://debian-handbook.info/contribute/">the instructions for
995 contributors</a>. A good way to contribute is to proofread the text
996 and update weblate if you find errors.</p>
997
998 <p>Our goal is still to make the Norwegian book available on paper as well as
999 electronic form.</p>
1000 </div>
1001 <div class="tags">
1002
1003
1004 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>.
1005
1006
1007 </div>
1008 </div>
1009 <div class="padding"></div>
1010
1011 <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>
1012 <div id="sidebar">
1013
1014
1015
1016 <h2>Archive</h2>
1017 <ul>
1018
1019 <li>2016
1020 <ul>
1021
1022 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/01/">January (3)</a></li>
1023
1024 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/02/">February (2)</a></li>
1025
1026 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/03/">March (3)</a></li>
1027
1028 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/04/">April (8)</a></li>
1029
1030 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/05/">May (8)</a></li>
1031
1032 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/06/">June (2)</a></li>
1033
1034 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/07/">July (2)</a></li>
1035
1036 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/08/">August (5)</a></li>
1037
1038 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/09/">September (2)</a></li>
1039
1040 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/10/">October (3)</a></li>
1041
1042 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/11/">November (4)</a></li>
1043
1044 </ul></li>
1045
1046 <li>2015
1047 <ul>
1048
1049 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/01/">January (7)</a></li>
1050
1051 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/02/">February (6)</a></li>
1052
1053 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/03/">March (1)</a></li>
1054
1055 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/04/">April (4)</a></li>
1056
1057 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/05/">May (3)</a></li>
1058
1059 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/06/">June (4)</a></li>
1060
1061 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/07/">July (6)</a></li>
1062
1063 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/08/">August (2)</a></li>
1064
1065 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/09/">September (2)</a></li>
1066
1067 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/10/">October (9)</a></li>
1068
1069 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/11/">November (6)</a></li>
1070
1071 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/12/">December (3)</a></li>
1072
1073 </ul></li>
1074
1075 <li>2014
1076 <ul>
1077
1078 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
1079
1080 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
1081
1082 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
1083
1084 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/04/">April (7)</a></li>
1085
1086 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/05/">May (1)</a></li>
1087
1088 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/06/">June (2)</a></li>
1089
1090 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/07/">July (2)</a></li>
1091
1092 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/08/">August (2)</a></li>
1093
1094 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/09/">September (5)</a></li>
1095
1096 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/10/">October (6)</a></li>
1097
1098 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/11/">November (3)</a></li>
1099
1100 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/12/">December (5)</a></li>
1101
1102 </ul></li>
1103
1104 <li>2013
1105 <ul>
1106
1107 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
1108
1109 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
1110
1111 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
1112
1113 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
1114
1115 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
1116
1117 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
1118
1119 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
1120
1121 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
1122
1123 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
1124
1125 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
1126
1127 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
1128
1129 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
1130
1131 </ul></li>
1132
1133 <li>2012
1134 <ul>
1135
1136 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
1137
1138 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
1139
1140 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
1141
1142 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
1143
1144 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
1145
1146 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
1147
1148 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
1149
1150 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
1151
1152 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
1153
1154 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
1155
1156 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
1157
1158 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
1159
1160 </ul></li>
1161
1162 <li>2011
1163 <ul>
1164
1165 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
1166
1167 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
1168
1169 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
1170
1171 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
1172
1173 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
1174
1175 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
1176
1177 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
1178
1179 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
1180
1181 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
1182
1183 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
1184
1185 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
1186
1187 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
1188
1189 </ul></li>
1190
1191 <li>2010
1192 <ul>
1193
1194 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
1195
1196 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
1197
1198 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
1199
1200 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
1201
1202 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
1203
1204 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
1205
1206 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
1207
1208 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
1209
1210 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
1211
1212 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
1213
1214 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
1215
1216 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
1217
1218 </ul></li>
1219
1220 <li>2009
1221 <ul>
1222
1223 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
1224
1225 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
1226
1227 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
1228
1229 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
1230
1231 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
1232
1233 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
1234
1235 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
1236
1237 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
1238
1239 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
1240
1241 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
1242
1243 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
1244
1245 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
1246
1247 </ul></li>
1248
1249 <li>2008
1250 <ul>
1251
1252 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
1253
1254 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
1255
1256 </ul></li>
1257
1258 </ul>
1259
1260
1261
1262 <h2>Tags</h2>
1263 <ul>
1264
1265 <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
1266
1267 <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
1268
1269 <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
1270
1271 <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
1272
1273 <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (9)</a></li>
1274
1275 <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (16)</a></li>
1276
1277 <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
1278
1279 <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
1280
1281 <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (139)</a></li>
1282
1283 <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (157)</a></li>
1284
1285 <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
1286
1287 <li><a href="http://people.skolelinux.org/pere/blog/tags/dld">dld (16)</a></li>
1288
1289 <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (23)</a></li>
1290
1291 <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
1292
1293 <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (332)</a></li>
1294
1295 <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
1296
1297 <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
1298
1299 <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (28)</a></li>
1300
1301 <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
1302
1303 <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (18)</a></li>
1304
1305 <li><a href="http://people.skolelinux.org/pere/blog/tags/h264">h264 (20)</a></li>
1306
1307 <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (42)</a></li>
1308
1309 <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (13)</a></li>
1310
1311 <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (19)</a></li>
1312
1313 <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
1314
1315 <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (8)</a></li>
1316
1317 <li><a href="http://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd (2)</a></li>
1318
1319 <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1320
1321 <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
1322
1323 <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (39)</a></li>
1324
1325 <li><a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (8)</a></li>
1326
1327 <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (280)</a></li>
1328
1329 <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (182)</a></li>
1330
1331 <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (26)</a></li>
1332
1333 <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1334
1335 <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (61)</a></li>
1336
1337 <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (95)</a></li>
1338
1339 <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
1340
1341 <li><a href="http://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
1342
1343 <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1344
1345 <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
1346
1347 <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (10)</a></li>
1348
1349 <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1350
1351 <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
1352
1353 <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1354
1355 <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (52)</a></li>
1356
1357 <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1358
1359 <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (5)</a></li>
1360
1361 <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (49)</a></li>
1362
1363 <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (4)</a></li>
1364
1365 <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (10)</a></li>
1366
1367 <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (43)</a></li>
1368
1369 <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (2)</a></li>
1370
1371 <li><a href="http://people.skolelinux.org/pere/blog/tags/usenix">usenix (2)</a></li>
1372
1373 <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
1374
1375 <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (59)</a></li>
1376
1377 <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
1378
1379 <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (38)</a></li>
1380
1381 </ul>
1382
1383
1384 </div>
1385 <p style="text-align: right">
1386 Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
1387 </p>
1388
1389 </body>
1390 </html>
Nettsider og blogg.