Generated.

[homepage.git] / blog / index.rss

diff --git a/blog/index.rss b/blog/index.rss
index 93bc85adb59b16d4d83c1c7841876118d92bf682..e42e39614e2a86dbe67edd3dba3a98a2389fd0f2 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -7,743 +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>syslog-trusted-timestamp - chain of trusted timestamps for your syslog</title>
-               <link>http://people.skolelinux.org/pere/blog/syslog_trusted_timestamp___chain_of_trusted_timestamps_for_your_syslog.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/syslog_trusted_timestamp___chain_of_trusted_timestamps_for_your_syslog.html</guid>
-                <pubDate>Sat, 2 Apr 2016 09:50:00 +0200</pubDate>
-               <description>&lt;p&gt;Two years ago, I had
-&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Public_Trusted_Timestamping_services_for_everyone.html&quot;&gt;a
-look at trusted timestamping options available&lt;/a&gt;, and among
-other things noted a still open
-&lt;a href=&quot;https://bugs.debian.org/742553&quot;&gt;bug in the tsget script&lt;/a&gt;
-included in openssl that made it harder than necessary to use openssl
-as a trusted timestamping client.  A few days ago I was told
-&lt;a href=&quot;https:/www.difi.no/&quot;&gt;the Norwegian government office DIFI&lt;/a&gt; is
-close to releasing their own trusted timestamp service, and in the
-process I was happy to learn about a replacement for the tsget script
-using only curl:&lt;/p&gt;
-
-&lt;p&gt;&lt;pre&gt;
-openssl ts -query -data &quot;/etc/shells&quot; -cert -sha256 -no_nonce \
+               <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;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; \
   | curl -s -H &quot;Content-Type: application/timestamp-query&quot; \

-         --data-binary &quot;@-&quot; http://zeitstempel.dfn.de &gt; etc-shells.tsr
-openssl ts -reply -text -in etc-shells.tsr
-&lt;/pre&gt;&lt;/p&gt;
-
-&lt;p&gt;This produces a binary timestamp file (etc-shells.tsr) which can be
-used to verify that the content of the file /etc/shell with the
-calculated sha256 hash existed at the point in time when the request
-was made.  The last command extract the content of the etc-shells.tsr
-in human readable form.  The idea behind such timestamp is to be able
-to prove using cryptography that the content of a file have not
-changed since the file was stamped.&lt;/p&gt;
-
-&lt;p&gt;To verify that the file on disk match the public key signature in
-the timestamp file, run the following commands.  It make sure you have
-the required certificate for the trusted timestamp service available
-and use it to compare the file content with the timestamp.  In
-production, one should of course use a better method to verify the
-service certificate.&lt;/p&gt;
-
-&lt;p&gt;&lt;pre&gt;
-wget -O ca-cert.txt https://pki.pca.dfn.de/global-services-ca/pub/cacert/chain.txt
-openssl ts -verify -data /etc/shells -in etc-shells.tsr -CAfile ca-cert.txt -text
-&lt;/pre&gt;&lt;/p&gt;
-
-&lt;p&gt;Wikipedia have a lot more information about
-&lt;a href=&quot;https://en.wikipedia.org/wiki/Trusted_timestamping&quot;&gt;trusted
-Timestamping&lt;/a&gt; and
-&lt;a href=&quot;https://en.wikipedia.org/wiki/Linked_timestamping&quot;&gt;linked
-timestamping&lt;/a&gt;, and there are several trusted timestamping services
-around, both as commercial services and as free and public services.
-Among the latter is
-&lt;a href=&quot;https://www.pki.dfn.de/zeitstempeldienst/&quot;&gt;the
-zeitstempel.dfn.de service&lt;/a&gt; mentioned above and
-&lt;a href=&quot;https://freetsa.org/&quot;&gt;freetsa.org service&lt;/a&gt; linked to from the
-wikipedia web site.  I believe the DIFI service should show up on
-https://tsa.difi.no, but it is not available to the public at the
-moment.  I hope this will change when it is into production.  The
-&lt;a href=&quot;https://tools.ietf.org/html/rfc3161&quot;&gt;RFC 3161&lt;/a&gt; trusted
-timestamping protocol standard is even implemented in LibreOffice,
-Microsoft Office and Adobe Acrobat, making it possible to verify when
-a document was created.&lt;/p&gt;
-
-&lt;p&gt;I would find it useful to be able to use such trusted timestamp
-service to make it possible to verify that my stored syslog files have
-not been tampered with.  This is not a new idea.  I found one example
-implemented on the Endian network appliances where
-&lt;a href=&quot;http://help.endian.com/entries/21518508-Enabling-Timestamping-on-log-files-&quot;&gt;the
-configuration of such feature was described in 2012&lt;/a&gt;.&lt;/p&gt;
-
-&lt;p&gt;But I could not find any free implementation of such feature when I
-searched, so I decided to try to
-&lt;a href=&quot;https://github.com/petterreinholdtsen/syslog-trusted-timestamp&quot;&gt;build
-a prototype named syslog-trusted-timestamp&lt;/a&gt;.  My idea is to
-generate a timestamp of the old log files after they are rotated, and
-store the timestamp in the new log file just after rotation.  This
-will form a chain that would make it possible to see if any old log
-files are tampered with.  But syslog is bad at handling kilobytes of
-binary data, so I decided to base64 encode the timestamp and add an ID
-and line sequence numbers to the base64 data to make it possible to
-reassemble the timestamp file again.  To use it, simply run it like
-this:
-
-&lt;p&gt;&lt;pre&gt;
-syslog-trusted-timestamp /path/to/list-of-log-files
-&lt;/pre&gt;&lt;/p&gt;
-
-&lt;p&gt;This will send a timestamp from one or more timestamp services (not
-yet decided nor implemented) for each listed file to the syslog using
-logger(1).  To verify the timestamp, the same program is used with the
---verify option:&lt;/p&gt;
-
-&lt;p&gt;&lt;pre&gt;
-syslog-trusted-timestamp --verify /path/to/log-file /path/to/log-with-timestamp
-&lt;/pre&gt;&lt;/p&gt;
-
-&lt;p&gt;The verification step is not yet well designed.  The current
-implementation depend on the file path being unique and unchanging,
-and this is not a solid assumption.  It also uses process number as
-timestamp ID, and this is bound to create ID collisions.  I hope to
-have time to come up with a better way to handle timestamp IDs and
-verification later.&lt;/p&gt;
-
-&lt;p&gt;Please check out
-&lt;a href=&quot;https://github.com/petterreinholdtsen/syslog-trusted-timestamp&quot;&gt;the
-prototype for syslog-trusted-timestamp on github&lt;/a&gt; and send
-suggestions and improvement, or let me know if there already exist a
-similar system for timestamping logs already to allow me to join
-forces with others with the same interest.&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&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
+      --data-binary &quot;@-&quot; http://zeitstempel.dfn.de &gt; $sha256.tsr
+&lt;/pre&gt;&lt;/blockquote&gt;&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;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;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>Full battery stats collector is now available in Debian</title>
-               <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
-                <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
-               <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
-extended collector that will collect the complete battery history for
-later processing and graphing.  The original collector store the
-battery level as percentage of last full level, while the new
-collector also record battery vendor, model, serial number, design
-full level, last full level and current battery level.  This make it
-possible to predict the lifetime of the battery as well as visualise
-the energy flow when the battery is charging or discharging.&lt;/p&gt;
-
-&lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
-in the version 0.5.1 package in unstable.  Get the new battery level graph
-and lifetime prediction by running:
-
-&lt;p&gt;&lt;pre&gt;
-/usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
-&lt;/pre&gt;&lt;/p&gt;
-
-&lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
-
-&lt;p&gt;The flow in/out of the battery can be seen by running (no menu
-entry yet):&lt;/p&gt;
-
-&lt;p&gt;&lt;pre&gt;
-/usr/share/battery-stats/battery-stats-graph-flow
-&lt;/pre&gt;&lt;/p&gt;
-
-&lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
-when there are few data points.  The graphs look a bit better with a
-few years of data.&lt;/p&gt;
-
-&lt;p&gt;A while back one important feature I use in the battery stats
-collector broke in Debian.  The scripts in
-&lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed.  I
-suspect it happened when Jessie started using systemd, but I do not
-know.  The issue is reported as
-&lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
-pm-utils.  I managed to work around it by adding an udev rule to call
-the collector script every time the power connector is connected and
-disconnected.  With this fix in place it was finally time to make a
-new release of the package, and get it into Debian.&lt;/p&gt;
-
-&lt;p&gt;If you are interested in how your laptop battery is doing, please
-check out the
-&lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
-in Debian unstable, or rebuild it on Jessie to get it working on
-Debian stable. :) The upstream source is available from
-&lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
-As always, patches are very welcome.&lt;/p&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;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;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;/blockquote&gt;
+
+&lt;p&gt;Dette oversetter Apertium slik:&lt;/p&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;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;/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>UsingQR - &quot;Electronic&quot; paper invoices using JSON and QR codes</title>
-               <link>http://people.skolelinux.org/pere/blog/UsingQR____Electronic__paper_invoices_using_JSON_and_QR_codes.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/UsingQR____Electronic__paper_invoices_using_JSON_and_QR_codes.html</guid>
-                <pubDate>Sat, 19 Mar 2016 09:40:00 +0100</pubDate>
-               <description>&lt;p&gt;Back in 2013 I proposed
-&lt;a href=&quot;http://people.skolelinux.org/pere/blog/_Electronic__paper_invoices___using_vCard_in_a_QR_code.html&quot;&gt;a
-way to make paper and PDF invoices easier to process electronically by
-adding a QR code with the key information about the invoice&lt;/a&gt;.  I
-suggested using vCard field definition, to get some standard format
-for name and address, but any format would work.  I did not do
-anything about the proposal, but hoped someone one day would make
-something like it.  It would make it possible to efficiently send
-machine readable invoices directly between seller and buyer.&lt;/p&gt;
-
-&lt;p&gt;This was the background when I came across a proposal and
-specification from the web based accounting and invoicing supplier
-&lt;a href=&quot;http://www.visma.com/&quot;&gt;Visma&lt;/a&gt; in Sweden called
-&lt;a href=&quot;http://usingqr.com/&quot;&gt;UsingQR&lt;/a&gt;.  Their PDF invoices contain
-a QR code with the key information of the invoice in JSON format.
-This is the typical content of a QR code following the UsingQR
-specification (based on a real world example, some numbers replaced to
-get a more bogus entry).  I&#39;ve reformatted the JSON to make it easier
-to read.  Normally this is all on one long line:&lt;/p&gt;
-
-&lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2016-03-19-qr-invoice.png&quot; align=&quot;right&quot;&gt;&lt;pre&gt;
-{
- &quot;vh&quot;:500.00,
- &quot;vm&quot;:0,
- &quot;vl&quot;:0,
- &quot;uqr&quot;:1,
- &quot;tp&quot;:1,
- &quot;nme&quot;:&quot;Din Leverandør&quot;,
- &quot;cc&quot;:&quot;NO&quot;,
- &quot;cid&quot;:&quot;997912345 MVA&quot;,
- &quot;iref&quot;:&quot;12300001&quot;,
- &quot;idt&quot;:&quot;20151022&quot;,
- &quot;ddt&quot;:&quot;20151105&quot;,
- &quot;due&quot;:2500.0000,
- &quot;cur&quot;:&quot;NOK&quot;,
- &quot;pt&quot;:&quot;BBAN&quot;,
- &quot;acc&quot;:&quot;17202612345&quot;,
- &quot;bc&quot;:&quot;BIENNOK1&quot;,
- &quot;adr&quot;:&quot;0313 OSLO&quot;
-}
-&lt;/pre&gt;&lt;/p&gt;
-
-&lt;/p&gt;The interpretation of the fields can be found in the
-&lt;a href=&quot;http://usingqr.com/wp-content/uploads/2014/06/UsingQR_specification1.pdf&quot;&gt;format
-specification&lt;/a&gt; (revision 2 from june 2014).  The format seem to
-have most of the information needed to handle accounting and payment
-of invoices, at least the fields I have needed so far here in
-Norway.&lt;/p&gt;
-
-&lt;p&gt;Unfortunately, the site and document do not mention anything about
-the patent, trademark and copyright status of the format and the
-specification.  Because of this, I asked the people behind it back in
-November to clarify.  Ann-Christine Savlid (ann-christine.savlid (at)
-visma.com) replied that Visma had not applied for patent or trademark
-protection for this format, and that there were no copyright based
-usage limitations for the format.  I urged her to make sure this was
-explicitly written on the web pages and in the specification, but
-unfortunately this has not happened yet.  So I guess if there is
-submarine patents, hidden trademarks or a will to sue for copyright
-infringements, those starting to use the UsingQR format might be at
-risk, but if this happen there is some legal defense in the fact that
-the people behind the format claimed it was safe to do so.  At least
-with patents, there is always
-&lt;a href=&quot;http://www.paperspecs.com/paper-news/beware-the-qr-code-patent-trap/&quot;&gt;a
-chance of getting sued...&lt;/a&gt;&lt;/p&gt;
-
-&lt;p&gt;I also asked if they planned to maintain the format in an
-independent standard organization to give others more confidence that
-they would participate in the standardization process on equal terms
-with Visma, but they had no immediate plans for this.  Their plan was
-to work with banks to try to get more users of the format, and
-evaluate the way forward if the format proved to be popular.  I hope
-they conclude that using an open standard organisation like
-&lt;a href=&quot;http://www.ietf.org/&quot;&gt;IETF&lt;/a&gt; is the correct place to
-maintain such specification.&lt;/p&gt;
-
-&lt;p&gt;&lt;strong&gt;Update 2016-03-20&lt;/strong&gt;: Via Twitter I became aware of
-&lt;a href=&quot;https://news.ycombinator.com/item?id=11319492&quot;&gt;some comments
-about this blog post&lt;/a&gt; that had several useful links and references to
-similar systems.  In the Czech republic, the Czech Banking Association
-standard #26, with short name SPAYD, uses QR codes with payment
-information.  More information is available from the Wikipedia page on
-&lt;a href=&quot;https://en.wikipedia.org/wiki/Short_Payment_Descriptor&quot;&gt;Short
-Payment Descriptor&lt;/a&gt;.  And in Germany, there is a system named
-&lt;a href=&quot;http://www.bezahlcode.de/&quot;&gt;BezahlCode&lt;/a&gt;,
-(&lt;a href=&quot;http://www.bezahlcode.de/wp-content/uploads/BezahlCode_TechDok.pdf&quot;&gt;specification
-v1.8 2013-12-05 available as PDF&lt;/a&gt;), which uses QR codes with
-URL-like formatting using &quot;bank:&quot; as the URI schema/protocol to
-provide the payment information.  There is also the
-&lt;a href=&quot;http://www.ferd-net.de/front_content.php?idcat=231&quot;&gt;ZUGFeRD&lt;/a&gt;
-file format that perhaps could be transfered using QR codes, but I am
-not sure if it is done already.  Last, in Bolivia there are reports
-that tax information since november 2014 need to be printed in QR
-format on invoices.  I have not been able to track down a
-specification for this format, because of my limited language skill
-sets.&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>Making battery measurements a little easier in Debian</title>
-               <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
-                <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
-               <description>&lt;p&gt;Back in September, I blogged about
-&lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
-system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
-how it showed the decay and death of this battery (now replaced).  I
-created a simple deb package to handle the collection and graphing,
-but did not want to upload it to Debian as there were already
-&lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
-package in Debian&lt;/a&gt; that should do the same thing, and I did not see
-a point of uploading a competing package when battery-stats could be
-fixed instead.  I reported a few bugs about its non-function, and
-hoped someone would step in and fix it.  But no-one did.&lt;/p&gt;
-
-&lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
-hands.  The end result is that I am now the new upstream developer of
-battery stats (&lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;available from github&lt;/a&gt;) and part of the team maintaining
-battery-stats in Debian, and the package in Debian unstable is finally
-able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
-information provided by the Linux kernel.  If you install the
-battery-stats package from unstable now, you will be able to get a
-graph of the current battery fill level, to get some idea about the
-status of the battery.  The source package build and work just fine in
-Debian testing and stable (and probably oldstable too, but I have not
-tested).  The default graph you get for that system look like this:&lt;/p&gt;
-
-&lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2016-03-15-battery-stats-graph-example.png&quot; width=&quot;70%&quot; align=&quot;center&quot;&gt;&lt;/p&gt;
-
-&lt;p&gt;My plans for the future is to merge my old scripts into the
-battery-stats package, as my old scripts collected a lot more details
-about the battery.  The scripts are merged into the upstream
-battery-stats git repository already, but I am not convinced they work
-yet, as I changed a lot of paths along the way.  Will have to test a
-bit more before I make a new release.&lt;/p&gt;
-
-&lt;p&gt;I will also consider changing the file format slightly, as I
-suspect the way I combine several values into one field might make it
-impossible to know the type of the value when using it for processing
-and graphing.&lt;/p&gt;
-
-&lt;p&gt;If you would like I would like to keep an close eye on your laptop
-battery, check out the battery-stats package in
-&lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
-on
-&lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
-I would love some help to improve the system further.&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>Creating, updating and checking debian/copyright semi-automatically</title>
-               <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
-                <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
-               <description>&lt;p&gt;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
-&lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
-readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
-
-&lt;p&gt;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
-&lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
-zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
-figuring out the options for doing this job automatically, or at least
-semi-automatically.&lt;/p&gt;
-
-&lt;p&gt;Lucikly, there are at least two tools available for generating the
-file based on the code in the source package,
-&lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
-and &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/cme&quot;&gt;cme&lt;/a&gt;&lt;/tt&gt;.  I&#39;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
-&lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
-blog posts from 2014&lt;/a&gt;.
-
-&lt;p&gt;To generate using debmake, use the -cc option:
-
-&lt;p&gt;&lt;pre&gt;
-debmake -cc &gt; debian/copyright
-&lt;/pre&gt;&lt;/p&gt;
-
-&lt;p&gt;Note there are some problems with python and non-ASCII names, so
-this might not be the best option.&lt;/p&gt;
-
-&lt;p&gt;The cme option is based on a config parsing library, and I found
-this approach in
-&lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
-blog post from 2015&lt;/a&gt;.  To generate using cme, use the &#39;update
-dpkg-copyright&#39; option:
-
-&lt;p&gt;&lt;pre&gt;
-cme update dpkg-copyright
-&lt;/pre&gt;&lt;/p&gt;
-
-&lt;p&gt;This will create or update debian/copyright.  The cme tool seem to
-handle UTF-8 names better than debmake.&lt;/p&gt;
-
-&lt;p&gt;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,
-&lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;.  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.&lt;/p&gt;
-
-&lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; 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.&lt;/p&gt;
-
-&lt;p&gt;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.&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&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
-
-&lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
-on how to use licensecheck and cdbs to create a draft copyright file
-
-&lt;p&gt;&lt;pre&gt;
-licensecheck --copyright -r `find * -type f` | \
-  /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
-&lt;/pre&gt;&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
-against using -quiet for new users, so I removed it from the proposed
-command line.&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>Using appstream in Debian to locate packages with firmware and mime type support</title>
-               <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
-                <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
-               <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
-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. :)&lt;/p&gt;
-
-&lt;p&gt;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:&lt;/p&gt;
-
-&lt;blockquote&gt;&lt;pre&gt;
-% apt install appstream
+               <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;

 [...]
 [...]

-% apt update
-[...]
-% appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
-  awk &#39;/Package:/ {print $2}&#39;
-firmware-qlogic
-%
-&lt;/pre&gt;&lt;/blockquote&gt;
-
-&lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
-appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
-a way appstream can use.&lt;/p&gt;
-
-&lt;p&gt;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 &lt;tt&gt;file
---mime-type&lt;/tt&gt;, 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:&lt;/p&gt;
-
-&lt;blockquote&gt;&lt;pre&gt;
-% apt install appstream
+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

 [...]
 [...]

-% apt update
-[...]
-% appstreamcli what-provides mimetype image/svg+xml | \
-  awk &#39;/Package:/ {print $2}&#39;
-bkchem
-phototonic
-inkscape
-shutter
-tetzle
-geeqie
-xia
-pinta
-gthumb
-karbon
-comix
-mirage
-viewnior
-postr
-ristretto
-kolourpaint4
-eog
-eom
-gimagereader
-midori
-%
-&lt;/pre&gt;&lt;/blockquote&gt;
-
-&lt;p&gt;I believe the MIME types are fetched from the desktop file for
-packages providing appstream metadata.&lt;/p&gt;
+&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>Creepy, visualise geotagged social media information - nice free software</title>
-               <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
-                <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
-               <description>&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;70%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2016-01-24-nice-creepy-desktop-window.png&quot;&gt;&lt;/p&gt;
-
-&lt;p&gt;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
-&lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;.  I
-discovered it when I read
-&lt;a href=&quot;http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-7787884.html&quot;&gt;an
-article about Creepy&lt;/a&gt; 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
-&lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
-Debian&lt;/a&gt; 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
-&lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p&gt;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
-&lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
-to locate Russian soldiers in Ukraine&lt;/a&gt;, 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.&lt;/p&gt;
-
-&lt;p&gt;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).&lt;/p&gt;
-
-&lt;p&gt;(I have uploaded
-&lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
-screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
-Creepy program in Debian.)&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>Always download Debian packages using Tor - the simple recipe</title>
-               <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
-                <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
-               <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
-&lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
-that those listening on the Internet lines would have good reason to
-believe a computer have a given security hole&lt;/a&gt; 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
-&lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
-to always use Tor to download packages from the Debian mirror&lt;/a&gt;.  He
-was not the first to propose this, as the
-&lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/apt-transport-tor&quot;&gt;apt-transport-tor&lt;/a&gt;&lt;/tt&gt;
-package by Tim Retout already existed to make it easy to convince apt
-to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
-aware of that package when I read the blog post from Richard.&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p&gt;Here is a short recipe for enabling this on your machine, by
-installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; 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
-&lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
-done in /etc/.&lt;/p&gt;
-
-&lt;blockquote&gt;&lt;pre&gt;
-apt install apt-transport-tor
-sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
-sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
-&lt;/pre&gt;&lt;/blockquote&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p&gt;This work in Debian Jessie and later.  Note that tools like
-&lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
-system, and do not work with these tor+http URLs.  For
-&lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
-which need a recent apt version currently only in unstable.  So if you
-need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
-is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
-enabled.  It would be great if it was the default on any Debian
-system.&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>Nedlasting fra NRK, som Matroska med undertekster</title>
-               <link>http://people.skolelinux.org/pere/blog/Nedlasting_fra_NRK__som_Matroska_med_undertekster.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Nedlasting_fra_NRK__som_Matroska_med_undertekster.html</guid>
-                <pubDate>Sat, 2 Jan 2016 13:50:00 +0100</pubDate>
-               <description>&lt;p&gt;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 &lt;a href=&quot;https://github.com/liangqi/nrkopptak&quot;&gt;tilgjengelig
-via github&lt;/a&gt;.&lt;/p&gt;
-
-&lt;p&gt;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&lt;/p&gt;
-
-&lt;p&gt;&lt;pre&gt;
-nrkopptak/bin/nrk-opptak k &lt;ahref=&quot;https://tv.nrk.no/serie/bmi-turne/MUHH45000115/sesong-1/episode-1&quot;&gt;https://tv.nrk.no/serie/bmi-turne/MUHH45000115/sesong-1/episode-1&lt;/a&gt;
-&lt;/pre&gt;&lt;/p&gt;
-
-&lt;p&gt;URL-eksemplet er dagens toppsak på tv.nrk.no.  Argument &#39;k&#39; ber
-scriptet laste ned og lagre som Matroska.  Det finnes en rekke andre
-muligheter for valg av kvalitet og format.&lt;/p&gt;
-
-&lt;p&gt;Jeg foretrekker dette scriptet fremfor youtube-dl, som
-&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK_med_den__nye__l_sningen.html&quot;&gt;
-nevnt i 2014 støtter NRK&lt;/a&gt; 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.&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>OpenALPR, find car license plates in video streams - nice free software</title>
-               <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
-                <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
-               <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, 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.&lt;/p&gt;
-
-&lt;p&gt;A few days I came across
-&lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
-project&lt;/a&gt;, a free software project to automatically discover and
-report license plates in images and video streams, and provide the
-&quot;car numbers&quot; in a machine readable format.  I&#39;ve been looking for
-such system for a while now, because I believe it is a bad idea that the
-&lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
-number plate recognition&lt;/a&gt; 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
-&lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
-Debian&lt;/a&gt;, 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.&lt;/p&gt;
-
-&lt;p&gt;Today we finally managed to get the package into shape and uploaded
-it into Debian, where it currently
-&lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
-in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
-
-&lt;p&gt;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.&lt;/p&gt;
-
-&lt;p&gt;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 &quot;debuild&quot; to build the source.  Or wait a bit until the
-package show up in unstable.&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>