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