blog/archive/2017/06/06.rss

   1 <?xml version="1.0" encoding="ISO-8859-1"?>
   2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
   3         <channel>
   4                 <title>Petter Reinholdtsen - Entries from June 2017</title>
   5                 <description>Entries from June 2017</description>
   6                 <link>http://www.hungry.com/~pere/blog/</link>
   7
   8
   9         <item>
  10                 <title>«Rapporten ser ikke på informasjonssikkerhet knyttet til personlig integritet»</title>
  11                 <link>http://www.hungry.com/~pere/blog/_Rapporten_ser_ikke_p__informasjonssikkerhet_knyttet_til_personlig_integritet_.html</link>
  12                 <guid isPermaLink="true">http://www.hungry.com/~pere/blog/_Rapporten_ser_ikke_p__informasjonssikkerhet_knyttet_til_personlig_integritet_.html</guid>
  13                 <pubDate>Tue, 27 Jun 2017 17:50:00 +0200</pubDate>
  14                 <description>&lt;p&gt;Jeg kom over teksten
  15 «&lt;a href=&quot;https://freedom-to-tinker.com/2017/06/21/killing-car-privacy-by-federal-mandate/&quot;&gt;Killing
  16 car privacy by federal mandate&lt;/a&gt;» av Leonid Reyzin på Freedom to
  17 Tinker i dag, og det gleder meg å se en god gjennomgang om hvorfor det
  18 er et urimelig inngrep i privatsfæren å la alle biler kringkaste sin
  19 posisjon og bevegelse via radio.  Det omtalte forslaget basert på
  20 Dedicated Short Range Communication (DSRC) kalles Basic Safety Message
  21 (BSM) i USA og Cooperative Awareness Message (CAM) i Europa, og det
  22 norske Vegvesenet er en av de som ser ut til å kunne tenke seg å
  23 pålegge alle biler å fjerne nok en bit av innbyggernes privatsfære.
  24 Anbefaler alle å lese det som står der.
  25
  26 &lt;p&gt;Mens jeg tittet litt på DSRC på biler i Norge kom jeg over et sitat
  27 jeg synes er illustrativt for hvordan det offentlige Norge håndterer
  28 problemstillinger rundt innbyggernes privatsfære i SINTEF-rapporten
  29 «&lt;a href=&quot;https://www.sintef.no/publikasjoner/publikasjon/Download/?pubid=SINTEF+A23933&quot;&gt;Informasjonssikkerhet
  30 i AutoPASS-brikker&lt;/a&gt;» av Trond Foss:&lt;/p&gt;
  31
  32 &lt;p&gt;&lt;blockquote&gt;
  33 «Rapporten ser ikke på informasjonssikkerhet knyttet til personlig
  34   integritet.»
  35 &lt;/blockquote&gt;&lt;/p&gt;
  36
  37 &lt;p&gt;Så enkelt kan det tydeligvis gjøres når en vurderer
  38 informasjonssikkerheten.  Det holder vel at folkene på toppen kan si
  39 at «Personvernet er ivaretatt», som jo er den populære intetsigende
  40 frasen som gjør at mange tror enkeltindividers integritet tas vare på.
  41 Sitatet fikk meg til å undres på hvor ofte samme tilnærming, å bare se
  42 bort fra behovet for personlig itegritet, blir valgt når en velger å
  43 legge til rette for nok et inngrep i privatsfæren til personer i
  44 Norge.  Det er jo sjelden det får reaksjoner.  Historien om
  45 reaksjonene på Helse Sør-Østs tjenesteutsetting er jo sørgelig nok et
  46 unntak og toppen av isfjellet, desverre.  Tror jeg fortsatt takker nei
  47 til både AutoPASS og holder meg så langt unna det norske helsevesenet
  48 som jeg kan, inntil de har demonstrert og dokumentert at de verdsetter
  49 individets privatsfære og personlige integritet høyere enn kortsiktig
  50 gevist og samfunnsnytte.&lt;/p&gt;
  51 </description>
  52         </item>
  53
  54         <item>
  55                 <title>Updated sales number for my Free Culture paper editions</title>
  56                 <link>http://www.hungry.com/~pere/blog/Updated_sales_number_for_my_Free_Culture_paper_editions.html</link>
  57                 <guid isPermaLink="true">http://www.hungry.com/~pere/blog/Updated_sales_number_for_my_Free_Culture_paper_editions.html</guid>
  58                 <pubDate>Mon, 12 Jun 2017 11:40:00 +0200</pubDate>
  59                 <description>&lt;p&gt;It is pleasing to see that the work we put down in publishing new
  60 editions of the classic &lt;a href=&quot;http://www.free-culture.cc/&quot;&gt;Free
  61 Culture book&lt;/a&gt; by the founder of the Creative Commons movement,
  62 Lawrence Lessig, is still being appreciated.  I had a look at the
  63 latest sales numbers for the paper edition today.  Not too impressive,
  64 but happy to see some buyers still exist.  All the revenue from the
  65 books is sent to the &lt;a href=&quot;https://creativecommons.org/&quot;&gt;Creative
  66 Commons Corporation&lt;/a&gt;, and they receive the largest cut if you buy
  67 directly from Lulu.  Most books are sold via Amazon, with Ingram
  68 second and only a small fraction directly from Lulu.  The ebook
  69 edition is available for free from
  70 &lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;Github&lt;/a&gt;.&lt;/p&gt;
  71
  72 &lt;table border=&quot;0&quot;&gt;
  73 &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;
  74 &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;
  75
  76 &lt;tr&gt;
  77   &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;
  78   &lt;td align=&quot;right&quot;&gt;3&lt;/td&gt;
  79   &lt;td align=&quot;right&quot;&gt;6&lt;/td&gt;
  80   &lt;td align=&quot;right&quot;&gt;15&lt;/td&gt;
  81 &lt;/tr&gt;
  82
  83 &lt;tr&gt;
  84   &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;
  85   &lt;td align=&quot;right&quot;&gt;7&lt;/td&gt;
  86   &lt;td align=&quot;right&quot;&gt;1&lt;/td&gt;
  87   &lt;td align=&quot;right&quot;&gt;0&lt;/td&gt;
  88 &lt;/tr&gt;
  89
  90 &lt;tr&gt;
  91   &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;
  92   &lt;td align=&quot;right&quot;&gt;14&lt;/td&gt;
  93   &lt;td align=&quot;right&quot;&gt;27&lt;/td&gt;
  94   &lt;td align=&quot;right&quot;&gt;16&lt;/td&gt;
  95 &lt;/tr&gt;
  96
  97 &lt;tr&gt;
  98   &lt;td&gt;Total&lt;/td&gt;
  99   &lt;td align=&quot;right&quot;&gt;24&lt;/td&gt;
 100   &lt;td align=&quot;right&quot;&gt;34&lt;/td&gt;
 101   &lt;td align=&quot;right&quot;&gt;31&lt;/td&gt;
 102 &lt;/tr&gt;
 103
 104 &lt;/table&gt;
 105
 106 &lt;p&gt;A bit sad to see the low sales number on the Norwegian edition, and
 107 a bit surprising the English edition still selling so well.&lt;/p&gt;
 108
 109 &lt;p&gt;If you would like to translate and publish the book in your native
 110 language, I would be happy to help make it happen.  Please get in
 111 touch.&lt;/p&gt;
 112 </description>
 113         </item>
 114
 115         <item>
 116                 <title>Release 0.1.1 of free software archive system Nikita announced</title>
 117                 <link>http://www.hungry.com/~pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html</link>
 118                 <guid isPermaLink="true">http://www.hungry.com/~pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html</guid>
 119                 <pubDate>Sat, 10 Jun 2017 00:40:00 +0200</pubDate>
 120                 <description>&lt;p&gt;I am very happy to report that the
 121 &lt;a href=&quot;https://github.com/hiOA-ABI/nikita-noark5-core&quot;&gt;Nikita Noark 5
 122 core project&lt;/a&gt; tagged its second release today.  The free software
 123 solution is an implementation of the Norwegian archive standard Noark
 124 5 used by government offices in Norway.  These were the changes in
 125 version 0.1.1 since version 0.1.0 (from NEWS.md):
 126
 127 &lt;ul&gt;
 128
 129  &lt;li&gt;Continued work on the angularjs GUI, including document upload.&lt;/li&gt;
 130  &lt;li&gt;Implemented correspondencepartPerson, correspondencepartUnit and
 131    correspondencepartInternal&lt;/li&gt;
 132  &lt;li&gt;Applied for coverity coverage and started submitting code on
 133    regualr basis.&lt;/li&gt;
 134  &lt;li&gt;Started fixing bugs reported by coverity&lt;/li&gt;
 135  &lt;li&gt;Corrected and completed HATEOAS links to make sure entire API is
 136    available via URLs in _links.&lt;/li&gt;
 137  &lt;li&gt;Corrected all relation URLs to use trailing slash.&lt;/li&gt;
 138  &lt;li&gt;Add initial support for storing data in ElasticSearch.&lt;/li&gt;
 139  &lt;li&gt;Now able to receive and store uploaded files in the archive.&lt;/li&gt;
 140  &lt;li&gt;Changed JSON output for object lists to have relations in _links.&lt;/li&gt;
 141  &lt;li&gt;Improve JSON output for empty object lists.&lt;/li&gt;
 142  &lt;li&gt;Now uses correct MIME type application/vnd.noark5-v4+json.&lt;/li&gt;
 143  &lt;li&gt;Added support for docker container images.&lt;/li&gt;
 144  &lt;li&gt;Added simple API browser implemented in JavaScript/Angular.&lt;/li&gt;
 145  &lt;li&gt;Started on archive client implemented in JavaScript/Angular.&lt;/li&gt;
 146  &lt;li&gt;Started on prototype to show the public mail journal.&lt;/li&gt;
 147  &lt;li&gt;Improved performance by disabling Sprint FileWatcher.&lt;/li&gt;
 148  &lt;li&gt;Added support for &#39;arkivskaper&#39;, &#39;saksmappe&#39; and &#39;journalpost&#39;.&lt;/li&gt;
 149  &lt;li&gt;Added support for some metadata codelists.&lt;/li&gt;
 150  &lt;li&gt;Added support for Cross-origin resource sharing (CORS).&lt;/li&gt;
 151  &lt;li&gt;Changed login method from Basic Auth to JSON Web Token (RFC 7519)
 152    style.&lt;/li&gt;
 153  &lt;li&gt;Added support for GET-ing ny-* URLs.&lt;/li&gt;
 154  &lt;li&gt;Added support for modifying entities using PUT and eTag.&lt;/li&gt;
 155  &lt;li&gt;Added support for returning XML output on request.&lt;/li&gt;
 156  &lt;li&gt;Removed support for English field and class names, limiting ourself
 157    to the official names.&lt;/li&gt;
 158  &lt;li&gt;...&lt;/li&gt;
 159
 160 &lt;/ul&gt;
 161
 162 &lt;p&gt;If this sound interesting to you, please contact us on IRC (#nikita
 163 on irc.freenode.net) or email
 164 (&lt;a href=&quot;https://lists.nuug.no/mailman/listinfo/nikita-noark&quot;&gt;nikita-noark
 165 mailing list).&lt;/p&gt;
 166 </description>
 167         </item>
 168
 169         <item>
 170                 <title>Idea for storing trusted timestamps in a Noark 5 archive</title>
 171                 <link>http://www.hungry.com/~pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html</link>
 172                 <guid isPermaLink="true">http://www.hungry.com/~pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html</guid>
 173                 <pubDate>Wed, 7 Jun 2017 21:40:00 +0200</pubDate>
 174                 <description>&lt;p&gt;&lt;em&gt;This is a copy of
 175 &lt;a href=&quot;https://lists.nuug.no/pipermail/nikita-noark/2017-June/000297.html&quot;&gt;an
 176 email I posted to the nikita-noark mailing list&lt;/a&gt;.  Please follow up
 177 there if you would like to discuss this topic.  The background is that
 178 we are making a free software archive system based on the Norwegian
 179 &lt;a href=&quot;https://www.arkivverket.no/forvaltning-og-utvikling/regelverk-og-standarder/noark-standarden&quot;&gt;Noark
 180 5 standard&lt;/a&gt; for government archives.&lt;/em&gt;&lt;/p&gt;
 181
 182 &lt;p&gt;I&#39;ve been wondering a bit lately how trusted timestamps could be
 183 stored in Noark 5.
 184 &lt;a href=&quot;https://en.wikipedia.org/wiki/Trusted_timestamping&quot;&gt;Trusted
 185 timestamps&lt;/a&gt; can be used to verify that some information
 186 (document/file/checksum/metadata) have not been changed since a
 187 specific time in the past.  This is useful to verify the integrity of
 188 the documents in the archive.&lt;/p&gt;
 189
 190 &lt;p&gt;Then it occured to me, perhaps the trusted timestamps could be
 191 stored as dokument variants (ie dokumentobjekt referered to from
 192 dokumentbeskrivelse) with the filename set to the hash it is
 193 stamping?&lt;/p&gt;
 194
 195 &lt;p&gt;Given a &quot;dokumentbeskrivelse&quot; with an associated &quot;dokumentobjekt&quot;,
 196 a new dokumentobjekt is associated with &quot;dokumentbeskrivelse&quot; with the
 197 same attributes as the stamped dokumentobjekt except these
 198 attributes:&lt;/p&gt;
 199
 200 &lt;ul&gt;
 201
 202 &lt;li&gt;format -&gt; &quot;RFC3161&quot;
 203 &lt;li&gt;mimeType -&gt; &quot;application/timestamp-reply&quot;
 204 &lt;li&gt;formatDetaljer -&gt; &quot;&amp;lt;source URL for timestamp service&amp;gt;&quot;
 205 &lt;li&gt;filenavn -&gt; &quot;&amp;lt;sjekksum&amp;gt;.tsr&quot;
 206
 207 &lt;/ul&gt;
 208
 209 &lt;p&gt;This assume a service following
 210 &lt;a href=&quot;https://tools.ietf.org/html/rfc3161&quot;&gt;IETF RFC 3161&lt;/a&gt; is
 211 used, which specifiy the given MIME type for replies and the .tsr file
 212 ending for the content of such trusted timestamp.  As far as I can
 213 tell from the Noark 5 specifications, it is OK to have several
 214 variants/renderings of a dokument attached to a given
 215 dokumentbeskrivelse objekt.  It might be stretching it a bit to make
 216 some of these variants represent crypto-signatures useful for
 217 verifying the document integrity instead of representing the dokument
 218 itself.&lt;/p&gt;
 219
 220 &lt;p&gt;Using the source of the service in formatDetaljer allow several
 221 timestamping services to be used.  This is useful to spread the risk
 222 of key compromise over several organisations.  It would only be a
 223 problem to trust the timestamps if all of the organisations are
 224 compromised.&lt;/p&gt;
 225
 226 &lt;p&gt;The following oneliner on Linux can be used to generate the tsr
 227 file.  $input is the path to the file to checksum, and $sha256 is the
 228 SHA-256 checksum of the file (ie the &quot;&lt;sjekksum&gt;.tsr&quot; value mentioned
 229 above).&lt;/p&gt;
 230
 231 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
 232 openssl ts -query -data &quot;$inputfile&quot; -cert -sha256 -no_nonce \
 233   | curl -s -H &quot;Content-Type: application/timestamp-query&quot; \
 234       --data-binary &quot;@-&quot; http://zeitstempel.dfn.de &gt; $sha256.tsr
 235 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 236
 237 &lt;p&gt;To verify the timestamp, you first need to download the public key
 238 of the trusted timestamp service, for example using this command:&lt;/p&gt;
 239
 240 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
 241 wget -O ca-cert.txt \
 242   https://pki.pca.dfn.de/global-services-ca/pub/cacert/chain.txt
 243 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 244
 245 &lt;p&gt;Note, the public key should be stored alongside the timestamps in
 246 the archive to make sure it is also available 100 years from now.  It
 247 is probably a good idea to standardise how and were to store such
 248 public keys, to make it easier to find for those trying to verify
 249 documents 100 or 1000 years from now. :)&lt;/p&gt;
 250
 251 &lt;p&gt;The verification itself is a simple openssl command:&lt;/p&gt;
 252
 253 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
 254 openssl ts -verify -data $inputfile -in $sha256.tsr \
 255   -CAfile ca-cert.txt -text
 256 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 257
 258 &lt;p&gt;Is there any reason this approach would not work?  Is it somehow against
 259 the Noark 5 specification?&lt;/p&gt;
 260 </description>
 261         </item>
 262
 263         <item>
 264                 <title>Når nynorskoversettelsen svikter til eksamen...</title>
 265                 <link>http://www.hungry.com/~pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</link>
 266                 <guid isPermaLink="true">http://www.hungry.com/~pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</guid>
 267                 <pubDate>Sat, 3 Jun 2017 08:20:00 +0200</pubDate>
 268                 <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
 269 melder i dag&lt;/a&gt; om feil i eksamensoppgavene for eksamen i politikk og
 270 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
 271 like.  Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
 272 på om den fri oversetterløsningen
 273 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium&lt;/a&gt; ville gjort en bedre
 274 jobb enn Utdanningsdirektoratet.  Det kan se slik ut.&lt;/p&gt;
 275
 276 &lt;p&gt;Her er bokmålsoppgaven fra eksamenen:&lt;/p&gt;
 277
 278 &lt;blockquote&gt;
 279 &lt;p&gt;Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
 280 rolle og muligheter til å håndtere internasjonale utfordringer, som
 281 for eksempel flykningekrisen.&lt;/p&gt;
 282
 283 &lt;p&gt;Vedlegge er eksempler på tekster som kan gi relevante perspektiver
 284 på temaet:&lt;/p&gt;
 285 &lt;ol&gt;
 286 &lt;li&gt;Flykningeregnskapet 2016, UNHCR og IDMC
 287 &lt;li&gt;«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
 288 &lt;/ol&gt;
 289
 290 &lt;/blockquote&gt;
 291
 292 &lt;p&gt;Dette oversetter Apertium slik:&lt;/p&gt;
 293
 294 &lt;blockquote&gt;
 295 &lt;p&gt;Drøft utfordringane knytte til nasjonalstatane sine og rolla til
 296 andre aktørar og høve til å handtera internasjonale utfordringar, som
 297 til dømes *flykningekrisen.&lt;/p&gt;
 298
 299 &lt;p&gt;Vedleggja er døme på tekster som kan gje relevante perspektiv på
 300 temaet:&lt;/p&gt;
 301
 302 &lt;ol&gt;
 303 &lt;li&gt;*Flykningeregnskapet 2016, *UNHCR og *IDMC&lt;/li&gt;
 304 &lt;li&gt;«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015&lt;/li&gt;
 305 &lt;/ol&gt;
 306
 307 &lt;/blockquote&gt;
 308
 309 &lt;p&gt;Ord som ikke ble forstått er markert med stjerne (*), og trenger
 310 ekstra språksjekk.  Men ingen ord er forsvunnet, slik det var i
 311 oppgaven elevene fikk presentert på eksamen.  Jeg mistenker dog at
 312 &quot;andre aktørers rolle og muligheter til ...&quot; burde vært oversatt til
 313 &quot;rolla til andre aktørar og deira høve til ...&quot; eller noe slikt, men
 314 det er kanskje flisespikking.  Det understreker vel bare at det alltid
 315 trengs korrekturlesning etter automatisk oversettelse.&lt;/p&gt;
 316 </description>
 317         </item>
 318
 319         </channel>
 320 </rss>