Generated.

[homepage.git] / blog / index.rss

diff --git a/blog/index.rss b/blog/index.rss
index 624313ff460bd80b7ac18ed7d0297605eedd107b..2b3c45abc93fa778bcf50a55c17d39efa68a0365 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -7,589 +7,539 @@
                 <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>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.md&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;
+               <title>Generating 3D prints in Debian using Cura and Slic3r(-prusa)</title>
+               <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</guid>
+                <pubDate>Mon, 9 Oct 2017 10:50:00 +0200</pubDate>
+               <description>&lt;p&gt;At my nearby maker space,
+&lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Sonen&lt;/a&gt;, I heard the story that it
+was easier to generate gcode files for theyr 3D printers (Ultimake 2+)
+on Windows and MacOS X than Linux, because the software involved had
+to be manually compiled and set up on Linux while premade packages
+worked out of the box on Windows and MacOS X.  I found this annoying,
+as the software involved,
+&lt;a href=&quot;https://github.com/Ultimaker/Cura&quot;&gt;Cura&lt;/a&gt;, is free software
+and should be trivial to get up and running on Linux if someone took
+the time to package it for the relevant distributions.  I even found
+&lt;a href=&quot;https://bugs.debian.org/706656&quot;&gt;a request for adding into
+Debian&lt;/a&gt; from 2013, which had seem some activity over the years but
+never resulted in the software showing up in Debian.  So a few days
+ago I offered my help to try to improve the situation.&lt;/p&gt;
+
+&lt;p&gt;Now I am very happy to see that all the packages required by a
+working Cura in Debian are uploaded into Debian and waiting in the NEW
+queue for the ftpmasters to have a look.  You can track the progress
+on
+&lt;a href=&quot;https://qa.debian.org/developer.php?email=3dprinter-general%40lists.alioth.debian.org&quot;&gt;the
+status page for the 3D printer team&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;The uploaded packages are a bit behind upstream, and was uploaded
+now to get slots in &lt;a href=&quot;https://ftp-master.debian.org/new.html&quot;&gt;the NEW
+queue&lt;/a&gt; while we work up updating the packages to the latest
+upstream version.&lt;/p&gt;
+
+&lt;p&gt;On a related note, two competitors for Cura, which I found harder
+to use and was unable to configure correctly for Ultimaker 2+ in the
+short time I spent on it, are already in Debian.  If you are looking
+for 3D printer &quot;slicers&quot; and want something already available in
+Debian, check out
+&lt;a href=&quot;https://tracker.debian.org/pkg/slic3r&quot;&gt;slic3r&lt;/a&gt; and
+&lt;a href=&quot;https://tracker.debian.org/pkg/slic3r-prusa&quot;&gt;slic3r-prusa&lt;/a&gt;.
+The latter is a fork of the former.&lt;/p&gt;

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

-               <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;
+               <title>Mangler du en skrue, eller har du en skrue løs?</title>
+               <link>http://people.skolelinux.org/pere/blog/Mangler_du_en_skrue__eller_har_du_en_skrue_l_s_.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Mangler_du_en_skrue__eller_har_du_en_skrue_l_s_.html</guid>
+                <pubDate>Wed, 4 Oct 2017 09:40:00 +0200</pubDate>
+               <description>Når jeg holder på med ulike prosjekter, så trenger jeg stadig ulike
+skruer.  Det siste prosjektet jeg holder på med er å lage
+&lt;a href=&quot;https://www.thingiverse.com/thing:676916&quot;&gt;en boks til en
+HDMI-touch-skjerm&lt;/a&gt; som skal brukes med Raspberry Pi.  Boksen settes
+sammen med skruer og bolter, og jeg har vært i tvil om hvor jeg kan
+få tak i de riktige skruene.  Clas Ohlson og Jernia i nærheten har
+sjelden hatt det jeg trenger.  Men her om dagen fikk jeg et fantastisk
+tips for oss som bor i Oslo.
+&lt;a href=&quot;http://www.zachskruer.no/&quot;&gt;Zachariassen Jernvare AS&lt;/a&gt; i
+&lt;a href=&quot;http://www.openstreetmap.org/?mlat=59.93421&amp;mlon=10.76795#map=19/59.93421/10.76795&quot;&gt;Hegermannsgate
+23A på Torshov&lt;/a&gt; har et fantastisk utvalg, og åpent mellom 09:00 og
+17:00.  De selger skruer, muttere, bolter, skiver etc i løs vekt, og
+så langt har jeg fått alt jeg har lett etter.  De har i tillegg det
+meste av annen jernvare, som verktøy, lamper, ledninger, etc.  Jeg
+håper de har nok kunder til å holde det gående lenge, da dette er en
+butikk jeg kommer til å besøke ofte.  Butikken er et funn å ha i
+nabolaget for oss som liker å bygge litt selv. :)&lt;/p&gt;

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

-               <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;
+               <title>Visualizing GSM radio chatter using gr-gsm and Hopglass</title>
+               <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</guid>
+                <pubDate>Fri, 29 Sep 2017 10:30:00 +0200</pubDate>
+               <description>&lt;p&gt;Every mobile phone announce its existence over radio to the nearby
+mobile cell towers.  And this radio chatter is available for anyone
+with a radio receiver capable of receiving them.  Details about the
+mobile phones with very good accuracy is of course collected by the
+phone companies, but this is not the topic of this blog post.  The
+mobile phone radio chatter make it possible to figure out when a cell
+phone is nearby, as it include the SIM card ID (IMSI).  By paying
+attention over time, one can see when a phone arrive and when it leave
+an area.  I believe it would be nice to make this information more
+available to the general public, to make more people aware of how
+their phones are announcing their whereabouts to anyone that care to
+listen.&lt;/p&gt;
+
+&lt;p&gt;I am very happy to report that we managed to get something
+visualizing this information up and running for
+&lt;a href=&quot;http://norwaymakers.org/osf17&quot;&gt;Oslo Skaperfestival 2017&lt;/a&gt;
+(Oslo Makers Festival) taking place today and tomorrow at Deichmanske
+library.  The solution is based on the
+&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html&quot;&gt;simple
+recipe for listening to GSM chatter&lt;/a&gt; I posted a few days ago, and
+will show up at the stand of &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Åpen
+Sone from the Computer Science department of the University of
+Oslo&lt;/a&gt;.  The presentation will show the nearby mobile phones (aka
+IMSIs) as dots in a web browser graph, with lines to the dot
+representing mobile base station it is talking to. It was working in
+the lab yesterday, and was moved into place this morning.&lt;/p&gt;
+
+&lt;p&gt;We set up a fairly powerful desktop machine using Debian
+Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
+connected and visualize the visible cell phone towers using an
+&lt;a href=&quot;https://github.com/marlow925/hopglass&quot;&gt;English version of
+Hopglass&lt;/a&gt;.  A fairly powerfull machine is needed as the
+grgsm_livemon_headless processes from
+&lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt; converting
+the radio signal to data packages is quite CPU intensive.&lt;/p&gt;
+                                       
+&lt;p&gt;The frequencies to listen to, are identified using a slightly
+patched scan-and-livemon (to set the --args values for each receiver),
+and the Hopglass data is generated using the
+&lt;a href=&quot;https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output&quot;&gt;patches
+in my meshviewer-output branch&lt;/a&gt;.  For some reason we could not get
+more than four SDRs working.  There is also a geographical map trying
+to show the location of the base stations, but I believe their
+coordinates are hardcoded to some random location in Germany, I
+believe.  The code should be replaced with code to look up location in
+a text file, a sqlite database or one of the online databases
+mentioned in
+&lt;a href=&quot;https://github.com/Oros42/IMSI-catcher/issues/14&quot;&gt;the github
+issue for the topic&lt;/a&gt;.
+
+&lt;p&gt;If this sound interesting, visit the stand at the festival!&lt;/p&gt;

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

-               <title>Detecting NFS hangs on Linux without hanging yourself...</title>
-               <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</guid>
-                <pubDate>Thu, 9 Mar 2017 15:20:00 +0100</pubDate>
-               <description>&lt;p&gt;Over the years, administrating thousand of NFS mounting linux
-computers at the time, I often needed a way to detect if the machine
-was experiencing NFS hang.  If you try to use &lt;tt&gt;df&lt;/tt&gt; or look at a
-file or directory affected by the hang, the process (and possibly the
-shell) will hang too.  So you want to be able to detect this without
-risking the detection process getting stuck too.  It has not been
-obvious how to do this.  When the hang has lasted a while, it is
-possible to find messages like these in dmesg:&lt;/p&gt;
-
-&lt;p&gt;&lt;blockquote&gt;
-nfs: server nfsserver not responding, still trying
-&lt;br&gt;nfs: server nfsserver OK
-&lt;/blockquote&gt;&lt;/p&gt;
-  
-&lt;p&gt;It is hard to know if the hang is still going on, and it is hard to
-be sure looking in dmesg is going to work.  If there are lots of other
-messages in dmesg the lines might have rotated out of site before they
-are noticed.&lt;/p&gt;
-
-&lt;p&gt;While reading through the nfs client implementation in linux kernel
-code, I came across some statistics that seem to give a way to detect
-it.  The om_timeouts sunrpc value in the kernel will increase every
-time the above log entry is inserted into dmesg.  And after digging a
-bit further, I discovered that this value show up in
-/proc/self/mountstats on Linux.&lt;/p&gt;
-
-&lt;p&gt;The mountstats content seem to be shared between files using the
-same file system context, so it is enough to check one of the
-mountstats files to get the state of the mount point for the machine.
-I assume this will not show lazy umounted NFS points, nor NFS mount
-points in a different process context (ie with a different filesystem
-view), but that does not worry me.&lt;/p&gt;
-
-&lt;p&gt;The content for a NFS mount point look similar to this:&lt;/p&gt;
-
-&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
-[...]
-device /dev/mapper/Debian-var mounted on /var with fstype ext3
-device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
-        opts:   rw,vers=3,rsize=65536,wsize=65536,namlen=255,acregmin=3,acregmax=60,acdirmin=30,acdirmax=60,soft,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=129.240.3.145,mountvers=3,mountport=4048,mountproto=udp,local_lock=all
-        age:    7863311
-        caps:   caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
-        sec:    flavor=1,pseudoflavor=1
-        events: 61063112 732346265 1028140 35486205 16220064 8162542 761447191 71714012 37189 3891185 45561809 110486139 4850138 420353 15449177 296502 52736725 13523379 0 52182 9016896 1231 0 0 0 0 0 
-        bytes:  166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809 
-        RPC iostats version: 1.0  p/v: 100003/3 (nfs)
-        xprt:   tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
-        per-op statistics
-                NULL: 0 0 0 0 0 0 0 0
-             GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
-             SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
-              LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
-              ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
-            READLINK: 125 125 0 20472 18620 0 1112 1118
-                READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
-               WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
-              CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
-               MKDIR: 3680 3680 0 773980 993920 26 23990 24245
-             SYMLINK: 903 903 0 233428 245488 6 5865 5917
-               MKNOD: 80 80 0 20148 21760 0 299 304
-              REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
-               RMDIR: 3367 3367 0 645112 484848 22 5782 6002
-              RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
-                LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
-             READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
-         READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
-              FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
-              FSINFO: 2 2 0 232 328 0 1 1
-            PATHCONF: 1 1 0 116 140 0 0 0
-              COMMIT: 0 0 0 0 0 0 0 0
-
-device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
-[...]
-&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
-
-&lt;p&gt;The key number to look at is the third number in the per-op list.
-It is the number of NFS timeouts experiences per file system
-operation.  Here 22 write timeouts and 5 access timeouts.  If these
-numbers are increasing, I believe the machine is experiencing NFS
-hang.  Unfortunately the timeout value do not start to increase right
-away.  The NFS operations need to time out first, and this can take a
-while.  The exact timeout value depend on the setup.  For example the
-defaults for TCP and UDP mount points are quite different, and the
-timeout value is affected by the soft, hard, timeo and retrans NFS
-mount options.&lt;/p&gt;
-
-&lt;p&gt;The only way I have been able to get working on Debian and RedHat
-Enterprise Linux for getting the timeout count is to peek in /proc/.
-But according to
-&lt;ahref=&quot;http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html&quot;&gt;Solaris
-10 System Administration Guide: Network Services&lt;/a&gt;, the &#39;nfsstat -c&#39;
-command can be used to get these timeout values.  But this do not work
-on Linux, as far as I can tell.  I
-&lt;ahref=&quot;http://bugs.debian.org/857043&quot;&gt;asked Debian about this&lt;/a&gt;,
-but have not seen any replies yet.&lt;/p&gt;
-
-&lt;p&gt;Is there a better way to figure out if a Linux NFS client is
-experiencing NFS hangs?  Is there a way to detect which processes are
-affected?  Is there a way to get the NFS mount going quickly once the
-network problem causing the NFS hang has been cleared?  I would very
-much welcome some clues, as we regularly run into NFS hangs.&lt;/p&gt;
+               <title>Easier recipe to observe the cell phones around you</title>
+               <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</guid>
+                <pubDate>Sun, 24 Sep 2017 08:30:00 +0200</pubDate>
+               <description>&lt;p&gt;A little more than a month ago I wrote
+&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html&quot;&gt;how
+to observe the SIM card ID (aka IMSI number) of mobile phones talking
+to nearby mobile phone base stations using Debian GNU/Linux and a
+cheap USB software defined radio&lt;/a&gt;, and thus being able to pinpoint
+the location of people and equipment (like cars and trains) with an
+accuracy of a few kilometer.  Since then we have worked to make the
+procedure even simpler, and it is now possible to do this without any
+manual frequency tuning and without building your own packages.&lt;/p&gt;
+
+&lt;p&gt;The &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt;
+package is now included in Debian testing and unstable, and the
+IMSI-catcher code no longer require root access to fetch and decode
+the GSM data collected using gr-gsm.&lt;/p&gt;
+
+&lt;p&gt;Here is an updated recipe, using packages built by Debian and a git
+clone of two python scripts:&lt;/p&gt;
+
+&lt;ol&gt;
+
+&lt;li&gt;Start with a Debian machine running the Buster version (aka
+  testing).&lt;/li&gt;
+
+&lt;li&gt;Run &#39;&lt;tt&gt;apt install gr-gsm python-numpy python-scipy
+  python-scapy&lt;/tt&gt;&#39; as root to install required packages.&lt;/li&gt;
+
+&lt;li&gt;Fetch the code decoding GSM packages using &#39;&lt;tt&gt;git clone
+  github.com/Oros42/IMSI-catcher.git&lt;/tt&gt;&#39;.&lt;/li&gt;
+
+&lt;li&gt;Insert USB software defined radio supported by GNU Radio.&lt;/li&gt;
+
+&lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
+  scan-and-livemon&lt;/tt&gt;&#39; to locate the frequency of nearby base
+  stations and start listening for GSM packages on one of them.&lt;/li&gt;
+
+&lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
+  simple_IMSI-catcher.py&lt;/tt&gt;&#39; to display the collected information.&lt;/li&gt;
+
+&lt;/ol&gt;
+
+&lt;p&gt;Note, due to a bug somewhere the scan-and-livemon program (actually
+&lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/issues/336&quot;&gt;its underlying
+program grgsm_scanner&lt;/a&gt;) do not work with the HackRF radio.  It does
+work with RTL 8232 and other similar USB radio receivers you can get
+very cheaply
+(&lt;a href=&quot;https://www.ebay.com/sch/items/?_nkw=rtl+2832&quot;&gt;for example
+from ebay&lt;/a&gt;), so for now the solution is to scan using the RTL radio
+and only use HackRF for fetching GSM data.&lt;/p&gt;
+
+&lt;p&gt;As far as I can tell, a cell phone only show up on one of the
+frequencies at the time, so if you are going to track and count every
+cell phone around you, you need to listen to all the frequencies used.
+To listen to several frequencies, use the --numrecv argument to
+scan-and-livemon to use several receivers.  Further, I am not sure if
+phones using 3G or 4G will show as talking GSM to base stations, so
+this approach might not see all phones around you.  I typically see
+0-400 IMSI numbers an hour when looking around where I live.&lt;/p&gt;
+
+&lt;p&gt;I&#39;ve tried to run the scanner on a
+&lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi 2 and 3
+running Debian Buster&lt;/a&gt;, but the grgsm_livemon_headless process seem
+to be too CPU intensive to keep up.  When GNU Radio print &#39;O&#39; to
+stdout, I am told there it is caused by a buffer overflow between the
+radio and GNU Radio, caused by the program being unable to read the
+GSM data fast enough.  If you see a stream of &#39;O&#39;s from the terminal
+where you started scan-and-livemon, you need a give the process more
+CPU power.  Perhaps someone are able to optimize the code to a point
+where it become possible to set up RPi3 based GSM sniffers?  I tried
+using Raspbian instead of Debian, but there seem to be something wrong
+with GNU Radio on raspbian, causing glibc to abort().&lt;/p&gt;

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

-               <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;
+               <title>Datalagringsdirektivet kaster skygger over Høyre og Arbeiderpartiet</title>
+               <link>http://people.skolelinux.org/pere/blog/Datalagringsdirektivet_kaster_skygger_over_H_yre_og_Arbeiderpartiet.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Datalagringsdirektivet_kaster_skygger_over_H_yre_og_Arbeiderpartiet.html</guid>
+                <pubDate>Thu, 7 Sep 2017 21:35:00 +0200</pubDate>
+               <description>&lt;p&gt;For noen dager siden publiserte Jon Wessel-Aas en bloggpost om
+«&lt;a href=&quot;http://www.uhuru.biz/?p=1821&quot;&gt;Konklusjonen om datalagring som
+EU-kommisjonen ikke ville at vi skulle få se&lt;/a&gt;».  Det er en
+interessant gjennomgang av EU-domstolens syn på snurpenotovervåkning
+av befolkningen, som er klar på at det er i strid med
+EU-lovgivingen.&lt;/p&gt;
+
+&lt;p&gt;Valgkampen går for fullt i Norge, og om noen få dager er siste
+frist for å avgi stemme.  En ting er sikkert, Høyre og Arbeiderpartiet
+får ikke min stemme
+&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Datalagringsdirektivet_gj_r_at_Oslo_H_yre_og_Arbeiderparti_ikke_f_r_min_stemme_i__r.html&quot;&gt;denne
+gangen heller&lt;/a&gt;.  Jeg har ikke glemt at de tvang igjennom loven som
+skulle pålegge alle data- og teletjenesteleverandører å overvåke alle
+sine kunder.  En lov som er vedtatt, og aldri opphevet igjen.&lt;/p&gt;
+
+&lt;p&gt;Det er tydelig fra diskusjonen rundt grenseløs digital overvåkning
+(eller &quot;Digital Grenseforsvar&quot; som det kalles i Orvellisk nytale) at
+hverken Høyre og Arbeiderpartiet har noen prinsipielle sperrer mot å
+overvåke hele befolkningen, og diskusjonen så langt tyder på at flere
+av de andre partiene heller ikke har det. Mange av
+&lt;a href=&quot;https://data.holderdeord.no/votes/1301946411e&quot;&gt;de som stemte
+for Datalagringsdirektivet i Stortinget&lt;/a&gt; (64 fra Arbeiderpartiet,
+25 fra Høyre) er fortsatt aktive og argumenterer fortsatt for å radere
+vekk mer av innbyggernes privatsfære.&lt;/p&gt;
+
+&lt;p&gt;Når myndighetene demonstrerer sin mistillit til folket, tror jeg
+folket selv bør legge litt innsats i å verne sitt privatliv, ved å ta
+i bruk ende-til-ende-kryptert kommunikasjon med sine kjente og kjære,
+og begrense hvor mye privat informasjon som deles med uvedkommende.
+Det er jo ingenting som tyder på at myndighetene kommer til å være vår
+privatsfære.
+&lt;a href=&quot;http://people.skolelinux.org/pere/blog/How_to_talk_with_your_loved_ones_in_private.html&quot;&gt;Det
+er mange muligheter&lt;/a&gt;.  Selv har jeg litt sans for
+&lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;, som er basert på p2p-teknologi
+uten sentral kontroll, er fri programvare, og støtter meldinger, tale
+og video.  Systemet er tilgjengelig ut av boksen fra
+&lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; og
+&lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, og det
+finnes pakker for Android, MacOSX og Windows.  Foreløpig er det få
+brukere med Ring, slik at jeg også bruker
+&lt;a href=&quot;https://signal.org/&quot;&gt;Signal&lt;/a&gt; som nettleserutvidelse.&lt;/p&gt;

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

-               <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;
+               <title>Simpler recipe on how to make a simple $7 IMSI Catcher using Debian</title>
+               <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</guid>
+                <pubDate>Wed, 9 Aug 2017 23:59:00 +0200</pubDate>
+               <description>&lt;p&gt;On friday, I came across an interesting article in the Norwegian
+web based ICT news magazine digi.no on
+&lt;a href=&quot;https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-60-kroner-na-kan-mobiler-kartlegges-av-alle/398588&quot;&gt;how
+to collect the IMSI numbers of nearby cell phones&lt;/a&gt; using the cheap
+DVB-T software defined radios.  The article refered to instructions
+and &lt;a href=&quot;https://www.youtube.com/watch?v=UjwgNd_as30&quot;&gt;a recipe by
+Keld Norman on Youtube on how to make a simple $7 IMSI Catcher&lt;/a&gt;, and I decided to test them out.&lt;/p&gt;
+
+&lt;p&gt;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-&gt;pip-&gt;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.&lt;/p&gt;
+
+&lt;p&gt;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&#39;ve been testing the
+collector for a few days now.&lt;/p&gt;
+
+&lt;p&gt;The updated and simpler recipe is thus to&lt;/p&gt;
+
+&lt;ol&gt;
+
+&lt;li&gt;start with a Debian machine running Stretch or newer,&lt;/li&gt;
+
+&lt;li&gt;build and install the gr-gsm package available from
+&lt;a href=&quot;http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/&quot;&gt;http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/&lt;/a&gt;,&lt;/li&gt;
+
+&lt;li&gt;clone the git repostory from &lt;a href=&quot;https://github.com/Oros42/IMSI-catcher&quot;&gt;https://github.com/Oros42/IMSI-catcher&lt;/a&gt;,&lt;/li&gt;
+
+&lt;li&gt;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).&lt;/li&gt;
+
+&lt;li&gt;go into the IMSI-catcher directory and run &#39;sudo python simple_IMSI-catcher.py&#39; to extract the IMSI numbers.&lt;/li&gt;
+
+&lt;/ol&gt;
+
+&lt;p&gt;To make it even easier in the future to get this sniffer up and
+running, I decided to package
+&lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/&quot;&gt;the gr-gsm project&lt;/a&gt;
+for Debian (&lt;a href=&quot;https://bugs.debian.org/871055&quot;&gt;WNPP
+#871055&lt;/a&gt;), 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.&lt;/p&gt;
+
+&lt;p&gt;I doubt this &quot;IMSI cacher&quot; is anywhere near as powerfull as
+commercial tools like
+&lt;a href=&quot;https://www.thespyphone.com/portable-imsi-imei-catcher/&quot;&gt;The
+Spy Phone Portable IMSI / IMEI Catcher&lt;/a&gt; or the
+&lt;a href=&quot;https://en.wikipedia.org/wiki/Stingray_phone_tracker&quot;&gt;Harris
+Stingray&lt;/a&gt;, 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...&lt;/p&gt;
+
+&lt;p&gt;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?&lt;/p&gt;

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

-               <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;
+               <title>Norwegian Bokmål edition of Debian Administrator&#39;s Handbook is now available</title>
+               <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</guid>
+                <pubDate>Tue, 25 Jul 2017 21:10:00 +0200</pubDate>
+               <description>&lt;p align=&quot;center&quot;&gt;&lt;img align=&quot;center&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2017-07-25-debian-handbook-nb-testprint.png&quot;/&gt;&lt;/p&gt;
+
+&lt;p&gt;I finally received a copy of the Norwegian Bokmål edition of
+&quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
+Handbook&lt;/a&gt;&quot;.  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
+&lt;a href=&quot;https://debian-handbook.info/get/#norwegian&quot;&gt;is available
+from lulu.com&lt;/a&gt;.  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
+&lt;a href=&quot;https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;read online
+as a web page&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;This is the second book I publish (the first was the book
+&quot;&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt;&quot; by Lawrence Lessig
+in
+&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html&quot;&gt;English&lt;/a&gt;,
+&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html&quot;&gt;French&lt;/a&gt;
+and
+&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html&quot;&gt;Norwegian
+Bokmål&lt;/a&gt;), and I am very excited to finally wrap up this
+project.  I hope
+&quot;&lt;a href=&quot;http://www.lulu.com/shop/rapha%C3%ABl-hertzog-and-roland-mas/h%C3%A5ndbok-for-debian-administratoren/paperback/product-23262290.html&quot;&gt;Håndbok
+for Debian-administratoren&lt;/a&gt;&quot; will be well received.&lt;/p&gt;

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

-               <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;
+               <title>«Rapporten ser ikke på informasjonssikkerhet knyttet til personlig integritet»</title>
+               <link>http://people.skolelinux.org/pere/blog/_Rapporten_ser_ikke_p__informasjonssikkerhet_knyttet_til_personlig_integritet_.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/_Rapporten_ser_ikke_p__informasjonssikkerhet_knyttet_til_personlig_integritet_.html</guid>
+                <pubDate>Tue, 27 Jun 2017 17:50:00 +0200</pubDate>
+               <description>&lt;p&gt;Jeg kom over teksten
+«&lt;a href=&quot;https://freedom-to-tinker.com/2017/06/21/killing-car-privacy-by-federal-mandate/&quot;&gt;Killing
+car privacy by federal mandate&lt;/a&gt;» 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.
+
+&lt;p&gt;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
+«&lt;a href=&quot;https://www.sintef.no/publikasjoner/publikasjon/Download/?pubid=SINTEF+A23933&quot;&gt;Informasjonssikkerhet
+i AutoPASS-brikker&lt;/a&gt;» av Trond Foss:&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;
+«Rapporten ser ikke på informasjonssikkerhet knyttet til personlig
+  integritet.»
+&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;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.&lt;/p&gt;

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

-               <title>Ruling ignored our objections to the seizure of popcorn-time.no (#domstolkontroll)</title>
-               <link>http://people.skolelinux.org/pere/blog/Ruling_ignored_our_objections_to_the_seizure_of_popcorn_time_no___domstolkontroll_.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ruling_ignored_our_objections_to_the_seizure_of_popcorn_time_no___domstolkontroll_.html</guid>
-                <pubDate>Mon, 13 Feb 2017 21:30:00 +0100</pubDate>
-               <description>&lt;p&gt;A few days ago, we received the ruling from
-&lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_day_in_court_challenging_seizure_of_popcorn_time_no_for__domstolkontroll.html&quot;&gt;my
-day in court&lt;/a&gt;.  The case in question is a challenge of the seizure
-of the DNS domain popcorn-time.no.  The ruling simply did not mention
-most of our arguments, and seemed to take everything ØKOKRIM said at
-face value, ignoring our demonstration and explanations.  But it is
-hard to tell for sure, as we still have not seen most of the documents
-in the case and thus were unprepared and unable to contradict several
-of the claims made in court by the opposition.  We are considering an
-appeal, but it is partly a question of funding, as it is costing us
-quite a bit to pay for our lawyer.  If you want to help, please
-&lt;a href=&quot;http://www.nuug.no/dns-beslag-donasjon.shtml&quot;&gt;donate to the
-NUUG defense fund&lt;/a&gt;.&lt;/p&gt;
-
-&lt;p&gt;The details of the case, as far as we know it, is available in
-Norwegian from
-&lt;a href=&quot;https://www.nuug.no/news/tags/dns-domenebeslag/&quot;&gt;the NUUG
-blog&lt;/a&gt;.  This also include
-&lt;a href=&quot;https://www.nuug.no/news/Avslag_etter_rettslig_h_ring_om_DNS_beslaget___vurderer_veien_videre.shtml&quot;&gt;the
-ruling itself&lt;/a&gt;.&lt;/p&gt;
+               <title>Updated sales number for my Free Culture paper editions</title>
+               <link>http://people.skolelinux.org/pere/blog/Updated_sales_number_for_my_Free_Culture_paper_editions.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Updated_sales_number_for_my_Free_Culture_paper_editions.html</guid>
+                <pubDate>Mon, 12 Jun 2017 11:40:00 +0200</pubDate>
+               <description>&lt;p&gt;It is pleasing to see that the work we put down in publishing new
+editions of the classic &lt;a href=&quot;http://www.free-culture.cc/&quot;&gt;Free
+Culture book&lt;/a&gt; by the founder of the Creative Commons movement,
+Lawrence Lessig, 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 &lt;a href=&quot;https://creativecommons.org/&quot;&gt;Creative
+Commons Corporation&lt;/a&gt;, 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
+&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;Github&lt;/a&gt;.&lt;/p&gt;
+
+&lt;table border=&quot;0&quot;&gt;
+&lt;tr&gt;&lt;th rowspan=&quot;2&quot; valign=&quot;bottom&quot;&gt;Title / language&lt;/th&gt;&lt;th colspan=&quot;3&quot;&gt;Quantity&lt;/th&gt;&lt;/tr&gt;
+&lt;tr&gt;&lt;th&gt;2016 jan-jun&lt;/th&gt;&lt;th&gt;2016 jul-dec&lt;/th&gt;&lt;th&gt;2017 jan-may&lt;/th&gt;&lt;/tr&gt;
+
+&lt;tr&gt;
+  &lt;td&gt;&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html&quot;&gt;Culture Libre / French&lt;/a&gt;&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;3&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;6&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;15&lt;/td&gt;
+&lt;/tr&gt;
+
+&lt;tr&gt;
+  &lt;td&gt;&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html&quot;&gt;Fri kultur / Norwegian&lt;/a&gt;&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;7&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;1&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;0&lt;/td&gt;
+&lt;/tr&gt;
+
+&lt;tr&gt;
+  &lt;td&gt;&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html&quot;&gt;Free Culture / English&lt;/a&gt;&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;14&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;27&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;16&lt;/td&gt;
+&lt;/tr&gt;
+
+&lt;tr&gt;
+  &lt;td&gt;Total&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;24&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;34&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;31&lt;/td&gt;
+&lt;/tr&gt;
+
+&lt;/table&gt;
+
+&lt;p&gt;A bit sad to see the low sales number on the Norwegian edition, and
+a bit surprising the English edition still selling so well.&lt;/p&gt;
+
+&lt;p&gt;If you would like to translate and publish the book in your native
+language, I would be happy to help make it happen.  Please get in
+touch.&lt;/p&gt;

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

-               <title>A day in court challenging seizure of popcorn-time.no for #domstolkontroll</title>
-               <link>http://people.skolelinux.org/pere/blog/A_day_in_court_challenging_seizure_of_popcorn_time_no_for__domstolkontroll.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_day_in_court_challenging_seizure_of_popcorn_time_no_for__domstolkontroll.html</guid>
-                <pubDate>Fri, 3 Feb 2017 11:10:00 +0100</pubDate>
-               <description>&lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;70%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2017-02-01-popcorn-time-in-court.jpeg&quot;&gt;&lt;/p&gt;
-
-&lt;p&gt;On Wednesday, I spent the entire day in court in Follo Tingrett
-representing &lt;a href=&quot;https://www.nuug.no/&quot;&gt;the member association
-NUUG&lt;/a&gt;, alongside &lt;a href=&quot;https://www.efn.no/&quot;&gt;the member
-association EFN&lt;/a&gt; and &lt;a href=&quot;http://www.imc.no&quot;&gt;the DNS registrar
-IMC&lt;/a&gt;, challenging the seizure of the DNS name popcorn-time.no.  It
-was interesting to sit in a court of law for the first time in my
-life.  Our team can be seen in the picture above: attorney Ola
-Tellesbø, EFN board member Tom Fredrik Blenning, IMC CEO Morten Emil
-Eriksen and NUUG board member Petter Reinholdtsen.&lt;/p&gt;
-
-&lt;p&gt;&lt;a href=&quot;http://www.domstol.no/no/Enkelt-domstol/follo-tingrett/Nar-gar-rettssaken/Beramming/?cid=AAAA1701301512081262234UJFBVEZZZZZEJBAvtale&quot;&gt;The
-case at hand&lt;/a&gt; is that the Norwegian National Authority for
-Investigation and Prosecution of Economic and Environmental Crime (aka
-Økokrim) decided on their own, to seize a DNS domain early last
-year, without following
-&lt;a href=&quot;https://www.norid.no/no/regelverk/navnepolitikk/#link12&quot;&gt;the
-official policy of the Norwegian DNS authority&lt;/a&gt; which require a
-court decision.  The web site in question was a site covering Popcorn
-Time.  And Popcorn Time is the name of a technology with both legal
-and illegal applications.  Popcorn Time is a client combining
-searching a Bittorrent directory available on the Internet with
-downloading/distribute content via Bittorrent and playing the
-downloaded content on screen.  It can be used illegally if it is used
-to distribute content against the will of the right holder, but it can
-also be used legally to play a lot of content, for example the
-millions of movies
-&lt;a href=&quot;https://archive.org/details/movies&quot;&gt;available from the
-Internet Archive&lt;/a&gt; or the collection
-&lt;a href=&quot;http://vodo.net/films/&quot;&gt;available from Vodo&lt;/a&gt;.  We created
-&lt;a href=&quot;magnet:?xt=urn:btih:86c1802af5a667ca56d3918aecb7d3c0f7173084&amp;dn=PresentasjonFolloTingrett.mov&amp;tr=udp%3A%2F%2Fpublic.popcorn-tracker.org%3A6969%2Fannounce&quot;&gt;a
-video demonstrating legally use of Popcorn Time&lt;/a&gt; and played it in
-Court.  It can of course be downloaded using Bittorrent.&lt;/p&gt;
-
-&lt;p&gt;I did not quite know what to expect from a day in court.  The
-government held on to their version of the story and we held on to
-ours, and I hope the judge is able to make sense of it all.  We will
-know in two weeks time.  Unfortunately I do not have high hopes, as
-the Government have the upper hand here with more knowledge about the
-case, better training in handling criminal law and in general higher
-standing in the courts than fairly unknown DNS registrar and member
-associations.  It is expensive to be right also in Norway.  So far the
-case have cost more than NOK 70 000,-.  To help fund the case, NUUG
-and EFN have asked for donations, and managed to collect around NOK 25
-000,- so far.  Given the presentation from the Government, I expect
-the government to appeal if the case go our way.  And if the case do
-not go our way, I hope we have enough funding to appeal.&lt;/p&gt;
-
-&lt;p&gt;From the other side came two people from Økokrim.  On the benches,
-appearing to be part of the group from the government were two people
-from the Simonsen Vogt Wiik lawyer office, and three others I am not
-quite sure who was.  Økokrim had proposed to present two witnesses
-from The Motion Picture Association, but this was rejected because
-they did not speak Norwegian and it was a bit late to bring in a
-translator, but perhaps the two from MPA were present anyway.  All
-seven appeared to know each other.  Good to see the case is take
-seriously.&lt;/p&gt;
-
-&lt;p&gt;If you, like me, believe the courts should be involved before a DNS
-domain is hijacked by the government, or you believe the Popcorn Time
-technology have a lot of useful and legal applications, I suggest you
-too &lt;a href=&quot;http://www.nuug.no/dns-beslag-donasjon.shtml&quot;&gt;donate to
-the NUUG defense fund&lt;/a&gt;.  Both Bitcoin and bank transfer are
-available. If NUUG get more than we need for the legal action (very
-unlikely), the rest will be spend promoting free software, open
-standards and unix-like operating systems in Norway, so no matter what
-happens the money will be put to good use.&lt;/p&gt;
-
-&lt;p&gt;If you want to lean more about the case, I recommend you check out
-&lt;a href=&quot;https://www.nuug.no/news/tags/dns-domenebeslag/&quot;&gt;the blog
-posts from NUUG covering the case&lt;/a&gt;.  They cover the legal arguments
-on both sides.&lt;/p&gt;
+               <title>Release 0.1.1 of free software archive system Nikita announced</title>
+               <link>http://people.skolelinux.org/pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html</guid>
+                <pubDate>Sat, 10 Jun 2017 00:40:00 +0200</pubDate>
+               <description>&lt;p&gt;I am very happy to report that the
+&lt;a href=&quot;https://github.com/hiOA-ABI/nikita-noark5-core&quot;&gt;Nikita Noark 5
+core project&lt;/a&gt; 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):
+
+&lt;ul&gt;
+
+ &lt;li&gt;Continued work on the angularjs GUI, including document upload.&lt;/li&gt;
+ &lt;li&gt;Implemented correspondencepartPerson, correspondencepartUnit and
+   correspondencepartInternal&lt;/li&gt;
+ &lt;li&gt;Applied for coverity coverage and started submitting code on
+   regualr basis.&lt;/li&gt;
+ &lt;li&gt;Started fixing bugs reported by coverity&lt;/li&gt;
+ &lt;li&gt;Corrected and completed HATEOAS links to make sure entire API is
+   available via URLs in _links.&lt;/li&gt;
+ &lt;li&gt;Corrected all relation URLs to use trailing slash.&lt;/li&gt;
+ &lt;li&gt;Add initial support for storing data in ElasticSearch.&lt;/li&gt;
+ &lt;li&gt;Now able to receive and store uploaded files in the archive.&lt;/li&gt;
+ &lt;li&gt;Changed JSON output for object lists to have relations in _links.&lt;/li&gt;
+ &lt;li&gt;Improve JSON output for empty object lists.&lt;/li&gt;
+ &lt;li&gt;Now uses correct MIME type application/vnd.noark5-v4+json.&lt;/li&gt;
+ &lt;li&gt;Added support for docker container images.&lt;/li&gt;
+ &lt;li&gt;Added simple API browser implemented in JavaScript/Angular.&lt;/li&gt;
+ &lt;li&gt;Started on archive client implemented in JavaScript/Angular.&lt;/li&gt;
+ &lt;li&gt;Started on prototype to show the public mail journal.&lt;/li&gt;
+ &lt;li&gt;Improved performance by disabling Sprint FileWatcher.&lt;/li&gt;
+ &lt;li&gt;Added support for &#39;arkivskaper&#39;, &#39;saksmappe&#39; and &#39;journalpost&#39;.&lt;/li&gt;
+ &lt;li&gt;Added support for some metadata codelists.&lt;/li&gt;
+ &lt;li&gt;Added support for Cross-origin resource sharing (CORS).&lt;/li&gt;
+ &lt;li&gt;Changed login method from Basic Auth to JSON Web Token (RFC 7519)
+   style.&lt;/li&gt;
+ &lt;li&gt;Added support for GET-ing ny-* URLs.&lt;/li&gt;
+ &lt;li&gt;Added support for modifying entities using PUT and eTag.&lt;/li&gt;
+ &lt;li&gt;Added support for returning XML output on request.&lt;/li&gt;
+ &lt;li&gt;Removed support for English field and class names, limiting ourself
+   to the official names.&lt;/li&gt;
+ &lt;li&gt;...&lt;/li&gt;
+ 
+&lt;/ul&gt;
+
+&lt;p&gt;If this sound interesting to you, please contact us on IRC (#nikita
+on irc.freenode.net) or email
+(&lt;a href=&quot;https://lists.nuug.no/mailman/listinfo/nikita-noark&quot;&gt;nikita-noark
+mailing list).&lt;/p&gt;

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