<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html">Creating, updating and checking debian/copyright semi-automatically</a></div>
- <div class="date">19th February 2016</div>
- <div class="body"><p>Making packages for Debian requires quite a lot of attention to
-details. And one of the details is the content of the
-debian/copyright file, which should list all relevant licenses used by
-the code in the package in question, preferably in
-<a href="https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/">machine
-readable DEP5 format</a>.</p>
-
-<p>For large packages with lots of contributors it is hard to write
-and update this file manually, and if you get some detail wrong, the
-package is normally rejected by the ftpmasters. So getting it right
-the first time around get the package into Debian faster, and save
-both you and the ftpmasters some work.. Today, while trying to figure
-out what was wrong with
-<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447">the
-zfsonlinux copyright file</a>, I decided to spend some time on
-figuring out the options for doing this job automatically, or at least
-semi-automatically.</p>
-
-<p>Lucikly, there are at least two tools available for generating the
-file based on the code in the source package,
-<tt><a href="https://tracker.debian.org/pkg/debmake">debmake</a></tt>
-and <tt><a href="https://tracker.debian.org/pkg/cme">cme</a></tt>. I'm
-not sure which one of them came first, but both seem to be able to
-create a sensible draft file. As far as I can tell, none of them can
-be trusted to get the result just right, so the content need to be
-polished a bit before the file is OK to upload. I found the debmake
-option in
-<a href="http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html">a
-blog posts from 2014</a>.
-
-<p>To generate using debmake, use the -cc option:
+ <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>
+ <div class="date"> 3rd November 2016</div>
+ <div class="body"><p>Jeg ble så imponert over
+<a href="https://www.nrk.no/norge/forbrukerradet-mener-aktivitetsarmband-strider-mot-norsk-lov-1.13209079">dagens
+gladnyhet på NRK</a>, om at Forbrukerrådet klager inn vilkårene for
+bruk av aktivitetsbånd fra Fitbit, Garmin, Jawbone og Mio til
+Datatilsynet og forbrukerombudet, at jeg sendte følgende brev til
+forbrukerrådet for å uttrykke min støtte:
-<p><pre>
-debmake -cc > debian/copyright
-</pre></p>
-
-<p>Note there are some problems with python and non-ASCII names, so
-this might not be the best option.</p>
-
-<p>The cme option is based on a config parsing library, and I found
-this approach in
-<a href="https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/">a
-blog post from 2015</a>. To generate using cme, use the 'update
-dpkg-copyright' option:
-
-<p><pre>
-cme update dpkg-copyright
-</pre></p>
-
-<p>This will create or update debian/copyright. The cme tool seem to
-handle UTF-8 names better than debmake.</p>
-
-<p>When the copyright file is created, I would also like some help to
-check if the file is correct. For this I found two good options,
-<tt>debmake -k</tt> and <tt>license-reconcile</tt>. The former seem
-to focus on license types and file matching, and is able to detect
-ineffective blocks in the copyright file. The latter reports missing
-copyright holders and years, but was confused by inconsistent license
-names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
-fix all issues reported by them before uploading. But I do not know
-if the tools and the ftpmasters agree on what is important to fix in a
-copyright file, so the package might still be rejected.</p>
-
-<p>The devscripts tool <tt>licensecheck</tt> deserve mentioning. It
-will read through the source and try to find all copyright statements.
-It is not comparing the result to the content of debian/copyright, but
-can be useful when verifying the content of the copyright file.</p>
-
-<p>Are you aware of better tools in Debian to create and update
-debian/copyright file. Please let me know, or blog about it on
-planet.debian.org.</p>
-
-<p>As usual, if you use Bitcoin and want to show your support of my
-activities, please send Bitcoin donations to my address
-<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
+<blockquote>
-<p><strong>Update 2016-02-20</strong>: I got a tip from Mike Gabriel
-on how to use licensecheck and cdbs to create a draft copyright file
+<p>Jeg ble veldig glad over å lese at Forbrukerrådet
+<a href="http://www.forbrukerradet.no/siste-nytt/klager-inn-aktivitetsarmband-for-brudd-pa-norsk-lov/">klager
+inn flere aktivitetsbånd til Datatilsynet for dårlige vilkår</a>. Jeg
+har ønsket meg et aktivitetsbånd som kan måle puls, bevegelse og
+gjerne også andre helserelaterte indikatorer en stund nå. De eneste
+jeg har funnet i salg gjør, som dere også har oppdaget, graverende
+inngrep i privatsfæren og sender informasjonen ut av huset til folk og
+organisasjoner jeg ikke ønsker å dele aktivitets- og helseinformasjon
+med. Jeg ønsker et alternativ som _ikke_ sender informasjon til
+skyen, men derimot bruker
+<a href="http://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html">en
+fritt og åpent standardisert</a> protokoll (eller i det minste en
+dokumentert protokoll uten patent- og opphavsrettslige
+bruksbegrensinger) til å kommunisere med datautstyr jeg kontrollerer.
+Er jo ikke interessert i å betale noen for å tilrøve seg
+personopplysninger fra meg. Desverre har jeg ikke funnet noe
+alternativ så langt.</p>
+
+<p>Det holder ikke å endre på bruksvilkårene for enhetene, slik
+Datatilsynet ofte legger opp til i sin behandling, når de gjør slik
+f.eks. Fitbit (den jeg har sett mest på). Fitbit krypterer
+informasjonen på enheten og sender den kryptert til leverandøren. Det
+gjør det i praksis umulig både å sjekke hva slags informasjon som
+sendes over, og umulig å ta imot informasjonen selv i stedet for
+Fitbit. Uansett hva slags historie som forteller i bruksvilkårene er
+en jo både prisgitt leverandørens godvilje og at de ikke tvinges av
+sitt lands myndigheter til å lyve til sine kunder om hvorvidt
+personopplysninger spres ut over det bruksvilkårene sier. Det er
+veldokumentert hvordan f.eks. USA tvinger selskaper vha. såkalte
+National security letters til å utlevere personopplysninger samtidig
+som de ikke får lov til å fortelle dette til kundene sine.</p>
+
+<p>Stå på, jeg er veldig glade for at dere har sett på saken. Vet
+dere om aktivitetsbånd i salg i dag som ikke tvinger en til å utlevere
+aktivitets- og helseopplysninger med leverandøren?</p>
-<p><pre>
-licensecheck --copyright -r `find * -type f` | \
- /usr/lib/cdbs/licensecheck2dep5 > debian/copyright.auto
-</pre></p>
-
-<p>He mentioned that he normally check the generated file into the
-version control system to make it easier to discover license and
-copyright changes in the upstream source. I will try to do the same
-with my packages in the future.</p>
+</blockquote>
-<p><strong>Update 2016-02-21</strong>: The cme author recommended
-against using -quiet for new users, so I removed it from the proposed
-command line.</p>
+<p>Jeg håper en konkurrent som respekterer kundenes privatliv klarer å
+nå opp i markedet, slik at det finnes et reelt alternativ for oss som
+har full tillit til at skyleverandører vil prioritere egen inntjening
+og myndighetspålegg langt over kundenes rett til privatliv. Jeg har
+ingen tiltro til at Datatilsynet vil kreve noe mer enn at vilkårene
+endres slik at de forklarer eksplisitt i hvor stor grad bruk av
+produktene utraderer privatsfæren til kundene. Det vil nok gjøre de
+innklagede armbåndene "lovlige", men fortsatt tvinge kundene til å
+dele sine personopplysninger med leverandøren.</p>
</div>
<div class="tags">
- 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>.
+ 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>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html">Using appstream in Debian to locate packages with firmware and mime type support</a></div>
- <div class="date"> 4th February 2016</div>
- <div class="body"><p>The <a href="https://wiki.debian.org/DEP-11">appstream system</a>
-is taking shape in Debian, and one provided feature is a very
-convenient way to tell you which package to install to make a given
-firmware file available when the kernel is looking for it. This can
-be done using apt-file too, but that is for someone else to blog
-about. :)</p>
-
-<p>Here is a small recipe to find the package with a given firmware
-file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
-picked from the set of firmware announced using appstream in Debian
-unstable. In general you would be looking for the firmware requested
-by the kernel during kernel module loading. To find the package
-providing the example file, do like this:</p>
-
-<blockquote><pre>
-% apt install appstream
-[...]
-% apt update
-[...]
-% appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
- awk '/Package:/ {print $2}'
-firmware-qlogic
-%
-</pre></blockquote>
-
-<p>See <a href="https://wiki.debian.org/AppStream/Guidelines">the
-appstream wiki</a> page to learn how to embed the package metadata in
-a way appstream can use.</p>
-
-<p>This same approach can be used to find any package supporting a
-given MIME type. This is very useful when you get a file you do not
-know how to handle. First find the mime type using <tt>file
---mime-type</tt>, and next look up the package providing support for
-it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
-and you can find all packages handling this type like this:</p>
-
-<blockquote><pre>
-% apt install appstream
-[...]
-% apt update
-[...]
-% appstreamcli what-provides mimetype image/svg+xml | \
- awk '/Package:/ {print $2}'
-bkchem
-phototonic
-inkscape
-shutter
-tetzle
-geeqie
-xia
-pinta
-gthumb
-karbon
-comix
-mirage
-viewnior
-postr
-ristretto
-kolourpaint4
-eog
-eom
-gimagereader
-midori
-%
-</pre></blockquote>
-
-<p>I believe the MIME types are fetched from the desktop file for
-packages providing appstream metadata.</p>
+ <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>
+ <div class="date">10th October 2016</div>
+ <div class="body"><p>In July
+<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
+wrote how to get the Signal Chrome/Chromium app working</a> without
+the ability to receive SMS messages (aka without a cell phone). It is
+time to share some experiences and provide an updated setup.</p>
+
+<p>The Signal app have worked fine for several months now, and I use
+it regularly to chat with my loved ones. I had a major snag at the
+end of my summer vacation, when the the app completely forgot my
+setup, identity and keys. The reason behind this major mess was
+running out of disk space. To avoid that ever happening again I have
+started storing everything in <tt>userdata/</tt> in git, to be able to
+roll back to an earlier version if the files are wiped by mistake. I
+had to use it once after introducing the git backup. When rolling
+back to an earlier version, one need to use the 'reset session' option
+in Signal to get going, and notify the people you talk with about the
+problem. I assume there is some sequence number tracking in the
+protocol to detect rollback attacks. The git repository is rather big
+(674 MiB so far), but I have not tried to figure out if some of the
+content can be added to a .gitignore file due to lack of spare
+time.</p>
+
+<p>I've also hit the 90 days timeout blocking, and noticed that this
+make it impossible to send messages using Signal. I could still
+receive them, but had to patch the code with a new timestamp to send.
+I believe the timeout is added by the developers to force people to
+upgrade to the latest version of the app, even when there is no
+protocol changes, to reduce the version skew among the user base and
+thus try to keep the number of support requests down.</p>
+
+<p>Since my original recipe, the Signal source code changed slightly,
+making the old patch fail to apply cleanly. Below is an updated
+patch, including the shell wrapper I use to start Signal. The
+original version required a new user to locate the JavaScript console
+and call a function from there. I got help from a friend with more
+JavaScript knowledge than me to modify the code to provide a GUI
+button instead. This mean that to get started you just need to run
+the wrapper and click the 'Register without mobile phone' to get going
+now. I've also modified the timeout code to always set it to 90 days
+in the future, to avoid having to patch the code regularly.</p>
+
+<p>So, the updated recipe for Debian Jessie:</p>
+
+<ol>
+
+<li>First, install required packages to get the source code and the
+browser you need. Signal only work with Chrome/Chromium, as far as I
+know, so you need to install it.
+
+<pre>
+apt install git tor chromium
+git clone https://github.com/WhisperSystems/Signal-Desktop.git
+</pre></li>
+
+<li>Modify the source code using command listed in the the patch
+block below.</li>
+
+<li>Start Signal using the run-signal-app wrapper (for example using
+<tt>`pwd`/run-signal-app</tt>).
+
+<li>Click on the 'Register without mobile phone', will in a phone
+number you can receive calls to the next minute, receive the
+verification code and enter it into the form field and press
+'Register'. Note, the phone number you use will be user Signal
+username, ie the way others can find you on Signal.</li>
+
+<li>You can now use Signal to contact others. Note, new contacts do
+not show up in the contact list until you restart Signal, and there is
+no way to assign names to Contacts. There is also no way to create or
+update chat groups. I suspect this is because the web app do not have
+a associated contact database.</li>
+
+</ol>
+
+<p>I am still a bit uneasy about using Signal, because of the way its
+main author moxie0 reject federation and accept dependencies to major
+corporations like Google (part of the code is fetched from Google) and
+Amazon (the central coordination point is owned by Amazon). See for
+example
+<a href="https://github.com/LibreSignal/LibreSignal/issues/37">the
+LibreSignal issue tracker</a> for a thread documenting the authors
+view on these issues. But the network effect is strong in this case,
+and several of the people I want to communicate with already use
+Signal. Perhaps we can all move to <a href="https://ring.cx/">Ring</a>
+once it <a href="https://bugs.debian.org/830265">work on my
+laptop</a>? It already work on Windows and Android, and is included
+in <a href="https://tracker.debian.org/pkg/ring">Debian</a> and
+<a href="https://launchpad.net/ubuntu/+source/ring">Ubuntu</a>, but not
+working on Debian Stable.</p>
+
+<p>Anyway, this is the patch I apply to the Signal code to get it
+working. It switch to the production servers, disable to timeout,
+make registration easier and add the shell wrapper:</p>
+
+<pre>
+cd Signal-Desktop; cat <<EOF | patch -p1
+diff --git a/js/background.js b/js/background.js
+index 24b4c1d..579345f 100644
+--- a/js/background.js
++++ b/js/background.js
+@@ -33,9 +33,9 @@
+ });
+ });
+
+- var SERVER_URL = 'https://textsecure-service-staging.whispersystems.org';
++ var SERVER_URL = 'https://textsecure-service-ca.whispersystems.org';
+ var SERVER_PORTS = [80, 4433, 8443];
+- var ATTACHMENT_SERVER_URL = 'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com';
++ var ATTACHMENT_SERVER_URL = 'https://whispersystems-textsecure-attachments.s3.amazonaws.com';
+ var messageReceiver;
+ window.getSocketStatus = function() {
+ if (messageReceiver) {
+diff --git a/js/expire.js b/js/expire.js
+index 639aeae..beb91c3 100644
+--- a/js/expire.js
++++ b/js/expire.js
+@@ -1,6 +1,6 @@
+ ;(function() {
+ 'use strict';
+- var BUILD_EXPIRATION = 0;
++ var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
+
+ window.extension = window.extension || {};
+
+diff --git a/js/views/install_view.js b/js/views/install_view.js
+index 7816f4f..1d6233b 100644
+--- a/js/views/install_view.js
++++ b/js/views/install_view.js
+@@ -38,7 +38,8 @@
+ return {
+ 'click .step1': this.selectStep.bind(this, 1),
+ 'click .step2': this.selectStep.bind(this, 2),
+- 'click .step3': this.selectStep.bind(this, 3)
++ 'click .step3': this.selectStep.bind(this, 3),
++ 'click .callreg': function() { extension.install('standalone') },
+ };
+ },
+ clearQR: function() {
+diff --git a/options.html b/options.html
+index dc0f28e..8d709f6 100644
+--- a/options.html
++++ b/options.html
+@@ -14,7 +14,10 @@
+ <div class='nav'>
+ <h1>{{ installWelcome }}</h1>
+ <p>{{ installTagline }}</p>
+- <div> <a class='button step2'>{{ installGetStartedButton }}</a> </div>
++ <div> <a class='button step2'>{{ installGetStartedButton }}</a>
++ <br> <a class="button callreg">Register without mobile phone</a>
++
++ </div>
+ <span class='dot step1 selected'></span>
+ <span class='dot step2'></span>
+ <span class='dot step3'></span>
+--- /dev/null 2016-10-07 09:55:13.730181472 +0200
++++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
+@@ -0,0 +1,12 @@
++#!/bin/sh
++set -e
++cd $(dirname $0)
++mkdir -p userdata
++userdata="`pwd`/userdata"
++if [ -d "$userdata" ] && [ ! -d "$userdata/.git" ] ; then
++ (cd $userdata && git init)
++fi
++(cd $userdata && git add . && git commit -m "Current status." || true)
++exec chromium \
++ --proxy-server="socks://localhost:9050" \
++ --user-data-dir=$userdata --load-and-launch-app=`pwd`
+EOF
+chmod a+rx run-signal-app
+</pre>
+
+<p>As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&label=PetterReinholdtsenBlog">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
</div>
<div class="tags">
- 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>.
+ 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>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html">Creepy, visualise geotagged social media information - nice free software</a></div>
- <div class="date">24th January 2016</div>
- <div class="body"><p>Most people seem not to realise that every time they walk around
-with the computerised radio beacon known as a mobile phone their
-position is tracked by the phone company and often stored for a long
-time (like every time a SMS is received or sent). And if their
-computerised radio beacon is capable of running programs (often called
-mobile apps) downloaded from the Internet, these programs are often
-also capable of tracking their location (if the app requested access
-during installation). And when these programs send out information to
-central collection points, the location is often included, unless
-extra care is taken to not send the location. The provided
-information is used by several entities, for good and bad (what is
-good and bad, depend on your point of view). What is certain, is that
-the private sphere and the right to free movement is challenged and
-perhaps even eradicated for those announcing their location this way,
-when they share their whereabouts with private and public
-entities.</p>
-
-<p align="center"><img width="70%" src="http://people.skolelinux.org/pere/blog/images/2016-01-24-nice-creepy-desktop-window.png"></p>
-
-<p>The phone company logs provide a register of locations to check out
-when one want to figure out what the tracked person was doing. It is
-unavailable for most of us, but provided to selected government
-officials, company staff, those illegally buying information from
-unfaithful servants and crackers stealing the information. But the
-public information can be collected and analysed, and a free software
-tool to do so is called
-<a href="http://www.geocreepy.com/">Creepy or Cree.py</a>. I
-discovered it when I read
-<a href="http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-7787884.html">an
-article about Creepy</a> in the Norwegian newspaper Aftenposten i
-November 2014, and decided to check if it was available in Debian.
-The python program was in Debian, but
-<a href="https://tracker.debian.org/pkg/creepy">the version in
-Debian</a> was completely broken and practically unmaintained. I
-uploaded a new version which did not work quite right, but did not
-have time to fix it then. This Christmas I decided to finally try to
-get Creepy operational in Debian. Now a fixed version is available in
-Debian unstable and testing, and almost all Debian specific patches
-are now included
-<a href="https://github.com/jkakavas/creepy">upstream</a>.</p>
-
-<p>The Creepy program visualises geolocation information fetched from
-Twitter, Instagram, Flickr and Google+, and allow one to get a
-complete picture of every social media message posted recently in a
-given area, or track the movement of a given individual across all
-these services. Earlier it was possible to use the search API of at
-least some of these services without identifying oneself, but these
-days it is impossible. This mean that to use Creepy, you need to
-configure it to log in as yourself on these services, and provide
-information to them about your search interests. This should be taken
-into account when using Creepy, as it will also share information
-about yourself with the services.</p>
-
-<p>The picture above show the twitter messages sent from (or at least
-geotagged with a position from) the city centre of Oslo, the capital
-of Norway. One useful way to use Creepy is to first look at
-information tagged with an area of interest, and next look at all the
-information provided by one or more individuals who was in the area.
-I tested it by checking out which celebrity provide their location in
-twitter messages by checkout out who sent twitter messages near a
-Norwegian TV station, and next could track their position over time,
-making it possible to locate their home and work place, among other
-things. A similar technique have been
-<a href="http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl">used
-to locate Russian soldiers in Ukraine</a>, and it is both a powerful
-tool to discover lying governments, and a useful tool to help people
-understand the value of the private information they provide to the
-public.</p>
-
-<p>The package is not trivial to backport to Debian Stable/Jessie, as
-it depend on several python modules currently missing in Jessie (at
-least python-instagram, python-flickrapi and
-python-requests-toolbelt).</p>
-
-<p>(I have uploaded
-<a href="https://screenshots.debian.net/package/creepy">the image to
-screenshots.debian.net</a> and licensed it under the same terms as the
-Creepy program in Debian.)</p>
+ <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>
+ <div class="date"> 8th October 2016</div>
+ <div class="body"><p>NRK
+<a href="https://nrkbeta.no/2016/09/02/securing-whistleblowers/">lanserte
+for noen uker siden</a> en ny
+<a href="https://www.nrk.no/varsle/">varslerportal som bruker
+SecureDrop til å ta imot tips</a> der det er vesentlig at ingen
+utenforstående får vite at NRK er tipset. Det er et langt steg
+fremover for NRK, og når en leser bloggposten om hva de har tenkt på
+og hvordan løsningen er satt opp virker det som om de har gjort en
+grundig jobb der. Men det er ganske mye ekstra jobb å motta tips via
+SecureDrop, så varslersiden skriver "Nyhetstips som ikke krever denne
+typen ekstra vern vil vi gjerne ha på nrk.no/03030", og 03030-siden
+foreslår i tillegg til et webskjema å bruke epost, SMS, telefon,
+personlig oppmøte og brevpost. Denne artikkelen handler disse andre
+metodene.</p>
+
+<p>Når en sender epost til en @nrk.no-adresse så vil eposten sendes ut
+av landet til datamaskiner kontrollert av Microsoft. En kan sjekke
+dette selv ved å slå opp epostleveringsadresse (MX) i DNS. For NRK er
+dette i dag "nrk-no.mail.protection.outlook.com". NRK har som en ser
+valgt å sette bort epostmottaket sitt til de som står bak outlook.com,
+dvs. Microsoft. En kan sjekke hvor nettverkstrafikken tar veien
+gjennom Internett til epostmottaket vha. programmet
+<tt>traceroute</tt>, og finne ut hvem som eier en Internett-adresse
+vha. whois-systemet. Når en gjør dette for epost-trafikk til @nrk.no
+ser en at trafikken fra Norge mot nrk-no.mail.protection.outlook.com
+går via Sverige mot enten Irland eller Tyskland (det varierer fra gang
+til gang og kan endre seg over tid).</p>
+
+<p>Vi vet fra
+<a href="https://no.wikipedia.org/wiki/FRA-loven">introduksjonen av
+FRA-loven</a> at IP-trafikk som passerer grensen til Sverige avlyttes
+av Försvarets radioanstalt (FRA). Vi vet videre takket være
+Snowden-bekreftelsene at trafikk som passerer grensen til
+Storbritannia avlyttes av Government Communications Headquarters
+(GCHQ). I tillegg er er det nettopp lansert et forslag i Norge om at
+forsvarets E-tjeneste skal få avlytte trafikk som krysser grensen til
+Norge. Jeg er ikke kjent med dokumentasjon på at Irland og Tyskland
+gjør det samme. Poenget er uansett at utenlandsk etterretning har
+mulighet til å snappe opp trafikken når en sender epost til @nrk.no.
+I tillegg er det selvsagt tilgjengelig for Microsoft som er underlagt USAs
+jurisdiksjon og
+<a href="https://www.theguardian.com/world/2013/jul/11/microsoft-nsa-collaboration-user-data">samarbeider
+med USAs etterretning på flere områder</a>. De som tipser NRK om
+nyheter via epost kan dermed gå ut fra at det blir kjent for mange
+andre enn NRK at det er gjort.</p>
+
+<p>Bruk av SMS og telefon registreres av blant annet telefonselskapene
+og er tilgjengelig i følge lov og forskrift for blant annet Politi,
+NAV og Finanstilsynet, i tillegg til IT-folkene hos telefonselskapene
+og deres overordnede. Hvis innringer eller mottaker bruker
+smarttelefon vil slik kontakt også gjøres tilgjengelig for ulike
+app-leverandører og de som lytter på trafikken mellom telefon og
+app-leverandør, alt etter hva som er installert på telefonene som
+brukes.</p>
+
+<p>Brevpost kan virke trygt, og jeg vet ikke hvor mye som registreres
+og lagres av postens datastyrte postsorteringssentraler. Det vil ikke
+overraske meg om det lagres hvor i landet hver konvolutt kommer fra og
+hvor den er adressert, i hvert fall for en kortere periode. Jeg vet
+heller ikke hvem slik informasjon gjøres tilgjengelig for. Det kan
+være nok til å ringe inn potensielle kilder når det krysses med hvem
+som kjente til aktuell informasjon og hvor de befant seg (tilgjengelig
+f.eks. hvis de bærer mobiltelefon eller bor i nærheten).</p>
+
+<p>Personlig oppmøte hos en NRK-journalist er antagelig det tryggeste,
+men en bør passe seg for å bruke NRK-kantina. Der bryter de nemlig
+<a href="http://www.lovdata.no/all/hl-19850524-028.html#14">Sentralbanklovens
+paragraf 14</a> og nekter folk å betale med kontanter. I stedet
+krever de at en varsle sin bankkortutsteder om hvor en befinner seg
+ved å bruke bankkort. Banktransaksjoner er tilgjengelig for
+bankkortutsteder (det være seg VISA, Mastercard, Nets og/eller en
+bank) i tillegg til politiet og i hvert fall tidligere med Se & Hør
+(via utro tjenere, slik det ble avslørt etter utgivelsen av boken
+«Livet, det forbannede» av Ken B. Rasmussen). Men hvor mange kjenner
+en NRK-journalist personlig? Besøk på NRK på Marienlyst krever at en
+registrerer sin ankost elektronisk i besøkssystemet. Jeg vet ikke hva
+som skjer med det datasettet, men har grunn til å tro at det sendes ut
+SMS til den en skal besøke med navnet som er oppgitt. Kanskje greit å
+oppgi falskt navn.</p>
+
+<p>Når så tipset er kommet frem til NRK skal det behandles
+redaksjonelt i NRK. Der vet jeg via ulike kilder at de fleste
+journalistene bruker lokalt installert programvare, men noen bruker
+Google Docs og andre skytjenester i strid med interne retningslinjer
+når de skriver. Hvordan vet en hvem det gjelder? Ikke vet jeg, men
+det kan være greit å spørre for å sjekke at journalisten har tenkt på
+problemstillingen, før en gir et tips. Og hvis tipset omtales internt
+på epost, er det jo grunn til å tro at også intern eposten vil deles
+med Microsoft og utenlands etterretning, slik tidligere nevnt, men det
+kan hende at det holdes internt i NRKs interne MS Exchange-løsning.
+Men Microsoft ønsker å få alle Exchange-kunder over "i skyen" (eller
+andre folks datamaskiner, som det jo innebærer), så jeg vet ikke hvor
+lenge det i så fall vil vare.</p>
+
+<p>I tillegg vet en jo at
+<a href="https://www.nrk.no/ytring/elektronisk-kildevern-i-nrk-1.11941196">NRK
+har valgt å gi nasjonal sikkerhetsmyndighet (NSM) tilgang til å se på
+intern og ekstern Internett-trafikk</a> hos NRK ved oppsett av såkalte
+VDI-noder, på tross av
+<a href="https://www.nrk.no/ytring/bekymring-for-nrks-kildevern-1.11941584">protester
+fra NRKs journalistlag</a>. Jeg vet ikke om den vil kunne snappe opp
+dokumenter som lagres på interne filtjenere eller dokumenter som lages
+i de interne webbaserte publiseringssystemene, men vet at hva noden
+ser etter på nettet kontrolleres av NSM og oppdateres automatisk, slik
+at det ikke gir så mye mening å sjekke hva noden ser etter i dag når
+det kan endres automatisk i morgen.</p>
+
+<p>Personlig vet jeg ikke om jeg hadde turt tipse NRK hvis jeg satt på
+noe som kunne være en trussel mot den bestående makten i Norge eller
+verden. Til det virker det å være for mange åpninger for
+utenforstående med andre prioriteter enn NRKs journalistiske fokus.
+Og den største truslen for en varsler er jo om metainformasjon kommer
+på avveie, dvs. informasjon om at en har vært i kontakt med en
+journalist. Det kan være nok til at en kommer i myndighetenes
+søkelys, og de færreste har nok operasjonell sikkerhet til at vil tåle
+slik flombelysning på sitt privatliv.</p>
</div>
<div class="tags">
- 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>.
+ 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>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html">Always download Debian packages using Tor - the simple recipe</a></div>
- <div class="date">15th January 2016</div>
- <div class="body"><p>During his DebConf15 keynote, Jacob Appelbaum
-<a href="https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/">observed
-that those listening on the Internet lines would have good reason to
-believe a computer have a given security hole</a> if it download a
-security fix from a Debian mirror. This is a good reason to always
-use encrypted connections to the Debian mirror, to make sure those
-listening do not know which IP address to attack. In August, Richard
-Hartmann observed that encryption was not enough, when it was possible
-to interfere download size to security patches or the fact that
-download took place shortly after a security fix was released, and
-<a href="http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/">proposed
-to always use Tor to download packages from the Debian mirror</a>. He
-was not the first to propose this, as the
-<tt><a href="https://tracker.debian.org/pkg/apt-transport-tor">apt-transport-tor</a></tt>
-package by Tim Retout already existed to make it easy to convince apt
-to use <a href="https://www.torproject.org/">Tor</a>, but I was not
-aware of that package when I read the blog post from Richard.</p>
-
-<p>Richard discussed the idea with Peter Palfrader, one of the Debian
-sysadmins, and he set up a Tor hidden service on one of the central
-Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
-it possible to download packages directly between two tor nodes,
-making sure the network traffic always were encrypted.</p>
-
-<p>Here is a short recipe for enabling this on your machine, by
-installing <tt>apt-transport-tor</tt> and replacing http and https
-urls with tor+http and tor+https, and using the hidden service instead
-of the official Debian mirror site. I recommend installing
-<tt>etckeeper</tt> before you start to have a history of the changes
-done in /etc/.</p>
-
-<blockquote><pre>
-apt install apt-transport-tor
-sed -i 's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%' /etc/apt/sources.list
-sed -i 's% http% tor+http%' /etc/apt/sources.list
-</pre></blockquote>
-
-<p>If you have more sources listed in /etc/apt/sources.list.d/, run
-the sed commands for these too. The sed command is assuming your are
-using the ftp.debian.org Debian mirror. Adjust the command (or just
-edit the file manually) to match your mirror.</p>
-
-<p>This work in Debian Jessie and later. Note that tools like
-<tt>apt-file</tt> only recently started using the apt transport
-system, and do not work with these tor+http URLs. For
-<tt>apt-file</tt> you need the version currently in experimental,
-which need a recent apt version currently only in unstable. So if you
-need a working <tt>apt-file</tt>, this is not for you.</p>
-
-<p>Another advantage from this change is that your machine will start
-using Tor regularly and at fairly random intervals (every time you
-update the package lists or upgrade or install a new package), thus
-masking other Tor traffic done from the same machine. Using Tor will
-become normal for the machine in question.</p>
-
-<p>On <a href="https://wiki.debian.org/FreedomBox">Freedombox</a>, APT
-is set up by default to use <tt>apt-transport-tor</tt> when Tor is
-enabled. It would be great if it was the default on any Debian
-system.</p>
+ <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>
+ <div class="date"> 7th October 2016</div>
+ <div class="body"><p><a href="http://packages.qa.debian.org/isenkram">The Isenkram
+system</a> provide a practical and easy way to figure out which
+packages support the hardware in a given machine. The command line
+tool <tt>isenkram-lookup</tt> and the tasksel options provide a
+convenient way to list and install packages relevant for the current
+hardware during system installation, both user space packages and
+firmware packages. The GUI background daemon on the other hand provide
+a pop-up proposing to install packages when a new dongle is inserted
+while using the computer. For example, if you plug in a smart card
+reader, the system will ask if you want to install <tt>pcscd</tt> if
+that package isn't already installed, and if you plug in a USB video
+camera the system will ask if you want to install <tt>cheese</tt> if
+cheese is currently missing. This already work just fine.</p>
+
+<p>But Isenkram depend on a database mapping from hardware IDs to
+package names. When I started no such database existed in Debian, so
+I made my own data set and included it with the isenkram package and
+made isenkram fetch the latest version of this database from git using
+http. This way the isenkram users would get updated package proposals
+as soon as I learned more about hardware related packages.</p>
+
+<p>The hardware is identified using modalias strings. The modalias
+design is from the Linux kernel where most hardware descriptors are
+made available as a strings that can be matched using filename style
+globbing. It handle USB, PCI, DMI and a lot of other hardware related
+identifiers.</p>
+
+<p>The downside to the Isenkram specific database is that there is no
+information about relevant distribution / Debian version, making
+isenkram propose obsolete packages too. But along came AppStream, a
+cross distribution mechanism to store and collect metadata about
+software packages. When I heard about the proposal, I contacted the
+people involved and suggested to add a hardware matching rule using
+modalias strings in the specification, to be able to use AppStream for
+mapping hardware to packages. This idea was accepted and AppStream is
+now a great way for a package to announce the hardware it support in a
+distribution neutral way. I wrote
+<a href="http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html">a
+recipe on how to add such meta-information</a> in a blog post last
+December. If you have a hardware related package in Debian, please
+announce the relevant hardware IDs using AppStream.</p>
+
+<p>In Debian, almost all packages that can talk to a LEGO Mindestorms
+RCX or NXT unit, announce this support using AppStream. The effect is
+that when you insert such LEGO robot controller into your Debian
+machine, Isenkram will propose to install the packages needed to get
+it working. The intention is that this should allow the local user to
+start programming his robot controller right away without having to
+guess what packages to use or which permissions to fix.</p>
+
+<p>But when I sat down with my son the other day to program our NXT
+unit using his Debian Stretch computer, I discovered something
+annoying. The local console user (ie my son) did not get access to
+the USB device for programming the unit. This used to work, but no
+longer in Jessie and Stretch. After some investigation and asking
+around on #debian-devel, I discovered that this was because udev had
+changed the mechanism used to grant access to local devices. The
+ConsoleKit mechanism from <tt>/lib/udev/rules.d/70-udev-acl.rules</tt>
+no longer applied, because LDAP users no longer was added to the
+plugdev group during login. Michael Biebl told me that this method
+was obsolete and the new method used ACLs instead. This was good
+news, as the plugdev mechanism is a mess when using a remote user
+directory like LDAP. Using ACLs would make sure a user lost device
+access when she logged out, even if the user left behind a background
+process which would retain the plugdev membership with the ConsoleKit
+setup. Armed with this knowledge I moved on to fix the access problem
+for the LEGO Mindstorms related packages.</p>
+
+<p>The new system uses a udev tag, 'uaccess'. It can either be
+applied directly for a device, or is applied in
+/lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
+LEGO Mindstorms udev rules did not have a class, I decided to add the
+tag directly in the udev rules files included in the packages. Here
+is one example. For the nqc C compiler for the RCX, the
+<tt>/lib/udev/rules.d/60-nqc.rules</tt> file now look like this:
+
+<p><pre>
+SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="0694", ATTR{idProduct}=="0001", \
+ SYMLINK+="rcx-%k", TAG+="uaccess"
+</pre></p>
+
+<p>The key part is the 'TAG+="uaccess"' at the end. I suspect all
+packages using plugdev in their /lib/udev/rules.d/ files should be
+changed to use this tag (either directly or indirectly via
+<tt>70-uaccess.rules</tt>). Perhaps a lintian check should be created
+to detect this?</p>
+
+<p>I've been unable to find good documentation on the uaccess feature.
+It is unclear to me if the uaccess tag is an internal implementation
+detail like the udev-acl tag used by
+<tt>/lib/udev/rules.d/70-udev-acl.rules</tt>. If it is, I guess the
+indirect method is the preferred way. Michael
+<a href="https://github.com/systemd/systemd/issues/4288">asked for more
+documentation from the systemd project</a> and I hope it will make
+this clearer. For now I use the generic classes when they exist and
+is already handled by <tt>70-uaccess.rules</tt>, and add the tag
+directly if no such class exist.</p>
+
+<p>To learn more about the isenkram system, please check out
+<a href="http://people.skolelinux.org/pere/blog/tags/isenkram/">my
+blog posts tagged isenkram</a>.</p>
+
+<p>To help out making life for LEGO constructors in Debian easier,
+please join us on our IRC channel
+<a href="irc://irc.debian.org/%23debian-lego">#debian-lego</a> and join
+the <a href="https://alioth.debian.org/projects/debian-lego/">Debian
+LEGO team</a> in the Alioth project we created yesterday. A mailing
+list is not yet created, but we are working on it. :)</p>
+
+<p>As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address
+<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&label=PetterReinholdtsenBlog">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
</div>
<div class="tags">
- 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>.
+ 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>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Nedlasting_fra_NRK__som_Matroska_med_undertekster.html">Nedlasting fra NRK, som Matroska med undertekster</a></div>
- <div class="date"> 2nd January 2016</div>
- <div class="body"><p>Det kommer stadig nye løsninger for å ta lagre unna innslag fra NRK
-for å se på det senere. For en stund tilbake kom jeg over et script
-nrkopptak laget av Ingvar Hagelund. Han fjernet riktignok sitt script
-etter forespørsel fra Erik Bolstad i NRK, men noen tok heldigvis og
-gjorde det <a href="https://github.com/liangqi/nrkopptak">tilgjengelig
-via github</a>.</p>
-
-<p>Scriptet kan lagre som MPEG4 eller Matroska, og bake inn
-undertekster i fila på et vis som blant annet VLC forstår. For å
-bruke scriptet, kopier ned git-arkivet og kjør</p>
-
-<p><pre>
-nrkopptak/bin/nrk-opptak k <ahref="https://tv.nrk.no/serie/bmi-turne/MUHH45000115/sesong-1/episode-1">https://tv.nrk.no/serie/bmi-turne/MUHH45000115/sesong-1/episode-1</a>
-</pre></p>
-
-<p>URL-eksemplet er dagens toppsak på tv.nrk.no. Argument 'k' ber
-scriptet laste ned og lagre som Matroska. Det finnes en rekke andre
-muligheter for valg av kvalitet og format.</p>
-
-<p>Jeg foretrekker dette scriptet fremfor youtube-dl, som
-<a href="http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK_med_den__nye__l_sningen.html">
-nevnt i 2014 støtter NRK</a> og en rekke andre videokilder, på grunn
-av at nrkopptak samler undertekster og video i en enkelt fil, hvilket
-gjør håndtering enklere på disk.</p>
+ <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>
+ <div class="date"> 9th September 2016</div>
+ <div class="body"><p>En av dagens nyheter er at Aftenpostens redaktør Espen Egil Hansen
+bruker
+<a href="https://www.nrk.no/kultur/aftenposten-brukar-heile-forsida-pa-facebook-kritikk-1.13126918">forsiden
+av papiravisen på et åpent brev til Facebooks sjef Mark Zuckerberg om
+Facebooks fjerning av bilder, tekster og sider de ikke liker</a>. Det
+må være uvant for redaktøren i avisen Aftenposten å stå med lua i
+handa og håpe på å bli hørt. Spesielt siden Aftenposten har vært med
+på å gi Facebook makten de nå demonstrerer at de har. Ved å melde seg
+inn i Facebook-samfunnet har de sagt ja til bruksvilkårene og inngått
+en antagelig bindende avtale. Kanskje de skulle lest og vurdert
+vilkårene litt nærmere før de sa ja, i stedet for å klage over at
+reglende de har valgt å akseptere blir fulgt? Personlig synes jeg
+vilkårene er uakseptable og det ville ikke falle meg inn å gå inn på
+en avtale med slike vilkår. I tillegg til uakseptable vilkår er det
+mange andre grunner til å unngå Facebook. Du kan finne en solid
+gjennomgang av flere slike argumenter hos
+<a href="https://stallman.org/facebook.html">Richard Stallmans side om
+Facebook</a>.
+
+<p>Jeg håper flere norske redaktører på samme vis må stå med lua i
+hånden inntil de forstår at de selv er med på å føre samfunnet på
+ville veier ved å omfavne Facebook slik de gjør når de omtaler og
+løfter frem saker fra Facebook, og tar i bruk Facebook som
+distribusjonskanal for sine nyheter. De bidrar til
+overvåkningssamfunnet og raderer ut lesernes privatsfære når de lenker
+til Facebook på sine sider, og låser seg selv inne i en omgivelse der
+det er Facebook, og ikke redaktøren, som sitter med makta.</p>
+
+<p>Men det vil nok ta tid, i et Norge der de fleste nettredaktører
+<a href="http://people.skolelinux.org/pere/blog/Snurpenot_overv_kning_av_sensitiv_personinformasjon.html">deler
+sine leseres personopplysinger med utenlands etterretning</a>.</p>
+
+<p>For øvrig burde varsleren Edward Snowden få politisk asyl i
+Norge.</p>
</div>
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
+ 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>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html">OpenALPR, find car license plates in video streams - nice free software</a></div>
- <div class="date">23rd December 2015</div>
- <div class="body"><p>When I was a kid, we used to collect "car numbers", as we used to
-call the car license plate numbers in those days. I would write the
-numbers down in my little book and compare notes with the other kids
-to see how many region codes we had seen and if we had seen some
-exotic or special region codes and numbers. It was a fun game to pass
-time, as we kids have plenty of it.</p>
-
-<p>A few days I came across
-<a href="https://github.com/openalpr/openalpr">the OpenALPR
-project</a>, a free software project to automatically discover and
-report license plates in images and video streams, and provide the
-"car numbers" in a machine readable format. I've been looking for
-such system for a while now, because I believe it is a bad idea that the
-<a href="https://en.wikipedia.org/wiki/Automatic_number_plate_recognition">automatic
-number plate recognition</a> tool only is available in the hands of
-the powerful, and want it to be available also for the powerless to
-even the score when it comes to surveillance and sousveillance. I
-discovered the developer
-<a href="https://bugs.debian.org/747509">wanted to get the tool into
-Debian</a>, and as I too wanted it to be in Debian, I volunteered to
-help him get it into shape to get the package uploaded into the Debian
-archive.</p>
-
-<p>Today we finally managed to get the package into shape and uploaded
-it into Debian, where it currently
-<a href="https://ftp-master.debian.org//new/openalpr_2.2.1-1.html">waits
-in the NEW queue</a> for review by the Debian ftpmasters.</p>
-
-<p>I guess you are wondering why on earth such tool would be useful
-for the common folks, ie those not running a large government
-surveillance system? Well, I plan to put it in a computer on my bike
-and in my car, tracking the cars nearby and allowing me to be notified
-when number plates on my watch list are discovered. Another use case
-was suggested by a friend of mine, who wanted to set it up at his home
-to open the car port automatically when it discovered the plate on his
-car. When I mentioned it perhaps was a bit foolhardy to allow anyone
-capable of placing his license plate number of a piece of cardboard to
-open his car port, men replied that it was always unlocked anyway. I
-guess for such use case it make sense. I am sure there are other use
-cases too, for those with imagination and a vision.</p>
-
-<p>If you want to build your own version of the Debian package, check
-out the upstream git source and symlink ./distros/debian to ./debian/
-before running "debuild" to build the source. Or wait a bit until the
-package show up in unstable.</p>
+ <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>
+ <div class="date"> 6th September 2016</div>
+ <div class="body"><p>I helga kom det et hårreisende forslag fra Lysne II-utvalget satt
+ned av Forsvarsdepartementet. Lysne II-utvalget var bedt om å vurdere
+ønskelista til Forsvarets etterretningstjeneste (e-tjenesten), og har
+kommet med
+<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
+om at e-tjenesten skal få lov til a avlytte all Internett-trafikk</a>
+som passerer Norges grenser. Få er klar over at dette innebærer at
+e-tjenesten får tilgang til epost sendt til de fleste politiske
+partiene på Stortinget. Regjeringspartiet Høyre (@hoyre.no),
+støttepartiene Venstre (@venstre.no) og Kristelig Folkeparti (@krf.no)
+samt Sosialistisk Ventreparti (@sv.no) og Miljøpartiet de grønne
+(@mdg.no) har nemlig alle valgt å ta imot eposten sin via utenlandske
+tjenester. Det betyr at hvis noen sender epost til noen med en slik
+adresse vil innholdet i eposten, om dette forslaget blir vedtatt, gjøres
+tilgjengelig for e-tjenesten. Venstre, Sosialistisk Ventreparti og
+Miljøpartiet De Grønne har valgt å motta sin epost hos Google,
+Kristelig Folkeparti har valgt å motta sin epost hos Microsoft, og
+Høyre har valgt å motta sin epost hos Comendo med mottak i Danmark og
+Irland. Kun Arbeiderpartiet og Fremskrittspartiet har valgt å motta
+eposten sin i Norge, hos henholdsvis Intility AS og Telecomputing
+AS.</p>
+
+<p>Konsekvensen er at epost inn og ut av de politiske organisasjonene,
+til og fra partimedlemmer og partiets tillitsvalgte vil gjøres
+tilgjengelig for e-tjenesten for analyse og sortering. Jeg mistenker
+at kunnskapen som slik blir tilgjengelig vil være nyttig hvis en
+ønsker å vite hvilke argumenter som treffer publikum når en ønsker å
+påvirke Stortingets representanter.</p
+
+<p>Ved hjelp av MX-oppslag i DNS for epost-domene, tilhørende
+whois-oppslag av IP-adressene og traceroute for å se hvorvidt
+trafikken går via utlandet kan enhver få bekreftet at epost sendt til
+de omtalte partiene vil gjøres tilgjengelig for forsvarets
+etterretningstjeneste hvis forslaget blir vedtatt. En kan også bruke
+den kjekke nett-tjenesten <a href="http://ipinfo.io/">ipinfo.io</a>
+for å få en ide om hvor i verden en IP-adresse hører til.</p>
+
+<p>På den positive siden vil forslaget gjøre at enda flere blir
+motivert til å ta grep for å bruke
+<a href="https://www.torproject.org/">Tor</a> og krypterte
+kommunikasjonsløsninger for å kommunisere med sine kjære, for å sikre
+at privatsfæren vernes. Selv bruker jeg blant annet
+<a href="https://www.freedomboxfoundation.org/">FreedomBox</a> og
+<a href="https://whispersystems.org/">Signal</a> til slikt. Ingen av
+dem er optimale, men de fungerer ganske bra allerede og øker kostnaden
+for dem som ønsker å invadere mitt privatliv.</p>
+
+<p>For øvrig burde varsleren Edward Snowden få politisk asyl i
+Norge.</p>
+
+<!--
+
+venstre.no
+ venstre.no mail is handled by 10 aspmx.l.google.com.
+ venstre.no mail is handled by 20 alt1.aspmx.l.google.com.
+ venstre.no mail is handled by 20 alt2.aspmx.l.google.com.
+ venstre.no mail is handled by 30 aspmx2.googlemail.com.
+ venstre.no mail is handled by 30 aspmx3.googlemail.com.
+
+traceroute to aspmx.l.google.com (173.194.222.27), 30 hops max, 60 byte packets
+ 1 uio-gw10.uio.no (129.240.6.1) 0.411 ms 0.438 ms 0.536 ms
+ 2 uio-gw8.uio.no (129.240.24.229) 0.375 ms 0.452 ms 0.548 ms
+ 3 oslo-gw1.uninett.no (128.39.65.17) 1.940 ms 1.950 ms 1.942 ms
+ 4 se-tug.nordu.net (109.105.102.108) 6.910 ms 6.949 ms 7.283 ms
+ 5 google-gw.nordu.net (109.105.98.6) 6.975 ms 6.967 ms 6.958 ms
+ 6 209.85.250.192 (209.85.250.192) 7.337 ms 7.286 ms 10.890 ms
+ 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
+ 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
+ 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
+10 * * *
+
+mdg.no
+ mdg.no mail is handled by 1 aspmx.l.google.com.
+ mdg.no mail is handled by 5 alt2.aspmx.l.google.com.
+ mdg.no mail is handled by 5 alt1.aspmx.l.google.com.
+ mdg.no mail is handled by 10 aspmx2.googlemail.com.
+ mdg.no mail is handled by 10 aspmx3.googlemail.com.
+sv.no
+ sv.no mail is handled by 1 aspmx.l.google.com.
+ sv.no mail is handled by 5 alt1.aspmx.l.google.com.
+ sv.no mail is handled by 5 alt2.aspmx.l.google.com.
+ sv.no mail is handled by 10 aspmx3.googlemail.com.
+ sv.no mail is handled by 10 aspmx2.googlemail.com.
+hoyre.no
+ hoyre.no mail is handled by 10 hoyre-no.mx1.comendosystems.com.
+ hoyre.no mail is handled by 20 hoyre-no.mx2.comendosystems.net.
+
+traceroute to hoyre-no.mx1.comendosystems.com (89.104.206.4), 30 hops max, 60 byte packets
+ 1 uio-gw10.uio.no (129.240.6.1) 0.450 ms 0.510 ms 0.591 ms
+ 2 uio-gw8.uio.no (129.240.24.229) 0.383 ms 0.508 ms 0.596 ms
+ 3 oslo-gw1.uninett.no (128.39.65.17) 0.311 ms 0.315 ms 0.300 ms
+ 4 se-tug.nordu.net (109.105.102.108) 6.837 ms 6.842 ms 6.834 ms
+ 5 dk-uni.nordu.net (109.105.97.10) 26.073 ms 26.085 ms 26.076 ms
+ 6 dix.1000m.soeborg.ip.comendo.dk (192.38.7.22) 15.372 ms 15.046 ms 15.123 ms
+ 7 89.104.192.65 (89.104.192.65) 15.875 ms 15.990 ms 16.239 ms
+ 8 89.104.192.179 (89.104.192.179) 15.676 ms 15.674 ms 15.664 ms
+ 9 03dm-com.mx1.staysecuregroup.com (89.104.206.4) 15.637 ms * *
+
+krf.no
+ krf.no mail is handled by 10 krf-no.mail.protection.outlook.com.
+
+traceroute to krf-no.mail.protection.outlook.com (213.199.154.42), 30 hops max, 60 byte packets
+ 1 uio-gw10.uio.no (129.240.6.1) 0.401 ms 0.438 ms 0.536 ms
+ 2 uio-gw8.uio.no (129.240.24.229) 11.076 ms 11.120 ms 11.204 ms
+ 3 oslo-gw1.uninett.no (128.39.65.17) 0.232 ms 0.234 ms 0.271 ms
+ 4 se-tug.nordu.net (109.105.102.108) 6.811 ms 6.820 ms 6.815 ms
+ 5 netnod-ix-ge-a-sth-4470.microsoft.com (195.245.240.181) 7.074 ms 7.013 ms 7.061 ms
+ 6 ae1-0.sto-96cbe-1b.ntwk.msn.net (104.44.225.161) 7.227 ms 7.362 ms 7.293 ms
+ 7 be-8-0.ibr01.ams.ntwk.msn.net (104.44.5.7) 41.993 ms 43.334 ms 41.939 ms
+ 8 be-1-0.ibr02.ams.ntwk.msn.net (104.44.4.214) 43.153 ms 43.507 ms 43.404 ms
+ 9 ae3-0.fra-96cbe-1b.ntwk.msn.net (104.44.5.17) 29.897 ms 29.831 ms 29.794 ms
+10 ae10-0.vie-96cbe-1a.ntwk.msn.net (198.206.164.1) 42.309 ms 42.130 ms 41.808 ms
+11 * ae8-0.vie-96cbe-1b.ntwk.msn.net (104.44.227.29) 41.425 ms *
+12 * * *
+
+arbeiderpartiet.no
+ arbeiderpartiet.no mail is handled by 10 mail.intility.com.
+ arbeiderpartiet.no mail is handled by 20 mail2.intility.com.
+
+traceroute to mail.intility.com (188.95.245.87), 30 hops max, 60 byte packets
+ 1 uio-gw10.uio.no (129.240.6.1) 0.486 ms 0.508 ms 0.649 ms
+ 2 uio-gw8.uio.no (129.240.24.229) 0.416 ms 0.508 ms 0.620 ms
+ 3 oslo-gw1.uninett.no (128.39.65.17) 0.276 ms 0.278 ms 0.275 ms
+ 4 te3-1-2.br1.fn3.as2116.net (193.156.90.3) 0.374 ms 0.371 ms 0.416 ms
+ 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
+ 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
+ 7 cD2EC45C1.static.as2116.net (193.69.236.210) 0.654 ms 0.615 ms 0.590 ms
+ 8 185.7.132.38 (185.7.132.38) 1.661 ms 1.808 ms 1.695 ms
+ 9 185.7.132.100 (185.7.132.100) 1.793 ms 1.943 ms 1.546 ms
+10 * * *
+
+frp.no
+ frp.no mail is handled by 10 mx03.telecomputing.no.
+ frp.no mail is handled by 20 mx01.telecomputing.no.
+
+traceroute to mx03.telecomputing.no (95.128.105.102), 30 hops max, 60 byte packets
+ 1 uio-gw10.uio.no (129.240.6.1) 0.378 ms 0.402 ms 0.479 ms
+ 2 uio-gw8.uio.no (129.240.24.229) 0.361 ms 0.458 ms 0.548 ms
+ 3 oslo-gw1.uninett.no (128.39.65.17) 0.361 ms 0.352 ms 0.336 ms
+ 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
+ 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
+ 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
+ 7 95.128.105.3 (95.128.105.3) 1.050 ms 1.288 ms 1.182 ms
+ 8 mx03.telecomputing.no (95.128.105.102) 0.717 ms 0.703 ms 0.692 ms
+
+-->
</div>
<div class="tags">
- 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>.
+ 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>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html">Using appstream with isenkram to install hardware related packages in Debian</a></div>
- <div class="date">20th December 2015</div>
- <div class="body"><p>Around three years ago, I created
-<a href="http://packages.qa.debian.org/isenkram">the isenkram
-system</a> to get a more practical solution in Debian for handing
-hardware related packages. A GUI system in the isenkram package will
-present a pop-up dialog when some hardware dongle supported by
-relevant packages in Debian is inserted into the machine. The same
-lookup mechanism to detect packages is available as command line
-tools in the isenkram-cli package. In addition to mapping hardware,
-it will also map kernel firmware files to packages and make it easy to
-install needed firmware packages automatically. The key for this
-system to work is a good way to map hardware to packages, in other
-words, allow packages to announce what hardware they will work
-with.</p>
-
-<p>I started by providing data files in the isenkram source, and
-adding code to download the latest version of these data files at run
-time, to ensure every user had the most up to date mapping available.
-I also added support for storing the mapping in the Packages file in
-the apt repositories, but did not push this approach because while I
-was trying to figure out how to best store hardware/package mappings,
-<a href="http://www.freedesktop.org/software/appstream/docs/">the
-appstream system</a> was announced. I got in touch and suggested to
-add the hardware mapping into that data set to be able to use
-appstream as a data source, and this was accepted at least for the
-Debian version of appstream.</p>
-
-<p>A few days ago using appstream in Debian for this became possible,
-and today I uploaded a new version 0.20 of isenkram adding support for
-appstream as a data source for mapping hardware to packages. The only
-package so far using appstream to announce its hardware support is my
-pymissile package. I got help from Matthias Klumpp with figuring out
-how do add the required
-<a href="https://appstream.debian.org/html/sid/main/metainfo/pymissile.html">metadata
-in pymissile</a>. I added a file debian/pymissile.metainfo.xml with
-this content:</p>
-
-<blockquote><pre>
-<?xml version="1.0" encoding="UTF-8"?>
-<component>
- <id>pymissile</id>
- <metadata_license>MIT</metadata_license>
- <name>pymissile</name>
- <summary>Control original Striker USB Missile Launcher</summary>
- <description>
- <p>
- Pymissile provides a curses interface to control an original
- Marks and Spencer / Striker USB Missile Launcher, as well as a
- motion control script to allow a webcamera to control the
- launcher.
- </p>
- </description>
- <provides>
- <modalias>usb:v1130p0202d*</modalias>
- </provides>
-</component>
-</pre></blockquote>
-
-<p>The key for isenkram is the component/provides/modalias value,
-which is a glob style match rule for hardware specific strings
-(modalias strings) provided by the Linux kernel. In this case, it
-will map to all USB devices with vendor code 1130 and product code
-0202.</p>
-
-<p>Note, it is important that the license of all the metadata files
-are compatible to have permissions to aggregate them into archive wide
-appstream files. Matthias suggested to use MIT or BSD licenses for
-these files. A challenge is figuring out a good id for the data, as
-it is supposed to be globally unique and shared across distributions
-(in other words, best to coordinate with upstream what to use). But
-it can be changed later or, so we went with the package name as
-upstream for this project is dormant.</p>
-
-<p>To get the metadata file installed in the correct location for the
-mirror update scripts to pick it up and include its content the
-appstream data source, the file must be installed in the binary
-package under /usr/share/appdata/. I did this by adding the following
-line to debian/pymissile.install:</p>
-
-<blockquote><pre>
-debian/pymissile.metainfo.xml usr/share/appdata
-</pre></blockquote>
-
-<p>With that in place, the command line tool isenkram-lookup will list
-all packages useful on the current computer automatically, and the GUI
-pop-up handler will propose to install the package not already
-installed if a hardware dongle is inserted into the machine in
-question.</p>
-
-<p>Details of the modalias field in appstream is available from the
-<a href="https://wiki.debian.org/DEP-11">DEP-11</a> proposal.</p>
-
-<p>To locate the modalias values of all hardware present in a machine,
-try running this command on the command line:</p>
-
-<blockquote><pre>
-cat $(find /sys/devices/|grep modalias)
-</pre></blockquote>
-
-<p>To learn more about the isenkram system, please check out
-<a href="http://people.skolelinux.org/pere/blog/tags/isenkram/">my
-blog posts tagged isenkram</a>.</p>
+ <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>
+ <div class="date">30th August 2016</div>
+ <div class="body"><p>In April we
+<a href="http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html">started
+to work</a> on a Norwegian Bokmål edition of the "open access" book on
+how to set up and administrate a Debian system. Today I am happy to
+report that the first draft is now publicly available. You can find
+it on <a href="https://debian-handbook.info/get/">get the Debian
+Administrator's Handbook page</a> (under Other languages). The first
+eight chapters have a first draft translation, and we are working on
+proofreading the content. If you want to help out, please start
+contributing using
+<a href="https://hosted.weblate.org/projects/debian-handbook/">the
+hosted weblate project page</a>, and get in touch using
+<a href="http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators">the
+translators mailing list</a>. Please also check out
+<a href="https://debian-handbook.info/contribute/">the instructions for
+contributors</a>. A good way to contribute is to proofread the text
+and update weblate if you find errors.</p>
+
+<p>Our goal is still to make the Norwegian book available on paper as well as
+electronic form.</p>
</div>
<div class="tags">
- 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>.
+ 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>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Bokhandeldistribusjon_av_boken_Fri_kultur_av_Lawrence_Lessig.html">Bokhandeldistribusjon av boken Fri kultur av Lawrence Lessig</a></div>
- <div class="date">14th December 2015</div>
- <div class="body"><p><strong>Besøk
-<a href="https://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">lulu.com</a>
-eller
-<a href="https://www.amazon.com/Fri-kultur-Norwegian-Lawrence-Lessig/dp/8269018236/">Amazon</a>
-for å kjøpe boken på papir, eller last ned ebook som
-<a href="https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/archive/freeculture.nb.pdf">PDF</a>,
-<a href="https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/archive/freeculture.nb.epub">ePub</a>
-eller
-<a href="https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/archive/freeculture.nb.mobi">MOBI</a>
-fra
-<a href="https://github.com/petterreinholdtsen/free-culture-lessig/">github</a>.</strong></p>
-
-<p>Jeg ble gledelig overrasket i dag da jeg oppdaget at boken jeg har
-gitt ut
-<a href="https://www.amazon.com/Fri-kultur-Norwegian-Lawrence-Lessig/dp/8269018236/">hadde
-dukket opp i Amazon</a>. Jeg hadde trodd det skulle ta lenger tid, da
-jeg fikk beskjed om at det skulle ta seks til åtte uker.
-Amazonoppføringen er et resultat av at jeg for noen uker siden
-diskuterte prissetting og håndtering av profitt med forfatteren. Det
-måtte avklares da bruksvilkårene til boken har krav om
-ikke-kommersiell bruk. Vi ble enige om at overskuddet fra salg av
-boken skal sendes til
-<a href="https://creativecommons.org/">Creative Commons-stiftelsen</a>.
-Med det på plass kunne jeg be
-<a href="https://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">lulu.com</a>
-om å gi boken «utvidet» distribusjon. Årsaken til at
-bokhandeldistribusjon var litt utfordrende er at bokhandlere krever
-mulighet for profitt på bøkene de selger (selvfølgelig), og dermed
-måtte de få lov til å selge til høyere pris enn lulu.com. I tillegg
-er det krav om samme pris på lulu.com og i bokhandlene, dermed blir
-prisen økt også hos lulu.com. Hva skulle jeg gjøre med den profitten
-uten å bryte med klausulen om ikkekommersiell? Løsningen var å gi
-bort profitten til CC-stiftelsen. Prisen på boken ble nesten
-tredoblet, til $19.99 (ca. 160,-) pluss frakt, men synligheten øker
-betraktelig når den kan finnes i katalogene til store nettbokhandlere.
-Det betyr at hvis du allerede har kjøpt boken har du fått den veldig
-billig, og kjøper du den nå, får du den fortsatt billig samt donerer i
-tillegg noen tiere til fremme av Creative Commons.</p>
-
-<p>Mens jeg var i gang med å titte etter informasjon om boken
-oppdaget jeg at den også var dukket opp på
-<a href="https://books.google.no/books?id=uKUGCwAAQBAJ">Google
-Books</a>, der en kan lese den på web. PDF-utgaven har ennå ikke
-dukket opp hos <a href="https://www.nb.no/">Nasjonalbiblioteket</a>,
-men det regner jeg med kommer på plass i løpet av noen uker. Boken er
-heller ikke dukket opp hos
-<a href="https://www.barnesandnoble.com/">Barnes & Noble</a> ennå, men
-jeg antar det bare er et tidsspørsmål før dette er på plass.</p>
-
-<p>Boken er dessverre ikke tilgjengelig fra norske bokhandlere, og
-kommer neppe til å bli det med det første. Årsaken er at for å få det
-til måtte jeg personlig håndtere bestilling av bøker, hvilket jeg ikke
-er interessert i å bruke tid på. Jeg kunne betalt ca 2000,- til
-<a href="http://www.bokbasen.no/">den norske bokbasen</a>, en felles
-database over bøker tilgjengelig for norske bokhandlere, for å få en
-oppføring der, men da måtte jeg tatt imot bestillinger på epost og
-sendt ut bøker selv. Det ville krevd at jeg var klar til å
-sende ut bøker på kort varsel, dvs. holdt meg med ekstra bøker,
-konvolutter og frimerker. Bokbasen har visst ikke opplegg for å be
-bokhandlene bestille direkte via web, så jeg droppet oppføring der.
-Jeg har spurt Haugen bok og Tronsmo direkte på epost om de er
-interessert i å ta inn boken i sin bestillingskatalog, men ikke fått
-svar, så jeg antar de ikke er interessert. Derimot har jeg fått en
-hyggelig henvendelse fra Biblioteksentralen som fortalte at de har
-lagt den inn i sin database slik at deres bibliotekskunder enkelt kan
-bestille den via dem.</p>
-
-<p>Boken er i følge
-<a href="http://bibsys-almaprimo.hosted.exlibrisgroup.com/primo_library/libweb/action/display.do?tabs=detailsTab&ct=display&fn=search&doc=BIBSYS_ILS71518423420002201&indx=1&recIds=BIBSYS_ILS71518423420002201&recIdxs=0&elementId=0&renderMode=poppedOut&displayMode=full&frbrVersion=&dscnt=0&tab=library_catalogue&dstmp=1448543801124&vl(freeText0)=fri%20kultur&vid=UBO&mode=Basic">Bibsys/Oria</a>
-og bokdatabasen til
-<a href="https://www.deich.folkebibl.no/cgi-bin/websok?tnr=1819617">Deichmanske</a>
-tilgjengelig fra flere biblioteker allerede, og alle eksemplarer er
-visst allerede utlånt med ventetid. Det synes jeg er veldig gledelig
-å se. Jeg håper mange kommer til å lese boken. Jeg tror den er
-spesielt egnet for foreldre og bekjente av oss nerder for å forklare
-hva slags problemer vi ser med dagens opphavsrettsregime.</p>
+ <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>
+ <div class="date">11th August 2016</div>
+ <div class="body"><p>This summer, I read a great article
+"<a href="https://www.usenix.org/publications/login/summer2016/curtsinger">coz:
+This Is the Profiler You're Looking For</a>" in USENIX ;login: about
+how to profile multi-threaded programs. It presented a system for
+profiling software by running experiences in the running program,
+testing how run time performance is affected by "speeding up" parts of
+the code to various degrees compared to a normal run. It does this by
+slowing down parallel threads while the "faster up" code is running
+and measure how this affect processing time. The processing time is
+measured using probes inserted into the code, either using progress
+counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
+can also measure unmodified code by measuring complete the program
+runtime and running the program several times instead.</p>
+
+<p>The project and presentation was so inspiring that I would like to
+get the system into Debian. I
+<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708">created
+a WNPP request for it</a> and contacted upstream to try to make the
+system ready for Debian by sending patches. The build process need to
+be changed a bit to avoid running 'git clone' to get dependencies, and
+to include the JavaScript web page used to visualize the collected
+profiling information included in the source package.
+But I expect that should work out fairly soon.</p>
+
+<p>The way the system work is fairly simple. To run an coz experiment
+on a binary with debug symbols available, start the program like this:
+
+<p><blockquote><pre>
+coz run --- program-to-run
+</pre></blockquote></p>
+
+<p>This will create a text file profile.coz with the instrumentation
+information. To show what part of the code affect the performance
+most, use a web browser and either point it to
+<a href="http://plasma-umass.github.io/coz/">http://plasma-umass.github.io/coz/</a>
+or use the copy from git (in the gh-pages branch). Check out this web
+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
+profiling more useful you include <coz.h> and insert the
+COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
+code, rebuild and run the profiler. This allow coz to do more
+targeted experiments.</p>
+
+<p>A video published by ACM
+<a href="https://www.youtube.com/watch?v=jE0V-p1odPg">presenting the
+Coz profiler</a> is available from Youtube. There is also a paper
+from the 25th Symposium on Operating Systems Principles available
+titled
+<a href="https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger">Coz:
+finding code that counts with causal profiling</a>.</p>
+
+<p><a href="https://github.com/plasma-umass/coz">The source code</a>
+for Coz is available from github. It will only build with clang
+because it uses a
+<a href="https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606">C++
+feature missing in GCC</a>, but I've submitted
+<a href="https://github.com/plasma-umass/coz/pull/67">a patch to solve
+it</a> and hope it will be included in the upstream source soon.</p>
+
+<p>Please get in touch if you, like me, would like to see this piece
+of software in Debian. I would very much like some help with the
+packaging effort, as I lack the in depth knowledge on how to package
+C++ libraries.</p>
</div>
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>.
+ 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>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html">The GNU General Public License is not magic pixie dust</a></div>
- <div class="date">30th November 2015</div>
- <div class="body"><p>A blog post from my fellow Debian developer Paul Wise titled
-"<a href="http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/">The
-GPL is not magic pixie dust</a>" explain the importance of making sure
-the <a href="http://www.gnu.org/copyleft/gpl.html">GPL</a> is enforced.
-I quote the blog post from Paul in full here with his permission:<p>
-
-<blockquote>
-
-<p><a href="https://sfconservancy.org/supporter/"><img src="https://sfconservancy.org/img/supporter-badge.png" width="194" height="90" alt="Become a Software Freedom Conservancy Supporter!" align="right" border="0" /></a></p>
-
-<blockquote>
-The GPL is not magic pixie dust. It does not work by itself.<br/>
-
-The first step is to choose a
-<a href="https://copyleft.org/">copyleft</a> license for your
-code.<br/>
-
-The next step is, when someone fails to follow that copyleft license,
-<b>it must be enforced</b><br/>
-
-and its a simple fact of our modern society that such type of
-work<br/>
-
-is incredibly expensive to do and incredibly difficult to do.
-</blockquote>
-
-<p><small>-- <a href="http://ebb.org/bkuhn/">Bradley Kuhn</a>, in
-<a href="http://faif.us/" title="Free as in Freedom">FaiF</a>
-<a href="http://faif.us/cast/2015/nov/24/0x57/">episode
-0x57</a></small></p>
-
-<p>As the Debian Website
-<a href="https://bugs.debian.org/794116">used</a>
-<a href="https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=1.24&r2=1.25">to</a>
-imply, public domain and permissively licensed software can lead to
-the production of more proprietary software as people discover useful
-software, extend it and or incorporate it into their hardware or
-software products. Copyleft licenses such as the GNU GPL were created
-to close off this avenue to the production of proprietary software but
-such licenses are not enough. With the ongoing adoption of Free
-Software by individuals and groups, inevitably the community's
-expectations of license compliance are violated, usually out of
-ignorance of the way Free Software works, but not always. As Karen
-and Bradley explained in <a href="http://faif.us/" title="Free as in
-Freedom">FaiF</a>
-<a href="http://faif.us/cast/2015/nov/24/0x57/">episode 0x57</a>,
-copyleft is nothing if no-one is willing and able to stand up in court
-to protect it. The reality of today's world is that legal
-representation is expensive, difficult and time consuming. With
-<a href="http://gpl-violations.org/">gpl-violations.org</a> in hiatus
-<a href="http://gpl-violations.org/news/20151027-homepage-recovers/">until</a>
-some time in 2016, the <a href="https://sfconservancy.org/">Software
-Freedom Conservancy</a> (a tax-exempt charity) is the major defender
-of the Linux project, Debian and other groups against GPL violations.
-In March the SFC supported a
-<a href="https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/">lawsuit
-by Christoph Hellwig</a> against VMware for refusing to
-<a href="https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html">comply
-with the GPL</a> in relation to their use of parts of the Linux
-kernel. Since then two of their sponsors pulled corporate funding and
-conferences
-<a href="https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/">blocked
-or cancelled their talks</a>. As a result they have decided to rely
-less on corporate funding and more on the broad community of
-individuals who support Free Software and copyleft. So the SFC has
-<a href="https://sfconservancy.org/news/2015/nov/23/2015fundraiser/">launched</a>
-a <a href="https://sfconservancy.org/supporter/">campaign</a> to create
-a community of folks who stand up for copyleft and the GPL by
-supporting their work on promoting and supporting copyleft and Free
-Software.</p>
-
-<p>If you support Free Software,
-<a href="https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/">like</a>
-what the SFC do, agree with their
-<a href="https://sfconservancy.org/linux-compliance/principles.html">compliance
-principles</a>, are happy about their
-<a href="https://sfconservancy.org/supporter/">successes</a> in 2015,
-work on a project that is an SFC
-<a href="https://sfconservancy.org/members/current/">member</a> and or
-just want to stand up for copyleft, please join
-<a href="https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA">Christopher
-Allan Webber</a>,
-<a href="https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/">Carol
-Smith</a>,
-<a href="http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/">Jono
-Bacon</a>, myself and
-<a href="https://sfconservancy.org/sponsors/#supporters">others</a> in
-becoming a
-<a href="https://sfconservancy.org/supporter/">supporter</a>. For the
-next week your donation will be
-<a href="https://sfconservancy.org/news/2015/nov/27/black-friday/">matched</a>
-by an anonymous donor. Please also consider asking your employer to
-match your donation or become a sponsor of SFC. Don't forget to
-spread the word about your support for SFC via email, your blog and or
-social media accounts.</p>
-
-</blockquote>
-
-<p>I agree with Paul on this topic and just signed up as a Supporter
-of Software Freedom Conservancy myself. Perhaps you should be a
-supporter too?</p>
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/Sales_number_for_the_Free_Culture_translation__first_half_of_2016.html">Sales number for the Free Culture translation, first half of 2016</a></div>
+ <div class="date"> 5th August 2016</div>
+ <div class="body"><p>As my regular readers probably remember, the last year I published
+a French and Norwegian translation of the classic
+<a href="http://www.free-culture.cc/">Free Culture book</a> by the
+founder of the Creative Commons movement, Lawrence Lessig. A bit less
+known is the fact that due to the way I created the translations,
+using docbook and po4a, I also recreated the English original. And
+because I already had created a new the PDF edition, I published it
+too. The revenue from the books are sent to the Creative Commons
+Corporation. In other words, I do not earn any money from this
+project, I just earn the warm fuzzy feeling that the text is available
+for a wider audience and more people can learn why the Creative
+Commons is needed.</p>
+
+<p>Today, just for fun, I had a look at the sales number over at
+Lulu.com, which take care of payment, printing and shipping. Much to
+my surprise, the English edition is selling better than both the
+French and Norwegian edition, despite the fact that it has been
+available in English since it was first published. In total, 24 paper
+books was sold for USD $19.99 between 2016-01-01 and 2016-07-31:</p>
+
+<table border="0">
+<tr><th>Title / language</th><th>Quantity</th></tr>
+<tr><td><a href="http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html">Culture Libre / French</a></td><td align="right">3</td></tr>
+<tr><td><a href="http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">Fri kultur / Norwegian</a></td><td align="right">7</td></tr>
+<tr><td><a href="http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html">Free Culture / English</a></td><td align="right">14</td></tr>
+</table>
+
+<p>The books are available both from Lulu.com and from large book
+stores like Amazon and Barnes&Noble. Most revenue, around $10 per
+book, is sent to the Creative Commons project when the book is sold
+directly by Lulu.com. The other channels give less revenue. The
+summary from Lulu tell me 10 books was sold via the Amazon channel, 10
+via Ingram (what is this?) and 4 directly by Lulu. And Lulu.com tells
+me that the revenue sent so far this year is USD $101.42. No idea
+what kind of sales numbers to expect, so I do not know if that is a
+good amount of sales for a 10 year old book or not. But it make me
+happy that the buyers find the book, and I hope they enjoy reading it
+as much as I did.</p>
+
+<p>The ebook edition is available for free from
+<a href="https://github.com/petterreinholdtsen/free-culture-lessig">Github</a>.</p>
+
+<p>If you would like to translate and publish the book in your native
+language, I would be happy to help make it happen. Please get in
+touch.</p>
</div>
<div class="tags">
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>.
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>.
</div>
<div class="padding"></div>
<div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html">PGP key transition statement for key EE4E02F9</a></div>
- <div class="date">17th November 2015</div>
- <div class="body"><p>I've needed a new OpenPGP key for a while, but have not had time to
-set it up properly. I wanted to generate it offline and have it
-available on <a href="http://shop.kernelconcepts.de/#openpgp">a OpenPGP
-smart card</a> for daily use, and learning how to do it and finding
-time to sit down with an offline machine almost took forever. But
-finally I've been able to complete the process, and have now moved
-from my old GPG key to a new GPG key. See
-<a href="http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt">the
-full transition statement, signed with both my old and new key</a> for
-the details. This is my new key:</p>
-
-<pre>
-pub 3936R/<a href="http://pgp.cs.uu.nl/stats/111D6B29EE4E02F9.html">111D6B29EE4E02F9</a> 2015-11-03 [expires: 2019-11-14]
- Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
-uid Petter Reinholdtsen <pere@hungry.com>
-uid Petter Reinholdtsen <pere@debian.org>
-sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
-sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
-sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
-</pre>
-
-<p>The key can be downloaded from the OpenPGP key servers, signed by
-my old key.</p>
-
-<p>If you signed my old key
-(<a href="http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html">DB4CCC4B2A30D729</a>),
-I'd very much appreciate a signature on my new key, details and
-instructions in the transition statement. I m happy to reciprocate if
-you have a similarly signed transition statement to present.</p>
+ <div class="title"><a href="http://people.skolelinux.org/pere/blog/Vitenskapen_tar_som_vanlig_feil_igjen___relativt_feil.html">Vitenskapen tar som vanlig feil igjen - relativt feil</a></div>
+ <div class="date"> 1st August 2016</div>
+ <div class="body"><p>For mange år siden leste jeg en klassisk tekst som gjorde såpass
+inntrykk på meg at jeg husker den fortsatt, flere år senere, og bruker
+argumentene fra den stadig vekk. Teksten var «The Relativity of
+Wrong» som Isaac Asimov publiserte i Skeptical Inquirer i 1989. Den
+gir litt perspektiv rundt formidlingen av vitenskapelige resultater.
+Jeg har hatt lyst til å kunne dele den også med folk som ikke
+behersker engelsk så godt, som barn og noen av mine eldre slektninger,
+og har savnet å ha den tilgjengelig på norsk. For to uker siden tok
+jeg meg sammen og kontaktet Asbjørn Dyrendal i foreningen Skepsis om
+de var interessert i å publisere en norsk utgave på bloggen sin, og da
+han var positiv tok jeg kontakt med Skeptical Inquirer og spurte om
+det var greit for dem. I løpet av noen dager fikk vi tilbakemelding
+fra Barry Karr hos The Skeptical Inquirer som hadde sjekket og fått OK
+fra Robyn Asimov som representerte arvingene i Asmiov-familien og gikk
+igang med oversettingen.</p>
+
+<p>Resultatet, <a href="http://www.skepsis.no/?p=1617">«Relativt
+feil»</a>, ble publisert på skepsis-bloggen for noen minutter siden.
+Jeg anbefaler deg på det varmeste å lese denne teksten og dele den med
+dine venner.</p>
+
+<p>For å håndtere oversettelsen og sikre at original og oversettelse
+var i sync brukte vi git, po4a, GNU make og Transifex. Det hele
+fungerte utmerket og gjorde det enkelt å dele tekstene og jobbe sammen
+om finpuss på formuleringene. Hadde hosted.weblate.org latt meg
+opprette nye prosjekter selv i stedet for å måtte kontakte
+administratoren der, så hadde jeg brukt weblate i stedet.</p>
</div>
<div class="tags">
- 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>.
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis</a>.
</div>
<li><a href="http://people.skolelinux.org/pere/blog/archive/2016/02/">February (2)</a></li>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2016/03/">March (3)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2016/04/">April (8)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2016/05/">May (8)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2016/06/">June (2)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2016/07/">July (2)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2016/08/">August (5)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2016/09/">September (2)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2016/10/">October (3)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2016/11/">November (1)</a></li>
+
</ul></li>
<li>2015
<li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (9)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (15)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (16)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (120)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (137)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (154)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (157)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/dld">dld (15)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/dld">dld (16)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (20)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (23)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (302)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (329)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (25)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (28)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (16)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (18)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/h264">h264 (20)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (42)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (11)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (13)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (19)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (37)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (39)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (7)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (8)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (273)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (280)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (177)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (182)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (22)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (26)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (58)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (61)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (92)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (94)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (45)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (51)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (4)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (5)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (48)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (49)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (3)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (4)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (10)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (36)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (42)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (2)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (55)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (59)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
projects / homepage.git / blobdiff