<atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
<item>
- <title>Opphavsretts-status for «Empty Socks» fra 1927?</title>
- <link>http://people.skolelinux.org/pere/blog/Opphavsretts_status_for__Empty_Socks__fra_1927_.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Opphavsretts_status_for__Empty_Socks__fra_1927_.html</guid>
- <pubDate>Fri, 12 Dec 2014 14:30:00 +0100</pubDate>
- <description><p>For noen dager siden
-<a href="http://www.nb.no/Hva-skjer/Aktuelt/Nyheter/Tapt-filmskatt-fra-Disney-funnet-i-Nasjonalbiblioteket">annonserte
-Nasjonalbiblioteket gladnyheten</a> om at de i sine arkiver hadde
-funnet et nitratfilm-eksemplar av en 87 år gammel Disney-film ved navn
-Empty Socks, en film som tidligere var antatt tapt og der det i følge
-nyhetsmeldinger var kun ca. 25 sekunder bevart for ettertiden.
-Nasjonalbiblioteket hadde 5 minutter og 30 sekunder av filmen i sitt
-magasin. Dette er flott for bevaringen av verdens kulturarv. 5,5
-minutter mindre tapt enn vi trodde av får felles historie.</p>
-
-<p>Men hvordan kunne filmen gå tapt, når arkivlovene i USA krevde at
-publiserte filmer på den tiden ble deponert i bibliotek? Forklaringen
-har jeg fra Lawrence Lessig og boken
-<a href="http://free-culture.cc/">Free Culture</a>, som jeg holder på
-<a href="https://github.com/petterreinholdtsen/free-culture-lessig">å
-oversette til norsk</a>:</p>
+ <title>Idea for storing trusted timestamps in a Noark 5 archive</title>
+ <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html</guid>
+ <pubDate>Wed, 7 Jun 2017 21:40:00 +0200</pubDate>
+ <description><p><em>This is a copy of
+<a href="https://lists.nuug.no/pipermail/nikita-noark/2017-June/000297.html">an
+email I posted to the nikita-noark mailing list</a>. Please follow up
+there if you would like to discuss this topic. The background is that
+we are making a free software archive system based on the Norwegian
+<a href="https://www.arkivverket.no/forvaltning-og-utvikling/regelverk-og-standarder/noark-standarden">Noark
+5 standard</a> for government archives.</em></p>
+
+<p>I've been wondering a bit lately how trusted timestamps could be
+stored in Noark 5.
+<a href="https://en.wikipedia.org/wiki/Trusted_timestamping">Trusted
+timestamps</a> can be used to verify that some information
+(document/file/checksum/metadata) have not been changed since a
+specific time in the past. This is useful to verify the integrity of
+the documents in the archive.</p>
+
+<p>Then it occured to me, perhaps the trusted timestamps could be
+stored as dokument variants (ie dokumentobjekt referered to from
+dokumentbeskrivelse) with the filename set to the hash it is
+stamping?</p>
+
+<p>Given a "dokumentbeskrivelse" with an associated "dokumentobjekt",
+a new dokumentobjekt is associated with "dokumentbeskrivelse" with the
+same attributes as the stamped dokumentobjekt except these
+attributes:</p>
-<p><blockquote>
-<p>Dette er delvis på grunn av loven. Opphavsrettseiere var tidlig i
- amerikansk opphavsrettslov nødt til å deponere kopier av sine verk i
- biblioteker. Disse kopiene skulle både sikre spredning av kunnskap,
- og sikre at det fantes en kopi av verket tilgjengelig når vernetiden
- utløp, slik at andre kunne få tilgang til og kopiere verket.</p>
-
-<p>Disse reglene gjaldt også for filmer. Men i 1915 gjorde
- kongressbiblioteket et unntak for film. Filmer kunne bli
- opphavsrettsbeskyttet så lenge det ble gjort slik deponering. Men
- filmskaperne fikk så lov til å låne tilbake de deponerte filmene -
- så lenge de ville uten noe kostnad. Bare i 1915 var det mer enn 5475
- filmer deponert og “lånt tilbake”. Dermed var det ikke noe eksemplar
- i noe bibliotek når vernetiden til filmen utløp. Eksemplaret
- eksisterer - hvis den finnes i det hele tatt - i arkivbiblioteket
- til filmselskapet.</p>
-</blockquote></p>
-
-<p>Nyheten gjorde meg nysgjerrig på om filmen kunne være falt i det
-fri. En 87 år gammel film kunne jo tenkes å ha blitt en del av
-allemannseiet, slik at vi alle kan bruke den til å bygge videre på vår
-felles kultur uten å måtte be om tillatelse - slik Walt Disney gjorde
-det i starten av sin karriere. Jeg spurte nasjonalbiblioteket, og de
-sa nei. Hvordan kan det ha seg med en så gammel film? Jeg besteme
-meg for å undersøke nærmere. En kan finne informasjon om den norske
-vernetiden på
-<a href="https://lovdata.no/dokument/NL/lov/1961-05-12-2">Lovdata</a>
-og </a>Wikipedia</A>. Her er et relevant <a
-href="https://no.wikipedia.org/wiki/Opphavsrett#Vernetid">utsnitt fra
-siden om opphavsrett i den norske Wikipedia</a>:</p>
-
-<p><blockquote>
- Ifølge åndsverkloven §§ 40-41 utløper vernetiden for et åndsverk 70
- år etter utløpet av opphavspersonens dødsår. [...] For filmverk
- gjelder særlige regler: Her kommer ikke alle mulige opphavspersoner
- i betraktning, men kun hovedregissøren, manusforfatteren,
- dialogforfatteren og komponisten av filmmusikken. Vernetiden
- begynner å løpe etter utgangen av dødsåret til den lengstlevende av
- disse. [...] Der opphavspersonen er ukjent, utløper opphavsretten 70
- år etter første kjente offentliggjørelse av verket. Det er kun de
- økonomiske rettighetene som faller bort i det vernetiden er
- utløpt. De ideelle rettighetene må fortsatt respekteres, noe som
- blant annet innebærer at man plikter å navngi opphavspersonen ved
- tilgjengeliggjøring.
-</blockquote></p>
-
-<p><a href="http://www.disneyshorts.org/shorts.aspx?shortID=75">I følge
-nettstedet X</a> er følgende personer gitt æren for denne
-kortfilmen:</p>
-
-<dl>
-
-<dt>Regissør</dt>
-<dd><a href="https://en.wikipedia.org/wiki/Walt_Disney">Walt Disney</a> (1901-12-05 – 1966-12-15) +70 år = 2037</dd>
-
-<dt>Animasjon
-<dd><a href="https://en.wikipedia.org/wiki/Ub_Iwerks">Ub Iwerks</a> (1901-03-24 – 1971-07-07) +70 år = 2042
-<br><a href="https://en.wikipedia.org/wiki/Rollin_Hamilton">Rollin "Ham" Hamilton</a> (1898-10-28 - 1951-06-03) +70 år = 2022
-<br><a href="https://en.wikipedia.org/wiki/Harman_and_Ising">Hugh Harman</a> (1903-08-31 – 1982-11-25) +70 år = 2053</dd>
+<ul>
-<dt>Kamera
-<dd>Mike Marcus (?-?)</dd>
+<li>format -> "RFC3161"
+<li>mimeType -> "application/timestamp-reply"
+<li>formatDetaljer -> "&lt;source URL for timestamp service&gt;"
+<li>filenavn -> "&lt;sjekksum&gt;.tsr"
-</dl>
+</ul>
-<p>Alle fødsels- og dødsdatoene er fra engelske Wikipedia. Det er
-ikke oppgitt navn på manusforfatter, dialogforfatter og komponist, men
-jeg mistenker at tegnerne vil få opphavsrettigheter på tegnefilmer her
-i Norge, og tar derfor med disse. Kameramannen vil ikke få noen
-rettigheter så vidt jeg forstår, og er derfor ignorert her.</p>
+<p>This assume a service following
+<a href="https://tools.ietf.org/html/rfc3161">IETF RFC 3161</a> is
+used, which specifiy the given MIME type for replies and the .tsr file
+ending for the content of such trusted timestamp. As far as I can
+tell from the Noark 5 specifications, it is OK to have several
+variants/renderings of a dokument attached to a given
+dokumentbeskrivelse objekt. It might be stretching it a bit to make
+some of these variants represent crypto-signatures useful for
+verifying the document integrity instead of representing the dokument
+itself.</p>
+
+<p>Using the source of the service in formatDetaljer allow several
+timestamping services to be used. This is useful to spread the risk
+of key compromise over several organisations. It would only be a
+problem to trust the timestamps if all of the organisations are
+compromised.</p>
+
+<p>The following oneliner on Linux can be used to generate the tsr
+file. $input is the path to the file to checksum, and $sha256 is the
+SHA-256 checksum of the file (ie the "<sjekksum>.tsr" value mentioned
+above).</p>
-<p>Slik jeg forstår den norske opphavsretten vil dermed dette
-filmverket bli allemannseie (også kalt å falle i det fri) i 2053, 126
-år etter at det ble laget. Hvis kun regissørens rettigheter er
-relevante, vil det skje i 2037, 110 år etter at det ble utgitt. Etter
-det vil enhver kunne dele det med alle de har lyst til, fremføre det
-offentlig eller klippe og lime i det for å lage sin egen film basert
-på det - helt uten å måtte spørre noen om lov.</p>
+<p><blockquote><pre>
+openssl ts -query -data "$inputfile" -cert -sha256 -no_nonce \
+ | curl -s -H "Content-Type: application/timestamp-query" \
+ --data-binary "@-" http://zeitstempel.dfn.de > $sha256.tsr
+</pre></blockquote></p>
-<p>Måtte så Nasjonalbiblioteket spørre om lov før de kunne kopiere
-sitt nitrat-eksemplar over på mer varig format? Nei, heldigvis.
-Åndsverklovens § 16 sier at arkiv, bibliotek, museer og undervisnings-
-og forskningsinstitusjoner har rett til å fremstille eksemplar av verk
-for konserverings- og sikringsformål og andre særskilte formål.</p>
-</description>
- </item>
-
- <item>
- <title>How to stay with sysvinit in Debian Jessie</title>
- <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
- <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
- <description><p>By now, it is well known that Debian Jessie will not be using
-sysvinit as its boot system by default. But how can one keep using
-sysvinit in Jessie? It is fairly easy, and here are a few recipes,
-courtesy of
-<a href="http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html">Erich
-Schubert</a> and
-<a href="http://smcv.pseudorandom.co.uk/2014/still_universal/">Simon
-McVittie</a>.
-
-<p>If you already are using Wheezy and want to upgrade to Jessie and
-keep sysvinit as your boot system, create a file
-<tt>/etc/apt/preferences.d/use-sysvinit</tt> with this content before
-you upgrade:</p>
+<p>To verify the timestamp, you first need to download the public key
+of the trusted timestamp service, for example using this command:</p>
<p><blockquote><pre>
-Package: systemd-sysv
-Pin: release o=Debian
-Pin-Priority: -1
-</pre></blockquote><p>
-
-<p>This file content will tell apt and aptitude to not consider
-installing systemd-sysv as part of any installation and upgrade
-solution when resolving dependencies, and thus tell it to avoid
-systemd as a default boot system. The end result should be that the
-upgraded system keep using sysvinit.</p>
-
-<p>If you are installing Jessie for the first time, there is no way to
-get sysvinit installed by default (debootstrap used by
-debian-installer have no option for this), but one can tell the
-installer to switch to sysvinit before the first boot. Either by
-using a kernel argument to the installer, or by adding a line to the
-preseed file used. First, the kernel command line argument:
+wget -O ca-cert.txt \
+ https://pki.pca.dfn.de/global-services-ca/pub/cacert/chain.txt
+</pre></blockquote></p>
-<p><blockquote><pre>
-preseed/late_command="in-target apt-get install --purge -y sysvinit-core"
-</pre></blockquote><p>
+<p>Note, the public key should be stored alongside the timestamps in
+the archive to make sure it is also available 100 years from now. It
+is probably a good idea to standardise how and were to store such
+public keys, to make it easier to find for those trying to verify
+documents 100 or 1000 years from now. :)</p>
-<p>Next, the line to use in a preseed file:</p>
+<p>The verification itself is a simple openssl command:</p>
<p><blockquote><pre>
-d-i preseed/late_command string in-target apt-get install -y sysvinit-core
-</pre></blockquote><p>
-
-<p>One can of course also do this after the first boot by installing
-the sysvinit-core package.</p>
-
-<p>I recommend only using sysvinit if you really need it, as the
-sysvinit boot sequence in Debian have several hardware specific bugs
-on Linux caused by the fact that it is unpredictable when hardware
-devices show up during boot. But on the other hand, the new default
-boot system still have a few rough edges I hope will be fixed before
-Jessie is released.</p>
-
-<p>Update 2014-11-26: Inspired by
-<ahref="https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg">a
-blog post by Torsten Glaser</a>, added --purge to the preseed
-line.</p>
-</description>
- </item>
-
- <item>
- <title>Hvordan vurderer regjeringen H.264-patentutfordringen?</title>
- <link>http://people.skolelinux.org/pere/blog/Hvordan_vurderer_regjeringen_H_264_patentutfordringen_.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Hvordan_vurderer_regjeringen_H_264_patentutfordringen_.html</guid>
- <pubDate>Sun, 16 Nov 2014 10:30:00 +0100</pubDate>
- <description><p>For en stund tilbake spurte jeg Fornyingsdepartementet om hvilke
-juridiske vurderinger rundt patentproblemstillingen som var gjort da
-H.264 ble tatt inn i <a href="http://standard.difi.no/">statens
-referansekatalog over standarder</a>. Stig Hornnes i FAD tipset meg
-om følgende som står i oppsumeringen til høringen om
-referansekatalogen versjon 2.0, som jeg siden ved hjelp av en
-innsynsforespørsel fikk tak i
-<a href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&do=get&target=kongelig-resolusjon.pdf">PDF-utgaven av</a>
-datert 2009-06-03 (saksnummer 200803291, saksbehandler Henrik
-Linnestad).</p>
-
-<p>Der står det følgende om problemstillingen:</p>
-
-<p><blockquote>
-<strong>4.4 Patentproblematikk</strong>
-
-<p>NUUG og Opera ser det som særlig viktig at forslagene knyttet til
-lyd og video baserer seg på de royalty-frie standardene Vorbis, Theora
-og FLAC.</p>
-
-<p>Kommentarene relaterer seg til at enkelte standarder er åpne, men
-inneholder tekniske prosedyrer som det i USA (og noen andre land som
-Japan) er gitt patentrettigheter til. I vårt tilfelle berører dette
-spesielt standardene Mp3 og H.264, selv om Politidirektoratet peker på
-at det muligens kan være tilsvarende problematikk også for Theora og
-Vorbis. Dette medfører at det i USA kan kreves royalties for bruk av
-tekniske løsninger knyttet til standardene, et krav som også
-håndheves. Patenter kan imidlertid bare hevdes i de landene hvor
-patentet er gitt, så amerikanske patenter gjelder ikke andre steder
-enn USA.</p>
-
-<p>Spesielt for utvikling av fri programvare er patenter
-problematisk. GPL, en "grunnleggende" lisens for distribusjon av fri
-programvare, avviser at programvare kan distribueres under denne
-lisensen hvis det inneholder referanser til patenterte rutiner som
-utløser krav om royalties. Det er imidlertid uproblematisk å
-distribuere fri programvareløsninger under GPL som benytter de
-aktuelle standardene innen eller mellom land som ikke anerkjenner
-patentene. Derfor finner vi også flere implementeringer av Mp3 og
-H.264 som er fri programvare, lisensiert under GPL.</p>
-
-<p>I Norge og EU er patentlovgivningen langt mer restriktiv enn i USA,
-men det er også her mulig å få patentert metoder for løsning av et
-problem som relaterer seg til databehandling. Det er AIF bekjent ikke
-relevante patenter i EU eller Norge hva gjelder H.264 og Mp3, men
-muligheten for at det finnes patenter uten at det er gjort krav om
-royalties eller at det senere vil gis slike patenter kan ikke helt
-avvises.</p>
-
-<p>AIF mener det er et behov for å gi offentlige virksomheter mulighet
-til å benytte antatt royaltyfrie åpne standarder som et likeverdig
-alternativ eller i tillegg til de markedsledende åpne standardene.</p>
-
-</blockquote></p>
+openssl ts -verify -data $inputfile -in $sha256.tsr \
+ -CAfile ca-cert.txt -text
+</pre></blockquote></p>
-<p>Det ser dermed ikke ut til at de har vurdert patentspørsmålet i
-sammenheng med opphavsrettsvilkår slik de er formulert for f.eks.
-Apple Final Cut Pro, Adobe Premiere Pro, Avid og Sorenson-verktøyene,
-der det kreves brukstillatelse for patenter som ikke er gyldige i
-Norge for å bruke disse verktøyene til annet en personlig og ikke
-kommersiell aktivitet når det gjelder H.264-video. Jeg må nok lete
-videre etter svar på det spørsmålet.</p>
+<p>Is there any reason this approach would not work? Is it somehow against
+the Noark 5 specification?</p>
</description>
</item>
<item>
- <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
- <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
- <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
- <description><p>The right to communicate with your friends and family in private,
-without anyone snooping, is a right every citicen have in a liberal
-democracy. But this right is under serious attack these days.</p>
-
-<p>A while back it occurred to me that one way to make the dragnet
-surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
-the whisleblower Snowden) more expensive for Internet email,
-is to deliver all email using SMTP via Tor. Such SMTP option would be
-a nice addition to the FreedomBox project if we could send email
-between FreedomBox machines without leaking metadata about the emails
-to the people peeking on the wire. I
-<a href="http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html">proposed
-this on the FreedomBox project mailing list in October</a> and got a
-lot of useful feedback and suggestions. It also became obvious to me
-that this was not a novel idea, as the same idea was tested and
-documented by Johannes Berg as early as 2006, and both
-<a href="https://github.com/pagekite/Mailpile/wiki/SMTorP">the
-Mailpile</a> and <a href="http://dee.su/cables">the Cables</a> systems
-propose a similar method / protocol to pass emails between users.</p>
-
-<p>To implement such system one need to set up a Tor hidden service
-providing the SMTP protocol on port 25, and use email addresses
-looking like username@hidden-service-name.onion. With such addresses
-the connections to port 25 on hidden-service-name.onion using Tor will
-go to the correct SMTP server. To do this, one need to configure the
-Tor daemon to provide the hidden service and the mail server to accept
-emails for this .onion domain. To learn more about Exim configuration
-in Debian and test the design provided by Johannes Berg in his FAQ, I
-set out yesterday to create a Debian package for making it trivial to
-set up such SMTP over Tor service based on Debian. Getting it to work
-were fairly easy, and
-<a href="https://github.com/petterreinholdtsen/exim4-smtorp">the
-source code for the Debian package</a> is available from github. I
-plan to move it into Debian if further testing prove this to be a
-useful approach.</p>
-
-<p>If you want to test this, set up a blank Debian machine without any
-mail system installed (or run <tt>apt-get purge exim4-config</tt> to
-get rid of exim4). Install tor, clone the git repository mentioned
-above, build the deb and install it on the machine. Next, run
-<tt>/usr/lib/exim4-smtorp/setup-exim-hidden-service</tt> and follow
-the instructions to get the service up and running. Restart tor and
-exim when it is done, and test mail delivery using swaks like
-this:</p>
-
-<p><blockquote><pre>
-torsocks swaks --server dutlqrrmjhtfa3vp.onion \
- --to fbx@dutlqrrmjhtfa3vp.onion
-</pre></blockquote></p>
-
-<p>This will test the SMTP delivery using tor. Replace the email
-address with your own address to test your server. :)</p>
-
-<p>The setup procedure is still to complex, and I hope it can be made
-easier and more automatic. Especially the tor setup need more work.
-Also, the package include a tor-smtp tool written in C, but its task
-should probably be rewritten in some script language to make the deb
-architecture independent. It would probably also make the code easier
-to review. The tor-smtp tool currently need to listen on a socket for
-exim to talk to it and is started using xinetd. It would be better if
-no daemon and no socket is needed. I suspect it is possible to get
-exim to run a command line tool for delivery instead of talking to a
-socket, and hope to figure out how in a future version of this
-system.</p>
-
-<p>Until I wipe my test machine, I can be reached using the
-<tt>fbx@dutlqrrmjhtfa3vp.onion</tt> mail address, deliverable over
-SMTorP. :)</p>
+ <title>Når nynorskoversettelsen svikter til eksamen...</title>
+ <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</guid>
+ <pubDate>Sat, 3 Jun 2017 08:20:00 +0200</pubDate>
+ <description><p><a href="http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-622459b.html">Aftenposten
+melder i dag</a> om feil i eksamensoppgavene for eksamen i politikk og
+menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
+like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
+på om den fri oversetterløsningen
+<a href="https://www.apertium.org/">Apertium</a> ville gjort en bedre
+jobb enn Utdanningsdirektoratet. Det kan se slik ut.</p>
+
+<p>Her er bokmålsoppgaven fra eksamenen:</p>
+
+<blockquote>
+<p>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
+rolle og muligheter til å håndtere internasjonale utfordringer, som
+for eksempel flykningekrisen.</p>
+
+<p>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
+på temaet:</p>
+<ol>
+<li>Flykningeregnskapet 2016, UNHCR og IDMC
+<li>«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
+</ol>
+
+</blockquote>
+
+<p>Dette oversetter Apertium slik:</p>
+
+<blockquote>
+<p>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
+andre aktørar og høve til å handtera internasjonale utfordringar, som
+til dømes *flykningekrisen.</p>
+
+<p>Vedleggja er døme på tekster som kan gje relevante perspektiv på
+temaet:</p>
+
+<ol>
+<li>*Flykningeregnskapet 2016, *UNHCR og *IDMC</li>
+<li>«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015</li>
+</ol>
+
+</blockquote>
+
+<p>Ord som ikke ble forstått er markert med stjerne (*), og trenger
+ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
+oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
+"andre aktørers rolle og muligheter til ..." burde vært oversatt til
+"rolla til andre aktørar og deira høve til ..." eller noe slikt, men
+det er kanskje flisespikking. Det understreker vel bare at det alltid
+trengs korrekturlesning etter automatisk oversettelse.</p>
</description>
</item>
<item>
- <title>First Jessie based Debian Edu released (alpha0)</title>
- <link>http://people.skolelinux.org/pere/blog/First_Jessie_based_Debian_Edu_released__alpha0_.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_Jessie_based_Debian_Edu_released__alpha0_.html</guid>
- <pubDate>Mon, 27 Oct 2014 20:40:00 +0100</pubDate>
- <description><p>I am happy to report that I on behalf of the Debian Edu team just
-sent out
-<a href="https://lists.debian.org/debian-edu-announce/2014/10/msg00000.html">this
-announcement</a>:</p>
-
-<pre>
-The Debian Edu Team is pleased to announce the release of Debian Edu
-Jessie 8.0+edu0~alpha0
-
-Debian Edu is a complete operating system for schools. Through its
-various installation profiles you can install servers, workstations
-and laptops which will work together on the school network. With
-Debian Edu, the teachers themselves or their technical support can
-roll out a complete multi-user multi-machine study environment within
-hours or a few days. Debian Edu comes with hundreds of applications
-pre-installed, but you can always add more packages from Debian.
-
-For those who want to give Debian Edu Jessie a try, download and
-installation instructions are available, including detailed
-instructions in the manual[1] explaining the first steps, such as
-setting up a network or adding users. Please note that the password
-for the user your prompted for during installation must have a length
-of at least 5 characters!
-
- [1] &lt;URL: <a href="https://wiki.debian.org/DebianEdu/Documentation/Jessie">https://wiki.debian.org/DebianEdu/Documentation/Jessie</a> &gt;
-
-Would you like to give your school's computer a longer life? Are you
-tired of sneaker administration, running from computer to computer
-reinstalling the operating system? Would you like to administrate all
-the computers in your school using only a couple of hours every week?
-Check out Debian Edu Jessie!
-
-Skolelinux is used by at least two hundred schools all over the world,
-mostly in Germany and Norway.
-
-About Debian Edu and Skolelinux
-===============================
-
-Debian Edu, also known as Skolelinux[2], is a Linux distribution based
-on Debian providing an out-of-the box environment of a completely
-configured school network. Immediately after installation a school
-server running all services needed for a school network is set up just
-waiting for users and machines being added via GOsa², a comfortable
-Web-UI. A netbooting environment is prepared using PXE, so after
-initial installation of the main server from CD or USB stick all other
-machines can be installed via the network. The provided school server
-provides LDAP database and Kerberos authentication service,
-centralized home directories, DHCP server, web proxy and many other
-services. The desktop contains more than 60 educational software
-packages[3] and more are available from the Debian archive, and
-schools can choose between KDE, Gnome, LXDE, Xfce and MATE desktop
-environment.
-
- [2] &lt;URL: <a href="http://www.skolelinux.org/">http://www.skolelinux.org/</a> &gt;
- [3] &lt;URL: <a href="http://people.skolelinux.org/pere/blog/Educational_applications_included_in_Debian_Edu___Skolelinux__the_screenshot_collection____.html">http://people.skolelinux.org/pere/blog/Educational_applications_included_in_Debian_Edu___Skolelinux__the_screenshot_collection____.html</a> &gt;
-
-Full release notes and manual
-=============================
-
-Below the download URLs there is a list of some of the new features
-and bugfixes of Debian Edu 8.0+edu0~alpha0 Codename Jessie. The full
-list is part of the manual. (See the feature list in the manual[4] for
-the English version.) For some languages manual translations are
-available, see the manual translation overview[5].
-
- [4] &lt;URL: <a href="https://wiki.debian.org/DebianEdu/Documentation/Jessie/Features">https://wiki.debian.org/DebianEdu/Documentation/Jessie/Features</a> &gt;
- [5] &lt;URL: <a href="http://maintainer.skolelinux.org/debian-edu-doc/">http://maintainer.skolelinux.org/debian-edu-doc/</a> &gt;
-
-Where to get it
----------------
-
-To download the multiarch netinstall CD release (624 MiB) you can use
-
- * <a href="ftp://ftp.skolelinux.org/skolelinux-cd/debian-edu-8.0+edu0~alpha0-CD.iso">ftp://ftp.skolelinux.org/skolelinux-cd/debian-edu-8.0+edu0~alpha0-CD.iso</a>
- * <a href="http://ftp.skolelinux.org/skolelinux-cd/debian-edu-8.0+edu0~alpha0-CD.iso">http://ftp.skolelinux.org/skolelinux-cd/debian-edu-8.0+edu0~alpha0-CD.iso</a>
- * rsync -avzP ftp.skolelinux.org::skolelinux-cd/debian-edu-8.0+edu0~alpha0-CD.iso .
-
-The SHA1SUM of this image is: 361188818e036ce67280a572f757de82ebfeb095
-
-New features for Debian Edu 8.0+edu0~alpha0 Codename Jessie released 2014-10-27
-===============================================================================
-
-
-Installation changes
---------------------
-
- * PXE installation now installs firmware automatically for the hardware present.
-
-Software updates
-----------------
-
-Everything which is new in Debian Jessie 8.0, eg:
-
- * Linux kernel 3.16.x
- * Desktop environments KDE "Plasma" 4.11.12, GNOME 3.14, Xfce 4.10,
- LXDE 0.5.6 and MATE 1.8 (KDE "Plasma" is installed by default; to
- choose one of the others see manual.)
- * the browsers Iceweasel 31 ESR and Chromium 38
- * !LibreOffice 4.3.3
- * GOsa 2.7.4
- * LTSP 5.5.4
- * CUPS print system 1.7.5
- * new boot framework: systemd
- * Educational toolbox GCompris 14.07
- * Music creator Rosegarden 14.02
- * Image editor Gimp 2.8.14
- * Virtual stargazer Stellarium 0.13.0
- * golearn 0.9
- * tuxpaint 0.9.22
- * New version of debian-installer from Debian Jessie.
- * Debian Jessie includes about 42000 packages available for
- installation.
- * More information about Debian Jessie 8.0 is provided in the release
- notes[6] and the installation manual[7].
-
- [6] &lt;URL: <a href="http://www.debian.org/releases/jessie/releasenotes">http://www.debian.org/releases/jessie/releasenotes</a> &gt;
- [7] &lt;URL: <a href="http://www.debian.org/releases/jessie/installmanual">http://www.debian.org/releases/jessie/installmanual</a> &gt;
-
-Fixed bugs
-----------
-
- * Inserting incorrect DNS information in Gosa will no longer break
- DNS completely, but instead stop DNS updates until the incorrect
- information is corrected (Debian bug #710362)
- * and many others.
-
-Documentation and translation updates
--------------------------------------
-
- * The Debian Edu Jessie Manual is fully translated to German, French,
- Italian, Danish and Dutch. Partly translated versions exist for
- Norwegian Bokmal and Spanish.
-
-Other changes
--------------
-
- * Due to new Squid settings, powering off or rebooting the main
- server takes more time.
- * To manage printers localhost:631 has to be used, currently www:631
- doesn't work.
-
-Regressions / known problems
-----------------------------
-
- * Installing LTSP chroot fails with a bug related to eatmydata about
- exim4-config failing to run its postinst (see Debian bug #765694
- and Debian bug #762103).
- * Munin collection is not properly configured on clients (Debian bug
- #764594). The fix is available in a newer version of munin-node.
- * PXE setup for Main Server and Thin Client Server setup does not
- work when installing on a machine without direct Internet access.
- Will be fixed when Debian bug #766960 is fixed in Jessie.
+ <title>Epost inn som arkivformat i Riksarkivarens forskrift?</title>
+ <link>http://people.skolelinux.org/pere/blog/Epost_inn_som_arkivformat_i_Riksarkivarens_forskrift_.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Epost_inn_som_arkivformat_i_Riksarkivarens_forskrift_.html</guid>
+ <pubDate>Thu, 27 Apr 2017 11:30:00 +0200</pubDate>
+ <description><p>I disse dager, med frist 1. mai, har Riksarkivaren ute en høring på
+sin forskrift. Som en kan se er det ikke mye tid igjen før fristen
+som går ut på søndag. Denne forskriften er det som lister opp hvilke
+formater det er greit å arkivere i
+<a href="http://www.arkivverket.no/arkivverket/Offentleg-forvalting/Noark/Noark-5">Noark
+5-løsninger</a> i Norge.</p>
+
+<p>Jeg fant høringsdokumentene hos
+<a href="https://www.arkivrad.no/aktuelt/riksarkivarens-forskrift-pa-horing">Norsk
+Arkivråd</a> etter å ha blitt tipset på epostlisten til
+<a href="https://github.com/hiOA-ABI/nikita-noark5-core">fri
+programvareprosjektet Nikita Noark5-Core</a>, som lager et Noark 5
+Tjenestegresesnitt. Jeg er involvert i Nikita-prosjektet og takket
+være min interesse for tjenestegrensesnittsprosjektet har jeg lest en
+god del Noark 5-relaterte dokumenter, og til min overraskelse oppdaget
+at standard epost ikke er på listen over godkjente formater som kan
+arkiveres. Høringen med frist søndag er en glimrende mulighet til å
+forsøke å gjøre noe med det. Jeg holder på med
+<a href="https://github.com/petterreinholdtsen/noark5-tester/blob/master/docs/hoering-arkivforskrift.tex">egen
+høringsuttalelse</a>, og lurer på om andre er interessert i å støtte
+forslaget om å tillate arkivering av epost som epost i arkivet.</p>
+
+<p>Er du igang med å skrive egen høringsuttalelse allerede? I så fall
+kan du jo vurdere å ta med en formulering om epost-lagring. Jeg tror
+ikke det trengs så mye. Her et kort forslag til tekst:</p>
-See the status page[8] for the complete list.
-
- [8] &lt;URL: <a href="https://wiki.debian.org/DebianEdu/Status/Jessie">https://wiki.debian.org/DebianEdu/Status/Jessie</a> &gt;
+<p><blockquote>
-How to report bugs
-------------------
-
-&lt;URL: <a href="http://wiki.debian.org/DebianEdu/HowTo/ReportBugs">http://wiki.debian.org/DebianEdu/HowTo/ReportBugs</a> &gt;
+ <p>Viser til høring sendt ut 2017-02-17 (Riksarkivarens referanse
+ 2016/9840 HELHJO), og tillater oss å sende inn noen innspill om
+ revisjon av Forskrift om utfyllende tekniske og arkivfaglige
+ bestemmelser om behandling av offentlige arkiver (Riksarkivarens
+ forskrift).</p>
-About Debian
-============
+ <p>Svært mye av vår kommuikasjon foregår i dag på e-post. Vi
+ foreslår derfor at Internett-e-post, slik det er beskrevet i IETF
+ RFC 5322,
+ <a href="https://tools.ietf.org/html/rfc5322">https://tools.ietf.org/html/rfc5322</a>. bør
+ inn som godkjent dokumentformat. Vi foreslår at forskriftens
+ oversikt over godkjente dokumentformater ved innlevering i § 5-16
+ endres til å ta med Internett-e-post.</p>
-The Debian Project was founded in 1993 by Ian Murdock to be a truly
-free community project. Since then the project has grown to be one of
-the largest and most influential open source projects. Thousands of
-volunteers from all over the world work together to create and
-maintain Debian software. Available in 70 languages, and supporting a
-huge range of computer types, Debian calls itself the universal
-operating system.
+</blockquote></p>
-Contact Information
-For further information, please visit the Debian web pages[9] or send
-mail to press@debian.org.
+<p>Som del av arbeidet med tjenestegrensesnitt har vi testet hvordan
+epost kan lagres i en Noark 5-struktur, og holder på å skrive et
+forslag om hvordan dette kan gjøres som vil bli sendt over til
+arkivverket så snart det er ferdig. De som er interesserte kan
+<a href="https://github.com/petterreinholdtsen/noark5-tester/blob/master/docs/epostlagring.md">følge
+fremdriften på web</a>.</p>
- [9] &lt;URL: <a href="http://www.debian.org/">http://www.debian.org/</a> &gt;
-</pre>
+<p>Oppdatering 2017-04-28: I dag ble høringuttalelsen jeg skrev
+ <a href="https://www.nuug.no/news/NUUGs_h_ringuttalelse_til_Riksarkivarens_forskrift.shtml">sendt
+ inn av foreningen NUUG</a>.</p>
</description>
</item>
<item>
- <title>I spent last weekend recording MakerCon Nordic</title>
- <link>http://people.skolelinux.org/pere/blog/I_spent_last_weekend_recording_MakerCon_Nordic.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/I_spent_last_weekend_recording_MakerCon_Nordic.html</guid>
- <pubDate>Thu, 23 Oct 2014 23:00:00 +0200</pubDate>
- <description><p>I spent last weekend at <a href="http://www.makercon.no/">Makercon
-Nordic</a>, a great conference and workshop for makers in Norway and
-the surrounding countries. I had volunteered on behalf of the
-Norwegian Unix Users Group (NUUG) to video record the talks, and we
-had a great and exhausting time recording the entire day, two days in
-a row. There were only two of us, Hans-Petter and me, and we used the
-regular video equipment for NUUG, with a
-<a href="http://dvswitch.alioth.debian.org/wiki/">dvswitch</a>, a
-camera and a VGA to DV convert box, and mixed video and slides
-live.</p>
-
-<p>Hans-Petter did the post-processing, consisting of uploading the
-around 180 GiB of raw video to Youtube, and the result is
-<a href="https://www.youtube.com/user/MakerConNordic/">now becoming
-public</a> on the MakerConNordic account. The videos have the license
-NUUG always use on our recordings, which is
-<a href="http://creativecommons.org/licenses/by-sa/3.0/no/">Creative
-Commons Navngivelse-Del på samme vilkår 3.0 Norge</a>. Many great
-talks available. Check it out! :)</p>
+ <title>Offentlig elektronisk postjournal blokkerer tilgang for utvalgte webklienter</title>
+ <link>http://people.skolelinux.org/pere/blog/Offentlig_elektronisk_postjournal_blokkerer_tilgang_for_utvalgte_webklienter.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Offentlig_elektronisk_postjournal_blokkerer_tilgang_for_utvalgte_webklienter.html</guid>
+ <pubDate>Thu, 20 Apr 2017 13:00:00 +0200</pubDate>
+ <description><p>Jeg oppdaget i dag at <a href="https://www.oep.no/">nettstedet som
+publiserer offentlige postjournaler fra statlige etater</a>, OEP, har
+begynt å blokkerer enkelte typer webklienter fra å få tilgang. Vet
+ikke hvor mange det gjelder, men det gjelder i hvert fall libwww-perl
+og curl. For å teste selv, kjør følgende:</p>
+
+<blockquote><pre>
+% curl -v -s https://www.oep.no/pub/report.xhtml?reportId=3 2>&1 |grep '< HTTP'
+< HTTP/1.1 404 Not Found
+% curl -v -s --header 'User-Agent:Opera/12.0' https://www.oep.no/pub/report.xhtml?reportId=3 2>&1 |grep '< HTTP'
+< HTTP/1.1 200 OK
+%
+</pre></blockquote>
+
+<p>Her kan en se at tjenesten gir «404 Not Found» for curl i
+standardoppsettet, mens den gir «200 OK» hvis curl hevder å være Opera
+versjon 12.0. Offentlig elektronisk postjournal startet blokkeringen
+2017-03-02.</p>
+
+<p>Blokkeringen vil gjøre det litt vanskeligere å maskinelt hente
+informasjon fra oep.no. Kan blokkeringen være gjort for å hindre
+automatisert innsamling av informasjon fra OEP, slik Pressens
+Offentlighetsutvalg gjorde for å dokumentere hvordan departementene
+hindrer innsyn i
+<a href="http://presse.no/dette-mener-np/undergraver-offentlighetsloven/">rapporten
+«Slik hindrer departementer innsyn» som ble publiserte i januar
+2017</a>. Det virker usannsynlig, da det jo er trivielt å bytte
+User-Agent til noe nytt.</p>
+
+<p>Finnes det juridisk grunnlag for det offentlige å diskriminere
+webklienter slik det gjøres her? Der tilgang gis eller ikke alt etter
+hva klienten sier at den heter? Da OEP eies av DIFI og driftes av
+Basefarm, finnes det kanskje noen dokumenter sendt mellom disse to
+aktørene man kan be om innsyn i for å forstå hva som har skjedd. Men
+<a href="https://www.oep.no/search/result.html?period=dateRange&fromDate=01.01.2016&toDate=01.04.2017&dateType=documentDate&caseDescription=&descType=both&caseNumber=&documentNumber=&sender=basefarm&senderType=both&documentType=all&legalAuthority=&archiveCode=&list2=196&searchType=advanced&Search=Search+in+records">postjournalen
+til DIFI viser kun to dokumenter</a> det siste året mellom DIFI og
+Basefarm.
+<a href="https://www.mimesbronn.no/request/blokkering_av_tilgang_til_oep_fo">Mimes brønn neste</a>,
+tenker jeg.</p>
</description>
</item>
<item>
- <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
- <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
- <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
- <description><p>If you ever had to moderate a mailman list, like the ones on
-alioth.debian.org, you know the web interface is fairly slow to
-operate. First you visit one web page, enter the moderation password
-and get a new page shown with a list of all the messages to moderate
-and various options for each email address. This take a while for
-every list you moderate, and you need to do it regularly to do a good
-job as a list moderator. But there is a quick alternative,
-<a href="http://heim.ifi.uio.no/kjetilho/hacks/#listadmin">the
-listadmin program</a>. It allow you to check lists for new messages
-to moderate in a fraction of a second. Here is a test run on two
-lists I recently took over:</p>
-
-<p><blockquote><pre>
-% time listadmin xiph
-fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
-fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
-
-real 0m1.709s
-user 0m0.232s
-sys 0m0.012s
-%
-</pre></blockquote></p>
-
-<p>In 1.7 seconds I had checked two mailing lists and confirmed that
-there are no message in the moderation queue. Every morning I
-currently moderate 68 mailman lists, and it normally take around two
-minutes. When I took over the two pkg-xiph lists above a few days
-ago, there were 400 emails waiting in the moderator queue. It took me
-less than 15 minutes to process them all using the listadmin
-program.</p>
-
-<p>If you install
-<a href="https://tracker.debian.org/pkg/listadmin">the listadmin
-package</a> from Debian and create a file <tt>~/.listadmin.ini</tt>
-with content like this, the moderation task is a breeze:</p>
-
-<p><blockquote><pre>
-username username@example.org
-spamlevel 23
-default discard
-discard_if_reason "Posting restricted to members only. Remove us from your mail list."
-
-password secret
-adminurl https://{domain}/mailman/admindb/{list}
-mailman-list@lists.example.com
-
-password hidden
-other-list@otherserver.example.org
-</pre></blockquote></p>
-
-<p>There are other options to set as well. Check the manual page to
-learn the details.</p>
-
-<p>If you are forced to moderate lists on a mailman installation where
-the SSL certificate is self signed or not properly signed by a
-generally accepted signing authority, you can set a environment
-variable when calling listadmin to disable SSL verification:</p>
+ <title>Free software archive system Nikita now able to store documents</title>
+ <link>http://people.skolelinux.org/pere/blog/Free_software_archive_system_Nikita_now_able_to_store_documents.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Free_software_archive_system_Nikita_now_able_to_store_documents.html</guid>
+ <pubDate>Sun, 19 Mar 2017 08:00:00 +0100</pubDate>
+ <description><p>The <a href="https://github.com/hiOA-ABI/nikita-noark5-core">Nikita
+Noark 5 core project</a> is implementing the Norwegian standard for
+keeping an electronic archive of government documents.
+<a href="http://www.arkivverket.no/arkivverket/Offentlig-forvaltning/Noark/Noark-5/English-version">The
+Noark 5 standard</a> document the requirement for data systems used by
+the archives in the Norwegian government, and the Noark 5 web interface
+specification document a REST web service for storing, searching and
+retrieving documents and metadata in such archive. I've been involved
+in the project since a few weeks before Christmas, when the Norwegian
+Unix User Group
+<a href="https://www.nuug.no/news/NOARK5_kjerne_som_fri_programvare_f_r_epostliste_hos_NUUG.shtml">announced
+it supported the project</a>. I believe this is an important project,
+and hope it can make it possible for the government archives in the
+future to use free software to keep the archives we citizens depend
+on. But as I do not hold such archive myself, personally my first use
+case is to store and analyse public mail journal metadata published
+from the government. I find it useful to have a clear use case in
+mind when developing, to make sure the system scratches one of my
+itches.</p>
+
+<p>If you would like to help make sure there is a free software
+alternatives for the archives, please join our IRC channel
+(<a href="irc://irc.freenode.net/%23nikita"">#nikita on
+irc.freenode.net</a>) and
+<a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">the
+project mailing list</a>.</p>
+
+<p>When I got involved, the web service could store metadata about
+documents. But a few weeks ago, a new milestone was reached when it
+became possible to store full text documents too. Yesterday, I
+completed an implementation of a command line tool
+<tt>archive-pdf</tt> to upload a PDF file to the archive using this
+API. The tool is very simple at the moment, and find existing
+<a href="https://en.wikipedia.org/wiki/Fonds">fonds</a>, series and
+files while asking the user to select which one to use if more than
+one exist. Once a file is identified, the PDF is associated with the
+file and uploaded, using the title extracted from the PDF itself. The
+process is fairly similar to visiting the archive, opening a cabinet,
+locating a file and storing a piece of paper in the archive. Here is
+a test run directly after populating the database with test data using
+our API tester:</p>
<p><blockquote><pre>
-PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
+~/src//noark5-tester$ ./archive-pdf mangelmelding/mangler.pdf
+using arkiv: Title of the test fonds created 2017-03-18T23:49:32.103446
+using arkivdel: Title of the test series created 2017-03-18T23:49:32.103446
+
+ 0 - Title of the test case file created 2017-03-18T23:49:32.103446
+ 1 - Title of the test file created 2017-03-18T23:49:32.103446
+Select which mappe you want (or search term): 0
+Uploading mangelmelding/mangler.pdf
+ PDF title: Mangler i spesifikasjonsdokumentet for NOARK 5 Tjenestegrensesnitt
+ File 2017/1: Title of the test case file created 2017-03-18T23:49:32.103446
+~/src//noark5-tester$
</pre></blockquote></p>
-<p>If you want to moderate a subset of the lists you take care of, you
-can provide an argument to the listadmin script like I do in the
-initial screen dump (the xiph argument). Using an argument, only
-lists matching the argument string will be processed. This make it
-quick to accept messages if you notice the moderation request in your
-email.</p>
-
-<p>Without the listadmin program, I would never be the moderator of 68
-mailing lists, as I simply do not have time to spend on that if the
-process was any slower. The listadmin program have saved me hours of
-time I could spend elsewhere over the years. It truly is nice free
-software.</p>
-
-<p>As usual, if you use Bitcoin and want to show your support of my
-activities, please send Bitcoin donations to my address
-<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&label=PetterReinholdtsenBlog">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
-
-<p>Update 2014-10-27: Added missing 'username' statement in
-configuration example. Also, I've been told that the
-PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
-sure why.</p>
+<p>You can see here how the fonds (arkiv) and serie (arkivdel) only had
+one option, while the user need to choose which file (mappe) to use
+among the two created by the API tester. The <tt>archive-pdf</tt>
+tool can be found in the git repository for the API tester.</p>
+
+<p>In the project, I have been mostly working on
+<a href="https://github.com/petterreinholdtsen/noark5-tester">the API
+tester</a> so far, while getting to know the code base. The API
+tester currently use
+<a href="https://en.wikipedia.org/wiki/HATEOAS">the HATEOAS links</a>
+to traverse the entire exposed service API and verify that the exposed
+operations and objects match the specification, as well as trying to
+create objects holding metadata and uploading a simple XML file to
+store. The tester has proved very useful for finding flaws in our
+implementation, as well as flaws in the reference site and the
+specification.</p>
+
+<p>The test document I uploaded is a summary of all the specification
+defects we have collected so far while implementing the web service.
+There are several unclear and conflicting parts of the specification,
+and we have
+<a href="https://github.com/petterreinholdtsen/noark5-tester/tree/master/mangelmelding">started
+writing down</a> the questions we get from implementing it. We use a
+format inspired by how <a href="http://www.opengroup.org/austin/">The
+Austin Group</a> collect defect reports for the POSIX standard with
+<a href="http://www.opengroup.org/austin/mantis.html">their
+instructions for the MANTIS defect tracker system</a>, in lack of an official way to structure defect reports for Noark 5 (our first submitted defect report was a <a href="https://github.com/petterreinholdtsen/noark5-tester/blob/master/mangelmelding/sendt/2017-03-15-mangel-prosess.md">request for a procedure for submitting defect reports</a> :).
+
+<p>The Nikita project is implemented using Java and Spring, and is
+fairly easy to get up and running using Docker containers for those
+that want to test the current code base. The API tester is
+implemented in Python.</p>
</description>
</item>
<item>
- <title>Debian Jessie, PXE and automatic firmware installation</title>
- <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
- <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
- <description><p>When PXE installing laptops with Debian, I often run into the
-problem that the WiFi card require some firmware to work properly.
-And it has been a pain to fix this using preseeding in Debian.
-Normally something more is needed. But thanks to
-<a href="https://packages.qa.debian.org/i/isenkram.html">my isenkram
-package</a> and its recent tasksel extension, it has now become easy
-to do this using simple preseeding.</p>
-
-<p>The isenkram-cli package provide tasksel tasks which will install
-firmware for the hardware found in the machine (actually, requested by
-the kernel modules for the hardware). (It can also install user space
-programs supporting the hardware detected, but that is not the focus
-of this story.)</p>
-
-<p>To get this working in the default installation, two preeseding
-values are needed. First, the isenkram-cli package must be installed
-into the target chroot (aka the hard drive) before tasksel is executed
-in the pkgsel step of the debian-installer system. This is done by
-preseeding the base-installer/includes debconf value to include the
-isenkram-cli package. The package name is next passed to debootstrap
-for installation. With the isenkram-cli package in place, tasksel
-will automatically use the isenkram tasks to detect hardware specific
-packages for the machine being installed and install them, because
-isenkram-cli contain tasksel tasks.</p>
-
-<p>Second, one need to enable the non-free APT repository, because
-most firmware unfortunately is non-free. This is done by preseeding
-the apt-mirror-setup step. This is unfortunate, but for a lot of
-hardware it is the only option in Debian.</p>
-
-<p>The end result is two lines needed in your preseeding file to get
-firmware installed automatically by the installer:</p>
-
-<p><blockquote><pre>
-base-installer base-installer/includes string isenkram-cli
-apt-mirror-setup apt-setup/non-free boolean true
-</pre></blockquote></p>
+ <title>Detecting NFS hangs on Linux without hanging yourself...</title>
+ <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</guid>
+ <pubDate>Thu, 9 Mar 2017 15:20:00 +0100</pubDate>
+ <description><p>Over the years, administrating thousand of NFS mounting linux
+computers at the time, I often needed a way to detect if the machine
+was experiencing NFS hang. If you try to use <tt>df</tt> or look at a
+file or directory affected by the hang, the process (and possibly the
+shell) will hang too. So you want to be able to detect this without
+risking the detection process getting stuck too. It has not been
+obvious how to do this. When the hang has lasted a while, it is
+possible to find messages like these in dmesg:</p>
-<p>The current version of isenkram-cli in testing/jessie will install
-both firmware and user space packages when using this method. It also
-do not work well, so use version 0.15 or later. Installing both
-firmware and user space packages might give you a bit more than you
-want, so I decided to split the tasksel task in two, one for firmware
-and one for user space programs. The firmware task is enabled by
-default, while the one for user space programs is not. This split is
-implemented in the package currently in unstable.</p>
-
-<p>If you decide to give this a go, please let me know (via email) how
-this recipe work for you. :)</p>
-
-<p>So, I bet you are wondering, how can this work. First and
-foremost, it work because tasksel is modular, and driven by whatever
-files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
-isenkram-cli package place two files for tasksel to find. First there
-is the task description file (/usr/share/tasksel/descs/isenkram.desc):</p>
-
-<p><blockquote><pre>
-Task: isenkram-packages
-Section: hardware
-Description: Hardware specific packages (autodetected by isenkram)
- Based on the detected hardware various hardware specific packages are
- proposed.
-Test-new-install: show show
-Relevance: 8
-Packages: for-current-hardware
-
-Task: isenkram-firmware
-Section: hardware
-Description: Hardware specific firmware packages (autodetected by isenkram)
- Based on the detected hardware various hardware specific firmware
- packages are proposed.
-Test-new-install: mark show
-Relevance: 8
-Packages: for-current-hardware-firmware
-</pre></blockquote></p>
-
-<p>The key parts are Test-new-install which indicate how the task
-should be handled and the Packages line referencing to a script in
-/usr/lib/tasksel/packages/. The scripts use other scripts to get a
-list of packages to install. The for-current-hardware-firmware script
-look like this to list relevant firmware for the machine:
+<p><blockquote>
+nfs: server nfsserver not responding, still trying
+<br>nfs: server nfsserver OK
+</blockquote></p>
+
+<p>It is hard to know if the hang is still going on, and it is hard to
+be sure looking in dmesg is going to work. If there are lots of other
+messages in dmesg the lines might have rotated out of site before they
+are noticed.</p>
+
+<p>While reading through the nfs client implementation in linux kernel
+code, I came across some statistics that seem to give a way to detect
+it. The om_timeouts sunrpc value in the kernel will increase every
+time the above log entry is inserted into dmesg. And after digging a
+bit further, I discovered that this value show up in
+/proc/self/mountstats on Linux.</p>
+
+<p>The mountstats content seem to be shared between files using the
+same file system context, so it is enough to check one of the
+mountstats files to get the state of the mount point for the machine.
+I assume this will not show lazy umounted NFS points, nor NFS mount
+points in a different process context (ie with a different filesystem
+view), but that does not worry me.</p>
+
+<p>The content for a NFS mount point look similar to this:</p>
<p><blockquote><pre>
-#!/bin/sh
-#
-PATH=/usr/sbin:$PATH
-export PATH
-isenkram-autoinstall-firmware -l
+[...]
+device /dev/mapper/Debian-var mounted on /var with fstype ext3
+device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
+ opts: rw,vers=3,rsize=65536,wsize=65536,namlen=255,acregmin=3,acregmax=60,acdirmin=30,acdirmax=60,soft,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=129.240.3.145,mountvers=3,mountport=4048,mountproto=udp,local_lock=all
+ age: 7863311
+ caps: caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
+ sec: flavor=1,pseudoflavor=1
+ events: 61063112 732346265 1028140 35486205 16220064 8162542 761447191 71714012 37189 3891185 45561809 110486139 4850138 420353 15449177 296502 52736725 13523379 0 52182 9016896 1231 0 0 0 0 0
+ bytes: 166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
+ RPC iostats version: 1.0 p/v: 100003/3 (nfs)
+ xprt: tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
+ per-op statistics
+ NULL: 0 0 0 0 0 0 0 0
+ GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
+ SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
+ LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
+ ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
+ READLINK: 125 125 0 20472 18620 0 1112 1118
+ READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
+ WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
+ CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
+ MKDIR: 3680 3680 0 773980 993920 26 23990 24245
+ SYMLINK: 903 903 0 233428 245488 6 5865 5917
+ MKNOD: 80 80 0 20148 21760 0 299 304
+ REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
+ RMDIR: 3367 3367 0 645112 484848 22 5782 6002
+ RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
+ LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
+ READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
+ READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
+ FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
+ FSINFO: 2 2 0 232 328 0 1 1
+ PATHCONF: 1 1 0 116 140 0 0 0
+ COMMIT: 0 0 0 0 0 0 0 0
+
+device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
+[...]
</pre></blockquote></p>
-<p>With those two pieces in place, the firmware is installed by
-tasksel during the normal d-i run. :)</p>
-
-<p>If you want to test what tasksel will install when isenkram-cli is
-installed, run <tt>DEBIAN_PRIORITY=critical tasksel --test
---new-install</tt> to get the list of packages that tasksel would
-install.</p>
-
-<p><a href="https://wiki.debian.org/DebianEdu/">Debian Edu</a> will be
-pilots in testing this feature, as isenkram is used there now to
-install firmware, replacing the earlier scripts.</p>
+<p>The key number to look at is the third number in the per-op list.
+It is the number of NFS timeouts experiences per file system
+operation. Here 22 write timeouts and 5 access timeouts. If these
+numbers are increasing, I believe the machine is experiencing NFS
+hang. Unfortunately the timeout value do not start to increase right
+away. The NFS operations need to time out first, and this can take a
+while. The exact timeout value depend on the setup. For example the
+defaults for TCP and UDP mount points are quite different, and the
+timeout value is affected by the soft, hard, timeo and retrans NFS
+mount options.</p>
+
+<p>The only way I have been able to get working on Debian and RedHat
+Enterprise Linux for getting the timeout count is to peek in /proc/.
+But according to
+<ahref="http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html">Solaris
+10 System Administration Guide: Network Services</a>, the 'nfsstat -c'
+command can be used to get these timeout values. But this do not work
+on Linux, as far as I can tell. I
+<ahref="http://bugs.debian.org/857043">asked Debian about this</a>,
+but have not seen any replies yet.</p>
+
+<p>Is there a better way to figure out if a Linux NFS client is
+experiencing NFS hangs? Is there a way to detect which processes are
+affected? Is there a way to get the NFS mount going quickly once the
+network problem causing the NFS hang has been cleared? I would very
+much welcome some clues, as we regularly run into NFS hangs.</p>
</description>
</item>
<item>
- <title>Ubuntu used to show the bread prizes at ICA Storo</title>
- <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
- <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
- <description><p>Today I came across an unexpected Ubuntu boot screen. Above the
-bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
-with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
-on a screen normally showing the bread types and prizes:</p>
-
-<p align="center"><img width="70%" src="http://people.skolelinux.org/pere/blog/images/2014-10-04-ubuntu-ica-storo-crop.jpeg"></p>
-
-<p>If it had booted as it was supposed to, I would never had known
-about this hidden Linux installation. It is interesting what
-<a href="http://revealingerrors.com/">errors can reveal</a>.</p>
+ <title>How does it feel to be wiretapped, when you should be doing the wiretapping...</title>
+ <link>http://people.skolelinux.org/pere/blog/How_does_it_feel_to_be_wiretapped__when_you_should_be_doing_the_wiretapping___.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_does_it_feel_to_be_wiretapped__when_you_should_be_doing_the_wiretapping___.html</guid>
+ <pubDate>Wed, 8 Mar 2017 11:50:00 +0100</pubDate>
+ <description><p>So the new president in the United States of America claim to be
+surprised to discover that he was wiretapped during the election
+before he was elected president. He even claim this must be illegal.
+Well, doh, if it is one thing the confirmations from Snowden
+documented, it is that the entire population in USA is wiretapped, one
+way or another. Of course the president candidates were wiretapped,
+alongside the senators, judges and the rest of the people in USA.</p>
+
+<p>Next, the Federal Bureau of Investigation ask the Department of
+Justice to go public rejecting the claims that Donald Trump was
+wiretapped illegally. I fail to see the relevance, given that I am
+sure the surveillance industry in USA believe they have all the legal
+backing they need to conduct mass surveillance on the entire
+world.</p>
+
+<p>There is even the director of the FBI stating that he never saw an
+order requesting wiretapping of Donald Trump. That is not very
+surprising, given how the FISA court work, with all its activity being
+secret. Perhaps he only heard about it?</p>
+
+<p>What I find most sad in this story is how Norwegian journalists
+present it. In a news reports the other day in the radio from the
+Norwegian National broadcasting Company (NRK), I heard the journalist
+claim that 'the FBI denies any wiretapping', while the reality is that
+'the FBI denies any illegal wiretapping'. There is a fundamental and
+important difference, and it make me sad that the journalists are
+unable to grasp it.</p>
+
+<p><strong>Update 2017-03-13:</strong> Look like
+<a href="https://theintercept.com/2017/03/13/rand-paul-is-right-nsa-routinely-monitors-americans-communications-without-warrants/">The
+Intercept report that US Senator Rand Paul confirm what I state above</a>.</p>
</description>
</item>
<item>
- <title>New lsdvd release version 0.17 is ready</title>
- <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
- <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
- <description><p>The <a href="https://sourceforge.net/p/lsdvd/">lsdvd project</a>
-got a new set of developers a few weeks ago, after the original
-developer decided to step down and pass the project to fresh blood.
-This project is now maintained by Petter Reinholdtsen and Steve
-Dibb.</p>
-
-<p>I just wrapped up
-<a href="https://sourceforge.net/p/lsdvd/mailman/message/32896061/">a
-new lsdvd release</a>, available in git or from
-<a href="https://sourceforge.net/projects/lsdvd/files/lsdvd/">the
-download page</a>. This is the changelog dated 2014-10-03 for version
-0.17.</p>
-
-<ul>
-
- <li>Ignore 'phantom' audio, subtitle tracks</li>
- <li>Check for garbage in the program chains, which indicate that a track is
- non-existant, to work around additional copy protection</li>
- <li>Fix displaying content type for audio tracks, subtitles</li>
- <li>Fix pallete display of first entry</li>
- <li>Fix include orders</li>
- <li>Ignore read errors in titles that would not be displayed anyway</li>
- <li>Fix the chapter count</li>
- <li>Make sure the array size and the array limit used when initialising
- the palette size is the same.</li>
- <li>Fix array printing.</li>
- <li>Correct subsecond calculations.</li>
- <li>Add sector information to the output format.</li>
- <li>Clean up code to be closer to ANSI C and compile without warnings
- with more GCC compiler warnings.</li>
+ <title>Norwegian Bokmål translation of The Debian Administrator's Handbook complete, proofreading in progress</title>
+ <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</guid>
+ <pubDate>Fri, 3 Mar 2017 14:50:00 +0100</pubDate>
+ <description><p>For almost a year now, we have been working on making a Norwegian
+Bokmål edition of <a href="https://debian-handbook.info/">The Debian
+Administrator's Handbook</a>. Now, thanks to the tireless effort of
+Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
+we are working on the proof reading to ensure consistent language and
+use of correct computer science terms. The plan is to make the book
+available on paper, as well as in electronic form. For that to
+happen, the proof reading must be completed and all the figures need
+to be translated. If you want to help out, get in touch.</p>
+
+<p><a href="http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf">A
+
+fresh PDF edition</a> in A4 format (the final book will have smaller
+pages) of the book created every morning is available for
+proofreading. If you find any errors, please
+<a href="https://hosted.weblate.org/projects/debian-handbook/">visit
+Weblate and correct the error</a>. The
+<a href="http://l.github.io/debian-handbook/stat/nb-NO/index.html">state
+of the translation including figures</a> is a useful source for those
+provide Norwegian bokmål screen shots and figures.</p>
+</description>
+ </item>
+
+ <item>
+ <title>Unlimited randomness with the ChaosKey?</title>
+ <link>http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</guid>
+ <pubDate>Wed, 1 Mar 2017 20:50:00 +0100</pubDate>
+ <description><p>A few days ago I ordered a small batch of
+<a href="http://altusmetrum.org/ChaosKey/">the ChaosKey</a>, a small
+USB dongle for generating entropy created by Bdale Garbee and Keith
+Packard. Yesterday it arrived, and I am very happy to report that it
+work great! According to its designers, to get it to work out of the
+box, you need the Linux kernel version 4.1 or later. I tested on a
+Debian Stretch machine (kernel version 4.9), and there it worked just
+fine, increasing the available entropy very quickly. I wrote a small
+test oneliner to test. It first print the current entropy level,
+drain /dev/random, and then print the entropy level for five seconds.
+Here is the situation without the ChaosKey inserted:</p>
+
+<blockquote><pre>
+% cat /proc/sys/kernel/random/entropy_avail; \
+ dd bs=1M if=/dev/random of=/dev/null count=1; \
+ for n in $(seq 1 5); do \
+ cat /proc/sys/kernel/random/entropy_avail; \
+ sleep 1; \
+ done
+300
+0+1 oppføringer inn
+0+1 oppføringer ut
+28 byte kopiert, 0,000264565 s, 106 kB/s
+4
+8
+12
+17
+21
+%
+</pre></blockquote>
+
+<p>The entropy level increases by 3-4 every second. In such case any
+application requiring random bits (like a HTTPS enabled web server)
+will halt and wait for more entrpy. And here is the situation with
+the ChaosKey inserted:</p>
+
+<blockquote><pre>
+% cat /proc/sys/kernel/random/entropy_avail; \
+ dd bs=1M if=/dev/random of=/dev/null count=1; \
+ for n in $(seq 1 5); do \
+ cat /proc/sys/kernel/random/entropy_avail; \
+ sleep 1; \
+ done
+1079
+0+1 oppføringer inn
+0+1 oppføringer ut
+104 byte kopiert, 0,000487647 s, 213 kB/s
+433
+1028
+1031
+1035
+1038
+%
+</pre></blockquote>
-</ul>
+<p>Quite the difference. :) I bought a few more than I need, in case
+someone want to buy one here in Norway. :)</p>
-<p>This change bring together patches for lsdvd in use in various
-Linux and Unix distributions, as well as patches submitted to the
-project the last nine years. Please check it out. :)</p>
+<p>Update: The dongle was presented at Debconf last year. You might
+find <a href="https://debconf16.debconf.org/talks/94/">the talk
+recording illuminating</a>. It explains exactly what the source of
+randomness is, if you are unable to spot it from the schema drawing
+available from the ChaosKey web site linked at the start of this blog
+post.</p>
+</description>
+ </item>
+
+ <item>
+ <title>Detect OOXML files with undefined behaviour?</title>
+ <link>http://people.skolelinux.org/pere/blog/Detect_OOXML_files_with_undefined_behaviour_.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Detect_OOXML_files_with_undefined_behaviour_.html</guid>
+ <pubDate>Tue, 21 Feb 2017 00:20:00 +0100</pubDate>
+ <description><p>I just noticed
+<a href="http://www.arkivrad.no/aktuelt/riksarkivarens-forskrift-pa-horing">the
+new Norwegian proposal for archiving rules in the goverment</a> list
+<a href="http://www.ecma-international.org/publications/standards/Ecma-376.htm">ECMA-376</a>
+/ ISO/IEC 29500 (aka OOXML) as valid formats to put in long term
+storage. Luckily such files will only be accepted based on
+pre-approval from the National Archive. Allowing OOXML files to be
+used for long term storage might seem like a good idea as long as we
+forget that there are plenty of ways for a "valid" OOXML document to
+have content with no defined interpretation in the standard, which
+lead to a question and an idea.</p>
+
+<p>Is there any tool to detect if a OOXML document depend on such
+undefined behaviour? It would be useful for the National Archive (and
+anyone else interested in verifying that a document is well defined)
+to have such tool available when considering to approve the use of
+OOXML. I'm aware of the
+<a href="https://github.com/arlm/officeotron/">officeotron OOXML
+validator</a>, but do not know how complete it is nor if it will
+report use of undefined behaviour. Are there other similar tools
+available? Please send me an email if you know of any such tool.</p>
</description>
</item>
projects / homepage.git / blobdiff