Generated.

[homepage.git] / blog / index.rss

<?xml version="1.0" encoding="utf-8"?>
<rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/' xmlns:atom="http://www.w3.org/2005/Atom">
        <channel>
                <title>Petter Reinholdtsen</title>
                <description></description>
                <link>http://people.skolelinux.org/pere/blog/</link>
                <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
        
        <item>
                <title>Of course USA looses in cyber war - NSA and friends made sure it would happen</title>
                <link>http://people.skolelinux.org/pere/blog/Of_course_USA_looses_in_cyber_war___NSA_and_friends_made_sure_it_would_happen.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Of_course_USA_looses_in_cyber_war___NSA_and_friends_made_sure_it_would_happen.html</guid>
                <pubDate>Fri, 19 Dec 2014 13:10:00 +0100</pubDate>
                <description>&lt;p&gt;So, Sony caved in
(&lt;a href=&quot;https://twitter.com/RobLowe/status/545338568512917504&quot;&gt;according
to Rob Lowe&lt;/a&gt;) and demonstrated that America lost its first cyberwar
(&lt;a href=&quot;https://twitter.com/newtgingrich/status/545339074975109122&quot;&gt;According
to Newt Gingrich&lt;/a&gt;).  It should not surprise anyone, when the
whistle blower Edward Snowden documented that the government of USA
and their allies for many years have done their best to make sure the
technology used by its citizens is filled with security holes allowing
the secret services to spy on its own population.  No one in their
right minds could believe that the ability to snoop on the people all
over the globe could only be used by the personnel authorized to do so
by the president of the United States of America.  If the capabilities
are there, they will be used by friend and foe alike, and now they are
being used to bring Sony on its knees.&lt;/p&gt;

&lt;p&gt;I doubt it will a lesson learned, and expect USA to loose its next
cyber war too, given how eager the western intelligence communities
(and probably the non-western too, but it is less in the news) seem to
be to continue its current dragnet surveillance practice.&lt;/p&gt;

&lt;p&gt;There is a reason why China and others are trying to move away from
Windows to Linux and other alternatives, and it is not to avoid
sending its hard earned dollars to Cayman Islands (or whatever
&lt;a href=&quot;https://en.wikipedia.org/wiki/Tax_haven&quot;&gt;tax haven&lt;/a&gt;
Microsoft is using these days to collect the majority of its
income. :)&lt;/p&gt;
</description>
        </item>
        
        <item>
                <title>Klarer ikke Microsoft å holde på hemmeligheter?</title>
                <link>http://people.skolelinux.org/pere/blog/Klarer_ikke_Microsoft___holde_p__hemmeligheter_.html</link>
                <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Klarer_ikke_Microsoft___holde_p__hemmeligheter_.html</guid>
                <pubDate>Thu, 18 Dec 2014 10:10:00 +0100</pubDate>
                <description>&lt;p&gt;Må Microsoft virkelig ha hjelp av unger for å holde på
hemmelighetene sine?&lt;/p&gt;

&lt;p&gt;I dag kom det en fascinerende artikkel i Aftenposten om
&lt;a href=&quot;http://www.osloby.no/nyheter/Microsoft-ba-om-a-fa-bruke-bilder-og-video-av-barna-dine-7831036.html&quot;&gt;hva
Microsoft har foreslått at foreldre går med på&lt;/a&gt; for å la ungene
delta på &lt;a href=&quot;http://www.kidsakoder.no/&quot;&gt;Lær kidsa koding&lt;/a&gt; på
skolen.  De ber foreldrene om å få bruke bilder og video av ungene
kommersielt og gratis i all fremtid, hvilket var så drøyt at
Arbeiderpartiets bystyrerepresentant
&lt;a href=&quot;https://no.wikipedia.org/wiki/Per_Anders_Langerød&quot;&gt;Per Anders
Torvik Langerød&lt;/a&gt; tok opp saken opp under bystyrets muntlige
spørretime onsdag.  Resultatet av dette er at Microsoft har trukket
tilbake teksten i samtykkeerklæringen og kommunikasjonsdirektør
Christine Korme i Microsoft sier i artikkelen at «Vi vil presentere en
ny erklæring som gjør det helt klart i hvilken forbindelse materialet
skal brukes, altså ikke-kommersielt», hvilket jo er fint.  Jeg lurer
virkelig på hvordan teksten kunne slippe ut til foreldrene i første
omgang.  Her har noen på skolen ikke fulgt med i timen, eller mangler
grunnleggende personverntrening.&lt;/p&gt;

&lt;p&gt;Men bildet av samtykkeerklæringen inneholder også en annen
problematisk klausul, som ikke omtales overhodet i
Aftenposten-artikkelen.  Neste punkt i erklæringen lyder:&lt;/p&gt;

&lt;p&gt;&lt;blockquote&gt;
«Du aksepterer ikke å bruke eller videreformidle til en tredjepart
noen hemmelige eller fortrolige opplysninger som gis av Microsoft i
løpet av elevens deltagelse.»
&lt;/blockquote&gt;&lt;/p&gt;

&lt;p&gt;Mener Microsoft virkelig at foreldre og barn skal ta ansvar for at
Microsoft ikke klarer å holde hemmelig og fortrolig informasjon for
seg selv når de besøker en offentlig norsk skole?  Jeg ville nektet
plent å signert på en avtale med en slik klausul, da det er Microsofts
ansvar å holde på sine hemmeligheter, og ikke noe mine barn og min
familie tar på oss erstatningsansvar for hvis de kommer på avveie.&lt;/p&gt;

&lt;p&gt;Jeg lurer på om noen har fått se den nye samtykkeerklæringen?
Inneholder den fortsatt klausul om hemmelighold?  Hvor mange er det
som hittil har signert på den gamle samtykkeerklæringen?  Hvor har den
vært brukt?  Savnet svar på disse spørsmålene i artikkelen, da de som
har signert på den gamle vel vil være bundet av den selv om ingen
flere signerer på den.&lt;/p&gt;

&lt;p&gt;Lær kidsa koding er et glimrende initiativ, og jeg skulle ønske
noen av &lt;a href=&quot;http://www.nuug.no/&quot;&gt;foreningen NUUGs&lt;/a&gt; medlemmer
hadde kapasitet til å delta i initiativet på NUUGs vegne.  Selv tar
jobb, familie og eksisterende prosjekter allerede all tid.  Slik
Microsoft tydeligvis holder på er det behov for noen med et annet syn
på livet som bidragsyter her.&lt;/p&gt;
</description>
        </item>
        
        <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>&lt;p&gt;For noen dager siden
&lt;a href=&quot;http://www.nb.no/Hva-skjer/Aktuelt/Nyheter/Tapt-filmskatt-fra-Disney-funnet-i-Nasjonalbiblioteket&quot;&gt;annonserte
Nasjonalbiblioteket gladnyheten&lt;/a&gt; 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 vår felles historie.&lt;/p&gt;

&lt;p&gt;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
&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt;, som jeg holder på
&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;å
oversette til norsk&lt;/a&gt;:&lt;/p&gt;

&lt;p&gt;&lt;blockquote&gt;
&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;
&lt;/blockquote&gt;&lt;/p&gt;

&lt;p&gt;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å
&lt;a href=&quot;https://lovdata.no/dokument/NL/lov/1961-05-12-2&quot;&gt;Lovdata&lt;/a&gt;
og &lt;/a&gt;Wikipedia&lt;/A&gt;.  Her er et relevant &lt;a
href=&quot;https://no.wikipedia.org/wiki/Opphavsrett#Vernetid&quot;&gt;utsnitt fra
siden om opphavsrett i den norske Wikipedia&lt;/a&gt;:&lt;/p&gt;

&lt;p&gt;&lt;blockquote&gt;
  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.
&lt;/blockquote&gt;&lt;/p&gt;

&lt;p&gt;I følge nettstedet
&lt;a href=&quot;http://www.disneyshorts.org/shorts.aspx?shortID=75&quot;&gt;The
Encyclopedia of Disney Animated Shorts&lt;/a&gt; er følgende personer gitt
æren for denne kortfilmen:&lt;/p&gt;

&lt;dl&gt;

&lt;dt&gt;Regissør&lt;/dt&gt;
&lt;dd&gt;&lt;a href=&quot;https://en.wikipedia.org/wiki/Walt_Disney&quot;&gt;Walt Disney&lt;/a&gt;           (1901-12-05 – 1966-12-15) +70 år = 2037&lt;/dd&gt;

&lt;dt&gt;Animasjon
&lt;dd&gt;&lt;a href=&quot;https://en.wikipedia.org/wiki/Ub_Iwerks&quot;&gt;Ub Iwerks&lt;/a&gt;             (1901-03-24 – 1971-07-07) +70 år = 2042
&lt;br&gt;&lt;a href=&quot;https://en.wikipedia.org/wiki/Rollin_Hamilton&quot;&gt;Rollin &quot;Ham&quot; Hamilton&lt;/a&gt; (1898-10-28 - 1951-06-03) +70 år = 2022
&lt;br&gt;&lt;a href=&quot;https://en.wikipedia.org/wiki/Harman_and_Ising&quot;&gt;Hugh Harman&lt;/a&gt;           (1903-08-31 – 1982-11-25) +70 år = 2053&lt;/dd&gt;

&lt;dt&gt;Kamera
&lt;dd&gt;Mike Marcus (?-?)&lt;/dd&gt;

&lt;/dl&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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 utgitt.  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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;
</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>&lt;p&gt;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
&lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
Schubert&lt;/a&gt; and
&lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
McVittie&lt;/a&gt;.

&lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
keep sysvinit as your boot system, create a file
&lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
you upgrade:&lt;/p&gt;

&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
Package: systemd-sysv
Pin: release o=Debian
Pin-Priority: -1
&lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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:

&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
&lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;

&lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;

&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
d-i preseed/late_command string in-target apt-get install -y sysvinit-core
&lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;

&lt;p&gt;One can of course also do this after the first boot by installing
the sysvinit-core package.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;Update 2014-11-26: Inspired by
&lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
line.&lt;/p&gt;
</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>&lt;p&gt;For en stund tilbake spurte jeg Fornyingsdepartementet om hvilke
juridiske vurderinger rundt patentproblemstillingen som var gjort da
H.264 ble tatt inn i &lt;a href=&quot;http://standard.difi.no/&quot;&gt;statens
referansekatalog over standarder&lt;/a&gt;.  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
&lt;a href=&quot;http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&amp;do=get&amp;target=kongelig-resolusjon.pdf&quot;&gt;PDF-utgaven av&lt;/a&gt;
datert 2009-06-03 (saksnummer 200803291, saksbehandler Henrik
Linnestad).&lt;/p&gt;

&lt;p&gt;Der står det følgende om problemstillingen:&lt;/p&gt;

&lt;p&gt;&lt;blockquote&gt;
&lt;strong&gt;4.4 Patentproblematikk&lt;/strong&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;Spesielt for utvikling av fri programvare er patenter
problematisk. GPL, en &quot;grunnleggende&quot; 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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;/blockquote&gt;&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;
</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>&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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
&lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
this on the FreedomBox project mailing list in October&lt;/a&gt; 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
&lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
propose a similar method / protocol to pass emails between users.&lt;/p&gt;

&lt;p&gt;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
&lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
source code for the Debian package&lt;/a&gt; is available from github.  I
plan to move it into Debian if further testing prove this to be a
useful approach.&lt;/p&gt;

&lt;p&gt;If you want to test this, set up a blank Debian machine without any
mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
get rid of exim4).  Install tor, clone the git repository mentioned
above, build the deb and install it on the machine.  Next, run
&lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; 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:&lt;/p&gt;

&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
torsocks swaks --server dutlqrrmjhtfa3vp.onion \
  --to fbx@dutlqrrmjhtfa3vp.onion
&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;

&lt;p&gt;This will test the SMTP delivery using tor.  Replace the email
address with your own address to test your server. :)&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;Until I wipe my test machine, I can be reached using the
&lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
SMTorP. :)&lt;/p&gt;
</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>&lt;p&gt;I am happy to report that I on behalf of the Debian Edu team just
sent out
&lt;a href=&quot;https://lists.debian.org/debian-edu-announce/2014/10/msg00000.html&quot;&gt;this
announcement&lt;/a&gt;:&lt;/p&gt;

&lt;pre&gt;
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] &amp;lt;URL: &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Jessie&quot;&gt;https://wiki.debian.org/DebianEdu/Documentation/Jessie&lt;/a&gt; &amp;gt;

Would you like to give your school&#39;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] &amp;lt;URL: &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;http://www.skolelinux.org/&lt;/a&gt; &amp;gt;
 [3] &amp;lt;URL: &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Educational_applications_included_in_Debian_Edu___Skolelinux__the_screenshot_collection____.html&quot;&gt;http://people.skolelinux.org/pere/blog/Educational_applications_included_in_Debian_Edu___Skolelinux__the_screenshot_collection____.html&lt;/a&gt; &amp;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] &amp;lt;URL: &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Jessie/Features&quot;&gt;https://wiki.debian.org/DebianEdu/Documentation/Jessie/Features&lt;/a&gt; &amp;gt;
 [5] &amp;lt;URL: &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;http://maintainer.skolelinux.org/debian-edu-doc/&lt;/a&gt; &amp;gt;

Where to get it
---------------

To download the multiarch netinstall CD release (624 MiB) you can use

 * &lt;a href=&quot;ftp://ftp.skolelinux.org/skolelinux-cd/debian-edu-8.0+edu0~alpha0-CD.iso&quot;&gt;ftp://ftp.skolelinux.org/skolelinux-cd/debian-edu-8.0+edu0~alpha0-CD.iso&lt;/a&gt;
 * &lt;a href=&quot;http://ftp.skolelinux.org/skolelinux-cd/debian-edu-8.0+edu0~alpha0-CD.iso&quot;&gt;http://ftp.skolelinux.org/skolelinux-cd/debian-edu-8.0+edu0~alpha0-CD.iso&lt;/a&gt;
 * 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 &quot;Plasma&quot; 4.11.12, GNOME 3.14, Xfce 4.10,
   LXDE 0.5.6 and MATE 1.8 (KDE &quot;Plasma&quot; 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] &amp;lt;URL: &lt;a href=&quot;http://www.debian.org/releases/jessie/releasenotes&quot;&gt;http://www.debian.org/releases/jessie/releasenotes&lt;/a&gt; &amp;gt;
 [7] &amp;lt;URL: &lt;a href=&quot;http://www.debian.org/releases/jessie/installmanual&quot;&gt;http://www.debian.org/releases/jessie/installmanual&lt;/a&gt; &amp;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&#39;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.

See the status page[8] for the complete list.

 [8] &amp;lt;URL: &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;https://wiki.debian.org/DebianEdu/Status/Jessie&lt;/a&gt; &amp;gt;

How to report bugs
------------------

&amp;lt;URL: &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/ReportBugs&quot;&gt;http://wiki.debian.org/DebianEdu/HowTo/ReportBugs&lt;/a&gt; &amp;gt;

About Debian
============

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.

Contact Information
For further information, please visit the Debian web pages[9] or send
mail to press@debian.org.

 [9] &amp;lt;URL: &lt;a href=&quot;http://www.debian.org/&quot;&gt;http://www.debian.org/&lt;/a&gt; &amp;gt;
&lt;/pre&gt;
</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>&lt;p&gt;I spent last weekend at &lt;a href=&quot;http://www.makercon.no/&quot;&gt;Makercon
Nordic&lt;/a&gt;, 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
&lt;a href=&quot;http://dvswitch.alioth.debian.org/wiki/&quot;&gt;dvswitch&lt;/a&gt;, a
camera and a VGA to DV convert box, and mixed video and slides
live.&lt;/p&gt;

&lt;p&gt;Hans-Petter did the post-processing, consisting of uploading the
around 180 GiB of raw video to Youtube, and the result is
&lt;a href=&quot;https://www.youtube.com/user/MakerConNordic/&quot;&gt;now becoming
public&lt;/a&gt; on the MakerConNordic account.  The videos have the license
NUUG always use on our recordings, which is
&lt;a href=&quot;http://creativecommons.org/licenses/by-sa/3.0/no/&quot;&gt;Creative
Commons Navngivelse-Del på samme vilkår 3.0 Norge&lt;/a&gt;.  Many great
talks available.  Check it out! :)&lt;/p&gt;
</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>&lt;p&gt;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,
&lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
listadmin program&lt;/a&gt;.  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:&lt;/p&gt;

&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
% 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
%
&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;If you install
&lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
with content like this, the moderation task is a breeze:&lt;/p&gt;

&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
username username@example.org
spamlevel 23
default discard
discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;

password secret
adminurl https://{domain}/mailman/admindb/{list}
mailman-list@lists.example.com

password hidden
other-list@otherserver.example.org
&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;

&lt;p&gt;There are other options to set as well.  Check the manual page to
learn the details.&lt;/p&gt;

&lt;p&gt;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:&lt;/p&gt;

&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
activities, please send Bitcoin donations to my address
&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;

&lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
configuration example.  Also, I&#39;ve been told that the
PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone.  Not
sure why.&lt;/p&gt;
</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>&lt;p&gt;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
&lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
package&lt;/a&gt; and its recent tasksel extension, it has now become easy
to do this using simple preseeding.&lt;/p&gt;

&lt;p&gt;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.)&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;The end result is two lines needed in your preseeding file to get
firmware installed automatically by the installer:&lt;/p&gt;

&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
base-installer base-installer/includes string isenkram-cli
apt-mirror-setup apt-setup/non-free boolean true
&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;If you decide to give this a go, please let me know (via email) how
this recipe work for you. :)&lt;/p&gt;

&lt;p&gt;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):&lt;/p&gt;

&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
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
&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;

&lt;p&gt;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:

&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
#!/bin/sh
#
PATH=/usr/sbin:$PATH
export PATH
isenkram-autoinstall-firmware -l
&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;

&lt;p&gt;With those two pieces in place, the firmware is installed by
tasksel during the normal d-i run. :)&lt;/p&gt;

&lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
--new-install&lt;/tt&gt; to get the list of packages that tasksel would
install.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
pilots in testing this feature, as isenkram is used there now to
install firmware, replacing the earlier scripts.&lt;/p&gt;
</description>
        </item>
        
        </channel>
</rss>