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