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