Ny post om valget.

[homepage.git] / blog / index.html

diff --git a/blog/index.html b/blog/index.html
index d97fb9135e5073436796d311e628a70f2a8c527c..7ee76c94b874dd2783d5a7df1f8e9443ac28638e 100644 (file)
--- a/blog/index.html
+++ b/blog/index.html
@@ -20,57 +20,96 @@
 
     
     <div class="entry">
 
     
     <div class="entry">

-      <div class="title"><a href="http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html">Making battery measurements a little easier in Debian</a></div>
-      <div class="date">15th March 2016</div>
-      <div class="body"><p>Back in September, I blogged about
-<a href="http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html">the
-system I wrote to collect statistics about my laptop battery</a>, 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
-<a href="https://tracker.debian.org/pkg/battery-stats">a battery-stats
-package in Debian</a> 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.</p>
-
-<p>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 (<a href="https://github.com/petterreinholdtsen/battery-stats">available from github</a>) 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 <tt>/sys/class/power_supply/</tt>
-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:</p>
-
-<p align="center"><img src="http://people.skolelinux.org/pere/blog/images/2016-03-15-battery-stats-graph-example.png" width="70%" align="center"></p>
-
-<p>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.</p>
-
-<p>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.</p>
-
-<p>If you would like I would like to keep an close eye on your laptop
-battery, check out the battery-stats package in
-<a href="https://tracker.debian.org/pkg/battery-stats">Debian</a> and
-on
-<a href="https://github.com/petterreinholdtsen/battery-stats">github</a>.
-I would love some help to improve the system further.</p>
+      <div class="title"><a href="http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html">Simpler recipe on how to make a simple $7 IMSI Catcher using Debian</a></div>
+      <div class="date"> 9th August 2017</div>
+      <div class="body"><p>On friday, I came across an interesting article in the Norwegian
+web based ICT news magazine digi.no on
+<a href="https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-60-kroner-na-kan-mobiler-kartlegges-av-alle/398588">how
+to collect the IMSI numbers of nearby cell phones</a> using the cheap
+DVB-T software defined radios.  The article refered to instructions
+and <a href="https://www.youtube.com/watch?v=UjwgNd_as30">a recipe by
+Keld Norman on Youtube on how to make a simple $7 IMSI Catcher</a>, and I decided to test them out.</p>
+
+<p>The instructions said to use Ubuntu, install pip using apt (to
+bypass apt), use pip to install pybombs (to bypass both apt and pip),
+and the ask pybombs to fetch and build everything you need from
+scratch.  I wanted to see if I could do the same on the most recent
+Debian packages, but this did not work because pybombs tried to build
+stuff that no longer build with the most recent openssl library or
+some other version skew problem.  While trying to get this recipe
+working, I learned that the apt->pip->pybombs route was a long detour,
+and the only piece of software dependency missing in Debian was the
+gr-gsm package.  I also found out that the lead upstream developer of
+gr-gsm (the name stand for GNU Radio GSM) project already had a set of
+Debian packages provided in an Ubuntu PPA repository.  All I needed to
+do was to dget the Debian source package and built it.</p>
+
+<p>The IMSI collector is a python script listening for packages on the
+loopback network device and printing to the terminal some specific GSM
+packages with IMSI numbers in them.  The code is fairly short and easy
+to understand.  The reason this work is because gr-gsm include a tool
+to read GSM data from a software defined radio like a DVB-T USB stick
+and other software defined radios, decode them and inject them into a
+network device on your Linux machine (using the loopback device by
+default).  This proved to work just fine, and I've been testing the
+collector for a few days now.</p>
+
+<p>The updated and simpler recipe is thus to</p>
+
+<ol>
+
+<li>start with a Debian machine running Stretch or newer,</li>
+
+<li>build and install the gr-gsm package available from
+<a href="http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/">http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/</a>,</li>
+
+<li>clone the git repostory from <a href="https://github.com/Oros42/IMSI-catcher">https://github.com/Oros42/IMSI-catcher</a>,</li>
+
+<li>run grgsm_livemon and adjust the frequency until the terminal
+where it was started is filled with a stream of text (meaning you
+found a GSM station).</li>
+
+<li>go into the IMSI-catcher directory and run 'sudo python simple_IMSI-catcher.py' to extract the IMSI numbers.</li>
+
+</ol>
+
+<p>To make it even easier in the future to get this sniffer up and
+running, I decided to package
+<a href="https://github.com/ptrkrysik/gr-gsm/">the gr-gsm project</a>
+for Debian (<a href="https://bugs.debian.org/871055">WNPP
+#871055</a>), and the package was uploaded into the NEW queue today.
+Luckily the gnuradio maintainer has promised to help me, as I do not
+know much about gnuradio stuff yet.</p>
+
+<p>I doubt this "IMSI cacher" is anywhere near as powerfull as
+commercial tools like
+<a href="https://www.thespyphone.com/portable-imsi-imei-catcher/">The
+Spy Phone Portable IMSI / IMEI Catcher</a> or the
+<a href="https://en.wikipedia.org/wiki/Stingray_phone_tracker">Harris
+Stingray</a>, but I hope the existance of cheap alternatives can make
+more people realise how their whereabouts when carrying a cell phone
+is easily tracked.  Seeing the data flow on the screen, realizing that
+I live close to a police station and knowing that the police is also
+wearing cell phones, I wonder how hard it would be for criminals to
+track the position of the police officers to discover when there are
+police near by, or for foreign military forces to track the location
+of the Norwegian military forces, or for anyone to track the location
+of government officials...</p>
+
+<p>It is worth noting that the data reported by the IMSI-catcher
+script mentioned above is only a fraction of the data broadcasted on
+the GSM network.  It will only collect one frequency at the time,
+while a typical phone will be using several frequencies, and not all
+phones will be using the frequencies tracked by the grgsm_livemod
+program.  Also, there is a lot of radio chatter being ignored by the
+simple_IMSI-catcher script, which would be collected by extending the
+parser code.  I wonder if gr-gsm can be set up to listen to more than
+one frequency?</p>

 </div>
       <div class="tags">
         
         
 </div>
       <div class="tags">
         
         

-        Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>. 
+        Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>. 

         
         
       </div>
         
         
       </div>


@@ -78,105 +117,37 @@ I would love some help to improve the system further.</p>
     <div class="padding"></div>
     
     <div class="entry">
     <div class="padding"></div>
     
     <div class="entry">

-      <div class="title"><a href="http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html">Creating, updating and checking debian/copyright semi-automatically</a></div>
-      <div class="date">19th February 2016</div>
-      <div class="body"><p>Making packages for Debian requires quite a lot of attention to
-details.  And one of the details is the content of the
-debian/copyright file, which should list all relevant licenses used by
-the code in the package in question, preferably in
-<a href="https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/">machine
-readable DEP5 format</a>.</p>
-
-<p>For large packages with lots of contributors it is hard to write
-and update this file manually, and if you get some detail wrong, the
-package is normally rejected by the ftpmasters.  So getting it right
-the first time around get the package into Debian faster, and save
-both you and the ftpmasters some work..  Today, while trying to figure
-out what was wrong with
-<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447">the
-zfsonlinux copyright file</a>, I decided to spend some time on
-figuring out the options for doing this job automatically, or at least
-semi-automatically.</p>
-
-<p>Lucikly, there are at least two tools available for generating the
-file based on the code in the source package,
-<tt><a href="https://tracker.debian.org/pkg/debmake">debmake</a></tt>
-and <tt><a href="https://tracker.debian.org/pkg/cme">cme</a></tt>.  I'm
-not sure which one of them came first, but both seem to be able to
-create a sensible draft file.  As far as I can tell, none of them can
-be trusted to get the result just right, so the content need to be
-polished a bit before the file is OK to upload.  I found the debmake
-option in
-<a href="http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html">a
-blog posts from 2014</a>.
-
-<p>To generate using debmake, use the -cc option:
-
-<p><pre>
-debmake -cc > debian/copyright
-</pre></p>
-
-<p>Note there are some problems with python and non-ASCII names, so
-this might not be the best option.</p>
-
-<p>The cme option is based on a config parsing library, and I found
-this approach in
-<a href="https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/">a
-blog post from 2015</a>.  To generate using cme, use the 'update
-dpkg-copyright' option:
-
-<p><pre>
-cme update dpkg-copyright
-</pre></p>
-
-<p>This will create or update debian/copyright.  The cme tool seem to
-handle UTF-8 names better than debmake.</p>
-
-<p>When the copyright file is created, I would also like some help to
-check if the file is correct.  For this I found two good options,
-<tt>debmake -k</tt> and <tt>license-reconcile</tt>.  The former seem
-to focus on license types and file matching, and is able to detect
-ineffective blocks in the copyright file.  The latter reports missing
-copyright holders and years, but was confused by inconsistent license
-names (like CDDL vs. CDDL-1.0).  I suspect it is good to use both and
-fix all issues reported by them before uploading.  But I do not know
-if the tools and the ftpmasters agree on what is important to fix in a
-copyright file, so the package might still be rejected.</p>
-
-<p>The devscripts tool <tt>licensecheck</tt> deserve mentioning.  It
-will read through the source and try to find all copyright statements.
-It is not comparing the result to the content of debian/copyright, but
-can be useful when verifying the content of the copyright file.</p>
-
-<p>Are you aware of better tools in Debian to create and update
-debian/copyright file.  Please let me know, or blog about it on
-planet.debian.org.</p>
-
-<p>As usual, if you use Bitcoin and want to show your support of my
-activities, please send Bitcoin donations to my address
-<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
-
-<p><strong>Update 2016-02-20</strong>: I got a tip from Mike Gabriel
-on how to use licensecheck and cdbs to create a draft copyright file
-
-<p><pre>
-licensecheck --copyright -r `find * -type f` | \
-  /usr/lib/cdbs/licensecheck2dep5 > debian/copyright.auto
-</pre></p>
-
-<p>He mentioned that he normally check the generated file into the
-version control system to make it easier to discover license and
-copyright changes in the upstream source.  I will try to do the same
-with my packages in the future.</p>
-
-<p><strong>Update 2016-02-21</strong>: The cme author recommended
-against using -quiet for new users, so I removed it from the proposed
-command line.</p>
+      <div class="title"><a href="http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html">Norwegian Bokmål edition of Debian Administrator's Handbook is now available</a></div>
+      <div class="date">25th July 2017</div>
+      <div class="body"><p align="center"><img align="center" src="http://people.skolelinux.org/pere/blog/images/2017-07-25-debian-handbook-nb-testprint.png"/></p>
+
+<p>I finally received a copy of the Norwegian Bokmål edition of
+"<a href="https://debian-handbook.info/">The Debian Administrator's
+Handbook</a>".  This test copy arrived in the mail a few days ago, and
+I am very happy to hold the result in my hand.   We spent around one and a half year translating it. This paperbook edition
+<a href="https://debian-handbook.info/get/#norwegian">is available
+from lulu.com</a>.  If you buy it quickly, you save 25% on the list
+price.  The book is also available for download in electronic form as
+PDF, EPUB and Mobipocket, as can be
+<a href="https://debian-handbook.info/browse/nb-NO/stable/">read online
+as a web page</a>.</p>
+
+<p>This is the second book I publish (the first was the book
+"<a href="http://free-culture.cc/">Free Culture</a>" by Lawrence Lessig
+in
+<a href="http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html">English</a>,
+<a href="http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html">French</a>
+and
+<a href="http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">Norwegian
+Bokmål</a>), and I am very excited to finally wrap up this
+project.  I hope
+"<a href="http://www.lulu.com/shop/rapha%C3%ABl-hertzog-and-roland-mas/h%C3%A5ndbok-for-debian-administratoren/paperback/product-23262290.html">Håndbok
+for Debian-administratoren</a>" will be well received.</p>

 </div>
       <div class="tags">
         
         
 </div>
       <div class="tags">
         
         

-        Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>. 
+        Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian-handbook">debian-handbook</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>. 

         
         
       </div>
         
         
       </div>


@@ -184,81 +155,50 @@ command line.</p>
     <div class="padding"></div>
     
     <div class="entry">
     <div class="padding"></div>
     
     <div class="entry">

-      <div class="title"><a href="http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html">Using appstream in Debian to locate packages with firmware and mime type support</a></div>
-      <div class="date"> 4th February 2016</div>
-      <div class="body"><p>The <a href="https://wiki.debian.org/DEP-11">appstream system</a>
-is taking shape in Debian, and one provided feature is a very
-convenient way to tell you which package to install to make a given
-firmware file available when the kernel is looking for it.  This can
-be done using apt-file too, but that is for someone else to blog
-about. :)</p>
-
-<p>Here is a small recipe to find the package with a given firmware
-file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
-picked from the set of firmware announced using appstream in Debian
-unstable.  In general you would be looking for the firmware requested
-by the kernel during kernel module loading.  To find the package
-providing the example file, do like this:</p>
-
-<blockquote><pre>
-% apt install appstream
-[...]
-% apt update
-[...]
-% appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
-  awk '/Package:/ {print $2}'
-firmware-qlogic
-%
-</pre></blockquote>
-
-<p>See <a href="https://wiki.debian.org/AppStream/Guidelines">the
-appstream wiki</a> page to learn how to embed the package metadata in
-a way appstream can use.</p>
-
-<p>This same approach can be used to find any package supporting a
-given MIME type.  This is very useful when you get a file you do not
-know how to handle.  First find the mime type using <tt>file
---mime-type</tt>, and next look up the package providing support for
-it.  Lets say you got an SVG file.  Its MIME type is image/svg+xml,
-and you can find all packages handling this type like this:</p>
-
-<blockquote><pre>
-% apt install appstream
-[...]
-% apt update
-[...]
-% appstreamcli what-provides mimetype image/svg+xml | \
-  awk '/Package:/ {print $2}'
-bkchem
-phototonic
-inkscape
-shutter
-tetzle
-geeqie
-xia
-pinta
-gthumb
-karbon
-comix
-mirage
-viewnior
-postr
-ristretto
-kolourpaint4
-eog
-eom
-gimagereader
-midori
-%
-</pre></blockquote>
-
-<p>I believe the MIME types are fetched from the desktop file for
-packages providing appstream metadata.</p>
+      <div class="title"><a href="http://people.skolelinux.org/pere/blog/_Rapporten_ser_ikke_p__informasjonssikkerhet_knyttet_til_personlig_integritet_.html">«Rapporten ser ikke på informasjonssikkerhet knyttet til personlig integritet»</a></div>
+      <div class="date">27th June 2017</div>
+      <div class="body"><p>Jeg kom over teksten
+«<a href="https://freedom-to-tinker.com/2017/06/21/killing-car-privacy-by-federal-mandate/">Killing
+car privacy by federal mandate</a>» av Leonid Reyzin på Freedom to
+Tinker i dag, og det gleder meg å se en god gjennomgang om hvorfor det
+er et urimelig inngrep i privatsfæren å la alle biler kringkaste sin
+posisjon og bevegelse via radio.  Det omtalte forslaget basert på
+Dedicated Short Range Communication (DSRC) kalles Basic Safety Message
+(BSM) i USA og Cooperative Awareness Message (CAM) i Europa, og det
+norske Vegvesenet er en av de som ser ut til å kunne tenke seg å
+pålegge alle biler å fjerne nok en bit av innbyggernes privatsfære.
+Anbefaler alle å lese det som står der.
+
+<p>Mens jeg tittet litt på DSRC på biler i Norge kom jeg over et sitat
+jeg synes er illustrativt for hvordan det offentlige Norge håndterer
+problemstillinger rundt innbyggernes privatsfære i SINTEF-rapporten
+«<a href="https://www.sintef.no/publikasjoner/publikasjon/Download/?pubid=SINTEF+A23933">Informasjonssikkerhet
+i AutoPASS-brikker</a>» av Trond Foss:</p>
+
+<p><blockquote>
+«Rapporten ser ikke på informasjonssikkerhet knyttet til personlig
+  integritet.»
+</blockquote></p>
+
+<p>Så enkelt kan det tydeligvis gjøres når en vurderer
+informasjonssikkerheten.  Det holder vel at folkene på toppen kan si
+at «Personvernet er ivaretatt», som jo er den populære intetsigende
+frasen som gjør at mange tror enkeltindividers integritet tas vare på.
+Sitatet fikk meg til å undres på hvor ofte samme tilnærming, å bare se
+bort fra behovet for personlig itegritet, blir valgt når en velger å
+legge til rette for nok et inngrep i privatsfæren til personer i
+Norge.  Det er jo sjelden det får reaksjoner.  Historien om
+reaksjonene på Helse Sør-Østs tjenesteutsetting er jo sørgelig nok et
+unntak og toppen av isfjellet, desverre.  Tror jeg fortsatt takker nei
+til både AutoPASS og holder meg så langt unna det norske helsevesenet
+som jeg kan, inntil de har demonstrert og dokumentert at de verdsetter
+individets privatsfære og personlige integritet høyere enn kortsiktig
+gevist og samfunnsnytte.</p>

 </div>
       <div class="tags">
         
         
 </div>
       <div class="tags">
         
         

-        Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>. 
+        Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>. 

         
         
       </div>
         
         
       </div>


@@ -266,91 +206,66 @@ packages providing appstream metadata.</p>
     <div class="padding"></div>
     
     <div class="entry">
     <div class="padding"></div>
     
     <div class="entry">

-      <div class="title"><a href="http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html">Creepy, visualise geotagged social media information - nice free software</a></div>
-      <div class="date">24th January 2016</div>
-      <div class="body"><p>Most people seem not to realise that every time they walk around
-with the computerised radio beacon known as a mobile phone their
-position is tracked by the phone company and often stored for a long
-time (like every time a SMS is received or sent).  And if their
-computerised radio beacon is capable of running programs (often called
-mobile apps) downloaded from the Internet, these programs are often
-also capable of tracking their location (if the app requested access
-during installation).  And when these programs send out information to
-central collection points, the location is often included, unless
-extra care is taken to not send the location.  The provided
-information is used by several entities, for good and bad (what is
-good and bad, depend on your point of view).  What is certain, is that
-the private sphere and the right to free movement is challenged and
-perhaps even eradicated for those announcing their location this way,
-when they share their whereabouts with private and public
-entities.</p>
-
-<p align="center"><img width="70%" src="http://people.skolelinux.org/pere/blog/images/2016-01-24-nice-creepy-desktop-window.png"></p>
-
-<p>The phone company logs provide a register of locations to check out
-when one want to figure out what the tracked person was doing.  It is
-unavailable for most of us, but provided to selected government
-officials, company staff, those illegally buying information from
-unfaithful servants and crackers stealing the information.  But the
-public information can be collected and analysed, and a free software
-tool to do so is called
-<a href="http://www.geocreepy.com/">Creepy or Cree.py</a>.  I
-discovered it when I read
-<a href="http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-7787884.html">an
-article about Creepy</a> in the Norwegian newspaper Aftenposten i
-November 2014, and decided to check if it was available in Debian.
-The python program was in Debian, but
-<a href="https://tracker.debian.org/pkg/creepy">the version in
-Debian</a> was completely broken and practically unmaintained.  I
-uploaded a new version which did not work quite right, but did not
-have time to fix it then.  This Christmas I decided to finally try to
-get Creepy operational in Debian.  Now a fixed version is available in
-Debian unstable and testing, and almost all Debian specific patches
-are now included
-<a href="https://github.com/jkakavas/creepy">upstream</a>.</p>
-
-<p>The Creepy program visualises geolocation information fetched from
-Twitter, Instagram, Flickr and Google+, and allow one to get a
-complete picture of every social media message posted recently in a
-given area, or track the movement of a given individual across all
-these services.  Earlier it was possible to use the search API of at
-least some of these services without identifying oneself, but these
-days it is impossible.  This mean that to use Creepy, you need to
-configure it to log in as yourself on these services, and provide
-information to them about your search interests.  This should be taken
-into account when using Creepy, as it will also share information
-about yourself with the services.</p>
-
-<p>The picture above show the twitter messages sent from (or at least
-geotagged with a position from) the city centre of Oslo, the capital
-of Norway.  One useful way to use Creepy is to first look at
-information tagged with an area of interest, and next look at all the
-information provided by one or more individuals who was in the area.
-I tested it by checking out which celebrity provide their location in
-twitter messages by checkout out who sent twitter messages near a
-Norwegian TV station, and next could track their position over time,
-making it possible to locate their home and work place, among other
-things.  A similar technique have been
-<a href="http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl">used
-to locate Russian soldiers in Ukraine</a>, and it is both a powerful
-tool to discover lying governments, and a useful tool to help people
-understand the value of the private information they provide to the
-public.</p>
-
-<p>The package is not trivial to backport to Debian Stable/Jessie, as
-it depend on several python modules currently missing in Jessie (at
-least python-instagram, python-flickrapi and
-python-requests-toolbelt).</p>
-
-<p>(I have uploaded
-<a href="https://screenshots.debian.net/package/creepy">the image to
-screenshots.debian.net</a> and licensed it under the same terms as the
-Creepy program in Debian.)</p>
+      <div class="title"><a href="http://people.skolelinux.org/pere/blog/Updated_sales_number_for_my_Free_Culture_paper_editions.html">Updated sales number for my Free Culture paper editions</a></div>
+      <div class="date">12th June 2017</div>
+      <div class="body"><p>It is pleasing to see that the work we put down in publishing new
+editions of the classic <a href="http://www.free-culture.cc/">Free
+Culture book</a> by the founder of the Creative Commons movement,
+Lawrence Lessig, is still being appreciated.  I had a look at the
+latest sales numbers for the paper edition today.  Not too impressive,
+but happy to see some buyers still exist.  All the revenue from the
+books is sent to the <a href="https://creativecommons.org/">Creative
+Commons Corporation</a>, and they receive the largest cut if you buy
+directly from Lulu.  Most books are sold via Amazon, with Ingram
+second and only a small fraction directly from Lulu.  The ebook
+edition is available for free from
+<a href="https://github.com/petterreinholdtsen/free-culture-lessig">Github</a>.</p>
+
+<table border="0">
+<tr><th rowspan="2" valign="bottom">Title / language</th><th colspan="3">Quantity</th></tr>
+<tr><th>2016 jan-jun</th><th>2016 jul-dec</th><th>2017 jan-may</th></tr>
+
+<tr>
+  <td><a href="http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html">Culture Libre / French</a></td>
+  <td align="right">3</td>
+  <td align="right">6</td>
+  <td align="right">15</td>
+</tr>
+
+<tr>
+  <td><a href="http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">Fri kultur / Norwegian</a></td>
+  <td align="right">7</td>
+  <td align="right">1</td>
+  <td align="right">0</td>
+</tr>
+
+<tr>
+  <td><a href="http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html">Free Culture / English</a></td>
+  <td align="right">14</td>
+  <td align="right">27</td>
+  <td align="right">16</td>
+</tr>
+
+<tr>
+  <td>Total</td>
+  <td align="right">24</td>
+  <td align="right">34</td>
+  <td align="right">31</td>
+</tr>
+
+</table>
+
+<p>A bit sad to see the low sales number on the Norwegian edition, and
+a bit surprising the English edition still selling so well.</p>
+
+<p>If you would like to translate and publish the book in your native
+language, I would be happy to help make it happen.  Please get in
+touch.</p>

 </div>
       <div class="tags">
         
         
 </div>
       <div class="tags">
         
         

-        Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software</a>. 
+        Tags: <a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>. 

         
         
       </div>
         
         
       </div>


@@ -358,72 +273,59 @@ Creepy program in Debian.)</p>
     <div class="padding"></div>
     
     <div class="entry">
     <div class="padding"></div>
     
     <div class="entry">

-      <div class="title"><a href="http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html">Always download Debian packages using Tor - the simple recipe</a></div>
-      <div class="date">15th January 2016</div>
-      <div class="body"><p>During his DebConf15 keynote, Jacob Appelbaum
-<a href="https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/">observed
-that those listening on the Internet lines would have good reason to
-believe a computer have a given security hole</a> if it download a
-security fix from a Debian mirror.  This is a good reason to always
-use encrypted connections to the Debian mirror, to make sure those
-listening do not know which IP address to attack.  In August, Richard
-Hartmann observed that encryption was not enough, when it was possible
-to interfere download size to security patches or the fact that
-download took place shortly after a security fix was released, and
-<a href="http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/">proposed
-to always use Tor to download packages from the Debian mirror</a>.  He
-was not the first to propose this, as the
-<tt><a href="https://tracker.debian.org/pkg/apt-transport-tor">apt-transport-tor</a></tt>
-package by Tim Retout already existed to make it easy to convince apt
-to use <a href="https://www.torproject.org/">Tor</a>, but I was not
-aware of that package when I read the blog post from Richard.</p>
-
-<p>Richard discussed the idea with Peter Palfrader, one of the Debian
-sysadmins, and he set up a Tor hidden service on one of the central
-Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
-it possible to download packages directly between two tor nodes,
-making sure the network traffic always were encrypted.</p>
-
-<p>Here is a short recipe for enabling this on your machine, by
-installing <tt>apt-transport-tor</tt> and replacing http and https
-urls with tor+http and tor+https, and using the hidden service instead
-of the official Debian mirror site.  I recommend installing
-<tt>etckeeper</tt> before you start to have a history of the changes
-done in /etc/.</p>
+      <div class="title"><a href="http://people.skolelinux.org/pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html">Release 0.1.1 of free software archive system Nikita announced</a></div>
+      <div class="date">10th June 2017</div>
+      <div class="body"><p>I am very happy to report that the
+<a href="https://github.com/hiOA-ABI/nikita-noark5-core">Nikita Noark 5
+core project</a> tagged its second release today.  The free software
+solution is an implementation of the Norwegian archive standard Noark
+5 used by government offices in Norway.  These were the changes in
+version 0.1.1 since version 0.1.0 (from NEWS.md):

 
 

-<blockquote><pre>
-apt install apt-transport-tor
-sed -i 's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%' /etc/apt/sources.list
-sed -i 's% http% tor+http%' /etc/apt/sources.list
-</pre></blockquote>
+<ul>
+
+ <li>Continued work on the angularjs GUI, including document upload.</li>
+ <li>Implemented correspondencepartPerson, correspondencepartUnit and
+   correspondencepartInternal</li>
+ <li>Applied for coverity coverage and started submitting code on
+   regualr basis.</li>
+ <li>Started fixing bugs reported by coverity</li>
+ <li>Corrected and completed HATEOAS links to make sure entire API is
+   available via URLs in _links.</li>
+ <li>Corrected all relation URLs to use trailing slash.</li>
+ <li>Add initial support for storing data in ElasticSearch.</li>
+ <li>Now able to receive and store uploaded files in the archive.</li>
+ <li>Changed JSON output for object lists to have relations in _links.</li>
+ <li>Improve JSON output for empty object lists.</li>
+ <li>Now uses correct MIME type application/vnd.noark5-v4+json.</li>
+ <li>Added support for docker container images.</li>
+ <li>Added simple API browser implemented in JavaScript/Angular.</li>
+ <li>Started on archive client implemented in JavaScript/Angular.</li>
+ <li>Started on prototype to show the public mail journal.</li>
+ <li>Improved performance by disabling Sprint FileWatcher.</li>
+ <li>Added support for 'arkivskaper', 'saksmappe' and 'journalpost'.</li>
+ <li>Added support for some metadata codelists.</li>
+ <li>Added support for Cross-origin resource sharing (CORS).</li>
+ <li>Changed login method from Basic Auth to JSON Web Token (RFC 7519)
+   style.</li>
+ <li>Added support for GET-ing ny-* URLs.</li>
+ <li>Added support for modifying entities using PUT and eTag.</li>
+ <li>Added support for returning XML output on request.</li>
+ <li>Removed support for English field and class names, limiting ourself
+   to the official names.</li>
+ <li>...</li>
+ 
+</ul>

 
 

-<p>If you have more sources listed in /etc/apt/sources.list.d/, run
-the sed commands for these too.  The sed command is assuming your are
-using the ftp.debian.org Debian mirror.  Adjust the command (or just
-edit the file manually) to match your mirror.</p>
-
-<p>This work in Debian Jessie and later.  Note that tools like
-<tt>apt-file</tt> only recently started using the apt transport
-system, and do not work with these tor+http URLs.  For
-<tt>apt-file</tt> you need the version currently in experimental,
-which need a recent apt version currently only in unstable.  So if you
-need a working <tt>apt-file</tt>, this is not for you.</p>
-
-<p>Another advantage from this change is that your machine will start
-using Tor regularly and at fairly random intervals (every time you
-update the package lists or upgrade or install a new package), thus
-masking other Tor traffic done from the same machine.  Using Tor will
-become normal for the machine in question.</p>
-
-<p>On <a href="https://wiki.debian.org/FreedomBox">Freedombox</a>, APT
-is set up by default to use <tt>apt-transport-tor</tt> when Tor is
-enabled.  It would be great if it was the default on any Debian
-system.</p>
+<p>If this sound interesting to you, please contact us on IRC (#nikita
+on irc.freenode.net) or email
+(<a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">nikita-noark
+mailing list).</p>

 </div>
       <div class="tags">
         
         
 </div>
       <div class="tags">
         
         

-        Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>. 
+        Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>. 

         
         
       </div>
         
         
       </div>


@@ -431,37 +333,99 @@ system.</p>
     <div class="padding"></div>
     
     <div class="entry">
     <div class="padding"></div>
     
     <div class="entry">

-      <div class="title"><a href="http://people.skolelinux.org/pere/blog/Nedlasting_fra_NRK__som_Matroska_med_undertekster.html">Nedlasting fra NRK, som Matroska med undertekster</a></div>
-      <div class="date"> 2nd January 2016</div>
-      <div class="body"><p>Det kommer stadig nye løsninger for å ta lagre unna innslag fra NRK
-for å se på det senere.  For en stund tilbake kom jeg over et script
-nrkopptak laget av Ingvar Hagelund.  Han fjernet riktignok sitt script
-etter forespørsel fra Erik Bolstad i NRK, men noen tok heldigvis og
-gjorde det <a href="https://github.com/liangqi/nrkopptak">tilgjengelig
-via github</a>.</p>
-
-<p>Scriptet kan lagre som MPEG4 eller Matroska, og bake inn
-undertekster i fila på et vis som blant annet VLC forstår.  For å
-bruke scriptet, kopier ned git-arkivet og kjør</p>
-
-<p><pre>
-nrkopptak/bin/nrk-opptak k <ahref="https://tv.nrk.no/serie/bmi-turne/MUHH45000115/sesong-1/episode-1">https://tv.nrk.no/serie/bmi-turne/MUHH45000115/sesong-1/episode-1</a>
-</pre></p>
-
-<p>URL-eksemplet er dagens toppsak på tv.nrk.no.  Argument 'k' ber
-scriptet laste ned og lagre som Matroska.  Det finnes en rekke andre
-muligheter for valg av kvalitet og format.</p>
-
-<p>Jeg foretrekker dette scriptet fremfor youtube-dl, som
-<a href="http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK_med_den__nye__l_sningen.html">
-nevnt i 2014 støtter NRK</a> og en rekke andre videokilder, på grunn
-av at nrkopptak samler undertekster og video i en enkelt fil, hvilket
-gjør håndtering enklere på disk.</p>
+      <div class="title"><a href="http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html">Idea for storing trusted timestamps in a Noark 5 archive</a></div>
+      <div class="date"> 7th June 2017</div>
+      <div class="body"><p><em>This is a copy of
+<a href="https://lists.nuug.no/pipermail/nikita-noark/2017-June/000297.html">an
+email I posted to the nikita-noark mailing list</a>.  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
+<a href="https://www.arkivverket.no/forvaltning-og-utvikling/regelverk-og-standarder/noark-standarden">Noark
+5 standard</a> for government archives.</em></p>
+
+<p>I've been wondering a bit lately how trusted timestamps could be
+stored in Noark 5.
+<a href="https://en.wikipedia.org/wiki/Trusted_timestamping">Trusted
+timestamps</a> 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.</p>
+
+<p>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?</p>
+
+<p>Given a "dokumentbeskrivelse" with an associated "dokumentobjekt",
+a new dokumentobjekt is associated with "dokumentbeskrivelse" with the
+same attributes as the stamped dokumentobjekt except these
+attributes:</p>
+
+<ul>
+
+<li>format -> "RFC3161"
+<li>mimeType -> "application/timestamp-reply"
+<li>formatDetaljer -> "&lt;source URL for timestamp service&gt;"
+<li>filenavn -> "&lt;sjekksum&gt;.tsr"
+
+</ul>
+
+<p>This assume a service following
+<a href="https://tools.ietf.org/html/rfc3161">IETF RFC 3161</a> 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.</p>
+
+<p>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.</p>
+
+<p>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 "<sjekksum>.tsr" value mentioned
+above).</p>
+
+<p><blockquote><pre>
+openssl ts -query -data "$inputfile" -cert -sha256 -no_nonce \
+  | curl -s -H "Content-Type: application/timestamp-query" \
+      --data-binary "@-" http://zeitstempel.dfn.de > $sha256.tsr
+</pre></blockquote></p>
+
+<p>To verify the timestamp, you first need to download the public key
+of the trusted timestamp service, for example using this command:</p>
+
+<p><blockquote><pre>
+wget -O ca-cert.txt \
+  https://pki.pca.dfn.de/global-services-ca/pub/cacert/chain.txt
+</pre></blockquote></p>
+
+<p>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. :)</p>
+
+<p>The verification itself is a simple openssl command:</p>
+
+<p><blockquote><pre>
+openssl ts -verify -data $inputfile -in $sha256.tsr \
+  -CAfile ca-cert.txt -text
+</pre></blockquote></p>
+
+<p>Is there any reason this approach would not work?  Is it somehow against
+the Noark 5 specification?</p>

 </div>
       <div class="tags">
         
         
 </div>
       <div class="tags">
         
         

-        Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>. 
+        Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>. 

         
         
       </div>
         
         
       </div>


@@ -469,58 +433,61 @@ gjør håndtering enklere på disk.</p>
     <div class="padding"></div>
     
     <div class="entry">
     <div class="padding"></div>
     
     <div class="entry">

-      <div class="title"><a href="http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html">OpenALPR, find car license plates in video streams - nice free software</a></div>
-      <div class="date">23rd December 2015</div>
-      <div class="body"><p>When I was a kid, we used to collect "car numbers", as we used to
-call the car license plate numbers in those days.  I would write the
-numbers down in my little book and compare notes with the other kids
-to see how many region codes we had seen and if we had seen some
-exotic or special region codes and numbers.  It was a fun game to pass
-time, as we kids have plenty of it.</p>
-
-<p>A few days I came across
-<a href="https://github.com/openalpr/openalpr">the OpenALPR
-project</a>, a free software project to automatically discover and
-report license plates in images and video streams, and provide the
-"car numbers" in a machine readable format.  I've been looking for
-such system for a while now, because I believe it is a bad idea that the
-<a href="https://en.wikipedia.org/wiki/Automatic_number_plate_recognition">automatic
-number plate recognition</a> tool only is available in the hands of
-the powerful, and want it to be available also for the powerless to
-even the score when it comes to surveillance and sousveillance.  I
-discovered the developer
-<a href="https://bugs.debian.org/747509">wanted to get the tool into
-Debian</a>, and as I too wanted it to be in Debian, I volunteered to
-help him get it into shape to get the package uploaded into the Debian
-archive.</p>
-
-<p>Today we finally managed to get the package into shape and uploaded
-it into Debian, where it currently
-<a href="https://ftp-master.debian.org//new/openalpr_2.2.1-1.html">waits
-in the NEW queue</a> for review by the Debian ftpmasters.</p>
-
-<p>I guess you are wondering why on earth such tool would be useful
-for the common folks, ie those not running a large government
-surveillance system?  Well, I plan to put it in a computer on my bike
-and in my car, tracking the cars nearby and allowing me to be notified
-when number plates on my watch list are discovered.  Another use case
-was suggested by a friend of mine, who wanted to set it up at his home
-to open the car port automatically when it discovered the plate on his
-car.  When I mentioned it perhaps was a bit foolhardy to allow anyone
-capable of placing his license plate number of a piece of cardboard to
-open his car port, men replied that it was always unlocked anyway.  I
-guess for such use case it make sense.  I am sure there are other use
-cases too, for those with imagination and a vision.</p>
-
-<p>If you want to build your own version of the Debian package, check
-out the upstream git source and symlink ./distros/debian to ./debian/
-before running "debuild" to build the source.  Or wait a bit until the
-package show up in unstable.</p>
+      <div class="title"><a href="http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html">Når nynorskoversettelsen svikter til eksamen...</a></div>
+      <div class="date"> 3rd June 2017</div>
+      <div class="body"><p><a href="http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-622459b.html">Aftenposten
+melder i dag</a> 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
+<a href="https://www.apertium.org/">Apertium</a> ville gjort en bedre
+jobb enn Utdanningsdirektoratet.  Det kan se slik ut.</p>
+
+<p>Her er bokmålsoppgaven fra eksamenen:</p>
+
+<blockquote>
+<p>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
+rolle og muligheter til å håndtere internasjonale utfordringer, som
+for eksempel flykningekrisen.</p>
+
+<p>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
+på temaet:</p>
+<ol>
+<li>Flykningeregnskapet 2016, UNHCR og IDMC
+<li>«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
+</ol>
+
+</blockquote>
+
+<p>Dette oversetter Apertium slik:</p>
+
+<blockquote>
+<p>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.</p>
+
+<p>Vedleggja er døme på tekster som kan gje relevante perspektiv på
+temaet:</p>
+
+<ol>
+<li>*Flykningeregnskapet 2016, *UNHCR og *IDMC</li>
+<li>«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015</li>
+</ol>
+
+</blockquote>
+
+<p>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
+"andre aktørers rolle og muligheter til ..." burde vært oversatt til
+"rolla til andre aktørar og deira høve til ..." eller noe slikt, men
+det er kanskje flisespikking.  Det understreker vel bare at det alltid
+trengs korrekturlesning etter automatisk oversettelse.</p>

 </div>
       <div class="tags">
         
         
 </div>
       <div class="tags">
         
         

-        Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software</a>. 
+        Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll</a>. 

         
         
       </div>
         
         
       </div>


@@ -528,114 +495,67 @@ package show up in unstable.</p>
     <div class="padding"></div>
     
     <div class="entry">
     <div class="padding"></div>
     
     <div class="entry">

-      <div class="title"><a href="http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html">Using appstream with isenkram to install hardware related packages in Debian</a></div>
-      <div class="date">20th December 2015</div>
-      <div class="body"><p>Around three years ago, I created
-<a href="http://packages.qa.debian.org/isenkram">the isenkram
-system</a> to get a more practical solution in Debian for handing
-hardware related packages.  A GUI system in the isenkram package will
-present a pop-up dialog when some hardware dongle supported by
-relevant packages in Debian is inserted into the machine.  The same
-lookup mechanism to detect packages is available as command line
-tools in the isenkram-cli package.  In addition to mapping hardware,
-it will also map kernel firmware files to packages and make it easy to
-install needed firmware packages automatically.  The key for this
-system to work is a good way to map hardware to packages, in other
-words, allow packages to announce what hardware they will work
-with.</p>
-
-<p>I started by providing data files in the isenkram source, and
-adding code to download the latest version of these data files at run
-time, to ensure every user had the most up to date mapping available.
-I also added support for storing the mapping in the Packages file in
-the apt repositories, but did not push this approach because while I
-was trying to figure out how to best store hardware/package mappings,
-<a href="http://www.freedesktop.org/software/appstream/docs/">the
-appstream system</a> was announced.  I got in touch and suggested to
-add the hardware mapping into that data set to be able to use
-appstream as a data source, and this was accepted at least for the
-Debian version of appstream.</p>
-
-<p>A few days ago using appstream in Debian for this became possible,
-and today I uploaded a new version 0.20 of isenkram adding support for
-appstream as a data source for mapping hardware to packages.  The only
-package so far using appstream to announce its hardware support is my
-pymissile package.  I got help from Matthias Klumpp with figuring out
-how do add the required
-<a href="https://appstream.debian.org/html/sid/main/metainfo/pymissile.html">metadata
-in pymissile</a>.  I added a file debian/pymissile.metainfo.xml with
-this content:</p>
-
-<blockquote><pre>
-&lt;?xml version="1.0" encoding="UTF-8"?&gt;
-&lt;component&gt;
-  &lt;id&gt;pymissile&lt;/id&gt;
-  &lt;metadata_license&gt;MIT&lt;/metadata_license&gt;
-  &lt;name&gt;pymissile&lt;/name&gt;
-  &lt;summary&gt;Control original Striker USB Missile Launcher&lt;/summary&gt;
-  &lt;description&gt;
-    &lt;p&gt;
-      Pymissile provides a curses interface to control an original
-      Marks and Spencer / Striker USB Missile Launcher, as well as a
-      motion control script to allow a webcamera to control the
-      launcher.
-    &lt;/p&gt;
-  &lt;/description&gt;
-  &lt;provides&gt;
-    &lt;modalias&gt;usb:v1130p0202d*&lt;/modalias&gt;
-  &lt;/provides&gt;
-&lt;/component&gt;
-</pre></blockquote>
-
-<p>The key for isenkram is the component/provides/modalias value,
-which is a glob style match rule for hardware specific strings
-(modalias strings) provided by the Linux kernel.  In this case, it
-will map to all USB devices with vendor code 1130 and product code
-0202.</p>
-
-<p>Note, it is important that the license of all the metadata files
-are compatible to have permissions to aggregate them into archive wide
-appstream files.  Matthias suggested to use MIT or BSD licenses for
-these files.  A challenge is figuring out a good id for the data, as
-it is supposed to be globally unique and shared across distributions
-(in other words, best to coordinate with upstream what to use).  But
-it can be changed later or, so we went with the package name as
-upstream for this project is dormant.</p>
-
-<p>To get the metadata file installed in the correct location for the
-mirror update scripts to pick it up and include its content the
-appstream data source, the file must be installed in the binary
-package under /usr/share/appdata/.  I did this by adding the following
-line to debian/pymissile.install:</p>
-
-<blockquote><pre>
-debian/pymissile.metainfo.xml usr/share/appdata
-</pre></blockquote>
-
-<p>With that in place, the command line tool isenkram-lookup will list
-all packages useful on the current computer automatically, and the GUI
-pop-up handler will propose to install the package not already
-installed if a hardware dongle is inserted into the machine in
-question.</p>
-
-<p>Details of the modalias field in appstream is available from the 
-<a href="https://wiki.debian.org/DEP-11">DEP-11</a> proposal.</p>
-
-<p>To locate the modalias values of all hardware present in a machine,
-try running this command on the command line:</p>
-
-<blockquote><pre>
-cat $(find /sys/devices/|grep modalias)
-</pre></blockquote>
-
-<p>To learn more about the isenkram system, please check out
-<a href="http://people.skolelinux.org/pere/blog/tags/isenkram/">my
-blog posts tagged isenkram</a>.</p>
+      <div class="title"><a href="http://people.skolelinux.org/pere/blog/Epost_inn_som_arkivformat_i_Riksarkivarens_forskrift_.html">Epost inn som arkivformat i Riksarkivarens forskrift?</a></div>
+      <div class="date">27th April 2017</div>
+      <div class="body"><p>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
+<a href="http://www.arkivverket.no/arkivverket/Offentleg-forvalting/Noark/Noark-5">Noark
+5-løsninger</a> i Norge.</p>
+
+<p>Jeg fant høringsdokumentene hos
+<a href="https://www.arkivrad.no/aktuelt/riksarkivarens-forskrift-pa-horing">Norsk
+Arkivråd</a> etter å ha blitt tipset på epostlisten til
+<a href="https://github.com/hiOA-ABI/nikita-noark5-core">fri
+programvareprosjektet Nikita Noark5-Core</a>, 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
+<a href="https://github.com/petterreinholdtsen/noark5-tester/blob/master/docs/hoering-arkivforskrift.tex">egen
+høringsuttalelse</a>, og lurer på om andre er interessert i å støtte
+forslaget om å tillate arkivering av epost som epost i arkivet.</p>
+
+<p>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:</p>
+
+<p><blockquote>
+
+  <p>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).</p>
+
+  <p>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,
+  <a href="https://tools.ietf.org/html/rfc5322">https://tools.ietf.org/html/rfc5322</a>. 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.</p>
+
+</blockquote></p>
+
+<p>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
+<a href="https://github.com/petterreinholdtsen/noark5-tester/blob/master/docs/epostlagring.md">følge
+fremdriften på web</a>.</p>
+
+<p>Oppdatering 2017-04-28: I dag ble høringuttalelsen jeg skrev
+  <a href="https://www.nuug.no/news/NUUGs_h_ringuttalelse_til_Riksarkivarens_forskrift.shtml">sendt
+  inn av foreningen NUUG</a>.</p>

 </div>
       <div class="tags">
         
         
 </div>
       <div class="tags">
         
         

-        Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram</a>. 
+        Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>. 

         
         
       </div>
         
         
       </div>


@@ -643,89 +563,52 @@ blog posts tagged isenkram</a>.</p>
     <div class="padding"></div>
     
     <div class="entry">
     <div class="padding"></div>
     
     <div class="entry">

-      <div class="title"><a href="http://people.skolelinux.org/pere/blog/Bokhandeldistribusjon_av_boken_Fri_kultur_av_Lawrence_Lessig.html">Bokhandeldistribusjon av boken Fri kultur av Lawrence Lessig</a></div>
-      <div class="date">14th December 2015</div>
-      <div class="body"><p><strong>Besøk
-<a href="https://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">lulu.com</a>
-eller
-<a href="https://www.amazon.com/Fri-kultur-Norwegian-Lawrence-Lessig/dp/8269018236/">Amazon</a>
-for å kjøpe boken på papir, eller last ned ebook som
-<a href="https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/archive/freeculture.nb.pdf">PDF</a>,
-<a href="https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/archive/freeculture.nb.epub">ePub</a>
-eller
-<a href="https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/archive/freeculture.nb.mobi">MOBI</a>
-fra
-<a href="https://github.com/petterreinholdtsen/free-culture-lessig/">github</a>.</strong></p>
-
-<p>Jeg ble gledelig overrasket i dag da jeg oppdaget at boken jeg har
-gitt ut
-<a href="https://www.amazon.com/Fri-kultur-Norwegian-Lawrence-Lessig/dp/8269018236/">hadde
-dukket opp i Amazon</a>.  Jeg hadde trodd det skulle ta lenger tid, da
-jeg fikk beskjed om at det skulle ta seks til åtte uker.
-Amazonoppføringen er et resultat av at jeg for noen uker siden
-diskuterte prissetting og håndtering av profitt med forfatteren.  Det
-måtte avklares da bruksvilkårene til boken har krav om
-ikke-kommersiell bruk.  Vi ble enige om at overskuddet fra salg av
-boken skal sendes til
-<a href="https://creativecommons.org/">Creative Commons-stiftelsen</a>.
-Med det på plass kunne jeg be
-<a href="https://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">lulu.com</a>
-om å gi boken «utvidet» distribusjon.  Årsaken til at
-bokhandeldistribusjon var litt utfordrende er at bokhandlere krever
-mulighet for profitt på bøkene de selger (selvfølgelig), og dermed
-måtte de få lov til å selge til høyere pris enn lulu.com.  I tillegg
-er det krav om samme pris på lulu.com og i bokhandlene, dermed blir
-prisen økt også hos lulu.com.  Hva skulle jeg gjøre med den profitten
-uten å bryte med klausulen om ikkekommersiell?  Løsningen var å gi
-bort profitten til CC-stiftelsen.  Prisen på boken ble nesten
-tredoblet, til $19.99 (ca. 160,-) pluss frakt, men synligheten øker
-betraktelig når den kan finnes i katalogene til store nettbokhandlere.
-Det betyr at hvis du allerede har kjøpt boken har du fått den veldig
-billig, og kjøper du den nå, får du den fortsatt billig samt donerer i
-tillegg noen tiere til fremme av Creative Commons.</p>
-
-<p>Mens jeg var i gang med å titte etter informasjon om boken 
-oppdaget jeg  at den også var dukket opp på
-<a href="https://books.google.no/books?id=uKUGCwAAQBAJ">Google
-Books</a>, der en kan lese den på web.  PDF-utgaven har ennå ikke
-dukket opp hos <a href="https://www.nb.no/">Nasjonalbiblioteket</a>,
-men det regner jeg med kommer på plass i løpet av noen uker.  Boken er
-heller ikke dukket opp hos
-<a href="https://www.barnesandnoble.com/">Barnes & Noble</a> ennå, men
-jeg antar det bare er et tidsspørsmål før dette er på plass.</p>
-
-<p>Boken er dessverre ikke tilgjengelig fra norske bokhandlere, og
-kommer neppe til å bli det med det første.  Årsaken er at for å få det
-til måtte jeg personlig håndtere bestilling av bøker, hvilket jeg ikke
-er interessert i å bruke tid på.  Jeg kunne betalt ca 2000,- til
-<a href="http://www.bokbasen.no/">den norske bokbasen</a>, en felles
-database over bøker tilgjengelig for norske bokhandlere, for å få en
-oppføring der, men da måtte jeg tatt imot bestillinger på epost og
-sendt ut bøker selv.  Det ville krevd at jeg var klar til å
-sende ut bøker på kort varsel, dvs. holdt meg med ekstra bøker,
-konvolutter og frimerker.  Bokbasen har visst ikke opplegg for å be
-bokhandlene bestille direkte via web, så jeg droppet oppføring der.
-Jeg har spurt Haugen bok og Tronsmo direkte på epost om de er
-interessert i å ta inn boken i sin bestillingskatalog, men ikke fått
-svar, så jeg antar de ikke er interessert.  Derimot har jeg fått en
-hyggelig henvendelse fra Biblioteksentralen som fortalte at de har
-lagt den inn i sin database slik at deres bibliotekskunder enkelt kan
-bestille den via dem.</p>
-
-<p>Boken er i følge
-<a href="http://bibsys-almaprimo.hosted.exlibrisgroup.com/primo_library/libweb/action/display.do?tabs=detailsTab&ct=display&fn=search&doc=BIBSYS_ILS71518423420002201&indx=1&recIds=BIBSYS_ILS71518423420002201&recIdxs=0&elementId=0&renderMode=poppedOut&displayMode=full&frbrVersion=&dscnt=0&tab=library_catalogue&dstmp=1448543801124&vl(freeText0)=fri%20kultur&vid=UBO&mode=Basic">Bibsys/Oria</a>
-og bokdatabasen til
-<a href="https://www.deich.folkebibl.no/cgi-bin/websok?tnr=1819617">Deichmanske</a>
-tilgjengelig fra flere biblioteker allerede, og alle eksemplarer er
-visst allerede utlånt med ventetid.  Det synes jeg er veldig gledelig
-å se.  Jeg håper mange kommer til å lese boken.  Jeg tror den er
-spesielt egnet for foreldre og bekjente av oss nerder for å forklare
-hva slags problemer vi ser med dagens opphavsrettsregime.</p>
+      <div class="title"><a href="http://people.skolelinux.org/pere/blog/Offentlig_elektronisk_postjournal_blokkerer_tilgang_for_utvalgte_webklienter.html">Offentlig elektronisk postjournal blokkerer tilgang for utvalgte webklienter</a></div>
+      <div class="date">20th April 2017</div>
+      <div class="body"><p>Jeg oppdaget i dag at <a href="https://www.oep.no/">nettstedet som
+publiserer offentlige postjournaler fra statlige etater</a>, 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:</p>
+
+<blockquote><pre>
+% curl -v -s https://www.oep.no/pub/report.xhtml?reportId=3 2>&1 |grep '< HTTP'
+< HTTP/1.1 404 Not Found
+% curl -v -s --header 'User-Agent:Opera/12.0' https://www.oep.no/pub/report.xhtml?reportId=3 2>&1 |grep '< HTTP'
+< HTTP/1.1 200 OK
+%
+</pre></blockquote>
+
+<p>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.</p>
+
+<p>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
+<a href="http://presse.no/dette-mener-np/undergraver-offentlighetsloven/">rapporten
+«Slik hindrer departementer innsyn» som ble publiserte i januar
+2017</a>.  Det virker usannsynlig, da det jo er trivielt å bytte
+User-Agent til noe nytt.</p>
+
+<p>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
+<a href="https://www.oep.no/search/result.html?period=dateRange&fromDate=01.01.2016&toDate=01.04.2017&dateType=documentDate&caseDescription=&descType=both&caseNumber=&documentNumber=&sender=basefarm&senderType=both&documentType=all&legalAuthority=&archiveCode=&list2=196&searchType=advanced&Search=Search+in+records">postjournalen
+til DIFI viser kun to dokumenter</a> det siste året mellom DIFI og
+Basefarm.
+<a href="https://www.mimesbronn.no/request/blokkering_av_tilgang_til_oep_fo">Mimes brønn neste</a>,
+tenker jeg.</p>

 </div>
       <div class="tags">
         
         
 </div>
       <div class="tags">
         
         

-        Tags: <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>. 
+        Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>. 

         
         
       </div>
         
         
       </div>


@@ -733,114 +616,101 @@ hva slags problemer vi ser med dagens opphavsrettsregime.</p>
     <div class="padding"></div>
     
     <div class="entry">
     <div class="padding"></div>
     
     <div class="entry">

-      <div class="title"><a href="http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html">The GNU General Public License is not magic pixie dust</a></div>
-      <div class="date">30th November 2015</div>
-      <div class="body"><p>A blog post from my fellow Debian developer Paul Wise titled
-"<a href="http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/">The
-GPL is not magic pixie dust</a>" explain the importance of making sure
-the <a href="http://www.gnu.org/copyleft/gpl.html">GPL</a> is enforced.
-I quote the blog post from Paul in full here with his permission:<p>
-
-<blockquote>
-
-<p><a href="https://sfconservancy.org/supporter/"><img src="https://sfconservancy.org/img/supporter-badge.png" width="194" height="90" alt="Become a Software Freedom Conservancy Supporter!" align="right" border="0" /></a></p>
-
-<blockquote>
-The GPL is not magic pixie dust. It does not work by itself.<br/>
-
-The first step is to choose a
-<a href="https://copyleft.org/">copyleft</a> license for your
-code.<br/>
-
-The next step is, when someone fails to follow that copyleft license,
-<b>it must be enforced</b><br/>
-
-and its a simple fact of our modern society that such type of
-work<br/>
-
-is incredibly expensive to do and incredibly difficult to do.
-</blockquote>
-
-<p><small>-- <a href="http://ebb.org/bkuhn/">Bradley Kuhn</a>, in
-<a href="http://faif.us/" title="Free as in Freedom">FaiF</a>
-<a href="http://faif.us/cast/2015/nov/24/0x57/">episode
-0x57</a></small></p>
-
-<p>As the Debian Website
-<a href="https://bugs.debian.org/794116">used</a>
-<a href="https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=1.24&amp;r2=1.25">to</a>
-imply, public domain and permissively licensed software can lead to
-the production of more proprietary software as people discover useful
-software, extend it and or incorporate it into their hardware or
-software products.  Copyleft licenses such as the GNU GPL were created
-to close off this avenue to the production of proprietary software but
-such licenses are not enough.  With the ongoing adoption of Free
-Software by individuals and groups, inevitably the community's
-expectations of license compliance are violated, usually out of
-ignorance of the way Free Software works, but not always.  As Karen
-and Bradley explained in <a href="http://faif.us/" title="Free as in
-Freedom">FaiF</a>
-<a href="http://faif.us/cast/2015/nov/24/0x57/">episode 0x57</a>,
-copyleft is nothing if no-one is willing and able to stand up in court
-to protect it.  The reality of today's world is that legal
-representation is expensive, difficult and time consuming.  With
-<a href="http://gpl-violations.org/">gpl-violations.org</a> in hiatus
-<a href="http://gpl-violations.org/news/20151027-homepage-recovers/">until</a>
-some time in 2016, the <a href="https://sfconservancy.org/">Software
-Freedom Conservancy</a> (a tax-exempt charity) is the major defender
-of the Linux project, Debian and other groups against GPL violations.
-In March the SFC supported a
-<a href="https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/">lawsuit
-by Christoph Hellwig</a> against VMware for refusing to
-<a href="https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html">comply
-with the GPL</a> in relation to their use of parts of the Linux
-kernel.  Since then two of their sponsors pulled corporate funding and
-conferences
-<a href="https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/">blocked
-or cancelled their talks</a>.  As a result they have decided to rely
-less on corporate funding and more on the broad community of
-individuals who support Free Software and copyleft.  So the SFC has
-<a href="https://sfconservancy.org/news/2015/nov/23/2015fundraiser/">launched</a>
-a <a href="https://sfconservancy.org/supporter/">campaign</a> to create
-a community of folks who stand up for copyleft and the GPL by
-supporting their work on promoting and supporting copyleft and Free
-Software.</p>
-
-<p>If you support Free Software,
-<a href="https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/">like</a>
-what the SFC do, agree with their
-<a href="https://sfconservancy.org/linux-compliance/principles.html">compliance
-principles</a>, are happy about their
-<a href="https://sfconservancy.org/supporter/">successes</a> in 2015,
-work on a project that is an SFC
-<a href="https://sfconservancy.org/members/current/">member</a> and or
-just want to stand up for copyleft, please join
-<a href="https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA">Christopher
-Allan Webber</a>,
-<a href="https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/">Carol
-Smith</a>,
-<a href="http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/">Jono
-Bacon</a>, myself and
-<a href="https://sfconservancy.org/sponsors/#supporters">others</a> in
-becoming a
-<a href="https://sfconservancy.org/supporter/">supporter</a>.  For the
-next week your donation will be
-<a href="https://sfconservancy.org/news/2015/nov/27/black-friday/">matched</a>
-by an anonymous donor.  Please also consider asking your employer to
-match your donation or become a sponsor of SFC.  Don't forget to
-spread the word about your support for SFC via email, your blog and or
-social media accounts.</p>
-
-</blockquote>
-
-<p>I agree with Paul on this topic and just signed up as a Supporter
-of Software Freedom Conservancy myself.  Perhaps you should be a
-supporter too?</p>
+      <div class="title"><a href="http://people.skolelinux.org/pere/blog/Free_software_archive_system_Nikita_now_able_to_store_documents.html">Free software archive system Nikita now able to store documents</a></div>
+      <div class="date">19th March 2017</div>
+      <div class="body"><p>The <a href="https://github.com/hiOA-ABI/nikita-noark5-core">Nikita
+Noark 5 core project</a> is implementing the Norwegian standard for
+keeping an electronic archive of government documents.
+<a href="http://www.arkivverket.no/arkivverket/Offentlig-forvaltning/Noark/Noark-5/English-version">The
+Noark 5 standard</a> 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've been involved
+in the project since a few weeks before Christmas, when the Norwegian
+Unix User Group
+<a href="https://www.nuug.no/news/NOARK5_kjerne_som_fri_programvare_f_r_epostliste_hos_NUUG.shtml">announced
+it supported the project</a>.  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.</p>
+
+<p>If you would like to help make sure there is a free software
+alternatives for the archives, please join our IRC channel
+(<a href="irc://irc.freenode.net/%23nikita"">#nikita on
+irc.freenode.net</a>) and
+<a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">the
+project mailing list</a>.</p>
+
+<p>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
+<tt>archive-pdf</tt> to upload a PDF file to the archive using this
+API.  The tool is very simple at the moment, and find existing
+<a href="https://en.wikipedia.org/wiki/Fonds">fonds</a>, 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:</p>
+
+<p><blockquote><pre>
+~/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$
+</pre></blockquote></p>
+
+<p>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 <tt>archive-pdf</tt>
+tool can be found in the git repository for the API tester.</p>
+
+<p>In the project, I have been mostly working on
+<a href="https://github.com/petterreinholdtsen/noark5-tester">the API
+tester</a> so far, while getting to know the code base.  The API
+tester currently use
+<a href="https://en.wikipedia.org/wiki/HATEOAS">the HATEOAS links</a>
+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.</p>
+
+<p>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
+<a href="https://github.com/petterreinholdtsen/noark5-tester/tree/master/mangelmelding">started
+writing down</a> the questions we get from implementing it.  We use a
+format inspired by how <a href="http://www.opengroup.org/austin/">The
+Austin Group</a> collect defect reports for the POSIX standard with
+<a href="http://www.opengroup.org/austin/mantis.html">their
+instructions for the MANTIS defect tracker system</a>, in lack of an official way to structure defect reports for Noark 5 (our first submitted defect report was a <a href="https://github.com/petterreinholdtsen/noark5-tester/blob/master/mangelmelding/sendt/2017-03-15-mangel-prosess.md">request for a procedure for submitting defect reports</a> :).
+
+<p>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.</p>

 </div>
       <div class="tags">
         
         
 </div>
       <div class="tags">
         
         

-        Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>. 
+        Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>. 

         
         
       </div>
         
         
       </div>


@@ -855,6 +725,25 @@ supporter too?</p>
 <h2>Archive</h2>
 <ul>
 
 <h2>Archive</h2>
 <ul>
 

+<li>2017
+<ul>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2017/01/">January (4)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2017/02/">February (3)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2017/03/">March (5)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2017/04/">April (2)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2017/06/">June (5)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2017/07/">July (1)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2017/08/">August (1)</a></li>
+
+</ul></li>
+

 <li>2016
 <ul>
 
 <li>2016
 <ul>
 


@@ -862,7 +751,25 @@ supporter too?</p>
 
 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/02/">February (2)</a></li>
 
 
 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/02/">February (2)</a></li>
 

-<li><a href="http://people.skolelinux.org/pere/blog/archive/2016/03/">March (1)</a></li>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2016/03/">March (3)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2016/04/">April (8)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2016/05/">May (8)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2016/06/">June (2)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2016/07/">July (2)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2016/08/">August (5)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2016/09/">September (2)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2016/10/">October (3)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2016/11/">November (8)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2016/12/">December (5)</a></li>

 
 </ul></li>
 
 
 </ul></li>
 


@@ -1095,43 +1002,45 @@ supporter too?</p>
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (9)</a></li>
 
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (9)</a></li>
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (15)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (16)</a></li>

 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
 
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (121)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (151)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (158)</a></li>

 
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (154)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/debian-handbook">debian-handbook (4)</a></li>

 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
 
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/dld">dld (15)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/dld">dld (16)</a></li>

 
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (20)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (24)</a></li>

 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
 
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (303)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (351)</a></li>

 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
 
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (25)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (30)</a></li>

 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
 
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (16)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (18)</a></li>

 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/h264">h264 (20)</a></li>
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (42)</a></li>
 
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/h264">h264 (20)</a></li>
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (42)</a></li>
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (11)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (15)</a></li>

 
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (19)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (20)</a></li>

 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
 
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
 


@@ -1143,21 +1052,21 @@ supporter too?</p>
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
 
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (37)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (39)</a></li>

 
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (7)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (9)</a></li>

 
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (273)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (291)</a></li>

 
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (177)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (189)</a></li>

 
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (22)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (33)</a></li>

 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
 
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (58)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (64)</a></li>

 
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (92)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (101)</a></li>

 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
 
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
 


@@ -1167,39 +1076,39 @@ supporter too?</p>
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
 
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (9)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (10)</a></li>

 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
 
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (5)</a></li>

 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
 
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (45)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (53)</a></li>

 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
 
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (4)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (5)</a></li>

 
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (48)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (55)</a></li>

 
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (3)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (6)</a></li>

 
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (10)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (11)</a></li>

 
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (36)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (49)</a></li>

 
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (2)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (3)</a></li>

 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/usenix">usenix (2)</a></li>
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
 
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/usenix">usenix (2)</a></li>
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (55)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (59)</a></li>

 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
 
 
  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
 

- <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (38)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (40)</a></li>

 
 </ul>
 
 
 </ul>