blog/index.rss

   1 <?xml version="1.0" encoding="utf-8"?>
   2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/' xmlns:atom="http://www.w3.org/2005/Atom">
   3         <channel>
   4                 <title>Petter Reinholdtsen</title>
   5                 <description></description>
   6                 <link>http://people.skolelinux.org/pere/blog/</link>
   7                 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
   8
   9         <item>
  10                 <title>Updated sales number for my Free Culture paper editions</title>
  11                 <link>http://people.skolelinux.org/pere/blog/Updated_sales_number_for_my_Free_Culture_paper_editions.html</link>
  12                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Updated_sales_number_for_my_Free_Culture_paper_editions.html</guid>
  13                 <pubDate>Mon, 12 Jun 2017 11:40:00 +0200</pubDate>
  14                 <description>&lt;p&gt;It is pleasing to see that the work we put down in publishing new
  15 editions of the classic &lt;a href=&quot;http://www.free-culture.cc/&quot;&gt;Free
  16 Culture book&lt;/a&gt; by the founder of the Creative Commons movement,
  17 Lawrence Lessig, is still being appreciated.  I had a look at the
  18 latest sales numbers for the paper edition today.  Not too impressive,
  19 but some buyers still exist.  All the revenue from the books are sent
  20 to the &lt;a href=&quot;https://creativecommons.org/&quot;&gt;Creative Commons
  21 Corporation&lt;/a&gt;, and they receive the largest cut if you buy directly
  22 from Lulu.  Most books are sold via Amazon, with Ingram second and
  23 only a small fraction directly from Lulu.  The ebook edition is
  24 available for free from
  25 &lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;Github&lt;/a&gt;.&lt;/p&gt;
  26
  27 &lt;table border=&quot;0&quot;&gt;
  28 &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;
  29 &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;
  30
  31 &lt;tr&gt;
  32   &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;
  33   &lt;td align=&quot;right&quot;&gt;3&lt;/td&gt;
  34   &lt;td align=&quot;right&quot;&gt;6&lt;/td&gt;
  35   &lt;td align=&quot;right&quot;&gt;15&lt;/td&gt;
  36 &lt;/tr&gt;
  37
  38 &lt;tr&gt;
  39   &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;
  40   &lt;td align=&quot;right&quot;&gt;7&lt;/td&gt;
  41   &lt;td align=&quot;right&quot;&gt;1&lt;/td&gt;
  42   &lt;td align=&quot;right&quot;&gt;0&lt;/td&gt;
  43 &lt;/tr&gt;
  44
  45 &lt;tr&gt;
  46   &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;
  47   &lt;td align=&quot;right&quot;&gt;14&lt;/td&gt;
  48   &lt;td align=&quot;right&quot;&gt;27&lt;/td&gt;
  49   &lt;td align=&quot;right&quot;&gt;16&lt;/td&gt;
  50 &lt;/tr&gt;
  51
  52 &lt;tr&gt;
  53   &lt;td&gt;Total&lt;/td&gt;
  54   &lt;td align=&quot;right&quot;&gt;24&lt;/td&gt;
  55   &lt;td align=&quot;right&quot;&gt;34&lt;/td&gt;
  56   &lt;td align=&quot;right&quot;&gt;31&lt;/td&gt;
  57 &lt;/tr&gt;
  58
  59 &lt;/table&gt;
  60
  61 &lt;p&gt;A bit sad to see the low sales number on the Norwegian edition, and
  62 a bit surprising the English edition still selling so well.&lt;/p&gt;
  63
  64 &lt;p&gt;If you would like to translate and publish the book in your native
  65 language, I would be happy to help make it happen.  Please get in
  66 touch.&lt;/p&gt;
  67 </description>
  68         </item>
  69
  70         <item>
  71                 <title>Release 0.1.1 of free software archive system Nikita announced</title>
  72                 <link>http://people.skolelinux.org/pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html</link>
  73                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html</guid>
  74                 <pubDate>Sat, 10 Jun 2017 00:40:00 +0200</pubDate>
  75                 <description>&lt;p&gt;I am very happy to report that the
  76 &lt;a href=&quot;https://github.com/hiOA-ABI/nikita-noark5-core&quot;&gt;Nikita Noark 5
  77 core project&lt;/a&gt; tagged its second release today.  The free software
  78 solution is an implementation of the Norwegian archive standard Noark
  79 5 used by government offices in Norway.  These were the changes in
  80 version 0.1.1 since version 0.1.0 (from NEWS.md):
  81
  82 &lt;ul&gt;
  83
  84  &lt;li&gt;Continued work on the angularjs GUI, including document upload.&lt;/li&gt;
  85  &lt;li&gt;Implemented correspondencepartPerson, correspondencepartUnit and
  86    correspondencepartInternal&lt;/li&gt;
  87  &lt;li&gt;Applied for coverity coverage and started submitting code on
  88    regualr basis.&lt;/li&gt;
  89  &lt;li&gt;Started fixing bugs reported by coverity&lt;/li&gt;
  90  &lt;li&gt;Corrected and completed HATEOAS links to make sure entire API is
  91    available via URLs in _links.&lt;/li&gt;
  92  &lt;li&gt;Corrected all relation URLs to use trailing slash.&lt;/li&gt;
  93  &lt;li&gt;Add initial support for storing data in ElasticSearch.&lt;/li&gt;
  94  &lt;li&gt;Now able to receive and store uploaded files in the archive.&lt;/li&gt;
  95  &lt;li&gt;Changed JSON output for object lists to have relations in _links.&lt;/li&gt;
  96  &lt;li&gt;Improve JSON output for empty object lists.&lt;/li&gt;
  97  &lt;li&gt;Now uses correct MIME type application/vnd.noark5-v4+json.&lt;/li&gt;
  98  &lt;li&gt;Added support for docker container images.&lt;/li&gt;
  99  &lt;li&gt;Added simple API browser implemented in JavaScript/Angular.&lt;/li&gt;
 100  &lt;li&gt;Started on archive client implemented in JavaScript/Angular.&lt;/li&gt;
 101  &lt;li&gt;Started on prototype to show the public mail journal.&lt;/li&gt;
 102  &lt;li&gt;Improved performance by disabling Sprint FileWatcher.&lt;/li&gt;
 103  &lt;li&gt;Added support for &#39;arkivskaper&#39;, &#39;saksmappe&#39; and &#39;journalpost&#39;.&lt;/li&gt;
 104  &lt;li&gt;Added support for some metadata codelists.&lt;/li&gt;
 105  &lt;li&gt;Added support for Cross-origin resource sharing (CORS).&lt;/li&gt;
 106  &lt;li&gt;Changed login method from Basic Auth to JSON Web Token (RFC 7519)
 107    style.&lt;/li&gt;
 108  &lt;li&gt;Added support for GET-ing ny-* URLs.&lt;/li&gt;
 109  &lt;li&gt;Added support for modifying entities using PUT and eTag.&lt;/li&gt;
 110  &lt;li&gt;Added support for returning XML output on request.&lt;/li&gt;
 111  &lt;li&gt;Removed support for English field and class names, limiting ourself
 112    to the official names.&lt;/li&gt;
 113  &lt;li&gt;...&lt;/li&gt;
 114
 115 &lt;/ul&gt;
 116
 117 &lt;p&gt;If this sound interesting to you, please contact us on IRC (#nikita
 118 on irc.freenode.net) or email
 119 (&lt;a href=&quot;https://lists.nuug.no/mailman/listinfo/nikita-noark&quot;&gt;nikita-noark
 120 mailing list).&lt;/p&gt;
 121 </description>
 122         </item>
 123
 124         <item>
 125                 <title>Idea for storing trusted timestamps in a Noark 5 archive</title>
 126                 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html</link>
 127                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html</guid>
 128                 <pubDate>Wed, 7 Jun 2017 21:40:00 +0200</pubDate>
 129                 <description>&lt;p&gt;&lt;em&gt;This is a copy of
 130 &lt;a href=&quot;https://lists.nuug.no/pipermail/nikita-noark/2017-June/000297.html&quot;&gt;an
 131 email I posted to the nikita-noark mailing list&lt;/a&gt;.  Please follow up
 132 there if you would like to discuss this topic.  The background is that
 133 we are making a free software archive system based on the Norwegian
 134 &lt;a href=&quot;https://www.arkivverket.no/forvaltning-og-utvikling/regelverk-og-standarder/noark-standarden&quot;&gt;Noark
 135 5 standard&lt;/a&gt; for government archives.&lt;/em&gt;&lt;/p&gt;
 136
 137 &lt;p&gt;I&#39;ve been wondering a bit lately how trusted timestamps could be
 138 stored in Noark 5.
 139 &lt;a href=&quot;https://en.wikipedia.org/wiki/Trusted_timestamping&quot;&gt;Trusted
 140 timestamps&lt;/a&gt; can be used to verify that some information
 141 (document/file/checksum/metadata) have not been changed since a
 142 specific time in the past.  This is useful to verify the integrity of
 143 the documents in the archive.&lt;/p&gt;
 144
 145 &lt;p&gt;Then it occured to me, perhaps the trusted timestamps could be
 146 stored as dokument variants (ie dokumentobjekt referered to from
 147 dokumentbeskrivelse) with the filename set to the hash it is
 148 stamping?&lt;/p&gt;
 149
 150 &lt;p&gt;Given a &quot;dokumentbeskrivelse&quot; with an associated &quot;dokumentobjekt&quot;,
 151 a new dokumentobjekt is associated with &quot;dokumentbeskrivelse&quot; with the
 152 same attributes as the stamped dokumentobjekt except these
 153 attributes:&lt;/p&gt;
 154
 155 &lt;ul&gt;
 156
 157 &lt;li&gt;format -&gt; &quot;RFC3161&quot;
 158 &lt;li&gt;mimeType -&gt; &quot;application/timestamp-reply&quot;
 159 &lt;li&gt;formatDetaljer -&gt; &quot;&amp;lt;source URL for timestamp service&amp;gt;&quot;
 160 &lt;li&gt;filenavn -&gt; &quot;&amp;lt;sjekksum&amp;gt;.tsr&quot;
 161
 162 &lt;/ul&gt;
 163
 164 &lt;p&gt;This assume a service following
 165 &lt;a href=&quot;https://tools.ietf.org/html/rfc3161&quot;&gt;IETF RFC 3161&lt;/a&gt; is
 166 used, which specifiy the given MIME type for replies and the .tsr file
 167 ending for the content of such trusted timestamp.  As far as I can
 168 tell from the Noark 5 specifications, it is OK to have several
 169 variants/renderings of a dokument attached to a given
 170 dokumentbeskrivelse objekt.  It might be stretching it a bit to make
 171 some of these variants represent crypto-signatures useful for
 172 verifying the document integrity instead of representing the dokument
 173 itself.&lt;/p&gt;
 174
 175 &lt;p&gt;Using the source of the service in formatDetaljer allow several
 176 timestamping services to be used.  This is useful to spread the risk
 177 of key compromise over several organisations.  It would only be a
 178 problem to trust the timestamps if all of the organisations are
 179 compromised.&lt;/p&gt;
 180
 181 &lt;p&gt;The following oneliner on Linux can be used to generate the tsr
 182 file.  $input is the path to the file to checksum, and $sha256 is the
 183 SHA-256 checksum of the file (ie the &quot;&lt;sjekksum&gt;.tsr&quot; value mentioned
 184 above).&lt;/p&gt;
 185
 186 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
 187 openssl ts -query -data &quot;$inputfile&quot; -cert -sha256 -no_nonce \
 188   | curl -s -H &quot;Content-Type: application/timestamp-query&quot; \
 189       --data-binary &quot;@-&quot; http://zeitstempel.dfn.de &gt; $sha256.tsr
 190 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 191
 192 &lt;p&gt;To verify the timestamp, you first need to download the public key
 193 of the trusted timestamp service, for example using this command:&lt;/p&gt;
 194
 195 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
 196 wget -O ca-cert.txt \
 197   https://pki.pca.dfn.de/global-services-ca/pub/cacert/chain.txt
 198 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 199
 200 &lt;p&gt;Note, the public key should be stored alongside the timestamps in
 201 the archive to make sure it is also available 100 years from now.  It
 202 is probably a good idea to standardise how and were to store such
 203 public keys, to make it easier to find for those trying to verify
 204 documents 100 or 1000 years from now. :)&lt;/p&gt;
 205
 206 &lt;p&gt;The verification itself is a simple openssl command:&lt;/p&gt;
 207
 208 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
 209 openssl ts -verify -data $inputfile -in $sha256.tsr \
 210   -CAfile ca-cert.txt -text
 211 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 212
 213 &lt;p&gt;Is there any reason this approach would not work?  Is it somehow against
 214 the Noark 5 specification?&lt;/p&gt;
 215 </description>
 216         </item>
 217
 218         <item>
 219                 <title>Når nynorskoversettelsen svikter til eksamen...</title>
 220                 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</link>
 221                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</guid>
 222                 <pubDate>Sat, 3 Jun 2017 08:20:00 +0200</pubDate>
 223                 <description>&lt;p&gt;&lt;a href=&quot;http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-622459b.html&quot;&gt;Aftenposten
 224 melder i dag&lt;/a&gt; om feil i eksamensoppgavene for eksamen i politikk og
 225 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
 226 like.  Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
 227 på om den fri oversetterløsningen
 228 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium&lt;/a&gt; ville gjort en bedre
 229 jobb enn Utdanningsdirektoratet.  Det kan se slik ut.&lt;/p&gt;
 230
 231 &lt;p&gt;Her er bokmålsoppgaven fra eksamenen:&lt;/p&gt;
 232
 233 &lt;blockquote&gt;
 234 &lt;p&gt;Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
 235 rolle og muligheter til å håndtere internasjonale utfordringer, som
 236 for eksempel flykningekrisen.&lt;/p&gt;
 237
 238 &lt;p&gt;Vedlegge er eksempler på tekster som kan gi relevante perspektiver
 239 på temaet:&lt;/p&gt;
 240 &lt;ol&gt;
 241 &lt;li&gt;Flykningeregnskapet 2016, UNHCR og IDMC
 242 &lt;li&gt;«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
 243 &lt;/ol&gt;
 244
 245 &lt;/blockquote&gt;
 246
 247 &lt;p&gt;Dette oversetter Apertium slik:&lt;/p&gt;
 248
 249 &lt;blockquote&gt;
 250 &lt;p&gt;Drøft utfordringane knytte til nasjonalstatane sine og rolla til
 251 andre aktørar og høve til å handtera internasjonale utfordringar, som
 252 til dømes *flykningekrisen.&lt;/p&gt;
 253
 254 &lt;p&gt;Vedleggja er døme på tekster som kan gje relevante perspektiv på
 255 temaet:&lt;/p&gt;
 256
 257 &lt;ol&gt;
 258 &lt;li&gt;*Flykningeregnskapet 2016, *UNHCR og *IDMC&lt;/li&gt;
 259 &lt;li&gt;«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015&lt;/li&gt;
 260 &lt;/ol&gt;
 261
 262 &lt;/blockquote&gt;
 263
 264 &lt;p&gt;Ord som ikke ble forstått er markert med stjerne (*), og trenger
 265 ekstra språksjekk.  Men ingen ord er forsvunnet, slik det var i
 266 oppgaven elevene fikk presentert på eksamen.  Jeg mistenker dog at
 267 &quot;andre aktørers rolle og muligheter til ...&quot; burde vært oversatt til
 268 &quot;rolla til andre aktørar og deira høve til ...&quot; eller noe slikt, men
 269 det er kanskje flisespikking.  Det understreker vel bare at det alltid
 270 trengs korrekturlesning etter automatisk oversettelse.&lt;/p&gt;
 271 </description>
 272         </item>
 273
 274         <item>
 275                 <title>Epost inn som arkivformat i Riksarkivarens forskrift?</title>
 276                 <link>http://people.skolelinux.org/pere/blog/Epost_inn_som_arkivformat_i_Riksarkivarens_forskrift_.html</link>
 277                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Epost_inn_som_arkivformat_i_Riksarkivarens_forskrift_.html</guid>
 278                 <pubDate>Thu, 27 Apr 2017 11:30:00 +0200</pubDate>
 279                 <description>&lt;p&gt;I disse dager, med frist 1. mai, har Riksarkivaren ute en høring på
 280 sin forskrift.  Som en kan se er det ikke mye tid igjen før fristen
 281 som går ut på søndag.  Denne forskriften er det som lister opp hvilke
 282 formater det er greit å arkivere i
 283 &lt;a href=&quot;http://www.arkivverket.no/arkivverket/Offentleg-forvalting/Noark/Noark-5&quot;&gt;Noark
 284 5-løsninger&lt;/a&gt; i Norge.&lt;/p&gt;
 285
 286 &lt;p&gt;Jeg fant høringsdokumentene hos
 287 &lt;a href=&quot;https://www.arkivrad.no/aktuelt/riksarkivarens-forskrift-pa-horing&quot;&gt;Norsk
 288 Arkivråd&lt;/a&gt; etter å ha blitt tipset på epostlisten til
 289 &lt;a href=&quot;https://github.com/hiOA-ABI/nikita-noark5-core&quot;&gt;fri
 290 programvareprosjektet Nikita Noark5-Core&lt;/a&gt;, som lager et Noark 5
 291 Tjenestegresesnitt.  Jeg er involvert i Nikita-prosjektet og takket
 292 være min interesse for tjenestegrensesnittsprosjektet har jeg lest en
 293 god del Noark 5-relaterte dokumenter, og til min overraskelse oppdaget
 294 at standard epost ikke er på listen over godkjente formater som kan
 295 arkiveres.  Høringen med frist søndag er en glimrende mulighet til å
 296 forsøke å gjøre noe med det.  Jeg holder på med
 297 &lt;a href=&quot;https://github.com/petterreinholdtsen/noark5-tester/blob/master/docs/hoering-arkivforskrift.tex&quot;&gt;egen
 298 høringsuttalelse&lt;/a&gt;, og lurer på om andre er interessert i å støtte
 299 forslaget om å tillate arkivering av epost som epost i arkivet.&lt;/p&gt;
 300
 301 &lt;p&gt;Er du igang med å skrive egen høringsuttalelse allerede?  I så fall
 302 kan du jo vurdere å ta med en formulering om epost-lagring. Jeg tror
 303 ikke det trengs så mye.  Her et kort forslag til tekst:&lt;/p&gt;
 304
 305 &lt;p&gt;&lt;blockquote&gt;
 306
 307   &lt;p&gt;Viser til høring sendt ut 2017-02-17 (Riksarkivarens referanse
 308   2016/9840 HELHJO), og tillater oss å sende inn noen innspill om
 309   revisjon av Forskrift om utfyllende tekniske og arkivfaglige
 310   bestemmelser om behandling av offentlige arkiver (Riksarkivarens
 311   forskrift).&lt;/p&gt;
 312
 313   &lt;p&gt;Svært mye av vår kommuikasjon foregår i dag på e-post.  Vi
 314   foreslår derfor at Internett-e-post, slik det er beskrevet i IETF
 315   RFC 5322,
 316   &lt;a href=&quot;https://tools.ietf.org/html/rfc5322&quot;&gt;https://tools.ietf.org/html/rfc5322&lt;/a&gt;. bør
 317   inn som godkjent dokumentformat.  Vi foreslår at forskriftens
 318   oversikt over godkjente dokumentformater ved innlevering i § 5-16
 319   endres til å ta med Internett-e-post.&lt;/p&gt;
 320
 321 &lt;/blockquote&gt;&lt;/p&gt;
 322
 323 &lt;p&gt;Som del av arbeidet med tjenestegrensesnitt har vi testet hvordan
 324 epost kan lagres i en Noark 5-struktur, og holder på å skrive et
 325 forslag om hvordan dette kan gjøres som vil bli sendt over til
 326 arkivverket så snart det er ferdig.  De som er interesserte kan
 327 &lt;a href=&quot;https://github.com/petterreinholdtsen/noark5-tester/blob/master/docs/epostlagring.md&quot;&gt;følge
 328 fremdriften på web&lt;/a&gt;.&lt;/p&gt;
 329
 330 &lt;p&gt;Oppdatering 2017-04-28: I dag ble høringuttalelsen jeg skrev
 331   &lt;a href=&quot;https://www.nuug.no/news/NUUGs_h_ringuttalelse_til_Riksarkivarens_forskrift.shtml&quot;&gt;sendt
 332   inn av foreningen NUUG&lt;/a&gt;.&lt;/p&gt;
 333 </description>
 334         </item>
 335
 336         <item>
 337                 <title>Offentlig elektronisk postjournal blokkerer tilgang for utvalgte webklienter</title>
 338                 <link>http://people.skolelinux.org/pere/blog/Offentlig_elektronisk_postjournal_blokkerer_tilgang_for_utvalgte_webklienter.html</link>
 339                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Offentlig_elektronisk_postjournal_blokkerer_tilgang_for_utvalgte_webklienter.html</guid>
 340                 <pubDate>Thu, 20 Apr 2017 13:00:00 +0200</pubDate>
 341                 <description>&lt;p&gt;Jeg oppdaget i dag at &lt;a href=&quot;https://www.oep.no/&quot;&gt;nettstedet som
 342 publiserer offentlige postjournaler fra statlige etater&lt;/a&gt;, OEP, har
 343 begynt å blokkerer enkelte typer webklienter fra å få tilgang.  Vet
 344 ikke hvor mange det gjelder, men det gjelder i hvert fall libwww-perl
 345 og curl.  For å teste selv, kjør følgende:&lt;/p&gt;
 346
 347 &lt;blockquote&gt;&lt;pre&gt;
 348 % curl -v -s https://www.oep.no/pub/report.xhtml?reportId=3 2&gt;&amp;1 |grep &#39;&lt; HTTP&#39;
 349 &lt; HTTP/1.1 404 Not Found
 350 % 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;
 351 &lt; HTTP/1.1 200 OK
 352 %
 353 &lt;/pre&gt;&lt;/blockquote&gt;
 354
 355 &lt;p&gt;Her kan en se at tjenesten gir «404 Not Found» for curl i
 356 standardoppsettet, mens den gir «200 OK» hvis curl hevder å være Opera
 357 versjon 12.0.  Offentlig elektronisk postjournal startet blokkeringen
 358 2017-03-02.&lt;/p&gt;
 359
 360 &lt;p&gt;Blokkeringen vil gjøre det litt vanskeligere å maskinelt hente
 361 informasjon fra oep.no.  Kan blokkeringen være gjort for å hindre
 362 automatisert innsamling av informasjon fra OEP, slik Pressens
 363 Offentlighetsutvalg gjorde for å dokumentere hvordan departementene
 364 hindrer innsyn i
 365 &lt;a href=&quot;http://presse.no/dette-mener-np/undergraver-offentlighetsloven/&quot;&gt;rapporten
 366 «Slik hindrer departementer innsyn» som ble publiserte i januar
 367 2017&lt;/a&gt;.  Det virker usannsynlig, da det jo er trivielt å bytte
 368 User-Agent til noe nytt.&lt;/p&gt;
 369
 370 &lt;p&gt;Finnes det juridisk grunnlag for det offentlige å diskriminere
 371 webklienter slik det gjøres her?  Der tilgang gis eller ikke alt etter
 372 hva klienten sier at den heter?  Da OEP eies av DIFI og driftes av
 373 Basefarm, finnes det kanskje noen dokumenter sendt mellom disse to
 374 aktørene man kan be om innsyn i for å forstå hva som har skjedd.  Men
 375 &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
 376 til DIFI viser kun to dokumenter&lt;/a&gt; det siste året mellom DIFI og
 377 Basefarm.
 378 &lt;a href=&quot;https://www.mimesbronn.no/request/blokkering_av_tilgang_til_oep_fo&quot;&gt;Mimes brønn neste&lt;/a&gt;,
 379 tenker jeg.&lt;/p&gt;
 380 </description>
 381         </item>
 382
 383         <item>
 384                 <title>Free software archive system Nikita now able to store documents</title>
 385                 <link>http://people.skolelinux.org/pere/blog/Free_software_archive_system_Nikita_now_able_to_store_documents.html</link>
 386                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Free_software_archive_system_Nikita_now_able_to_store_documents.html</guid>
 387                 <pubDate>Sun, 19 Mar 2017 08:00:00 +0100</pubDate>
 388                 <description>&lt;p&gt;The &lt;a href=&quot;https://github.com/hiOA-ABI/nikita-noark5-core&quot;&gt;Nikita
 389 Noark 5 core project&lt;/a&gt; is implementing the Norwegian standard for
 390 keeping an electronic archive of government documents.
 391 &lt;a href=&quot;http://www.arkivverket.no/arkivverket/Offentlig-forvaltning/Noark/Noark-5/English-version&quot;&gt;The
 392 Noark 5 standard&lt;/a&gt; document the requirement for data systems used by
 393 the archives in the Norwegian government, and the Noark 5 web interface
 394 specification document a REST web service for storing, searching and
 395 retrieving documents and metadata in such archive.  I&#39;ve been involved
 396 in the project since a few weeks before Christmas, when the Norwegian
 397 Unix User Group
 398 &lt;a href=&quot;https://www.nuug.no/news/NOARK5_kjerne_som_fri_programvare_f_r_epostliste_hos_NUUG.shtml&quot;&gt;announced
 399 it supported the project&lt;/a&gt;.  I believe this is an important project,
 400 and hope it can make it possible for the government archives in the
 401 future to use free software to keep the archives we citizens depend
 402 on.  But as I do not hold such archive myself, personally my first use
 403 case is to store and analyse public mail journal metadata published
 404 from the government.  I find it useful to have a clear use case in
 405 mind when developing, to make sure the system scratches one of my
 406 itches.&lt;/p&gt;
 407
 408 &lt;p&gt;If you would like to help make sure there is a free software
 409 alternatives for the archives, please join our IRC channel
 410 (&lt;a href=&quot;irc://irc.freenode.net/%23nikita&quot;&quot;&gt;#nikita on
 411 irc.freenode.net&lt;/a&gt;) and
 412 &lt;a href=&quot;https://lists.nuug.no/mailman/listinfo/nikita-noark&quot;&gt;the
 413 project mailing list&lt;/a&gt;.&lt;/p&gt;
 414
 415 &lt;p&gt;When I got involved, the web service could store metadata about
 416 documents.  But a few weeks ago, a new milestone was reached when it
 417 became possible to store full text documents too.  Yesterday, I
 418 completed an implementation of a command line tool
 419 &lt;tt&gt;archive-pdf&lt;/tt&gt; to upload a PDF file to the archive using this
 420 API.  The tool is very simple at the moment, and find existing
 421 &lt;a href=&quot;https://en.wikipedia.org/wiki/Fonds&quot;&gt;fonds&lt;/a&gt;, series and
 422 files while asking the user to select which one to use if more than
 423 one exist.  Once a file is identified, the PDF is associated with the
 424 file and uploaded, using the title extracted from the PDF itself.  The
 425 process is fairly similar to visiting the archive, opening a cabinet,
 426 locating a file and storing a piece of paper in the archive.  Here is
 427 a test run directly after populating the database with test data using
 428 our API tester:&lt;/p&gt;
 429
 430 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
 431 ~/src//noark5-tester$ ./archive-pdf mangelmelding/mangler.pdf
 432 using arkiv: Title of the test fonds created 2017-03-18T23:49:32.103446
 433 using arkivdel: Title of the test series created 2017-03-18T23:49:32.103446
 434
 435  0 - Title of the test case file created 2017-03-18T23:49:32.103446
 436  1 - Title of the test file created 2017-03-18T23:49:32.103446
 437 Select which mappe you want (or search term): 0
 438 Uploading mangelmelding/mangler.pdf
 439   PDF title: Mangler i spesifikasjonsdokumentet for NOARK 5 Tjenestegrensesnitt
 440   File 2017/1: Title of the test case file created 2017-03-18T23:49:32.103446
 441 ~/src//noark5-tester$
 442 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 443
 444 &lt;p&gt;You can see here how the fonds (arkiv) and serie (arkivdel) only had
 445 one option, while the user need to choose which file (mappe) to use
 446 among the two created by the API tester.  The &lt;tt&gt;archive-pdf&lt;/tt&gt;
 447 tool can be found in the git repository for the API tester.&lt;/p&gt;
 448
 449 &lt;p&gt;In the project, I have been mostly working on
 450 &lt;a href=&quot;https://github.com/petterreinholdtsen/noark5-tester&quot;&gt;the API
 451 tester&lt;/a&gt; so far, while getting to know the code base.  The API
 452 tester currently use
 453 &lt;a href=&quot;https://en.wikipedia.org/wiki/HATEOAS&quot;&gt;the HATEOAS links&lt;/a&gt;
 454 to traverse the entire exposed service API and verify that the exposed
 455 operations and objects match the specification, as well as trying to
 456 create objects holding metadata and uploading a simple XML file to
 457 store.  The tester has proved very useful for finding flaws in our
 458 implementation, as well as flaws in the reference site and the
 459 specification.&lt;/p&gt;
 460
 461 &lt;p&gt;The test document I uploaded is a summary of all the specification
 462 defects we have collected so far while implementing the web service.
 463 There are several unclear and conflicting parts of the specification,
 464 and we have
 465 &lt;a href=&quot;https://github.com/petterreinholdtsen/noark5-tester/tree/master/mangelmelding&quot;&gt;started
 466 writing down&lt;/a&gt; the questions we get from implementing it.  We use a
 467 format inspired by how &lt;a href=&quot;http://www.opengroup.org/austin/&quot;&gt;The
 468 Austin Group&lt;/a&gt; collect defect reports for the POSIX standard with
 469 &lt;a href=&quot;http://www.opengroup.org/austin/mantis.html&quot;&gt;their
 470 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; :).
 471
 472 &lt;p&gt;The Nikita project is implemented using Java and Spring, and is
 473 fairly easy to get up and running using Docker containers for those
 474 that want to test the current code base.  The API tester is
 475 implemented in Python.&lt;/p&gt;
 476 </description>
 477         </item>
 478
 479         <item>
 480                 <title>Detecting NFS hangs on Linux without hanging yourself...</title>
 481                 <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</link>
 482                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</guid>
 483                 <pubDate>Thu, 9 Mar 2017 15:20:00 +0100</pubDate>
 484                 <description>&lt;p&gt;Over the years, administrating thousand of NFS mounting linux
 485 computers at the time, I often needed a way to detect if the machine
 486 was experiencing NFS hang.  If you try to use &lt;tt&gt;df&lt;/tt&gt; or look at a
 487 file or directory affected by the hang, the process (and possibly the
 488 shell) will hang too.  So you want to be able to detect this without
 489 risking the detection process getting stuck too.  It has not been
 490 obvious how to do this.  When the hang has lasted a while, it is
 491 possible to find messages like these in dmesg:&lt;/p&gt;
 492
 493 &lt;p&gt;&lt;blockquote&gt;
 494 nfs: server nfsserver not responding, still trying
 495 &lt;br&gt;nfs: server nfsserver OK
 496 &lt;/blockquote&gt;&lt;/p&gt;
 497
 498 &lt;p&gt;It is hard to know if the hang is still going on, and it is hard to
 499 be sure looking in dmesg is going to work.  If there are lots of other
 500 messages in dmesg the lines might have rotated out of site before they
 501 are noticed.&lt;/p&gt;
 502
 503 &lt;p&gt;While reading through the nfs client implementation in linux kernel
 504 code, I came across some statistics that seem to give a way to detect
 505 it.  The om_timeouts sunrpc value in the kernel will increase every
 506 time the above log entry is inserted into dmesg.  And after digging a
 507 bit further, I discovered that this value show up in
 508 /proc/self/mountstats on Linux.&lt;/p&gt;
 509
 510 &lt;p&gt;The mountstats content seem to be shared between files using the
 511 same file system context, so it is enough to check one of the
 512 mountstats files to get the state of the mount point for the machine.
 513 I assume this will not show lazy umounted NFS points, nor NFS mount
 514 points in a different process context (ie with a different filesystem
 515 view), but that does not worry me.&lt;/p&gt;
 516
 517 &lt;p&gt;The content for a NFS mount point look similar to this:&lt;/p&gt;
 518
 519 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
 520 [...]
 521 device /dev/mapper/Debian-var mounted on /var with fstype ext3
 522 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
 523         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
 524         age:    7863311
 525         caps:   caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
 526         sec:    flavor=1,pseudoflavor=1
 527         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
 528         bytes:  166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
 529         RPC iostats version: 1.0  p/v: 100003/3 (nfs)
 530         xprt:   tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
 531         per-op statistics
 532                 NULL: 0 0 0 0 0 0 0 0
 533              GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
 534              SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
 535               LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
 536               ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
 537             READLINK: 125 125 0 20472 18620 0 1112 1118
 538                 READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
 539                WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
 540               CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
 541                MKDIR: 3680 3680 0 773980 993920 26 23990 24245
 542              SYMLINK: 903 903 0 233428 245488 6 5865 5917
 543                MKNOD: 80 80 0 20148 21760 0 299 304
 544               REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
 545                RMDIR: 3367 3367 0 645112 484848 22 5782 6002
 546               RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
 547                 LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
 548              READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
 549          READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
 550               FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
 551               FSINFO: 2 2 0 232 328 0 1 1
 552             PATHCONF: 1 1 0 116 140 0 0 0
 553               COMMIT: 0 0 0 0 0 0 0 0
 554
 555 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
 556 [...]
 557 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 558
 559 &lt;p&gt;The key number to look at is the third number in the per-op list.
 560 It is the number of NFS timeouts experiences per file system
 561 operation.  Here 22 write timeouts and 5 access timeouts.  If these
 562 numbers are increasing, I believe the machine is experiencing NFS
 563 hang.  Unfortunately the timeout value do not start to increase right
 564 away.  The NFS operations need to time out first, and this can take a
 565 while.  The exact timeout value depend on the setup.  For example the
 566 defaults for TCP and UDP mount points are quite different, and the
 567 timeout value is affected by the soft, hard, timeo and retrans NFS
 568 mount options.&lt;/p&gt;
 569
 570 &lt;p&gt;The only way I have been able to get working on Debian and RedHat
 571 Enterprise Linux for getting the timeout count is to peek in /proc/.
 572 But according to
 573 &lt;ahref=&quot;http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html&quot;&gt;Solaris
 574 10 System Administration Guide: Network Services&lt;/a&gt;, the &#39;nfsstat -c&#39;
 575 command can be used to get these timeout values.  But this do not work
 576 on Linux, as far as I can tell.  I
 577 &lt;ahref=&quot;http://bugs.debian.org/857043&quot;&gt;asked Debian about this&lt;/a&gt;,
 578 but have not seen any replies yet.&lt;/p&gt;
 579
 580 &lt;p&gt;Is there a better way to figure out if a Linux NFS client is
 581 experiencing NFS hangs?  Is there a way to detect which processes are
 582 affected?  Is there a way to get the NFS mount going quickly once the
 583 network problem causing the NFS hang has been cleared?  I would very
 584 much welcome some clues, as we regularly run into NFS hangs.&lt;/p&gt;
 585 </description>
 586         </item>
 587
 588         <item>
 589                 <title>How does it feel to be wiretapped, when you should be doing the wiretapping...</title>
 590                 <link>http://people.skolelinux.org/pere/blog/How_does_it_feel_to_be_wiretapped__when_you_should_be_doing_the_wiretapping___.html</link>
 591                 <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>
 592                 <pubDate>Wed, 8 Mar 2017 11:50:00 +0100</pubDate>
 593                 <description>&lt;p&gt;So the new president in the United States of America claim to be
 594 surprised to discover that he was wiretapped during the election
 595 before he was elected president.  He even claim this must be illegal.
 596 Well, doh, if it is one thing the confirmations from Snowden
 597 documented, it is that the entire population in USA is wiretapped, one
 598 way or another.  Of course the president candidates were wiretapped,
 599 alongside the senators, judges and the rest of the people in USA.&lt;/p&gt;
 600
 601 &lt;p&gt;Next, the Federal Bureau of Investigation ask the Department of
 602 Justice to go public rejecting the claims that Donald Trump was
 603 wiretapped illegally.  I fail to see the relevance, given that I am
 604 sure the surveillance industry in USA believe they have all the legal
 605 backing they need to conduct mass surveillance on the entire
 606 world.&lt;/p&gt;
 607
 608 &lt;p&gt;There is even the director of the FBI stating that he never saw an
 609 order requesting wiretapping of Donald Trump.  That is not very
 610 surprising, given how the FISA court work, with all its activity being
 611 secret.  Perhaps he only heard about it?&lt;/p&gt;
 612
 613 &lt;p&gt;What I find most sad in this story is how Norwegian journalists
 614 present it.  In a news reports the other day in the radio from the
 615 Norwegian National broadcasting Company (NRK), I heard the journalist
 616 claim that &#39;the FBI denies any wiretapping&#39;, while the reality is that
 617 &#39;the FBI denies any illegal wiretapping&#39;.  There is a fundamental and
 618 important difference, and it make me sad that the journalists are
 619 unable to grasp it.&lt;/p&gt;
 620
 621 &lt;p&gt;&lt;strong&gt;Update 2017-03-13:&lt;/strong&gt; Look like
 622 &lt;a href=&quot;https://theintercept.com/2017/03/13/rand-paul-is-right-nsa-routinely-monitors-americans-communications-without-warrants/&quot;&gt;The
 623 Intercept report that US Senator Rand Paul confirm what I state above&lt;/a&gt;.&lt;/p&gt;
 624 </description>
 625         </item>
 626
 627         <item>
 628                 <title>Norwegian Bokmål translation of The Debian Administrator&#39;s Handbook complete, proofreading in progress</title>
 629                 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</link>
 630                 <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>
 631                 <pubDate>Fri, 3 Mar 2017 14:50:00 +0100</pubDate>
 632                 <description>&lt;p&gt;For almost a year now, we have been working on making a Norwegian
 633 Bokmål edition of &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
 634 Administrator&#39;s Handbook&lt;/a&gt;.  Now, thanks to the tireless effort of
 635 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
 636 we are working on the proof reading to ensure consistent language and
 637 use of correct computer science terms.  The plan is to make the book
 638 available on paper, as well as in electronic form.  For that to
 639 happen, the proof reading must be completed and all the figures need
 640 to be translated.  If you want to help out, get in touch.&lt;/p&gt;
 641
 642 &lt;p&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf&quot;&gt;A
 643
 644 fresh PDF edition&lt;/a&gt; in A4 format (the final book will have smaller
 645 pages) of the book created every morning is available for
 646 proofreading.  If you find any errors, please
 647 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;visit
 648 Weblate and correct the error&lt;/a&gt;.  The
 649 &lt;a href=&quot;http://l.github.io/debian-handbook/stat/nb-NO/index.html&quot;&gt;state
 650 of the translation including figures&lt;/a&gt; is a useful source for those
 651 provide Norwegian bokmål screen shots and figures.&lt;/p&gt;
 652 </description>
 653         </item>
 654
 655         </channel>
 656 </rss>