Generated.

[homepage.git] / blog / index.rss

diff --git a/blog/index.rss b/blog/index.rss
index b4880a0717c8c91cee3a5f3cba03402ee442927d..e42e39614e2a86dbe67edd3dba3a98a2389fd0f2 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -7,876 +7,634 @@
                 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
        
        <item>
                 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
        
        <item>

-               <title>Aktivitetsbånd som beskytter privatsfæren</title>
-               <link>http://people.skolelinux.org/pere/blog/Aktivitetsb_nd_som_beskytter_privatsf_ren.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Aktivitetsb_nd_som_beskytter_privatsf_ren.html</guid>
-                <pubDate>Thu, 3 Nov 2016 09:55:00 +0100</pubDate>
-               <description>&lt;p&gt;Jeg ble så imponert over
-&lt;a href=&quot;https://www.nrk.no/norge/forbrukerradet-mener-aktivitetsarmband-strider-mot-norsk-lov-1.13209079&quot;&gt;dagens
-gladnyhet på NRK&lt;/a&gt;, 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:
+               <title>Idea for storing trusted timestamps in a Noark 5 archive</title>
+               <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html</guid>
+                <pubDate>Wed, 7 Jun 2017 21:40:00 +0200</pubDate>
+               <description>&lt;p&gt;&lt;em&gt;This is a copy of
+&lt;a href=&quot;https://lists.nuug.no/pipermail/nikita-noark/2017-June/000297.html&quot;&gt;an
+email I posted to the nikita-noark mailing list&lt;/a&gt;.  Please follow up
+there if you would like to discuss this topic.  The background is that
+we are making a free software archive system based on the Norwegian
+&lt;a href=&quot;https://www.arkivverket.no/forvaltning-og-utvikling/regelverk-og-standarder/noark-standarden&quot;&gt;Noark
+5 standard&lt;/a&gt; for government archives.&lt;/em&gt;&lt;/p&gt;
+
+&lt;p&gt;I&#39;ve been wondering a bit lately how trusted timestamps could be
+stored in Noark 5.
+&lt;a href=&quot;https://en.wikipedia.org/wiki/Trusted_timestamping&quot;&gt;Trusted
+timestamps&lt;/a&gt; can be used to verify that some information
+(document/file/checksum/metadata) have not been changed since a
+specific time in the past.  This is useful to verify the integrity of
+the documents in the archive.&lt;/p&gt;
+
+&lt;p&gt;Then it occured to me, perhaps the trusted timestamps could be
+stored as dokument variants (ie dokumentobjekt referered to from
+dokumentbeskrivelse) with the filename set to the hash it is
+stamping?&lt;/p&gt;
+
+&lt;p&gt;Given a &quot;dokumentbeskrivelse&quot; with an associated &quot;dokumentobjekt&quot;,
+a new dokumentobjekt is associated with &quot;dokumentbeskrivelse&quot; with the
+same attributes as the stamped dokumentobjekt except these
+attributes:&lt;/p&gt;
+
+&lt;ul&gt;
+
+&lt;li&gt;format -&gt; &quot;RFC3161&quot;
+&lt;li&gt;mimeType -&gt; &quot;application/timestamp-reply&quot;
+&lt;li&gt;formatDetaljer -&gt; &quot;&amp;lt;source URL for timestamp service&amp;gt;&quot;
+&lt;li&gt;filenavn -&gt; &quot;&amp;lt;sjekksum&amp;gt;.tsr&quot;
+
+&lt;/ul&gt;
+
+&lt;p&gt;This assume a service following
+&lt;a href=&quot;https://tools.ietf.org/html/rfc3161&quot;&gt;IETF RFC 3161&lt;/a&gt; is
+used, which specifiy the given MIME type for replies and the .tsr file
+ending for the content of such trusted timestamp.  As far as I can
+tell from the Noark 5 specifications, it is OK to have several
+variants/renderings of a dokument attached to a given
+dokumentbeskrivelse objekt.  It might be stretching it a bit to make
+some of these variants represent crypto-signatures useful for
+verifying the document integrity instead of representing the dokument
+itself.&lt;/p&gt;
+
+&lt;p&gt;Using the source of the service in formatDetaljer allow several
+timestamping services to be used.  This is useful to spread the risk
+of key compromise over several organisations.  It would only be a
+problem to trust the timestamps if all of the organisations are
+compromised.&lt;/p&gt;
+
+&lt;p&gt;The following oneliner on Linux can be used to generate the tsr
+file.  $input is the path to the file to checksum, and $sha256 is the
+SHA-256 checksum of the file (ie the &quot;&lt;sjekksum&gt;.tsr&quot; value mentioned
+above).&lt;/p&gt;

 
 

-&lt;blockquote&gt;
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+openssl ts -query -data &quot;$inputfile&quot; -cert -sha256 -no_nonce \
+  | curl -s -H &quot;Content-Type: application/timestamp-query&quot; \
+      --data-binary &quot;@-&quot; http://zeitstempel.dfn.de &gt; $sha256.tsr
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;

 
 

-&lt;p&gt;Jeg ble veldig glad over å lese at Forbrukerrådet
-&lt;a href=&quot;http://www.forbrukerradet.no/siste-nytt/klager-inn-aktivitetsarmband-for-brudd-pa-norsk-lov/&quot;&gt;klager
-inn flere aktivitetsbånd til Datatilsynet for dårlige vilkår&lt;/a&gt;.  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
-&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html&quot;&gt;en
-fritt og åpent standardisert&lt;/a&gt; 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.&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p&gt;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?&lt;/p&gt;
+&lt;p&gt;To verify the timestamp, you first need to download the public key
+of the trusted timestamp service, for example using this command:&lt;/p&gt;

 
 

-&lt;/blockquote&gt;
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+wget -O ca-cert.txt \
+  https://pki.pca.dfn.de/global-services-ca/pub/cacert/chain.txt
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;Note, the public key should be stored alongside the timestamps in
+the archive to make sure it is also available 100 years from now.  It
+is probably a good idea to standardise how and were to store such
+public keys, to make it easier to find for those trying to verify
+documents 100 or 1000 years from now. :)&lt;/p&gt;

 
 

-&lt;p&gt;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 &quot;lovlige&quot;, men fortsatt tvinge kundene til å
-dele sine personopplysninger med leverandøren.&lt;/p&gt;
+&lt;p&gt;The verification itself is a simple openssl command:&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+openssl ts -verify -data $inputfile -in $sha256.tsr \
+  -CAfile ca-cert.txt -text
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;Is there any reason this approach would not work?  Is it somehow against
+the Noark 5 specification?&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
-               <link>http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
-                <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
-               <description>&lt;p&gt;In July
-&lt;a href=&quot;http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html&quot;&gt;I
-wrote how to get the Signal Chrome/Chromium app working&lt;/a&gt; without
-the ability to receive SMS messages (aka without a cell phone).  It is
-time to share some experiences and provide an updated setup.&lt;/p&gt;
-
-&lt;p&gt;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 &lt;tt&gt;userdata/&lt;/tt&gt; 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 &#39;reset session&#39; 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.&lt;/p&gt;
-
-&lt;p&gt;I&#39;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.&lt;/p&gt;
-
-&lt;p&gt;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 &#39;Register without mobile phone&#39; to get going
-now.  I&#39;ve also modified the timeout code to always set it to 90 days
-in the future, to avoid having to patch the code regularly.&lt;/p&gt;
-
-&lt;p&gt;So, the updated recipe for Debian Jessie:&lt;/p&gt;
-
-&lt;ol&gt;
+               <title>Når nynorskoversettelsen svikter til eksamen...</title>
+               <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</guid>
+                <pubDate>Sat, 3 Jun 2017 08:20:00 +0200</pubDate>
+               <description>&lt;p&gt;&lt;a href=&quot;http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-622459b.html&quot;&gt;Aftenposten
+melder i dag&lt;/a&gt; om feil i eksamensoppgavene for eksamen i politikk og
+menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
+like.  Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
+på om den fri oversetterløsningen
+&lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium&lt;/a&gt; ville gjort en bedre
+jobb enn Utdanningsdirektoratet.  Det kan se slik ut.&lt;/p&gt;
+
+&lt;p&gt;Her er bokmålsoppgaven fra eksamenen:&lt;/p&gt;

 
 

-&lt;li&gt;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.
+&lt;blockquote&gt;
+&lt;p&gt;Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
+rolle og muligheter til å håndtere internasjonale utfordringer, som
+for eksempel flykningekrisen.&lt;/p&gt;

 
 

-&lt;pre&gt;
-apt install git tor chromium
-git clone https://github.com/WhisperSystems/Signal-Desktop.git
-&lt;/pre&gt;&lt;/li&gt;
+&lt;p&gt;Vedlegge er eksempler på tekster som kan gi relevante perspektiver
+på temaet:&lt;/p&gt;
+&lt;ol&gt;
+&lt;li&gt;Flykningeregnskapet 2016, UNHCR og IDMC
+&lt;li&gt;«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
+&lt;/ol&gt;

 
 

-&lt;li&gt;Modify the source code using command listed in the the patch
-block below.&lt;/li&gt;
+&lt;/blockquote&gt;

 
 

-&lt;li&gt;Start Signal using the run-signal-app wrapper (for example using
-&lt;tt&gt;`pwd`/run-signal-app&lt;/tt&gt;).
+&lt;p&gt;Dette oversetter Apertium slik:&lt;/p&gt;

 
 

-&lt;li&gt;Click on the &#39;Register without mobile phone&#39;, 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
-&#39;Register&#39;.  Note, the phone number you use will be user Signal
-username, ie the way others can find you on Signal.&lt;/li&gt;
+&lt;blockquote&gt;
+&lt;p&gt;Drøft utfordringane knytte til nasjonalstatane sine og rolla til
+andre aktørar og høve til å handtera internasjonale utfordringar, som
+til dømes *flykningekrisen.&lt;/p&gt;

 
 

-&lt;li&gt;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.&lt;/li&gt;
+&lt;p&gt;Vedleggja er døme på tekster som kan gje relevante perspektiv på
+temaet:&lt;/p&gt;

 
 

+&lt;ol&gt;
+&lt;li&gt;*Flykningeregnskapet 2016, *UNHCR og *IDMC&lt;/li&gt;
+&lt;li&gt;«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015&lt;/li&gt;

 &lt;/ol&gt;
 
 &lt;/ol&gt;
 

-&lt;p&gt;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
-&lt;a href=&quot;https://github.com/LibreSignal/LibreSignal/issues/37&quot;&gt;the
-LibreSignal issue tracker&lt;/a&gt; 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 &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;
-once it &lt;a href=&quot;https://bugs.debian.org/830265&quot;&gt;work on my
-laptop&lt;/a&gt;?  It already work on Windows and Android, and is included
-in &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; and
-&lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, but not
-working on Debian Stable.&lt;/p&gt;
-
-&lt;p&gt;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:&lt;/p&gt;
-
-&lt;pre&gt;
-cd Signal-Desktop; cat &amp;lt;&amp;lt;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 = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
-+    var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org&#39;;
-     var SERVER_PORTS = [80, 4433, 8443];
--    var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
-+    var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
-     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() {
-     &#39;use strict&#39;;
--    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 {
-                 &#39;click .step1&#39;: this.selectStep.bind(this, 1),
-                 &#39;click .step2&#39;: this.selectStep.bind(this, 2),
--                &#39;click .step3&#39;: this.selectStep.bind(this, 3)
-+                &#39;click .step3&#39;: this.selectStep.bind(this, 3),
-+                &#39;click .callreg&#39;: function() { extension.install(&#39;standalone&#39;) },
-             };
-         },
-         clearQR: function() {
-diff --git a/options.html b/options.html
-index dc0f28e..8d709f6 100644
---- a/options.html
-+++ b/options.html
-@@ -14,7 +14,10 @@
-         &amp;lt;div class=&#39;nav&#39;&gt;
-           &amp;lt;h1&gt;{{ installWelcome }}&amp;lt;/h1&gt;
-           &amp;lt;p&gt;{{ installTagline }}&amp;lt;/p&gt;
--          &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt; &amp;lt;/div&gt;
-+          &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt;
-+          &amp;lt;br&gt; &amp;lt;a class=&quot;button callreg&quot;&gt;Register without mobile phone&amp;lt;/a&gt;
-+
-+        &amp;lt;/div&gt;
-           &amp;lt;span class=&#39;dot step1 selected&#39;&gt;&amp;lt;/span&gt;
-           &amp;lt;span class=&#39;dot step2&#39;&gt;&amp;lt;/span&gt;
-           &amp;lt;span class=&#39;dot step3&#39;&gt;&amp;lt;/span&gt;
---- /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=&quot;`pwd`/userdata&quot;
-+if [ -d &quot;$userdata&quot; ] &amp;&amp; [ ! -d &quot;$userdata/.git&quot; ] ; then
-+    (cd $userdata &amp;&amp; git init)
-+fi
-+(cd $userdata &amp;&amp; git add . &amp;&amp; git commit -m &quot;Current status.&quot; || true)
-+exec chromium \
-+  --proxy-server=&quot;socks://localhost:9050&quot; \
-+  --user-data-dir=$userdata --load-and-launch-app=`pwd`
-EOF
-chmod a+rx run-signal-app
-&lt;/pre&gt;
-
-&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
-activities, please send Bitcoin donations to my address
-&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
+&lt;/blockquote&gt;
+
+&lt;p&gt;Ord som ikke ble forstått er markert med stjerne (*), og trenger
+ekstra språksjekk.  Men ingen ord er forsvunnet, slik det var i
+oppgaven elevene fikk presentert på eksamen.  Jeg mistenker dog at
+&quot;andre aktørers rolle og muligheter til ...&quot; burde vært oversatt til
+&quot;rolla til andre aktørar og deira høve til ...&quot; eller noe slikt, men
+det er kanskje flisespikking.  Det understreker vel bare at det alltid
+trengs korrekturlesning etter automatisk oversettelse.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>NRKs kildevern når NRK-epost deles med utenlands etterretning?</title>
-               <link>http://people.skolelinux.org/pere/blog/NRKs_kildevern_n_r_NRK_epost_deles_med_utenlands_etterretning_.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/NRKs_kildevern_n_r_NRK_epost_deles_med_utenlands_etterretning_.html</guid>
-                <pubDate>Sat, 8 Oct 2016 08:15:00 +0200</pubDate>
-               <description>&lt;p&gt;NRK
-&lt;a href=&quot;https://nrkbeta.no/2016/09/02/securing-whistleblowers/&quot;&gt;lanserte
-for noen uker siden&lt;/a&gt; en ny
-&lt;a href=&quot;https://www.nrk.no/varsle/&quot;&gt;varslerportal som bruker
-SecureDrop til å ta imot tips&lt;/a&gt; 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 &quot;Nyhetstips som ikke krever denne
-typen ekstra vern vil vi gjerne ha på nrk.no/03030&quot;, 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.&lt;/p&gt;
-
-&lt;p&gt;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 &quot;nrk-no.mail.protection.outlook.com&quot;.  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
-&lt;tt&gt;traceroute&lt;/tt&gt;, 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).&lt;/p&gt;
-
-&lt;p&gt;Vi vet fra
-&lt;a href=&quot;https://no.wikipedia.org/wiki/FRA-loven&quot;&gt;introduksjonen av
-FRA-loven&lt;/a&gt; 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
-&lt;a href=&quot;https://www.theguardian.com/world/2013/jul/11/microsoft-nsa-collaboration-user-data&quot;&gt;samarbeider
-med USAs etterretning på flere områder&lt;/a&gt;.  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.&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p&gt;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).&lt;/p&gt;
-
-&lt;p&gt;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
-&lt;a href=&quot;http://www.lovdata.no/all/hl-19850524-028.html#14&quot;&gt;Sentralbanklovens
-paragraf 14&lt;/a&gt; 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 &amp; 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.&lt;/p&gt;
-
-&lt;p&gt;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 &quot;i skyen&quot; (eller
-andre folks datamaskiner, som det jo innebærer), så jeg vet ikke hvor
-lenge det i så fall vil vare.&lt;/p&gt;
-
-&lt;p&gt;I tillegg vet en jo at
-&lt;a href=&quot;https://www.nrk.no/ytring/elektronisk-kildevern-i-nrk-1.11941196&quot;&gt;NRK
-har valgt å gi nasjonal sikkerhetsmyndighet (NSM) tilgang til å se på
-intern og ekstern Internett-trafikk&lt;/a&gt; hos NRK ved oppsett av såkalte
-VDI-noder, på tross av
-&lt;a href=&quot;https://www.nrk.no/ytring/bekymring-for-nrks-kildevern-1.11941584&quot;&gt;protester
-fra NRKs journalistlag&lt;/a&gt;.  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.&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
+               <title>Epost inn som arkivformat i Riksarkivarens forskrift?</title>
+               <link>http://people.skolelinux.org/pere/blog/Epost_inn_som_arkivformat_i_Riksarkivarens_forskrift_.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Epost_inn_som_arkivformat_i_Riksarkivarens_forskrift_.html</guid>
+                <pubDate>Thu, 27 Apr 2017 11:30:00 +0200</pubDate>
+               <description>&lt;p&gt;I disse dager, med frist 1. mai, har Riksarkivaren ute en høring på
+sin forskrift.  Som en kan se er det ikke mye tid igjen før fristen
+som går ut på søndag.  Denne forskriften er det som lister opp hvilke
+formater det er greit å arkivere i
+&lt;a href=&quot;http://www.arkivverket.no/arkivverket/Offentleg-forvalting/Noark/Noark-5&quot;&gt;Noark
+5-løsninger&lt;/a&gt; i Norge.&lt;/p&gt;
+
+&lt;p&gt;Jeg fant høringsdokumentene hos
+&lt;a href=&quot;https://www.arkivrad.no/aktuelt/riksarkivarens-forskrift-pa-horing&quot;&gt;Norsk
+Arkivråd&lt;/a&gt; etter å ha blitt tipset på epostlisten til
+&lt;a href=&quot;https://github.com/hiOA-ABI/nikita-noark5-core&quot;&gt;fri
+programvareprosjektet Nikita Noark5-Core&lt;/a&gt;, som lager et Noark 5
+Tjenestegresesnitt.  Jeg er involvert i Nikita-prosjektet og takket
+være min interesse for tjenestegrensesnittsprosjektet har jeg lest en
+god del Noark 5-relaterte dokumenter, og til min overraskelse oppdaget
+at standard epost ikke er på listen over godkjente formater som kan
+arkiveres.  Høringen med frist søndag er en glimrende mulighet til å
+forsøke å gjøre noe med det.  Jeg holder på med
+&lt;a href=&quot;https://github.com/petterreinholdtsen/noark5-tester/blob/master/docs/hoering-arkivforskrift.tex&quot;&gt;egen
+høringsuttalelse&lt;/a&gt;, og lurer på om andre er interessert i å støtte
+forslaget om å tillate arkivering av epost som epost i arkivet.&lt;/p&gt;
+
+&lt;p&gt;Er du igang med å skrive egen høringsuttalelse allerede?  I så fall
+kan du jo vurdere å ta med en formulering om epost-lagring. Jeg tror
+ikke det trengs så mye.  Her et kort forslag til tekst:&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;
+
+  &lt;p&gt;Viser til høring sendt ut 2017-02-17 (Riksarkivarens referanse
+  2016/9840 HELHJO), og tillater oss å sende inn noen innspill om
+  revisjon av Forskrift om utfyllende tekniske og arkivfaglige
+  bestemmelser om behandling av offentlige arkiver (Riksarkivarens
+  forskrift).&lt;/p&gt;
+
+  &lt;p&gt;Svært mye av vår kommuikasjon foregår i dag på e-post.  Vi
+  foreslår derfor at Internett-e-post, slik det er beskrevet i IETF
+  RFC 5322,
+  &lt;a href=&quot;https://tools.ietf.org/html/rfc5322&quot;&gt;https://tools.ietf.org/html/rfc5322&lt;/a&gt;. bør
+  inn som godkjent dokumentformat.  Vi foreslår at forskriftens
+  oversikt over godkjente dokumentformater ved innlevering i § 5-16
+  endres til å ta med Internett-e-post.&lt;/p&gt;
+
+&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;Som del av arbeidet med tjenestegrensesnitt har vi testet hvordan
+epost kan lagres i en Noark 5-struktur, og holder på å skrive et
+forslag om hvordan dette kan gjøres som vil bli sendt over til
+arkivverket så snart det er ferdig.  De som er interesserte kan
+&lt;a href=&quot;https://github.com/petterreinholdtsen/noark5-tester/blob/master/docs/epostlagring.md&quot;&gt;følge
+fremdriften på web&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;Oppdatering 2017-04-28: I dag ble høringuttalelsen jeg skrev
+  &lt;a href=&quot;https://www.nuug.no/news/NUUGs_h_ringuttalelse_til_Riksarkivarens_forskrift.shtml&quot;&gt;sendt
+  inn av foreningen NUUG&lt;/a&gt;.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
-               <link>http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
-                <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
-               <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
-system&lt;/a&gt; provide a practical and easy way to figure out which
-packages support the hardware in a given machine.  The command line
-tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; 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 &lt;tt&gt;pcscd&lt;/tt&gt; if
-that package isn&#39;t already installed, and if you plug in a USB video
-camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
-cheese is currently missing.  This already work just fine.&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p&gt;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
-&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html&quot;&gt;a
-recipe on how to add such meta-information&lt;/a&gt; in a blog post last
-December.  If you have a hardware related package in Debian, please
-announce the relevant hardware IDs using AppStream.&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p&gt;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 &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
-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.&lt;/p&gt;
-
-&lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;.  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
-&lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:
-
-&lt;p&gt;&lt;pre&gt;
-SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
-    SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
-&lt;/pre&gt;&lt;/p&gt;
-
-&lt;p&gt;The key part is the &#39;TAG+=&quot;uaccess&quot;&#39; 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
-&lt;tt&gt;70-uaccess.rules&lt;/tt&gt;).  Perhaps a lintian check should be created
-to detect this?&lt;/p&gt;
-
-&lt;p&gt;I&#39;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
-&lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;.  If it is, I guess the
-indirect method is the preferred way.  Michael
-&lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
-documentation from the systemd project&lt;/a&gt; and I hope it will make
-this clearer.  For now I use the generic classes when they exist and
-is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
-directly if no such class exist.&lt;/p&gt;
-
-&lt;p&gt;To learn more about the isenkram system, please check out
-&lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
-blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
-
-&lt;p&gt;To help out making life for LEGO constructors in Debian easier,
-please join us on our IRC channel
-&lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
-the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
-LEGO team&lt;/a&gt; in the Alioth project we created yesterday.  A mailing
-list is not yet created, but we are working on it. :)&lt;/p&gt;
-
-&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
-activities, please send Bitcoin donations to my address
-&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
+               <title>Offentlig elektronisk postjournal blokkerer tilgang for utvalgte webklienter</title>
+               <link>http://people.skolelinux.org/pere/blog/Offentlig_elektronisk_postjournal_blokkerer_tilgang_for_utvalgte_webklienter.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Offentlig_elektronisk_postjournal_blokkerer_tilgang_for_utvalgte_webklienter.html</guid>
+                <pubDate>Thu, 20 Apr 2017 13:00:00 +0200</pubDate>
+               <description>&lt;p&gt;Jeg oppdaget i dag at &lt;a href=&quot;https://www.oep.no/&quot;&gt;nettstedet som
+publiserer offentlige postjournaler fra statlige etater&lt;/a&gt;, OEP, har
+begynt å blokkerer enkelte typer webklienter fra å få tilgang.  Vet
+ikke hvor mange det gjelder, men det gjelder i hvert fall libwww-perl
+og curl.  For å teste selv, kjør følgende:&lt;/p&gt;
+
+&lt;blockquote&gt;&lt;pre&gt;
+% curl -v -s https://www.oep.no/pub/report.xhtml?reportId=3 2&gt;&amp;1 |grep &#39;&lt; HTTP&#39;
+&lt; HTTP/1.1 404 Not Found
+% curl -v -s --header &#39;User-Agent:Opera/12.0&#39; https://www.oep.no/pub/report.xhtml?reportId=3 2&gt;&amp;1 |grep &#39;&lt; HTTP&#39;
+&lt; HTTP/1.1 200 OK
+%
+&lt;/pre&gt;&lt;/blockquote&gt;
+
+&lt;p&gt;Her kan en se at tjenesten gir «404 Not Found» for curl i
+standardoppsettet, mens den gir «200 OK» hvis curl hevder å være Opera
+versjon 12.0.  Offentlig elektronisk postjournal startet blokkeringen
+2017-03-02.&lt;/p&gt;
+
+&lt;p&gt;Blokkeringen vil gjøre det litt vanskeligere å maskinelt hente
+informasjon fra oep.no.  Kan blokkeringen være gjort for å hindre
+automatisert innsamling av informasjon fra OEP, slik Pressens
+Offentlighetsutvalg gjorde for å dokumentere hvordan departementene
+hindrer innsyn i
+&lt;a href=&quot;http://presse.no/dette-mener-np/undergraver-offentlighetsloven/&quot;&gt;rapporten
+«Slik hindrer departementer innsyn» som ble publiserte i januar
+2017&lt;/a&gt;.  Det virker usannsynlig, da det jo er trivielt å bytte
+User-Agent til noe nytt.&lt;/p&gt;
+
+&lt;p&gt;Finnes det juridisk grunnlag for det offentlige å diskriminere
+webklienter slik det gjøres her?  Der tilgang gis eller ikke alt etter
+hva klienten sier at den heter?  Da OEP eies av DIFI og driftes av
+Basefarm, finnes det kanskje noen dokumenter sendt mellom disse to
+aktørene man kan be om innsyn i for å forstå hva som har skjedd.  Men
+&lt;a href=&quot;https://www.oep.no/search/result.html?period=dateRange&amp;fromDate=01.01.2016&amp;toDate=01.04.2017&amp;dateType=documentDate&amp;caseDescription=&amp;descType=both&amp;caseNumber=&amp;documentNumber=&amp;sender=basefarm&amp;senderType=both&amp;documentType=all&amp;legalAuthority=&amp;archiveCode=&amp;list2=196&amp;searchType=advanced&amp;Search=Search+in+records&quot;&gt;postjournalen
+til DIFI viser kun to dokumenter&lt;/a&gt; det siste året mellom DIFI og
+Basefarm.
+&lt;a href=&quot;https://www.mimesbronn.no/request/blokkering_av_tilgang_til_oep_fo&quot;&gt;Mimes brønn neste&lt;/a&gt;,
+tenker jeg.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Aftenposten-redaktøren med lua i hånda</title>
-               <link>http://people.skolelinux.org/pere/blog/Aftenposten_redakt_ren_med_lua_i_h_nda.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Aftenposten_redakt_ren_med_lua_i_h_nda.html</guid>
-                <pubDate>Fri, 9 Sep 2016 11:30:00 +0200</pubDate>
-               <description>&lt;p&gt;En av dagens nyheter er at Aftenpostens redaktør Espen Egil Hansen
-bruker
-&lt;a href=&quot;https://www.nrk.no/kultur/aftenposten-brukar-heile-forsida-pa-facebook-kritikk-1.13126918&quot;&gt;forsiden
-av papiravisen på et åpent brev til Facebooks sjef Mark Zuckerberg om
-Facebooks fjerning av bilder, tekster og sider de ikke liker&lt;/a&gt;.  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
-&lt;a href=&quot;https://stallman.org/facebook.html&quot;&gt;Richard Stallmans side om
-Facebook&lt;/a&gt;.
-
-&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p&gt;Men det vil nok ta tid, i et Norge der de fleste nettredaktører
-&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Snurpenot_overv_kning_av_sensitiv_personinformasjon.html&quot;&gt;deler
-sine leseres personopplysinger med utenlands etterretning&lt;/a&gt;.&lt;/p&gt;
-
-&lt;p&gt;For øvrig burde varsleren Edward Snowden få politisk asyl i
-Norge.&lt;/p&gt;
+               <title>Free software archive system Nikita now able to store documents</title>
+               <link>http://people.skolelinux.org/pere/blog/Free_software_archive_system_Nikita_now_able_to_store_documents.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Free_software_archive_system_Nikita_now_able_to_store_documents.html</guid>
+                <pubDate>Sun, 19 Mar 2017 08:00:00 +0100</pubDate>
+               <description>&lt;p&gt;The &lt;a href=&quot;https://github.com/hiOA-ABI/nikita-noark5-core&quot;&gt;Nikita
+Noark 5 core project&lt;/a&gt; is implementing the Norwegian standard for
+keeping an electronic archive of government documents.
+&lt;a href=&quot;http://www.arkivverket.no/arkivverket/Offentlig-forvaltning/Noark/Noark-5/English-version&quot;&gt;The
+Noark 5 standard&lt;/a&gt; document the requirement for data systems used by
+the archives in the Norwegian government, and the Noark 5 web interface
+specification document a REST web service for storing, searching and
+retrieving documents and metadata in such archive.  I&#39;ve been involved
+in the project since a few weeks before Christmas, when the Norwegian
+Unix User Group
+&lt;a href=&quot;https://www.nuug.no/news/NOARK5_kjerne_som_fri_programvare_f_r_epostliste_hos_NUUG.shtml&quot;&gt;announced
+it supported the project&lt;/a&gt;.  I believe this is an important project,
+and hope it can make it possible for the government archives in the
+future to use free software to keep the archives we citizens depend
+on.  But as I do not hold such archive myself, personally my first use
+case is to store and analyse public mail journal metadata published
+from the government.  I find it useful to have a clear use case in
+mind when developing, to make sure the system scratches one of my
+itches.&lt;/p&gt;
+
+&lt;p&gt;If you would like to help make sure there is a free software
+alternatives for the archives, please join our IRC channel
+(&lt;a href=&quot;irc://irc.freenode.net/%23nikita&quot;&quot;&gt;#nikita on
+irc.freenode.net&lt;/a&gt;) and
+&lt;a href=&quot;https://lists.nuug.no/mailman/listinfo/nikita-noark&quot;&gt;the
+project mailing list&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;When I got involved, the web service could store metadata about
+documents.  But a few weeks ago, a new milestone was reached when it
+became possible to store full text documents too.  Yesterday, I
+completed an implementation of a command line tool
+&lt;tt&gt;archive-pdf&lt;/tt&gt; to upload a PDF file to the archive using this
+API.  The tool is very simple at the moment, and find existing
+&lt;a href=&quot;https://en.wikipedia.org/wiki/Fonds&quot;&gt;fonds&lt;/a&gt;, series and
+files while asking the user to select which one to use if more than
+one exist.  Once a file is identified, the PDF is associated with the
+file and uploaded, using the title extracted from the PDF itself.  The
+process is fairly similar to visiting the archive, opening a cabinet,
+locating a file and storing a piece of paper in the archive.  Here is
+a test run directly after populating the database with test data using
+our API tester:&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+~/src//noark5-tester$ ./archive-pdf mangelmelding/mangler.pdf
+using arkiv: Title of the test fonds created 2017-03-18T23:49:32.103446
+using arkivdel: Title of the test series created 2017-03-18T23:49:32.103446
+
+ 0 - Title of the test case file created 2017-03-18T23:49:32.103446
+ 1 - Title of the test file created 2017-03-18T23:49:32.103446
+Select which mappe you want (or search term): 0
+Uploading mangelmelding/mangler.pdf
+  PDF title: Mangler i spesifikasjonsdokumentet for NOARK 5 Tjenestegrensesnitt
+  File 2017/1: Title of the test case file created 2017-03-18T23:49:32.103446
+~/src//noark5-tester$
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;You can see here how the fonds (arkiv) and serie (arkivdel) only had
+one option, while the user need to choose which file (mappe) to use
+among the two created by the API tester.  The &lt;tt&gt;archive-pdf&lt;/tt&gt;
+tool can be found in the git repository for the API tester.&lt;/p&gt;
+
+&lt;p&gt;In the project, I have been mostly working on
+&lt;a href=&quot;https://github.com/petterreinholdtsen/noark5-tester&quot;&gt;the API
+tester&lt;/a&gt; so far, while getting to know the code base.  The API
+tester currently use
+&lt;a href=&quot;https://en.wikipedia.org/wiki/HATEOAS&quot;&gt;the HATEOAS links&lt;/a&gt;
+to traverse the entire exposed service API and verify that the exposed
+operations and objects match the specification, as well as trying to
+create objects holding metadata and uploading a simple XML file to
+store.  The tester has proved very useful for finding flaws in our
+implementation, as well as flaws in the reference site and the
+specification.&lt;/p&gt;
+
+&lt;p&gt;The test document I uploaded is a summary of all the specification
+defects we have collected so far while implementing the web service.
+There are several unclear and conflicting parts of the specification,
+and we have
+&lt;a href=&quot;https://github.com/petterreinholdtsen/noark5-tester/tree/master/mangelmelding&quot;&gt;started
+writing down&lt;/a&gt; the questions we get from implementing it.  We use a
+format inspired by how &lt;a href=&quot;http://www.opengroup.org/austin/&quot;&gt;The
+Austin Group&lt;/a&gt; collect defect reports for the POSIX standard with
+&lt;a href=&quot;http://www.opengroup.org/austin/mantis.html&quot;&gt;their
+instructions for the MANTIS defect tracker system&lt;/a&gt;, in lack of an official way to structure defect reports for Noark 5 (our first submitted defect report was a &lt;a href=&quot;https://github.com/petterreinholdtsen/noark5-tester/blob/master/mangelmelding/sendt/2017-03-15-mangel-prosess.md&quot;&gt;request for a procedure for submitting defect reports&lt;/a&gt; :).
+
+&lt;p&gt;The Nikita project is implemented using Java and Spring, and is
+fairly easy to get up and running using Docker containers for those
+that want to test the current code base.  The API tester is
+implemented in Python.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>E-tjenesten ber om innsyn i eposten til partiene på Stortinget</title>
-               <link>http://people.skolelinux.org/pere/blog/E_tjenesten_ber_om_innsyn_i_eposten_til_partiene_p__Stortinget.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/E_tjenesten_ber_om_innsyn_i_eposten_til_partiene_p__Stortinget.html</guid>
-                <pubDate>Tue, 6 Sep 2016 23:00:00 +0200</pubDate>
-               <description>&lt;p&gt;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
-&lt;a href=&quot;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&quot;&gt;forslag
-om at e-tjenesten skal få lov til a avlytte all Internett-trafikk&lt;/a&gt;
-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.&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p
-
-&lt;p&gt;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 &lt;a href=&quot;http://ipinfo.io/&quot;&gt;ipinfo.io&lt;/a&gt;
-for å få en ide om hvor i verden en IP-adresse hører til.&lt;/p&gt;
-
-&lt;p&gt;På den positive siden vil forslaget gjøre at enda flere blir
-motivert til å ta grep for å bruke
-&lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt; og krypterte
-kommunikasjonsløsninger for å kommunisere med sine kjære, for å sikre
-at privatsfæren vernes.  Selv bruker jeg blant annet
-&lt;a href=&quot;https://www.freedomboxfoundation.org/&quot;&gt;FreedomBox&lt;/a&gt; og
-&lt;a href=&quot;https://whispersystems.org/&quot;&gt;Signal&lt;/a&gt; til slikt.  Ingen av
-dem er optimale, men de fungerer ganske bra allerede og øker kostnaden
-for dem som ønsker å invadere mitt privatliv.&lt;/p&gt;
-
-&lt;p&gt;For øvrig burde varsleren Edward Snowden få politisk asyl i
-Norge.&lt;/p&gt;
-
-&lt;!--
-
-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
-
---&gt;
+               <title>Detecting NFS hangs on Linux without hanging yourself...</title>
+               <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</guid>
+                <pubDate>Thu, 9 Mar 2017 15:20:00 +0100</pubDate>
+               <description>&lt;p&gt;Over the years, administrating thousand of NFS mounting linux
+computers at the time, I often needed a way to detect if the machine
+was experiencing NFS hang.  If you try to use &lt;tt&gt;df&lt;/tt&gt; or look at a
+file or directory affected by the hang, the process (and possibly the
+shell) will hang too.  So you want to be able to detect this without
+risking the detection process getting stuck too.  It has not been
+obvious how to do this.  When the hang has lasted a while, it is
+possible to find messages like these in dmesg:&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;
+nfs: server nfsserver not responding, still trying
+&lt;br&gt;nfs: server nfsserver OK
+&lt;/blockquote&gt;&lt;/p&gt;
+  
+&lt;p&gt;It is hard to know if the hang is still going on, and it is hard to
+be sure looking in dmesg is going to work.  If there are lots of other
+messages in dmesg the lines might have rotated out of site before they
+are noticed.&lt;/p&gt;
+
+&lt;p&gt;While reading through the nfs client implementation in linux kernel
+code, I came across some statistics that seem to give a way to detect
+it.  The om_timeouts sunrpc value in the kernel will increase every
+time the above log entry is inserted into dmesg.  And after digging a
+bit further, I discovered that this value show up in
+/proc/self/mountstats on Linux.&lt;/p&gt;
+
+&lt;p&gt;The mountstats content seem to be shared between files using the
+same file system context, so it is enough to check one of the
+mountstats files to get the state of the mount point for the machine.
+I assume this will not show lazy umounted NFS points, nor NFS mount
+points in a different process context (ie with a different filesystem
+view), but that does not worry me.&lt;/p&gt;
+
+&lt;p&gt;The content for a NFS mount point look similar to this:&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+[...]
+device /dev/mapper/Debian-var mounted on /var with fstype ext3
+device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
+        opts:   rw,vers=3,rsize=65536,wsize=65536,namlen=255,acregmin=3,acregmax=60,acdirmin=30,acdirmax=60,soft,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=129.240.3.145,mountvers=3,mountport=4048,mountproto=udp,local_lock=all
+        age:    7863311
+        caps:   caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
+        sec:    flavor=1,pseudoflavor=1
+        events: 61063112 732346265 1028140 35486205 16220064 8162542 761447191 71714012 37189 3891185 45561809 110486139 4850138 420353 15449177 296502 52736725 13523379 0 52182 9016896 1231 0 0 0 0 0 
+        bytes:  166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809 
+        RPC iostats version: 1.0  p/v: 100003/3 (nfs)
+        xprt:   tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
+        per-op statistics
+                NULL: 0 0 0 0 0 0 0 0
+             GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
+             SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
+              LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
+              ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
+            READLINK: 125 125 0 20472 18620 0 1112 1118
+                READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
+               WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
+              CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
+               MKDIR: 3680 3680 0 773980 993920 26 23990 24245
+             SYMLINK: 903 903 0 233428 245488 6 5865 5917
+               MKNOD: 80 80 0 20148 21760 0 299 304
+              REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
+               RMDIR: 3367 3367 0 645112 484848 22 5782 6002
+              RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
+                LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
+             READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
+         READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
+              FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
+              FSINFO: 2 2 0 232 328 0 1 1
+            PATHCONF: 1 1 0 116 140 0 0 0
+              COMMIT: 0 0 0 0 0 0 0 0
+
+device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
+[...]
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;The key number to look at is the third number in the per-op list.
+It is the number of NFS timeouts experiences per file system
+operation.  Here 22 write timeouts and 5 access timeouts.  If these
+numbers are increasing, I believe the machine is experiencing NFS
+hang.  Unfortunately the timeout value do not start to increase right
+away.  The NFS operations need to time out first, and this can take a
+while.  The exact timeout value depend on the setup.  For example the
+defaults for TCP and UDP mount points are quite different, and the
+timeout value is affected by the soft, hard, timeo and retrans NFS
+mount options.&lt;/p&gt;
+
+&lt;p&gt;The only way I have been able to get working on Debian and RedHat
+Enterprise Linux for getting the timeout count is to peek in /proc/.
+But according to
+&lt;ahref=&quot;http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html&quot;&gt;Solaris
+10 System Administration Guide: Network Services&lt;/a&gt;, the &#39;nfsstat -c&#39;
+command can be used to get these timeout values.  But this do not work
+on Linux, as far as I can tell.  I
+&lt;ahref=&quot;http://bugs.debian.org/857043&quot;&gt;asked Debian about this&lt;/a&gt;,
+but have not seen any replies yet.&lt;/p&gt;
+
+&lt;p&gt;Is there a better way to figure out if a Linux NFS client is
+experiencing NFS hangs?  Is there a way to detect which processes are
+affected?  Is there a way to get the NFS mount going quickly once the
+network problem causing the NFS hang has been cleared?  I would very
+much welcome some clues, as we regularly run into NFS hangs.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
-               <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</guid>
-                <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
-               <description>&lt;p&gt;In April we
-&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html&quot;&gt;started
-to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; 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 &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
-Administrator&#39;s Handbook page&lt;/a&gt; (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
-&lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
-hosted weblate project page&lt;/a&gt;, and get in touch using
-&lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
-translators mailing list&lt;/a&gt;.  Please also check out
-&lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
-contributors&lt;/a&gt;.  A good way to contribute is to proofread the text
-and update weblate if you find errors.&lt;/p&gt;
-
-&lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
-electronic form.&lt;/p&gt;
+               <title>How does it feel to be wiretapped, when you should be doing the wiretapping...</title>
+               <link>http://people.skolelinux.org/pere/blog/How_does_it_feel_to_be_wiretapped__when_you_should_be_doing_the_wiretapping___.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_does_it_feel_to_be_wiretapped__when_you_should_be_doing_the_wiretapping___.html</guid>
+                <pubDate>Wed, 8 Mar 2017 11:50:00 +0100</pubDate>
+               <description>&lt;p&gt;So the new president in the United States of America claim to be
+surprised to discover that he was wiretapped during the election
+before he was elected president.  He even claim this must be illegal.
+Well, doh, if it is one thing the confirmations from Snowden
+documented, it is that the entire population in USA is wiretapped, one
+way or another.  Of course the president candidates were wiretapped,
+alongside the senators, judges and the rest of the people in USA.&lt;/p&gt;
+
+&lt;p&gt;Next, the Federal Bureau of Investigation ask the Department of
+Justice to go public rejecting the claims that Donald Trump was
+wiretapped illegally.  I fail to see the relevance, given that I am
+sure the surveillance industry in USA believe they have all the legal
+backing they need to conduct mass surveillance on the entire
+world.&lt;/p&gt;
+
+&lt;p&gt;There is even the director of the FBI stating that he never saw an
+order requesting wiretapping of Donald Trump.  That is not very
+surprising, given how the FISA court work, with all its activity being
+secret.  Perhaps he only heard about it?&lt;/p&gt;
+
+&lt;p&gt;What I find most sad in this story is how Norwegian journalists
+present it.  In a news reports the other day in the radio from the
+Norwegian National broadcasting Company (NRK), I heard the journalist
+claim that &#39;the FBI denies any wiretapping&#39;, while the reality is that
+&#39;the FBI denies any illegal wiretapping&#39;.  There is a fundamental and
+important difference, and it make me sad that the journalists are
+unable to grasp it.&lt;/p&gt;
+
+&lt;p&gt;&lt;strong&gt;Update 2017-03-13:&lt;/strong&gt; Look like
+&lt;a href=&quot;https://theintercept.com/2017/03/13/rand-paul-is-right-nsa-routinely-monitors-americans-communications-without-warrants/&quot;&gt;The
+Intercept report that US Senator Rand Paul confirm what I state above&lt;/a&gt;.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
-               <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
-                <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
-               <description>&lt;p&gt;This summer, I read a great article
-&quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
-This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; 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 &quot;speeding up&quot; parts of
-the code to various degrees compared to a normal run.  It does this by
-slowing down parallel threads while the &quot;faster up&quot; 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.&lt;/p&gt;
-
-&lt;p&gt;The project and presentation was so inspiring that I would like to
-get the system into Debian.  I
-&lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
-a WNPP request for it&lt;/a&gt; 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 &#39;git clone&#39; 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.&lt;/p&gt;
-
-&lt;p&gt;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:
-
-&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
-coz run --- program-to-run
-&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
-
-&lt;p&gt;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
-&lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
-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 &amp;lt;coz.h&amp;gt; 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.&lt;/p&gt;
-
-&lt;p&gt;A video published by ACM
-&lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
-Coz profiler&lt;/a&gt; is available from Youtube.  There is also a paper
-from the 25th Symposium on Operating Systems Principles available
-titled
-&lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
-finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;
-
-&lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
-for Coz is available from github.  It will only build with clang
-because it uses a
-&lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
-feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
-&lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
-it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
+               <title>Norwegian Bokmål translation of The Debian Administrator&#39;s Handbook complete, proofreading in progress</title>
+               <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</guid>
+                <pubDate>Fri, 3 Mar 2017 14:50:00 +0100</pubDate>
+               <description>&lt;p&gt;For almost a year now, we have been working on making a Norwegian
+Bokmål edition of &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
+Administrator&#39;s Handbook&lt;/a&gt;.  Now, thanks to the tireless effort of
+Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
+we are working on the proof reading to ensure consistent language and
+use of correct computer science terms.  The plan is to make the book
+available on paper, as well as in electronic form.  For that to
+happen, the proof reading must be completed and all the figures need
+to be translated.  If you want to help out, get in touch.&lt;/p&gt;
+
+&lt;p&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf&quot;&gt;A
+
+fresh PDF edition&lt;/a&gt; in A4 format (the final book will have smaller
+pages) of the book created every morning is available for
+proofreading.  If you find any errors, please
+&lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;visit
+Weblate and correct the error&lt;/a&gt;.  The
+&lt;a href=&quot;http://l.github.io/debian-handbook/stat/nb-NO/index.html&quot;&gt;state
+of the translation including figures&lt;/a&gt; is a useful source for those
+provide Norwegian bokmål screen shots and figures.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Sales number for the Free Culture translation, first half of 2016</title>
-               <link>http://people.skolelinux.org/pere/blog/Sales_number_for_the_Free_Culture_translation__first_half_of_2016.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sales_number_for_the_Free_Culture_translation__first_half_of_2016.html</guid>
-                <pubDate>Fri, 5 Aug 2016 22:45:00 +0200</pubDate>
-               <description>&lt;p&gt;As my regular readers probably remember, the last year I published
-a French and Norwegian translation of the classic
-&lt;a href=&quot;http://www.free-culture.cc/&quot;&gt;Free Culture book&lt;/a&gt; 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.&lt;/p&gt;
-
-&lt;p&gt;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:&lt;/p&gt;
-
-&lt;table border=&quot;0&quot;&gt;
-&lt;tr&gt;&lt;th&gt;Title / language&lt;/th&gt;&lt;th&gt;Quantity&lt;/th&gt;&lt;/tr&gt;
-&lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html&quot;&gt;Culture Libre / French&lt;/a&gt;&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;3&lt;/td&gt;&lt;/tr&gt;
-&lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html&quot;&gt;Fri kultur / Norwegian&lt;/a&gt;&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;7&lt;/td&gt;&lt;/tr&gt;
-&lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html&quot;&gt;Free Culture / English&lt;/a&gt;&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;14&lt;/td&gt;&lt;/tr&gt;
-&lt;/table&gt;
-
-&lt;p&gt;The books are available both from Lulu.com and from large book
-stores like Amazon and Barnes&amp;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.&lt;/p&gt;
-
-&lt;p&gt;The ebook edition is available for free from
-&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;Github&lt;/a&gt;.&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
+               <title>Unlimited randomness with the ChaosKey?</title>
+               <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</guid>
+                <pubDate>Wed, 1 Mar 2017 20:50:00 +0100</pubDate>
+               <description>&lt;p&gt;A few days ago I ordered a small batch of
+&lt;a href=&quot;http://altusmetrum.org/ChaosKey/&quot;&gt;the ChaosKey&lt;/a&gt;, a small
+USB dongle for generating entropy created by Bdale Garbee and Keith
+Packard.  Yesterday it arrived, and I am very happy to report that it
+work great!  According to its designers, to get it to work out of the
+box, you need the Linux kernel version 4.1 or later.  I tested on a
+Debian Stretch machine (kernel version 4.9), and there it worked just
+fine, increasing the available entropy very quickly.  I wrote a small
+test oneliner to test.  It first print the current entropy level,
+drain /dev/random, and then print the entropy level for five seconds.
+Here is the situation without the ChaosKey inserted:&lt;/p&gt;
+
+&lt;blockquote&gt;&lt;pre&gt;
+% cat /proc/sys/kernel/random/entropy_avail; \
+  dd bs=1M if=/dev/random of=/dev/null count=1; \
+  for n in $(seq 1 5); do \
+     cat /proc/sys/kernel/random/entropy_avail; \
+     sleep 1; \
+  done
+300
+0+1 oppføringer inn
+0+1 oppføringer ut
+28 byte kopiert, 0,000264565 s, 106 kB/s
+4
+8
+12
+17
+21
+%
+&lt;/pre&gt;&lt;/blockquote&gt;
+
+&lt;p&gt;The entropy level increases by 3-4 every second.  In such case any
+application requiring random bits (like a HTTPS enabled web server)
+will halt and wait for more entrpy.  And here is the situation with
+the ChaosKey inserted:&lt;/p&gt;
+
+&lt;blockquote&gt;&lt;pre&gt;
+% cat /proc/sys/kernel/random/entropy_avail; \
+  dd bs=1M if=/dev/random of=/dev/null count=1; \
+  for n in $(seq 1 5); do \
+     cat /proc/sys/kernel/random/entropy_avail; \
+     sleep 1; \
+  done
+1079
+0+1 oppføringer inn
+0+1 oppføringer ut
+104 byte kopiert, 0,000487647 s, 213 kB/s
+433
+1028
+1031
+1035
+1038
+%
+&lt;/pre&gt;&lt;/blockquote&gt;
+
+&lt;p&gt;Quite the difference. :) I bought a few more than I need, in case
+someone want to buy one here in Norway. :)&lt;/p&gt;
+
+&lt;p&gt;Update: The dongle was presented at Debconf last year.  You might
+find &lt;a href=&quot;https://debconf16.debconf.org/talks/94/&quot;&gt;the talk
+recording illuminating&lt;/a&gt;.  It explains exactly what the source of
+randomness is, if you are unable to spot it from the schema drawing
+available from the ChaosKey web site linked at the start of this blog
+post.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Vitenskapen tar som vanlig feil igjen - relativt feil</title>
-               <link>http://people.skolelinux.org/pere/blog/Vitenskapen_tar_som_vanlig_feil_igjen___relativt_feil.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Vitenskapen_tar_som_vanlig_feil_igjen___relativt_feil.html</guid>
-                <pubDate>Mon, 1 Aug 2016 16:00:00 +0200</pubDate>
-               <description>&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p&gt;Resultatet, &lt;a href=&quot;http://www.skepsis.no/?p=1617&quot;&gt;«Relativt
-feil»&lt;/a&gt;, ble publisert på skepsis-bloggen for noen minutter siden.
-Jeg anbefaler deg på det varmeste å lese denne teksten og dele den med
-dine venner.&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
+               <title>Detect OOXML files with undefined behaviour?</title>
+               <link>http://people.skolelinux.org/pere/blog/Detect_OOXML_files_with_undefined_behaviour_.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Detect_OOXML_files_with_undefined_behaviour_.html</guid>
+                <pubDate>Tue, 21 Feb 2017 00:20:00 +0100</pubDate>
+               <description>&lt;p&gt;I just noticed
+&lt;a href=&quot;http://www.arkivrad.no/aktuelt/riksarkivarens-forskrift-pa-horing&quot;&gt;the
+new Norwegian proposal for archiving rules in the goverment&lt;/a&gt; list
+&lt;a href=&quot;http://www.ecma-international.org/publications/standards/Ecma-376.htm&quot;&gt;ECMA-376&lt;/a&gt;
+/ ISO/IEC 29500 (aka OOXML) as valid formats to put in long term
+storage.  Luckily such files will only be accepted based on
+pre-approval from the National Archive.  Allowing OOXML files to be
+used for long term storage might seem like a good idea as long as we
+forget that there are plenty of ways for a &quot;valid&quot; OOXML document to
+have content with no defined interpretation in the standard, which
+lead to a question and an idea.&lt;/p&gt;
+
+&lt;p&gt;Is there any tool to detect if a OOXML document depend on such
+undefined behaviour?  It would be useful for the National Archive (and
+anyone else interested in verifying that a document is well defined)
+to have such tool available when considering to approve the use of
+OOXML.  I&#39;m aware of the
+&lt;a href=&quot;https://github.com/arlm/officeotron/&quot;&gt;officeotron OOXML
+validator&lt;/a&gt;, but do not know how complete it is nor if it will
+report use of undefined behaviour.  Are there other similar tools
+available?  Please send me an email if you know of any such tool.&lt;/p&gt;

 </description>
        </item>
        
 </description>
        </item>