blog/archive/2014/03/index.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2           "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr">
   4   <head>
   5     <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
   6     <title>Petter Reinholdtsen: entries from March 2014</title>
   7     <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/style.css" />
   8     <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/vim.css" />
   9     <link rel="alternate" title="RSS Feed" href="03.rss" type="application/rss+xml" />
  10   </head>
  11   <body>
  12     <!-- XML FEED -->
  13     <div class="title">
  14  <h1>
  15      <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
  16
  17  </h1>
  18
  19 </div>
  20
  21
  22     <h3>Entries from March 2014.</h3>
  23
  24     <div class="entry">
  25       <div class="title">
  26         <a href="http://people.skolelinux.org/pere/blog/Public_Trusted_Timestamping_services_for_everyone.html">Public Trusted Timestamping services for everyone</a>
  27       </div>
  28       <div class="date">
  29         25th March 2014
  30       </div>
  31       <div class="body">
  32         <p>Did you ever need to store logs or other files in a way that would
  33 allow it to be used as evidence in court, and needed a way to
  34 demonstrate without reasonable doubt that the file had not been
  35 changed since it was created?  Or, did you ever need to document that
  36 a given document was received at some point in time, like some
  37 archived document or the answer to an exam, and not changed after it
  38 was received?  The problem in these settings is to remove the need to
  39 trust yourself and your computers, while still being able to prove
  40 that a file is the same as it was at some given time in the past.</p>
  41
  42 <p>A solution to these problems is to have a trusted third party
  43 "stamp" the document and verify that at some given time the document
  44 looked a given way.  Such
  45 <a href="https://en.wikipedia.org/wiki/Notarius">notarius</a> service
  46 have been around for thousands of years, and its digital equivalent is
  47 called a
  48 <a href="http://en.wikipedia.org/wiki/Trusted_timestamping">trusted
  49 timestamping service</a>.  <a href="http://www.ietf.org/">The Internet
  50 Engineering Task Force</a> standardised how such service could work a
  51 few years ago as <a href="http://tools.ietf.org/html/rfc3161">RFC
  52 3161</a>.  The mechanism is simple.  Create a hash of the file in
  53 question, send it to a trusted third party which add a time stamp to
  54 the hash and sign the result with its private key, and send back the
  55 signed hash + timestamp.  Anyone with the document and the signature
  56 can then verify that the document matches the signature by creating
  57 their own hash and checking the signature using the trusted third
  58 party public key.  There are several commercial services around
  59 providing such timestamping.  A quick search for
  60 "<a href="https://duckduckgo.com/?q=rfc+3161+service">rfc 3161
  61 service</a>" pointed me to at least
  62 <a href="https://www.digistamp.com/technical/how-a-digital-time-stamp-works/">DigiStamp</a>,
  63 <a href="http://www.quovadisglobal.co.uk/CertificateServices/SigningServices/TimeStamp.aspx">Quo
  64 Vadis</a>,
  65 <a href="https://www.globalsign.com/timestamp-service/">Global Sign</a>
  66 and <a href="http://www.globaltrustfinder.com/TSADefault.aspx">Global
  67 Trust Finder</a>.  The system work as long as the private key of the
  68 trusted third party is not compromised.</p>
  69
  70 <p>But as far as I can tell, there are very few public trusted
  71 timestamp services available for everyone.  I've been looking for one
  72 for a while now. But yesterday I found one over at
  73 <a href="https://www.pki.dfn.de/zeitstempeldienst/">Deutches
  74 Forschungsnetz</a>mentioned in
  75 <a href="http://www.d-mueller.de/blog/dealing-with-trusted-timestamps-in-php-rfc-3161/">a
  76 blog by David Müller</a>.  I then found a good recipe on how to use
  77 over at the
  78 <a href="http://www.rz.uni-greifswald.de/support/dfn-pki-zertifikate/zeitstempeldienst.html">University
  79 of Greifswald</a>.  The OpenSSL library contain both server and tools
  80 to use and set up your own signing service.  See the ts(1SSL),
  81 tsget(1SSL) manual pages for more details.  The following shell script
  82 demonstrate how to extract a signed timestamp for any file on the disk
  83 in a Debian environment:
  84
  85 <p><blockquote><pre>
  86 #!/bin/sh
  87 set -e
  88 url="http://zeitstempel.dfn.de"
  89 caurl="https://pki.pca.dfn.de/global-services-ca/pub/cacert/chain.txt"
  90 reqfile=$(mktemp -t tmp.XXXXXXXXXX.tsq)
  91 resfile=$(mktemp -t tmp.XXXXXXXXXX.tsr)
  92 cafile=chain.txt
  93 if [ ! -f $cafile ] ; then
  94     wget -O $cafile "$caurl"
  95 fi
  96 openssl ts -query -data "$1" -cert | tee "$reqfile" \
  97     | /usr/lib/ssl/misc/tsget -h "$url" -o "$resfile"
  98 openssl ts -reply -in "$resfile" -text 1>&2
  99 openssl ts -verify -data "$1" -in "$resfile" -CAfile "$cafile" 1>&2
 100 base64 < "$resfile"
 101 rm "$reqfile" "$resfile"
 102 </pre></blockquote></p>
 103
 104 <p>The argument to the script is the file to timestamp, and the output
 105 is a base64 encoded version of the signature to STDOUT and details
 106 about the signature to STDERR.  Note that due to
 107 <a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742553">a bug
 108 in the tsget script</a>, you might need to modify the included script
 109 and remove the last line.  Or just write your own HTTP uploader using
 110 curl. :) Now you too can prove and verify that files have not been
 111 changed.</p>
 112
 113 <p>But the Internet need more public trusted timestamp services.
 114 Perhaps something for <a href="http://www.uninett.no/">Uninett</a> or
 115 my work place the <a href="http://www.uio.no/">University of Oslo</a>
 116 to set up?</p>
 117
 118       </div>
 119       <div class="tags">
 120
 121
 122         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>.
 123
 124
 125       </div>
 126     </div>
 127     <div class="padding"></div>
 128
 129     <div class="entry">
 130       <div class="title">
 131         <a href="http://people.skolelinux.org/pere/blog/Video_DVD_reader_library___python_dvdvideo___nice_free_software.html">Video DVD reader library / python-dvdvideo - nice free software</a>
 132       </div>
 133       <div class="date">
 134         21st March 2014
 135       </div>
 136       <div class="body">
 137         <p>Keeping your DVD collection safe from scratches and curious
 138 children fingers while still having it available when you want to see a
 139 movie is not straight forward.  My preferred method at the moment is
 140 to store a full copy of the ISO on a hard drive, and use VLC, Popcorn
 141 Hour or other useful players to view the resulting file.  This way the
 142 subtitles and bonus material are still available and using the ISO is
 143 just like inserting the original DVD record in the DVD player.</p>
 144
 145 <p>Earlier I used dd for taking security copies, but it do not handle
 146 DVDs giving read errors (which are quite a few of them).  I've also
 147 tried using
 148 <a href="http://people.skolelinux.org/pere/blog/Ripping_problematic_DVDs_using_dvdbackup_and_genisoimage.html">dvdbackup
 149 and genisoimage</a>, but these days I use the marvellous python library
 150 and program
 151 <a href="http://bblank.thinkmo.de/blog/new-software-python-dvdvideo">python-dvdvideo</a>
 152 written by Bastian Blank.  It is
 153 <a href="http://packages.qa.debian.org/p/python-dvdvideo.html">in Debian
 154 already</a> and the binary package name is python3-dvdvideo. Instead
 155 of trying to read every block from the DVD, it parses the file
 156 structure and figure out which block on the DVD is actually in used,
 157 and only read those blocks from the DVD.  This work surprisingly well,
 158 and I have been able to almost backup my entire DVD collection using
 159 this method.</p> So far, python-dvdvideo have failed on between 10 and
 160 20 DVDs, which is a small fraction of my collection.  The most common
 161 problem is
 162 <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720831">DVDs
 163 using UTF-16 instead of UTF-8 characters</a>, which according to
 164 Bastian is against the DVD specification (and seem to cause some
 165 players to fail too).  A rarer problem is what seem to be inconsistent
 166 DVD structures, as the python library
 167 <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723079">claim
 168 there is a overlap between objects</a>.  An equally rare problem claim
 169 <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741878">some
 170 value is out of range</a>.  No idea what is going on there.  I wish I
 171 knew enough about the DVD format to fix these, to ensure my movie
 172 collection will stay with me in the future.</p>
 173
 174 <p>So, if you need to keep your DVDs safe, back them up using
 175 python-dvdvideo. :)</p>
 176
 177       </div>
 178       <div class="tags">
 179
 180
 181         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
 182
 183
 184       </div>
 185     </div>
 186     <div class="padding"></div>
 187
 188     <div class="entry">
 189       <div class="title">
 190         <a href="http://people.skolelinux.org/pere/blog/Norsk_utgave_av_Alaveteli___WhatDoTheyKnow_p__trappene.html">Norsk utgave av Alaveteli / WhatDoTheyKnow på trappene</a>
 191       </div>
 192       <div class="date">
 193         16th March 2014
 194       </div>
 195       <div class="body">
 196         <p>Det offentlige Norge har mye kunnskap og informasjon.  Men hvordan
 197 kan en få tilgang til den på en enkel måte?  Takket være et lite
 198 knippe lover og tilhørende forskrifter, blant annet
 199 <a href="http://lovdata.no/dokument/NL/lov/2006-05-19-16">offentlighetsloven</a>,
 200 <a href="http://lovdata.no/dokument/NL/lov/2003-05-09-31">miljøinformasjonsloven</a>
 201 og
 202 <a href="http://lovdata.no/dokument/NL/lov/1967-02-10/">forvaltningsloven</a>
 203 har en rett til å spørre det offentlige og få svar.  Men det finnes
 204 intet offentlig arkiv over hva andre har spurt om, og dermed risikerer en
 205 å måtte forstyrre myndighetene gang på gang for å få tak i samme
 206 informasjonen på nytt.  <a href="http://www.mysociety.org/">Britiske
 207 mySociety</a> har laget tjenesten
 208 <a href="http://www.whatdotheyknow.com/">WhatDoTheyKnow</a> som gjør
 209 noe med dette.  I Storbritannia blir WhatdoTheyKnow brukt i
 210 <a href="http://www.mysociety.org/2011/07/01/whatdotheyknows-share-of-central-government-foi-requests-q2-2011/">ca
 211 15% av alle innsynsforespørsler mot sentraladministrasjonen</a>.
 212 Prosjektet heter <a href="http://www.alaveteli.org/">Alaveteli</A>, og
 213 er takk i bruk en rekke steder etter at løsningen ble generalisert og
 214 gjort mulig å oversette.  Den hjelper borgerne med å be om innsyn,
 215 rådgir ved purringer og klager og lar alle se hvilke henvendelser som
 216 er sendt til det offentlige og hvilke svar som er kommet inn, i et
 217 søkpart arkiv.  Her i Norge holder vi i foreningen NUUG på å få opp en
 218 norsk utgave av Alaveteli, og her trenger vi din hjelp med
 219 oversettelsen.</p>
 220
 221 <p>Så langt er 76 % av Alaveteli oversatt til norsk bokmål, men vi
 222 skulle gjerne vært oppe i 100 % før lansering.  Oversettelsen gjøres
 223 på <a href="https://www.transifex.com/projects/p/alaveteli/">Transifex,
 224 der enhver som registrerer seg</a> og ber om tilgang til
 225 bokmålsoversettelsen får bidra.  Vi har satt opp en test av tjenesten
 226 (som ikke sender epost til det offentlige, kun til oss som holder på å
 227 sette opp tjenesten) på maskinen
 228 <a href="http://alaveteli-dev.nuug.no/">alaveteli-dev.nuug.no</a>, der
 229 en kan se hvordan de oversatte meldingen blir seende ut på nettsiden.
 230 Når tjenesten lanseres vil den hete
 231 <a href="https://www.mimesbrønn.no/">Mimes brønn</a>, etter
 232 visdomskilden som Odin måtte gi øyet sitt for å få drikke i.  Den
 233 nettsiden er er ennå ikke klar til bruk.</p>
 234
 235 <p>Hvis noen vil oversette til nynorsk også, så skal vi finne ut
 236 hvordan vi lager en flerspråklig tjeneste.  Men i første omgang er
 237 fokus på bokmålsoversettelsen, der vi selv har nok peiling til å ha
 238 fått oversatt 76%, men trenger hjelp for å komme helt i mål. :)</p>
 239
 240       </div>
 241       <div class="tags">
 242
 243
 244         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>.
 245
 246
 247       </div>
 248     </div>
 249     <div class="padding"></div>
 250
 251     <div class="entry">
 252       <div class="title">
 253         <a href="http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html">Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</a>
 254       </div>
 255       <div class="date">
 256         14th March 2014
 257       </div>
 258       <div class="body">
 259         <p>The <a href="https://wiki.debian.org/FreedomBox">Freedombox
 260 project</a> is working on providing the software and hardware for
 261 making it easy for non-technical people to host their data and
 262 communication at home, and being able to communicate with their
 263 friends and family encrypted and away from prying eyes.  It has been
 264 going on for a while, and is slowly progressing towards a new test
 265 release (0.2).</p>
 266
 267 <p>And what day could be better than the Pi day to announce that the
 268 new version will provide "hard drive" / SD card / USB stick images for
 269 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
 270 system), and can also be installed using a Debian installer preseed
 271 file.  The Debian based Freedombox is now based on Debian Jessie,
 272 where most of the needed packages used are already present.  Only one,
 273 the freedombox-setup package, is missing.  To try to build your own
 274 boot image to test the current status, fetch the freedom-maker scripts
 275 and build using
 276 <a href="http://packages.qa.debian.org/vmdebootstrap">vmdebootstrap</a>
 277 with a user with sudo access to become root:
 278
 279 <pre>
 280 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
 281   freedom-maker
 282 sudo apt-get install git vmdebootstrap mercurial python-docutils \
 283   mktorrent extlinux virtualbox qemu-user-static binfmt-support \
 284   u-boot-tools
 285 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
 286 </pre>
 287
 288 <p>Root access is needed to run debootstrap and mount loopback
 289 devices.  See the README for more details on the build. If you do not
 290 want all three images, trim the make line.  But note that thanks to <a
 291 href="https://bugs.debian.org/741407">a race condition in
 292 vmdebootstrap</a>, the build might fail without the patch to the
 293 kpartx call.</p>
 294
 295 <p>If you instead want to install using a Debian CD and the preseed
 296 method, boot a Debian Wheezy ISO and use this boot argument to load
 297 the preseed values:</p>
 298
 299 <pre>
 300 url=<a href="http://www.reinholdtsen.name/freedombox/preseed-jessie.dat">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat</a>
 301 </pre>
 302
 303 <p>But note that due to <a href="https://bugs.debian.org/740673">a
 304 recently introduced bug in apt in Jessie</a>, the installer will
 305 currently hang while setting up APT sources.  Killing the
 306 '<tt>apt-cdrom ident</tt>' process when it hang a few times during the
 307 installation will get the installation going.  This affect all
 308 installations in Jessie, and I expect it will be fixed soon.</p>
 309
 310 Give it a go and let us know how it goes on the mailing list, and help
 311 us get the new release published. :) Please join us on
 312 <a href="irc://irc.debian.org:6667/%23freedombox">IRC (#freedombox on
 313 irc.debian.org)</a> and
 314 <a href="http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss">the
 315 mailing list</a> if you want to help make this vision come true.</p>
 316
 317       </div>
 318       <div class="tags">
 319
 320
 321         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
 322
 323
 324       </div>
 325     </div>
 326     <div class="padding"></div>
 327
 328     <div class="entry">
 329       <div class="title">
 330         <a href="http://people.skolelinux.org/pere/blog/How_to_add_extra_storage_servers_in_Debian_Edu___Skolelinux.html">How to add extra storage servers in Debian Edu / Skolelinux</a>
 331       </div>
 332       <div class="date">
 333         12th March 2014
 334       </div>
 335       <div class="body">
 336         <p>On larger sites, it is useful to use a dedicated storage server for
 337 storing user home directories and data.  The design for handling this
 338 in <a href="http://www.skolelinux.org/">Debian Edu / Skolelinux</a>, is
 339 to update the automount rules in LDAP and let the automount daemon on
 340 the clients take care of the rest.  I was reminded about the need to
 341 document this better when one of the customers of
 342 <a href="http://www.slxdrift.no/">Skolelinux Drift AS</a>, where I am
 343 on the board of directors, asked about how to do this.  The steps to
 344 get this working are the following:</p>
 345
 346 <p><ol>
 347
 348 <li>Add new storage server in DNS.  I use nas-server.intern as the
 349 example host here.</li>
 350
 351 <li>Add automoun LDAP information about this server in LDAP, to allow
 352 all clients to automatically mount it on reqeust.</li>
 353
 354 <li>Add the relevant entries in tjener.intern:/etc/fstab, because
 355 tjener.intern do not use automount to avoid mounting loops.</li>
 356
 357 </ol></p>
 358
 359 <p>DNS entries are added in GOsa², and not described here.  Follow the
 360 <a href="https://wiki.debian.org/DebianEdu/Documentation/Wheezy/GettingStarted">instructions
 361 in the manual</a> (Machine Management with GOsa² in section Getting
 362 started).</p>
 363
 364 <p>Ensure that the NFS export points on the server are exported to the
 365 relevant subnets or machines:</p>
 366
 367 <p><blockquote><pre>
 368 root@tjener:~# showmount -e nas-server
 369 Export list for nas-server:
 370 /storage         10.0.0.0/8
 371 root@tjener:~#
 372 </pre></blockquote></p>
 373
 374 <p>Here everything on the backbone network is granted access to the
 375 /storage export.  With NFSv3 it is slightly better to limit it to
 376 netgroup membership or single IP addresses to have some limits on the
 377 NFS access.</p>
 378
 379 <p>The next step is to update LDAP.  This can not be done using GOsa²,
 380 because it lack a module for automount.  Instead, use ldapvi and add
 381 the required LDAP objects using an editor.</p>
 382
 383 <p><blockquote><pre>
 384 ldapvi --ldap-conf -ZD '(cn=admin)' -b ou=automount,dc=skole,dc=skolelinux,dc=no
 385 </pre></blockquote></p>
 386
 387 <p>When the editor show up, add the following LDAP objects at the
 388 bottom of the document.  The "/&" part in the last LDAP object is a
 389 wild card matching everything the nas-server exports, removing the
 390 need to list individual mount points in LDAP.</p>
 391
 392 <p><blockquote><pre>
 393 add cn=nas-server,ou=auto.skole,ou=automount,dc=skole,dc=skolelinux,dc=no
 394 objectClass: automount
 395 cn: nas-server
 396 automountInformation: -fstype=autofs --timeout=60 ldap:ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no
 397
 398 add ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no
 399 objectClass: top
 400 objectClass: automountMap
 401 ou: auto.nas-server
 402
 403 add cn=/,ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no
 404 objectClass: automount
 405 cn: /
 406 automountInformation: -fstype=nfs,tcp,rsize=32768,wsize=32768,rw,intr,hard,nodev,nosuid,noatime nas-server.intern:/&
 407 </pre></blockquote></p>
 408
 409 <p>The last step to remember is to mount the relevant mount points in
 410 tjener.intern by adding them to /etc/fstab, creating the mount
 411 directories using mkdir and running "mount -a" to mount them.</p>
 412
 413 <p>When this is done, your users should be able to access the files on
 414 the storage server directly by just visiting the
 415 /tjener/nas-server/storage/ directory using any application on any
 416 workstation, LTSP client or LTSP server.</p>
 417
 418       </div>
 419       <div class="tags">
 420
 421
 422         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap</a>.
 423
 424
 425       </div>
 426     </div>
 427     <div class="padding"></div>
 428
 429     <div class="entry">
 430       <div class="title">
 431         <a href="http://people.skolelinux.org/pere/blog/Hvordan_b_r_RFC_822_formattert_epost_lagres_i_en_NOARK5_database_.html">Hvordan bør RFC 822-formattert epost lagres i en NOARK5-database?</a>
 432       </div>
 433       <div class="date">
 434          7th March 2014
 435       </div>
 436       <div class="body">
 437         <p>For noen uker siden ble NXCs fri programvarelisenserte
 438 NOARK5-løsning
 439 <a href="http://www.nuug.no/aktiviteter/20140211-noark/">presentert hos
 440 NUUG</a> (video
 441 <a href="https://www.youtube.com/watch?v=JCb_dNS3MHQ">på youtube
 442 foreløbig</a>), og det fikk meg til å titte litt mer på NOARK5,
 443 standarden for arkivhåndtering i det offentlige Norge.  Jeg lurer på
 444 om denne kjernen kan være nyttig i et par av mine prosjekter, og for ett
 445 av dem er det mest aktuelt å lagre epost.  Jeg klarte ikke finne noen
 446 anbefaling om hvordan RFC 822-formattert epost (aka Internett-epost)
 447 burde lagres i NOARK5, selv om jeg vet at noen arkiver tar
 448 PDF-utskrift av eposten med sitt epostprogram og så arkiverer PDF-en
 449 (eller enda værre, tar papirutskrift og lagrer bildet av eposten som
 450 PDF i arkivet).</p>
 451
 452 <p>Det er ikke så mange formater som er akseptert av riksarkivet til
 453 langtidsoppbevaring av offentlige arkiver, og PDF og XML er de mest
 454 aktuelle i så måte.  Det slo meg at det måtte da finnes en eller annen
 455 egnet XML-representasjon og at det kanskje var enighet om hvilken som
 456 burde brukes, så jeg tok mot til meg og spurte
 457 <a href="http://samdok.com/">SAMDOK</a>, en gruppe tilknyttet
 458 arkivverket som ser ut til å jobbe med NOARK-samhandling, om de hadde
 459 noen anbefalinger:
 460
 461 <p><blockquote>
 462 <p>Hei.</p>
 463
 464 <p>Usikker på om dette er riktig forum å ta opp mitt spørsmål, men jeg
 465 lurer på om det er definert en anbefaling om hvordan RFC
 466 822-formatterte epost (aka vanlig Internet-epost) bør lages håndteres
 467 i NOARK5, slik at en bevarer all informasjon i eposten
 468 (f.eks. Received-linjer).  Finnes det en anbefalt XML-mapping ala den
 469 som beskrives på
 470 &lt;URL: <a href="https://www.informit.com/articles/article.aspx?p=32074">https://www.informit.com/articles/article.aspx?p=32074</a> &gt;?  Mitt
 471 mål er at det skal være mulig å lagre eposten i en NOARK5-kjerne og
 472 kunne få ut en identisk formattert kopi av opprinnelig epost ved
 473 behov.</p>
 474 </blockquote></p>
 475
 476 <p>Postmottaker hos SAMDOK mente spørsmålet heller burde stilles
 477 direkte til riksarkivet, og jeg fikk i dag svar derfra formulert av
 478 seniorrådgiver Geir Ivar Tungesvik:</p>
 479
 480 <p><blockquote>
 481 <p>Riksarkivet har ingen anbefalinger når det gjelder konvertering fra
 482 e-post til XML.  Det står arkivskaper fritt å eventuelt definere/bruke
 483 eget format.  Inklusive da - som det spørres om - et format der det er
 484 mulig å re-etablere e-post format ut fra XML-en.  XML (e-post)
 485 dokumenter må være referert i arkivstrukturen, og det må vedlegges et
 486 gyldig XML skjema (.xsd) for XML-filene. Arkivskaper står altså fritt
 487 til å gjøre hva de vil, bare det dokumenteres og det kan dannes et
 488 utrekk ved avlevering til depot.</p>
 489
 490 <p>De obligatoriske kravene i Noark 5 standarden må altså oppfylles -
 491 etter dialog med Riksarkivet i forbindelse med godkjenning. For
 492 offentlige arkiv er det særlig viktig med filene loependeJournal.xml
 493 og offentligJournal.xml. Private arkiv som vil forholde seg til Noark
 494 5 standarden er selvsagt frie til å bruke det som er relevant for dem
 495 av obligatoriske krav.</p>
 496 </blockquote></p>
 497
 498 <p>Det ser dermed ut for meg som om det er et lite behov for å
 499 standardisere XML-lagring av RFC-822-formatterte meldinger.  Noen som
 500 vet om god spesifikasjon i så måte?  I tillegg til den omtalt over,
 501 har jeg kommet over flere aktuelle beskrivelser (søk på "rfc 822
 502 xml", så finner du aktuelle alternativer).</p>
 503
 504 <ul>
 505
 506 <li><a href="http://www.openhealth.org/xmtp/">XML MIME Transformation
 507 protocol (XMTP)</a> fra OpenHealth, sist oppdatert 2001.</li>
 508
 509 <li><a href="https://tools.ietf.org/html/draft-klyne-message-rfc822-xml-03">An
 510 XML format for mail and other messages</a> utkast fra IETF datert
 511 2001.</li>
 512
 513 <li><a href="http://www.informit.com/articles/article.aspx?p=32074">xMail:
 514 E-mail as XML</a> en artikkel fra 2003 som beskriver python-modulen
 515 rfc822 som gir ut XML-representasjon av en RFC 822-formattert epost.</li>
 516
 517 </ul>
 518
 519 <p>Finnes det andre og bedre spesifikasjoner for slik lagring?  Send
 520 meg en epost hvis du har innspill.</p>
 521
 522       </div>
 523       <div class="tags">
 524
 525
 526         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>.
 527
 528
 529       </div>
 530     </div>
 531     <div class="padding"></div>
 532
 533     <p style="text-align: right;"><a href="03.rss"><img src="http://people.skolelinux.org/pere/blog/xml.gif" alt="RSS Feed" width="36" height="14" /></a></p>
 534     <div id="sidebar">
 535
 536
 537
 538 <h2>Archive</h2>
 539 <ul>
 540
 541 <li>2014
 542 <ul>
 543
 544 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
 545
 546 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
 547
 548 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/03/">March (6)</a></li>
 549
 550 </ul></li>
 551
 552 <li>2013
 553 <ul>
 554
 555 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
 556
 557 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
 558
 559 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
 560
 561 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
 562
 563 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
 564
 565 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
 566
 567 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
 568
 569 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
 570
 571 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
 572
 573 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
 574
 575 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
 576
 577 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
 578
 579 </ul></li>
 580
 581 <li>2012
 582 <ul>
 583
 584 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
 585
 586 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
 587
 588 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
 589
 590 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
 591
 592 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
 593
 594 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
 595
 596 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
 597
 598 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
 599
 600 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
 601
 602 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
 603
 604 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
 605
 606 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
 607
 608 </ul></li>
 609
 610 <li>2011
 611 <ul>
 612
 613 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
 614
 615 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
 616
 617 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
 618
 619 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
 620
 621 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
 622
 623 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
 624
 625 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
 626
 627 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
 628
 629 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
 630
 631 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
 632
 633 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
 634
 635 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
 636
 637 </ul></li>
 638
 639 <li>2010
 640 <ul>
 641
 642 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
 643
 644 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
 645
 646 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
 647
 648 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
 649
 650 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
 651
 652 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
 653
 654 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
 655
 656 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
 657
 658 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
 659
 660 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
 661
 662 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
 663
 664 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
 665
 666 </ul></li>
 667
 668 <li>2009
 669 <ul>
 670
 671 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
 672
 673 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
 674
 675 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
 676
 677 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
 678
 679 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
 680
 681 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
 682
 683 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
 684
 685 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
 686
 687 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
 688
 689 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
 690
 691 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
 692
 693 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
 694
 695 </ul></li>
 696
 697 <li>2008
 698 <ul>
 699
 700 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
 701
 702 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
 703
 704 </ul></li>
 705
 706 </ul>
 707
 708
 709
 710 <h2>Tags</h2>
 711 <ul>
 712
 713  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
 714
 715  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
 716
 717  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
 718
 719  <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
 720
 721  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (8)</a></li>
 722
 723  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (14)</a></li>
 724
 725  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
 726
 727  <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
 728
 729  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (95)</a></li>
 730
 731  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (145)</a></li>
 732
 733  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
 734
 735  <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (10)</a></li>
 736
 737  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
 738
 739  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (240)</a></li>
 740
 741  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (21)</a></li>
 742
 743  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
 744
 745  <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (12)</a></li>
 746
 747  <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (6)</a></li>
 748
 749  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (11)</a></li>
 750
 751  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (39)</a></li>
 752
 753  <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (7)</a></li>
 754
 755  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (18)</a></li>
 756
 757  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
 758
 759  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (7)</a></li>
 760
 761  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
 762
 763  <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (7)</a></li>
 764
 765  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (26)</a></li>
 766
 767  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (242)</a></li>
 768
 769  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (162)</a></li>
 770
 771  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (11)</a></li>
 772
 773  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
 774
 775  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (46)</a></li>
 776
 777  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (69)</a></li>
 778
 779  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
 780
 781  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
 782
 783  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (2)</a></li>
 784
 785  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (9)</a></li>
 786
 787  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
 788
 789  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
 790
 791  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
 792
 793  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (36)</a></li>
 794
 795  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
 796
 797  <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (4)</a></li>
 798
 799  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (44)</a></li>
 800
 801  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (3)</a></li>
 802
 803  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (9)</a></li>
 804
 805  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (22)</a></li>
 806
 807  <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (1)</a></li>
 808
 809  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
 810
 811  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (40)</a></li>
 812
 813  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
 814
 815  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (29)</a></li>
 816
 817 </ul>
 818
 819
 820     </div>
 821     <p style="text-align: right">
 822  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
 823 </p>
 824
 825   </body>
 826 </html>