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://people.skolelinux.org/pere/blog/</link>
   7
   8
   9         <item>
  10                 <title>Release 0.1.1 of free software archive system Nikita announced</title>
  11                 <link>http://people.skolelinux.org/pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html</link>
  12                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html</guid>
  13                 <pubDate>Sat, 10 Jun 2017 00:40:00 +0200</pubDate>
  14                 <description>&lt;p&gt;I am very happy to report that the
  15 &lt;a href=&quot;https://github.com/hiOA-ABI/nikita-noark5-core&quot;&gt;Nikita Noark 5
  16 core project&lt;/a&gt; tagged its second release today.  The free software
  17 solution is an implementation of the Norwegian archive standard Noark
  18 5 used by government offices in Norway.  These were the changes in
  19 version 0.1.1 since version 0.1.0 (from NEWS.md):
  20
  21 &lt;ul&gt;
  22
  23  &lt;li&gt;Continued work on the angularjs GUI, including document upload.&lt;/li&gt;
  24  &lt;li&gt;Implemented correspondencepartPerson, correspondencepartUnit and
  25    correspondencepartInternal&lt;/li&gt;
  26  &lt;li&gt;Applied for coverity coverage and started submitting code on
  27    regualr basis.&lt;/li&gt;
  28  &lt;li&gt;Started fixing bugs reported by coverity&lt;/li&gt;
  29  &lt;li&gt;Corrected and completed HATEOAS links to make sure entire API is
  30    available via URLs in _links.&lt;/li&gt;
  31  &lt;li&gt;Corrected all relation URLs to use trailing slash.&lt;/li&gt;
  32  &lt;li&gt;Add initial support for storing data in ElasticSearch.&lt;/li&gt;
  33  &lt;li&gt;Now able to receive and store uploaded files in the archive.&lt;/li&gt;
  34  &lt;li&gt;Changed JSON output for object lists to have relations in _links.&lt;/li&gt;
  35  &lt;li&gt;Improve JSON output for empty object lists.&lt;/li&gt;
  36  &lt;li&gt;Now uses correct MIME type application/vnd.noark5-v4+json.&lt;/li&gt;
  37  &lt;li&gt;Added support for docker container images.&lt;/li&gt;
  38  &lt;li&gt;Added simple API browser implemented in JavaScript/Angular.&lt;/li&gt;
  39  &lt;li&gt;Started on archive client implemented in JavaScript/Angular.&lt;/li&gt;
  40  &lt;li&gt;Started on prototype to show the public mail journal.&lt;/li&gt;
  41  &lt;li&gt;Improved performance by disabling Sprint FileWatcher.&lt;/li&gt;
  42  &lt;li&gt;Added support for &#39;arkivskaper&#39;, &#39;saksmappe&#39; and &#39;journalpost&#39;.&lt;/li&gt;
  43  &lt;li&gt;Added support for some metadata codelists.&lt;/li&gt;
  44  &lt;li&gt;Added support for Cross-origin resource sharing (CORS).&lt;/li&gt;
  45  &lt;li&gt;Changed login method from Basic Auth to JSON Web Token (RFC 7519)
  46    style.&lt;/li&gt;
  47  &lt;li&gt;Added support for GET-ing ny-* URLs.&lt;/li&gt;
  48  &lt;li&gt;Added support for modifying entities using PUT and eTag.&lt;/li&gt;
  49  &lt;li&gt;Added support for returning XML output on request.&lt;/li&gt;
  50  &lt;li&gt;Removed support for English field and class names, limiting ourself
  51    to the official names.&lt;/li&gt;
  52  &lt;li&gt;...&lt;/li&gt;
  53
  54 &lt;/ul&gt;
  55
  56 &lt;p&gt;If this sound interesting to you, please contact us on IRC (#nikita
  57 on irc.freenode.net) or email
  58 (&lt;a href=&quot;https://lists.nuug.no/mailman/listinfo/nikita-noark&quot;&gt;nikita-noark
  59 mailing list).&lt;/p&gt;
  60 </description>
  61         </item>
  62
  63         <item>
  64                 <title>Idea for storing trusted timestamps in a Noark 5 archive</title>
  65                 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html</link>
  66                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html</guid>
  67                 <pubDate>Wed, 7 Jun 2017 21:40:00 +0200</pubDate>
  68                 <description>&lt;p&gt;&lt;em&gt;This is a copy of
  69 &lt;a href=&quot;https://lists.nuug.no/pipermail/nikita-noark/2017-June/000297.html&quot;&gt;an
  70 email I posted to the nikita-noark mailing list&lt;/a&gt;.  Please follow up
  71 there if you would like to discuss this topic.  The background is that
  72 we are making a free software archive system based on the Norwegian
  73 &lt;a href=&quot;https://www.arkivverket.no/forvaltning-og-utvikling/regelverk-og-standarder/noark-standarden&quot;&gt;Noark
  74 5 standard&lt;/a&gt; for government archives.&lt;/em&gt;&lt;/p&gt;
  75
  76 &lt;p&gt;I&#39;ve been wondering a bit lately how trusted timestamps could be
  77 stored in Noark 5.
  78 &lt;a href=&quot;https://en.wikipedia.org/wiki/Trusted_timestamping&quot;&gt;Trusted
  79 timestamps&lt;/a&gt; can be used to verify that some information
  80 (document/file/checksum/metadata) have not been changed since a
  81 specific time in the past.  This is useful to verify the integrity of
  82 the documents in the archive.&lt;/p&gt;
  83
  84 &lt;p&gt;Then it occured to me, perhaps the trusted timestamps could be
  85 stored as dokument variants (ie dokumentobjekt referered to from
  86 dokumentbeskrivelse) with the filename set to the hash it is
  87 stamping?&lt;/p&gt;
  88
  89 &lt;p&gt;Given a &quot;dokumentbeskrivelse&quot; with an associated &quot;dokumentobjekt&quot;,
  90 a new dokumentobjekt is associated with &quot;dokumentbeskrivelse&quot; with the
  91 same attributes as the stamped dokumentobjekt except these
  92 attributes:&lt;/p&gt;
  93
  94 &lt;ul&gt;
  95
  96 &lt;li&gt;format -&gt; &quot;RFC3161&quot;
  97 &lt;li&gt;mimeType -&gt; &quot;application/timestamp-reply&quot;
  98 &lt;li&gt;formatDetaljer -&gt; &quot;&amp;lt;source URL for timestamp service&amp;gt;&quot;
  99 &lt;li&gt;filenavn -&gt; &quot;&amp;lt;sjekksum&amp;gt;.tsr&quot;
 100
 101 &lt;/ul&gt;
 102
 103 &lt;p&gt;This assume a service following
 104 &lt;a href=&quot;https://tools.ietf.org/html/rfc3161&quot;&gt;IETF RFC 3161&lt;/a&gt; is
 105 used, which specifiy the given MIME type for replies and the .tsr file
 106 ending for the content of such trusted timestamp.  As far as I can
 107 tell from the Noark 5 specifications, it is OK to have several
 108 variants/renderings of a dokument attached to a given
 109 dokumentbeskrivelse objekt.  It might be stretching it a bit to make
 110 some of these variants represent crypto-signatures useful for
 111 verifying the document integrity instead of representing the dokument
 112 itself.&lt;/p&gt;
 113
 114 &lt;p&gt;Using the source of the service in formatDetaljer allow several
 115 timestamping services to be used.  This is useful to spread the risk
 116 of key compromise over several organisations.  It would only be a
 117 problem to trust the timestamps if all of the organisations are
 118 compromised.&lt;/p&gt;
 119
 120 &lt;p&gt;The following oneliner on Linux can be used to generate the tsr
 121 file.  $input is the path to the file to checksum, and $sha256 is the
 122 SHA-256 checksum of the file (ie the &quot;&lt;sjekksum&gt;.tsr&quot; value mentioned
 123 above).&lt;/p&gt;
 124
 125 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
 126 openssl ts -query -data &quot;$inputfile&quot; -cert -sha256 -no_nonce \
 127   | curl -s -H &quot;Content-Type: application/timestamp-query&quot; \
 128       --data-binary &quot;@-&quot; http://zeitstempel.dfn.de &gt; $sha256.tsr
 129 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 130
 131 &lt;p&gt;To verify the timestamp, you first need to download the public key
 132 of the trusted timestamp service, for example using this command:&lt;/p&gt;
 133
 134 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
 135 wget -O ca-cert.txt \
 136   https://pki.pca.dfn.de/global-services-ca/pub/cacert/chain.txt
 137 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 138
 139 &lt;p&gt;Note, the public key should be stored alongside the timestamps in
 140 the archive to make sure it is also available 100 years from now.  It
 141 is probably a good idea to standardise how and were to store such
 142 public keys, to make it easier to find for those trying to verify
 143 documents 100 or 1000 years from now. :)&lt;/p&gt;
 144
 145 &lt;p&gt;The verification itself is a simple openssl command:&lt;/p&gt;
 146
 147 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
 148 openssl ts -verify -data $inputfile -in $sha256.tsr \
 149   -CAfile ca-cert.txt -text
 150 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 151
 152 &lt;p&gt;Is there any reason this approach would not work?  Is it somehow against
 153 the Noark 5 specification?&lt;/p&gt;
 154 </description>
 155         </item>
 156
 157         <item>
 158                 <title>Når nynorskoversettelsen svikter til eksamen...</title>
 159                 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</link>
 160                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</guid>
 161                 <pubDate>Sat, 3 Jun 2017 08:20:00 +0200</pubDate>
 162                 <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
 163 melder i dag&lt;/a&gt; om feil i eksamensoppgavene for eksamen i politikk og
 164 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
 165 like.  Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
 166 på om den fri oversetterløsningen
 167 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium&lt;/a&gt; ville gjort en bedre
 168 jobb enn Utdanningsdirektoratet.  Det kan se slik ut.&lt;/p&gt;
 169
 170 &lt;p&gt;Her er bokmålsoppgaven fra eksamenen:&lt;/p&gt;
 171
 172 &lt;blockquote&gt;
 173 &lt;p&gt;Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
 174 rolle og muligheter til å håndtere internasjonale utfordringer, som
 175 for eksempel flykningekrisen.&lt;/p&gt;
 176
 177 &lt;p&gt;Vedlegge er eksempler på tekster som kan gi relevante perspektiver
 178 på temaet:&lt;/p&gt;
 179 &lt;ol&gt;
 180 &lt;li&gt;Flykningeregnskapet 2016, UNHCR og IDMC
 181 &lt;li&gt;«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
 182 &lt;/ol&gt;
 183
 184 &lt;/blockquote&gt;
 185
 186 &lt;p&gt;Dette oversetter Apertium slik:&lt;/p&gt;
 187
 188 &lt;blockquote&gt;
 189 &lt;p&gt;Drøft utfordringane knytte til nasjonalstatane sine og rolla til
 190 andre aktørar og høve til å handtera internasjonale utfordringar, som
 191 til dømes *flykningekrisen.&lt;/p&gt;
 192
 193 &lt;p&gt;Vedleggja er døme på tekster som kan gje relevante perspektiv på
 194 temaet:&lt;/p&gt;
 195
 196 &lt;ol&gt;
 197 &lt;li&gt;*Flykningeregnskapet 2016, *UNHCR og *IDMC&lt;/li&gt;
 198 &lt;li&gt;«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015&lt;/li&gt;
 199 &lt;/ol&gt;
 200
 201 &lt;/blockquote&gt;
 202
 203 &lt;p&gt;Ord som ikke ble forstått er markert med stjerne (*), og trenger
 204 ekstra språksjekk.  Men ingen ord er forsvunnet, slik det var i
 205 oppgaven elevene fikk presentert på eksamen.  Jeg mistenker dog at
 206 &quot;andre aktørers rolle og muligheter til ...&quot; burde vært oversatt til
 207 &quot;rolla til andre aktørar og deira høve til ...&quot; eller noe slikt, men
 208 det er kanskje flisespikking.  Det understreker vel bare at det alltid
 209 trengs korrekturlesning etter automatisk oversettelse.&lt;/p&gt;
 210 </description>
 211         </item>
 212
 213         </channel>
 214 </rss>