<atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
<item>
- <title>New book, "Fri kultur" by @lessig, a Norwegian Bokmål translation of "Free Culture" from 2004</title>
- <link>http://people.skolelinux.org/pere/blog/New_book___Fri_kultur__by__lessig__a_Norwegian_Bokm_l_translation_of__Free_Culture__from_2004.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_book___Fri_kultur__by__lessig__a_Norwegian_Bokm_l_translation_of__Free_Culture__from_2004.html</guid>
- <pubDate>Sat, 31 Oct 2015 09:00:00 +0100</pubDate>
- <description><p>People keep asking me where to get the various forms of the book I
-published last week, the Norwegian Bokmål edition of Lawrence Lessigs
-book Free Culture. It was published on paper via lulu.com, and is
-also available in PDF, ePub and MOBI format. I currently sell the
-paper edition for self cost from lulu.com, but might extend the
-distribution to book stores like Amazon and Barnes & Noble later.
-This will double the price and force me to make a profit from selling
-the book. Anyway, here are links to get the book in different
-formats:</p>
+ <title>Idea for storing trusted timestamps in a Noark 5 archive</title>
+ <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html</guid>
+ <pubDate>Wed, 7 Jun 2017 21:40:00 +0200</pubDate>
+ <description><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><a href="http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22406445.html">Buy
- paper edition from lulu.com</a></li>
-
- <li><a href="https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/archive/freeculture.nb.pdf">Download
- PDF, size 7.9 MiB</a> (gratis/free)</li>
-
- <li><a href="https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/archive/freeculture.nb.epub">Download
- ePub, size 11 MiB</a> (gratis/free)</li>
-
- <li><a href="https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/archive/freeculture.nb.mobi">Download
- MOBI, size 3.8 MiB</a> (gratis/free)</li>
+<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>Note that the MOBI version have problems with the table of content,
-at least with the viewers I have been able to test. And the ePub file
-have several problems according to
-<a href="https://github.com/IDPF/epubcheck">epubcheck</a>, but seem
-to display fine in the viewers I have tested. All the files needed to
-create the book in various forms are available from
-<a href="https://github.com/petterreinholdtsen/free-culture-lessig">the
-github project page</a>.</p>
-
-<p>The project got press coverage from the Norwegian IT news site
-digi.no. Check out the article
-"<a href="http://www.digi.no/juss_og_samfunn/2015/10/29/vil-apne-politikernes-oyne-for-creative-commons">Vil
-åpne politikernes øyne for Creative Commons</a>".</li>
-
-<p>I've <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">blogged
-about the project</a> as it moved along. The blogs document the translation
-progress and insights I had along the way.</p>
+<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>
</description>
</item>
<item>
- <title>Gavebok overlevert Stortinget i dag</title>
- <link>http://people.skolelinux.org/pere/blog/Gavebok_overlevert_Stortinget_i_dag.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gavebok_overlevert_Stortinget_i_dag.html</guid>
- <pubDate>Thu, 29 Oct 2015 11:50:00 +0100</pubDate>
- <description><p>Like før kl. 11 i dag leverte jeg fem esker med gaveinnpakkede
-bøker til Stortinget, for utdeling til alle stortingsrepresentanter.
-Det ble etterfulgt av følgende pressemelding. Stor takk til NUUG for
-lån av epostliste for å sende ut pressemeldingen.</p>
+ <title>Når nynorskoversettelsen svikter til eksamen...</title>
+ <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</guid>
+ <pubDate>Sat, 3 Jun 2017 08:20:00 +0200</pubDate>
+ <description><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><strong>Er opphavsretten for streng, spør ny bok</strong></p>
-
-<p>I dag kommer boken «<a href="http://free-culture.cc/">Fri
-kultur</a>» av Lawrence Lessig ut på norsk. Boken handler om
-utviklingen og utvidelsene opphavsretten har hatt de siste 40 årene.
-Boken er i dag gitt i gave til alle stortingsrepresentantene.
-Oversetter og utgiver Petter Reinholdtsen håper Stortinget vil tenke
-seg om to ganger neste gang det er snakk om utvidelse av
-opphavsretten.</p>
-
-<p>Boken forteller om hvordan store medieaktører ved hjelp av
-opphavsretten bruker teknologi til å begrense kulturen og kontrollere
-kreativiteten. Den er skrevet av stifteren av
-<a href="https://creativecommons.org/">Creative Commons</a>, professor
-Lawrence Lessig, som for tiden er med i kampen om å bli Demokratenes
-<a href="https://lessig2016.us/">presidentkandidat i USA sitt
-presidentvalg i 2016</a>. Lessig ble sist omtalt i norske medier da
-NRK i høst viste dokumentaren «Kampen for et demokratisk internett»
-som også er
-<a href="https://archive.org/details/TheInternetsOwnBoyTheStoryOfAaronSwartz">tilgjengelig
-fra The Internet Archive</a>.</p>
-
-<p>Boken beskriver hvordan opphavsrettens makt i USA har blitt
-betydelig utvidet etter 1974 langs fem kritiske akser: varighet (fra
-32 til 95 år), omfang (fra utgivere til alle), rekkevidde (gjelder nå
-enhver fremvisning via datamaskin), kontroll (avledede verk er
-definert så bredt at i praksis alle nye åndsverk risikerer søksmål fra
-en opphavsrettsinnehaver) og til sist maktkonsentrasjon og integrering
-av mediebransjen. Den dokumenterer også hvordan medieindustrien har
-lyktes med å bruke rettsvesenet til å begrense konkurranse, og i
-praksis har skaffet seg vetorett over teknologiske nyvinninger.
-Nedlasting av fritt, lovlig og i utgangspunktet gratis materiale
-stoppes med tekniske sperrer og lobbyert lovvern av sperrene.</p>
-
-<p>Utvidelsene illustreres i boken med ulike eksempler. For eksempel
-en demonstrasjon av at Walt Disney ville ha blitt ansett som en
-opphavsrettspirat dersom han gjorde i dag det han gjorde på
-1930-tallet. Boken beskriver hvordan vern av åndsverk er bra, men at
-mer vern ikke nødvendigvis er bedre.<?p>
-
-<p>Petter Reinholdtsen, som sammen med flere frivillige har oversatt
-boken på fritiden de siste 3 årene, håper at boken vil gjøre en
-forskjell. «Når en vet hvordan opphavsrettens varighet i Norge, uten
-opposisjon på Stortinget, ble utvidet nok en gang i mai i fjor, og
-hvordan Norges handelspartner USA gjennom de nye handelsavtalene
-Trans-Pacific Partnership og Transatlantic Trade and Investment
-Partnership
-<a href="https://www.eff.org/deeplinks/2015/10/final-leaked-tpp-text-all-we-feared">ønsker
-å utvide opphavsrettens makt også i andre land</a>, håper jeg at flere
-vil spørre: Er det virkelig fornuftig å gjøre de samme utvidelsene i
-Norge?», spør han. «Jeg håper boken kan bidra til kunnskap og
-forståelse, og kan gi Stortinget et bedre grunnlag til å ta riktige
-beslutninger som ivaretar befolkningens og samfunnets interesser i
-Norge.»</p>
-
-<p>Petter Reinholdtsen er en mangeårig fri programvareutvikler som har
-vært med på å lage systemer som operativsystemet Debian, IT-løsningen
-Skolelinux, borgerportalen FiksGataMi og innsynstjenesten Mimes brønn.
-Han forteller han selv har opplevd problemene utvidet varighet,
-omfang, rekkevidde og kontroll i opphavsretten medfører og at boken
-var en oppvekker. «Jeg håper andre finner boken like interessant som
-jeg gjorde. Boken kan
-<a href="https://github.com/petterreinholdtsen/free-culture-lessig">lastes
-gratis ned fra github</a> eller
-<a href="http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22406445.html">kjøpes
-på papir fra lulu.com</a>,» avslutter Reinholdtsen.</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>Så får vi se om det har noen positiv effekt. :)</p>
+<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>
</description>
</item>
<item>
- <title>"Fri kultur" av @lessig - norsk utgave av "Free Culture" tilgjengelig på papir, PDF og ePub</title>
- <link>http://people.skolelinux.org/pere/blog/_Fri_kultur__av__lessig___norsk_utgave_av__Free_Culture__tilgjengelig_p__papir__PDF_og_ePub.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/_Fri_kultur__av__lessig___norsk_utgave_av__Free_Culture__tilgjengelig_p__papir__PDF_og_ePub.html</guid>
- <pubDate>Wed, 28 Oct 2015 09:30:00 +0100</pubDate>
- <description><p><a href="http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22406445.html">Klikk her for å kjøpe boken</a>.</p>
-
-<p>I 2004, mens <a href="https://creativecommons.org/">Creative
-Commons-bevegelsen</a> vokste frem, skrev bevegelsens stifter Lawrence
-Lessig boken
-<a href="https://en.wikipedia.org/wiki/Free_Culture_(book)">Free
-Culture</a> for å forklare problemene med økene åndsverksregulering og
-for å foreslå noen løsninger. Jeg leste boken den gangen, og den både
-inspirerte meg og endret på hvordan jeg så på opphavsrettslovigving.
-Jeg skulle ønske flere folk leste denne boken. Den gir en god
-gjennomgang av hvordan økende åndsverksregulering skader både
-nyskapning og kulturlivet, og skisserer hvordan både lovgivere og oss
-vanlige borgere kan bidra for å få slutt på dette.</p>
-
-<p>Derfor bestemte jeg meg sommeren 2012 for å oversette den til norsk
-bokmål og gjøre den tilgjengelig for de blant mine venner og familie
-som foretrekker å lese bøker på norsk. Jeg oversatte boken ved hjelp
-av docbook og en gettext PO-fil, og endte opp med to utgaver, en på
-norsk og en på engelsk. Den engelske publiserte jeg i forrige uke, og
-den norske utgaven på papir
-<a href="http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22406445.html">er
-nå klar for salg</a>. Jeg fikk heldigvis hjelp med oversetting og
-korrekturlesing av den norske utgaven fra en rekke frivillige. Se
-side 245 for en komplett liste. Slik ser omslaget ut:
-
-<p align="center"><a href="http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22406445.html"><img align="center" src="http://people.skolelinux.org/pere/blog/images/2015-10-28-free-culture-norwegian-published-cover.png"/></a></p>
-
-<p>I tillegg til den norske og engelske utgaven holder vi på med en
-fransk utgave. Den koordineres av dblatex-utvikleren Benoît Guillon,
-og oversettelsen var komplett denne uka men må korrekturleses før den
-kan gis ut. Flere frivillige trengs her, så ta kontakt med Benoît
-hvis du vil bidra.</p>
-
-<p>Boken er også tilgjengelig i PDF, ePub og MOBI-format fra
-<a href="https://github.com/petterreinholdtsen/free-culture-lessig">min
-github-prosjektside</a>. Merk at ePub og MOBI-utgavene har noen
-formatteringsproblemer som jeg tror kommer av feil i docbook-verktøyet
-dbtoepub (Debian BTS-rapporter
-<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795842">#795842</a>
-og
-<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796871">#796871</a>),
-men jeg har ikke tatt meg tid til å undersøke problemene. For de som
-vil ha elektronisk kopi anbefaler jeg å bruke PDF- og ePub-utgaven i
-denne omgang, da de ser ut til å hånderes bra av de fremviserne jeg
-har tilgjengelig.</p>
-
-<p>Etter at oversettelsen til bokmål var ferdig klarte jeg å overtale
-<a href="http://www.nuugfoundation.no/">NUUG Foundation</a> til å
-sponse trykking av boken. Det er årsaken til at stiftelsens logo er
-på baksiden av omslaget. Jeg er svært takknemlig for dette, og bruker
-bidraget til å gi en kopi av den norske utgaven til alle
-Stortingsrepresentanter og andre beslutningstakere her i Norge.</p>
+ <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><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>
</description>
</item>
<item>
- <title>"Free Culture" by @lessig - The background story for Creative Commons - new edition available</title>
- <link>http://people.skolelinux.org/pere/blog/_Free_Culture__by__lessig___The_background_story_for_Creative_Commons___new_edition_available.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/_Free_Culture__by__lessig___The_background_story_for_Creative_Commons___new_edition_available.html</guid>
- <pubDate>Fri, 23 Oct 2015 12:10:00 +0200</pubDate>
- <description><p><a href="http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22402863.html">Click
-here to buy the book</a>.</p>
-
-<p>In 2004, as the <a href="https://creativecommons.org/">Creative Commons
-movement</a> gained momentum, its creator Lawrence Lessig wrote the
-book <a href="https://en.wikipedia.org/wiki/Free_Culture_(book)">Free
-Culture</a> to explain the problems with increasing copyright
-regulation and suggest some solutions. I read the book back then and
-was very moved by it. Reading the book inspired me and changed the
-way I looked on copyright law, and I would love it if more people
-would read it too.</p>
-
-<p>Because of this, I decided in the summer of 2012 to translate it to
-Norwegian Bokmål and publish it for those of my friends and family
-that prefer to read books in Norwegian. I translated the book using
-docbook and a gettext PO file, and a byproduct of this process is a
-new edition of the English original. I've been in touch with the
-author during by work, and he said it was fine with him if I also
-published an English version. So I decided to do so. Today, I made
-this edition
-<a href="http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22402863.html">available
-for sale on Lulu.com</a>, for those interested in a paper book. This
-is the cover:
-
-<p align="center"><a href="http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22402863.html"><img align="center" src="http://people.skolelinux.org/pere/blog/images/2015-10-23-free-culture-english-published-cover.png"/></a></p>
-
-<p>The Norwegian Bokmål version will be available for purchase in a
-few days. I also plan to publish a French version in a few weeks or
-months, depending on the amount of people with knowledge of French to
-join the translation project. So far there is only one active
-person, but the French book is almost completely translated but
-need some proof reading.</p>
-
-<p>The book is also available in PDF, ePub and MOBI formats from
-<a href="https://github.com/petterreinholdtsen/free-culture-lessig">my
-github project page</a>. Note the ePub and MOBI versions have some
-formatting problems I believe is due to bugs in the docbook tool
-dbtoepub (Debian BTS issues
-<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795842">#795842</a>
-and
-<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796871">#796871</a>),
-but I have not taken the time to investigate. I recommend the PDF and
-ePub version for now, as they seem to show up fine in the viewers I
-have available.</p>
-
-<p>After the translation to Norwegian Bokmål was complete, I was able
-to secure some sponsoring from
-<a href="http://www.nuugfoundation.no/">the NUUG Foundation</a> to
-print the book. This is the reason their logo is located on the back
-cover. I am very grateful for their contribution, and will use it to
-give a copy of the Norwegian edition to members of the Norwegian
-Parliament and other decision makers here in Norway.</p>
+ <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><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>
</description>
</item>
<item>
- <title>EU-domstolen konkluderer motsatt av Skatteetaten når det gjelder Bitcoin</title>
- <link>http://people.skolelinux.org/pere/blog/EU_domstolen_konkluderer_motsatt_av_Skatteetaten_n_r_det_gjelder_Bitcoin.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/EU_domstolen_konkluderer_motsatt_av_Skatteetaten_n_r_det_gjelder_Bitcoin.html</guid>
- <pubDate>Thu, 22 Oct 2015 13:20:00 +0200</pubDate>
- <description><p>Bitcoin er i litt vinden i Norge for tiden, med
-<a href="http://www.nrk.no/ytring/en-digital-robin-hood-1.12604681">kronikk
-om bitcoin-overføringer på tvers av landegrensene</A> hos NRK Ytring
-for to dager siden og
-<a href="https://tv.nrk.no/program/KOID25009815/kapital-bitcoin-en-digital-pengebinge">dokumentar
-om bitcoin</a> på NRK 2 i forgårs og i går. I den sammenhengen er det
-spesielt hyggelig med en gladnyhet fra EU om Bitcoin.</p>
-
-<p>I dag konkluderte EU-domstolen at
-<a href="http://curia.europa.eu/juris/document/document.jsf?text=&docid=170305&pageIndex=0&doclang=en&mode=req&dir=&occ=first&part=1&cid=604079">Bitcoin-kjøp
-fra Bitcoin-børser ikke er MVA-pliktig</a> (sak C‑264/14). Fant
-<a href="http://www.reuters.com/article/2015/10/22/us-bitcoin-tax-eu-idUSKCN0SG0X920151022">nyheten
-først hos Reuters</a>, etter tips fra innehaveren av
-<a href="http://www.bitmynt.no/">Bitmynt</a>. EU-domstolens avgjørelse
-er stikk i strid med
-<a href="http://www.skatteetaten.no/no/Radgiver/Rettskilder/Uttalelser/Prinsipputtalelser/Bruk-av-bitcoins--skatte--og-avgiftsmessige-konsekvenser/">annonseringen
-fra Skatteetaten i 2013</a>, der de konkluderte med at bitcoin er et
-«formuesobjekter» som det skulle betales mva på ved kjøp og salg.
-Dermed la Skatteetaten opp til dobbel MVA-betaling hvis en kjøpte noe
-med Bitcoin fra Norge (først mva på kjøp av Bitcoin, deretter mva på
-det en kjøper med Bitcoin). Jeg lurer på om denne avgjørelsen får
-Skatteetaten til å bytte mening. Gleder meg til fortsettelsen.</p>
+ <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><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>
</description>
</item>
<item>
- <title>Lawrence Lessig interviewed Edward Snowden a year ago</title>
- <link>http://people.skolelinux.org/pere/blog/Lawrence_Lessig_interviewed_Edward_Snowden_a_year_ago.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lawrence_Lessig_interviewed_Edward_Snowden_a_year_ago.html</guid>
- <pubDate>Mon, 19 Oct 2015 11:50:00 +0200</pubDate>
- <description><p>Last year, <a href="https://lessig2016.us/">US president candidate
-in the Democratic Party</a> Lawrence interviewed Edward Snowden. The
-one hour interview was
-<a href="https://www.youtube.com/watch?v=o_Sr96TFQQE">published by
-Harvard Law School 2014-10-23 on Youtube</a>, and the meeting took
-place 2014-10-20.</p>
-
-<p>The questions are very good, and there is lots of useful
-information to be learned and very interesting issues to think about
-being raised. Please check it out.</p>
-
-<iframe width="560" height="315" src="https://www.youtube.com/embed/o_Sr96TFQQE" frameborder="0" allowfullscreen></iframe>
-
-<p>I find it especially interesting to hear again that Snowden did try
-to bring up his reservations through the official channels without any
-luck. It is in sharp contrast to the answers made 2013-11-06 by the
-Norwegian prime minister Erna Solberg to the Norwegian Parliament,
-<a href="https://tale.holderdeord.no/speeches/s131106/68">claiming
-Snowden is no Whistle-Blower</a> because he should have taken up his
-concerns internally and using official channels. It make me sad
-that this is the political leadership we have here in Norway.</p>
+ <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><p>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 <tt>df</tt> 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:</p>
+
+<p><blockquote>
+nfs: server nfsserver not responding, still trying
+<br>nfs: server nfsserver OK
+</blockquote></p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>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.</p>
+
+<p>The content for a NFS mount point look similar to this:</p>
+
+<p><blockquote><pre>
+[...]
+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
+[...]
+</pre></blockquote></p>
+
+<p>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.</p>
+
+<p>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
+<ahref="http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html">Solaris
+10 System Administration Guide: Network Services</a>, the 'nfsstat -c'
+command can be used to get these timeout values. But this do not work
+on Linux, as far as I can tell. I
+<ahref="http://bugs.debian.org/857043">asked Debian about this</a>,
+but have not seen any replies yet.</p>
+
+<p>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.</p>
</description>
</item>
<item>
- <title>The Story of Aaron Swartz - Let us all weep!</title>
- <link>http://people.skolelinux.org/pere/blog/The_Story_of_Aaron_Swartz___Let_us_all_weep_.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Story_of_Aaron_Swartz___Let_us_all_weep_.html</guid>
- <pubDate>Thu, 8 Oct 2015 12:10:00 +0200</pubDate>
- <description><p>The movie "<a href="http://www.takepart.com/internets-own-boy">The
-Internet's Own Boy: The Story of Aaron Swartz</a>" is both inspiring
-and depressing at the same time. The work of Aaron Swartz has
-inspired me in my work, and I am grateful of all the improvements he
-was able to initiate or complete. I wish I am able to do as much good
-in my life as he did in his. Every minute of this 1:45 long movie is
-inspiring in documenting how much impact a single person can have on
-improving the society and this world. And it is depressing in
-documenting how the law enforcement of USA (and other countries) is
-corrupted to a point where they can push a bright kid to his death for
-downloading too many scientific articles. Aaron is dead. Let us all
-weep.</p>
-
-<p>The movie is also available on
-<a href="https://www.youtube.com/watch?v=vXr-2hwTk58">Youtube</a>. I
-wish there were Norwegian subtitles available, so I could show it to
-my parents.</p>
+ <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><p>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.</p>
+
+<p>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.</p>
+
+<p>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?</p>
+
+<p>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 'the FBI denies any wiretapping', while the reality is that
+'the FBI denies any illegal wiretapping'. There is a fundamental and
+important difference, and it make me sad that the journalists are
+unable to grasp it.</p>
+
+<p><strong>Update 2017-03-13:</strong> Look like
+<a href="https://theintercept.com/2017/03/13/rand-paul-is-right-nsa-routinely-monitors-americans-communications-without-warrants/">The
+Intercept report that US Senator Rand Paul confirm what I state above</a>.</p>
</description>
</item>
<item>
- <title>Alle Stortingets mobiltelefoner kontrolleres fra USA...</title>
- <link>http://people.skolelinux.org/pere/blog/Alle_Stortingets_mobiltelefoner_kontrolleres_fra_USA___.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Alle_Stortingets_mobiltelefoner_kontrolleres_fra_USA___.html</guid>
- <pubDate>Wed, 7 Oct 2015 09:55:00 +0200</pubDate>
- <description><p>Jeg lot meg fascinere av
-<a href="http://www.aftenposten.no/nyheter/iriks/politikk/Stortinget-har-tilgang-til-a-fjernstyre-600-mobiler-8192692.html">en
-artikkel i Aftenposten</a> der det fortelles at «over 600 telefoner som
-benyttes av stortingsrepresentanter, rådgivere og ansatte på
-Stortinget, kan «fjernstyres» ved hjelp av
-<a href="https://play.google.com/store/apps/details?id=com.airwatch.androidagent">programvaren
-Airwatch</a>, et såkalte MDM-program (Mobile Device Managment)». Det
-hele bagatelliseres av Stortingets IT-stab, men det er i hovedsak på
-grunn av at journalisten ikke stiller de relevante spørsmålene. For
-meg er det relevante spørsmålet hvem som har lovlig tilgang (i henhold
-til lokal lovgiving, dvs. i hvert fall i Norge, Sverige, UK og USA)
-til informasjon om og på telefonene, og hvor enkelt det er å skaffe
-seg tilgang til hvor mobilene befinner seg og informasjon som befinner
-seg på telefonene ved hjelp av utro tjenere, trusler, innbrudd og
-andre ulovlige metoder.</p>
-
-<p>Bruken av AirWatch betyr i realiteten at USAs etteretning og
-politimyndigheter har full tilgang til stortingets mobiltelefoner,
-inkludert posisjon og innhold, takket være
-<a href="https://en.wikipedia.org/wiki/Foreign_Intelligence_Surveillance_Act_of_1978_Amendments_Act_of_2008">FISAAA-loven</a>
-og
-"<a href="https://en.wikipedia.org/wiki/National_security_letter">National
-Security Letters</a>" og det enkle faktum at selskapet
-<a href="http://www.airwatch.com/">AirWatch</a> er kontrollert av et
-selskap i USA. I tillegg er det kjent at flere lands
-etterretningstjenester kan lytte på trafikken når den passerer
-landegrensene.</p>
-
-<p>Jeg har bedt om mer informasjon
-<a href="https://www.mimesbronn.no/request/saksnummer_for_saker_anganede_br">fra
-Stortinget om bruken av AirWatch</a> via Mimes brønn så får vi se hva
-de har å fortelle om saken. Fant ingenting om 'airwatch' i
-postjournalen til Stortinget, så jeg trenger hjelp før jeg kan be om
-innsyn i konkrete dokumenter.</p>
-
-<p>Oppdatering 2015-10-07: Jeg er blitt spurt hvorfor jeg antar at
-AirWatch-agenten rapporterer til USA og ikke direkte til Stortingets
-egen infrastruktur. Det stemmer at det er teknisk mulig å sette
-opp mobiltelefonene til å rapportere til datamaskiner som eies av
-Stortinget. Jeg antar det rapporteres til AirWatch sine sentrale
-tjenester basert på det jeg leste fra beskrivelsen av
-<a href="http://www.airwatch.com/solutions/mobile-device-management/">Mobile
-Device Management</A> på AirWatch sine egne nettsider, koblet med at
-det brukes en standard app som kan hentes fra "app-butikkene" for å få
-tilgang. Enten må app-en settes opp individuelt hos Stortinget, eller
-så får den beskjed fra AirWatch i USA om hvor den skal koble seg opp.
-I det første tilfellet vil den ikke rapportere direkte til USA, men
-til programvare utviklet av AirWatch som kjører på en maskin under
-Stortingets kontroll. Det er litt bedre, men fortsatt vil det være
-umulig for Stortinget å være sikker på hva programvaren som tar imot
-forbindelser gjør. Jeg ser fra beskrivelsen av
-<a href="http://www.airwatch.com/differentiators/enterprise-integration/">Enterprice
-Integration</a> hos AirWatch at det er mulig å ha lokal installasjon,
-og håper innsynsforespørsler mot Stortinget kan fortelle mer om
-hvordan ting konkret fungerer der.</p>
+ <title>Norwegian Bokmål translation of The Debian Administrator'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><p>For almost a year now, we have been working on making a Norwegian
+Bokmål edition of <a href="https://debian-handbook.info/">The Debian
+Administrator's Handbook</a>. 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.</p>
+
+<p><a href="http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf">A
+
+fresh PDF edition</a> 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
+<a href="https://hosted.weblate.org/projects/debian-handbook/">visit
+Weblate and correct the error</a>. The
+<a href="http://l.github.io/debian-handbook/stat/nb-NO/index.html">state
+of the translation including figures</a> is a useful source for those
+provide Norwegian bokmål screen shots and figures.</p>
</description>
</item>
<item>
- <title>French Docbook/PDF/EPUB/MOBI edition of the Free Culture book</title>
- <link>http://people.skolelinux.org/pere/blog/French_Docbook_PDF_EPUB_MOBI_edition_of_the_Free_Culture_book.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/French_Docbook_PDF_EPUB_MOBI_edition_of_the_Free_Culture_book.html</guid>
- <pubDate>Thu, 1 Oct 2015 13:20:00 +0200</pubDate>
- <description><p>As I wrap up the Norwegian version of
-<a href="https://github.com/petterreinholdtsen/free-culture-lessig">Free
-Culture</a> book by Lawrence Lessig (still waiting for my final proof
-reading copy to arrive in the mail), my great
-<a href="http://dblatex.sourceforge.net/">dblatex</a> helper and
-developer of the dblatex docbook processor, Benoît Guillon, decided a
-to try to create a French version of the book. He started with the
-French translation available from the
-<a href="http://www.wikilivres.ca/wiki/Culture_libre">Wikilivres wiki
-pages</a>, and wrote a program to convert it into a PO file, allowing
-the translation to be integrated into the po4a based framework I use
-to create the Norwegian translation from the English edition. We meet
-on the <a href="irc://irc.freenode.net/%23dblatex">#dblatex IRC
-channel</a> to discuss the work. If you want to help create a French
-edition, check out
-<a href="https://github.com/marsgui/free-culture-lessig">his git
-repository</a> and join us on IRC. If the French edition look good,
-we might publish it as a paper book on lulu.com. A French version of
-the drawings and the cover need to be provided for this to happen.</p>
+ <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><p>A few days ago I ordered a small batch of
+<a href="http://altusmetrum.org/ChaosKey/">the ChaosKey</a>, 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:</p>
+
+<blockquote><pre>
+% 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
+%
+</pre></blockquote>
+
+<p>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:</p>
+
+<blockquote><pre>
+% 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
+%
+</pre></blockquote>
+
+<p>Quite the difference. :) I bought a few more than I need, in case
+someone want to buy one here in Norway. :)</p>
+
+<p>Update: The dongle was presented at Debconf last year. You might
+find <a href="https://debconf16.debconf.org/talks/94/">the talk
+recording illuminating</a>. 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.</p>
</description>
</item>
<item>
- <title>The life and death of a laptop battery</title>
- <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
- <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
- <description><p>When I get a new laptop, the battery life time at the start is OK.
-But this do not last. The last few laptops gave me a feeling that
-within a year, the life time is just a fraction of what it used to be,
-and it slowly become painful to use the laptop without power connected
-all the time. Because of this, when I got a new Thinkpad X230 laptop
-about two years ago, I decided to monitor its battery state to have
-more hard facts when the battery started to fail.</p>
-
-<img src="http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png"/>
-
-<p>First I tried to find a sensible Debian package to record the
-battery status, assuming that this must be a problem already handled
-by someone else. I found
-<a href="https://tracker.debian.org/pkg/battery-stats">battery-stats</a>,
-which collects statistics from the battery, but it was completely
-broken. I sent a few suggestions to the maintainer, but decided to
-write my own collector as a shell script while I waited for feedback
-from him. Via
-<a href="http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html">a
-blog post about the battery development on a MacBook Air</a> I also
-discovered
-<a href="https://github.com/jradavenport/batlog.git">batlog</a>, not
-available in Debian.</p>
-
-<p>I started my collector 2013-07-15, and it has been collecting
-battery stats ever since. Now my
-/var/log/hjemmenett-battery-status.log file contain around 115,000
-measurements, from the time the battery was working great until now,
-when it is unable to charge above 7% of original capacity. My
-collector shell script is quite simple and look like this:</p>
-
-<pre>
-#!/bin/sh
-# Inspired by
-# http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
-# See also
-# http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
-logfile=/var/log/hjemmenett-battery-status.log
-
-files="manufacturer model_name technology serial_number \
- energy_full energy_full_design energy_now cycle_count status"
-
-if [ ! -e "$logfile" ] ; then
- (
- printf "timestamp,"
- for f in $files; do
- printf "%s," $f
- done
- echo
- ) > "$logfile"
-fi
-
-log_battery() {
- # Print complete message in one echo call, to avoid race condition
- # when several log processes run in parallel.
- msg=$(printf "%s," $(date +%s); \
- for f in $files; do \
- printf "%s," $(cat $f); \
- done)
- echo "$msg"
-}
-
-cd /sys/class/power_supply
-
-for bat in BAT*; do
- (cd $bat && log_battery >> "$logfile")
-done
-</pre>
-
-<p>The script is called when the power management system detect a
-change in the power status (power plug in or out), and when going into
-and out of hibernation and suspend. In addition, it collect a value
-every 10 minutes. This make it possible for me know when the battery
-is discharging, charging and how the maximum charge change over time.
-The code for the Debian package
-<a href="https://github.com/petterreinholdtsen/battery-status">is now
-available on github</a>.</p>
-
-<p>The collected log file look like this:</p>
-
-<pre>
-timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
-1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
-[...]
-1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
-1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
-</pre>
-
-<p>I wrote a small script to create a graph of the charge development
-over time. This graph depicted above show the slow death of my laptop
-battery.</p>
-
-<p>But why is this happening? Why are my laptop batteries always
-dying in a year or two, while the batteries of space probes and
-satellites keep working year after year. If we are to believe
-<a href="http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries">Battery
-University</a>, the cause is me charging the battery whenever I have a
-chance, and the fix is to not charge the Lithium-ion batteries to 100%
-all the time, but to stay below 90% of full charge most of the time.
-I've been told that the Tesla electric cars
-<a href="http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit">limit
-the charge of their batteries to 80%</a>, with the option to charge to
-100% when preparing for a longer trip (not that I would want a car
-like Tesla where rights to privacy is abandoned, but that is another
-story), which I guess is the option we should have for laptops on
-Linux too.</p>
-
-<p>Is there a good and generic way with Linux to tell the battery to
-stop charging at 80%, unless requested to charge to 100% once in
-preparation for a longer trip? I found
-<a href="http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity">one
-recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
-80%</a>, but could not get it to work (kernel module refused to
-load).</p>
-
-<p>I wonder why the battery capacity was reported to be more than 100%
-at the start. I also wonder why the "full capacity" increases some
-times, and if it is possible to repeat the process to get the battery
-back to design capacity. And I wonder if the discharge and charge
-speed change over time, or if this stay the same. I did not yet try
-to write a tool to calculate the derivative values of the battery
-level, but suspect some interesting insights might be learned from
-those.</p>
-
-<p>Update 2015-09-24: I got a tip to install the packages
-acpi-call-dkms and tlp (unfortunately missing in Debian stable)
-packages instead of the tp-smapi-dkms package I had tried to use
-initially, and use 'tlp setcharge 40 80' to change when charging start
-and stop. I've done so now, but expect my existing battery is toast
-and need to be replaced. The proposal is unfortunately Thinkpad
-specific.</p>
+ <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><p>I just noticed
+<a href="http://www.arkivrad.no/aktuelt/riksarkivarens-forskrift-pa-horing">the
+new Norwegian proposal for archiving rules in the goverment</a> list
+<a href="http://www.ecma-international.org/publications/standards/Ecma-376.htm">ECMA-376</a>
+/ 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 "valid" OOXML document to
+have content with no defined interpretation in the standard, which
+lead to a question and an idea.</p>
+
+<p>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'm aware of the
+<a href="https://github.com/arlm/officeotron/">officeotron OOXML
+validator</a>, 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.</p>
</description>
</item>