1 <?xml version=
"1.0" encoding=
"utf-8"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/' xmlns:
atom=
"http://www.w3.org/2005/Atom">
4 <title>Petter Reinholdtsen
</title>
5 <description></description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
7 <atom:link href=
"http://people.skolelinux.org/pere/blog/index.rss" rel=
"self" type=
"application/rss+xml" />
10 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass
</title>
11 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</guid>
13 <pubDate>Fri,
29 Sep
2017 10:
30:
00 +
0200</pubDate>
14 <description><p
>Every mobile phone announce its existence over radio to the nearby
15 mobile cell towers. And this radio chatter is available for anyone
16 with a radio receiver capable of receiving them. Details about the
17 mobile phones with very good accuracy is of course collected by the
18 phone companies, but this is not the topic of this blog post. The
19 mobile phone radio chatter make it possible to figure out when a cell
20 phone is nearby, as it include the SIM card ID (IMSI). By paying
21 attention over time, one can see when a phone arrive and when it leave
22 an area. I believe it would be nice to make this information more
23 available to the general public, to make more people aware of how
24 their phones are announcing their whereabouts to anyone that care to
27 <p
>I am very happy to report that we managed to get something
28 visualizing this information up and running for
29 <a href=
"http://norwaymakers.org/osf17
">Oslo Skaperfestival
2017</a
>
30 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
31 library. The solution is based on the
32 <a href=
"http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
">simple
33 recipe for listening to GSM chatter
</a
> I posted a few days ago, and
34 will show up at the stand of
<a href=
"http://sonen.ifi.uio.no/
">Åpen
35 Sone from the Computer Science department of the University of
36 Oslo
</a
>. The presentation will show the nearby mobile phones (aka
37 IMSIs) as dots in a web browser graph, with lines to the dot
38 representing mobile base station it is talking to. It was working in
39 the lab yesterday, and was moved into place this morning.
</p
>
41 <p
>We set up a fairly powerful desktop machine using Debian
42 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
43 connected and visualize the visible cell phone towers using an
44 <a href=
"https://github.com/marlow925/hopglass
">English version of
45 Hopglass
</a
>. A fairly powerfull machine is needed as the
46 grgsm_livemon_headless processes from
47 <a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
> converting
48 the radio signal to data packages is quite CPU intensive.
</p
>
50 <p
>The frequencies to listen to, are identified using a slightly
51 patched scan-and-livemon (to set the --args values for each receiver),
52 and the Hopglass data is generated using the
53 <a href=
"https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output
">patches
54 in my meshviewer-output branch
</a
>. For some reason we could not get
55 more than four SDRs working. There is also a geographical map trying
56 to show the location of the base stations, but I believe their
57 coordinates are hardcoded to some random location in Germany, I
58 believe. The code should be replaced with code to look up location in
59 a text file, a sqlite database or one of the online databases
61 <a href=
"https://github.com/Oros42/IMSI-catcher/issues/
14">the github
62 issue for the topic
</a
>.
64 <p
>If this sound interesting, visit the stand at the festival!
</p
>
69 <title>Easier recipe to observe the cell phones around you
</title>
70 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</link>
71 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</guid>
72 <pubDate>Sun,
24 Sep
2017 08:
30:
00 +
0200</pubDate>
73 <description><p
>A little more than a month ago I wrote
74 <a href=
"http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
">how
75 to observe the SIM card ID (aka IMSI number) of mobile phones talking
76 to nearby mobile phone base stations using Debian GNU/Linux and a
77 cheap USB software defined radio
</a
>, and thus being able to pinpoint
78 the location of people and equipment (like cars and trains) with an
79 accuracy of a few kilometer. Since then we have worked to make the
80 procedure even simpler, and it is now possible to do this without any
81 manual frequency tuning and without building your own packages.
</p
>
83 <p
>The
<a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
>
84 package is now included in Debian testing and unstable, and the
85 IMSI-catcher code no longer require root access to fetch and decode
86 the GSM data collected using gr-gsm.
</p
>
88 <p
>Here is an updated recipe, using packages built by Debian and a git
89 clone of two python scripts:
</p
>
93 <li
>Start with a Debian machine running the Buster version (aka
96 <li
>Run
'<tt
>apt install gr-gsm python-numpy python-scipy
97 python-scapy
</tt
>' as root to install required packages.
</li
>
99 <li
>Fetch the code decoding GSM packages using
'<tt
>git clone
100 github.com/Oros42/IMSI-catcher.git
</tt
>'.
</li
>
102 <li
>Insert USB software defined radio supported by GNU Radio.
</li
>
104 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
105 scan-and-livemon
</tt
>' to locate the frequency of nearby base
106 stations and start listening for GSM packages on one of them.
</li
>
108 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
109 simple_IMSI-catcher.py
</tt
>' to display the collected information.
</li
>
113 <p
>Note, due to a bug somewhere the scan-and-livemon program (actually
114 <a href=
"https://github.com/ptrkrysik/gr-gsm/issues/
336">its underlying
115 program grgsm_scanner
</a
>) do not work with the HackRF radio. It does
116 work with RTL
8232 and other similar USB radio receivers you can get
118 (
<a href=
"https://www.ebay.com/sch/items/?_nkw=rtl+
2832">for example
119 from ebay
</a
>), so for now the solution is to scan using the RTL radio
120 and only use HackRF for fetching GSM data.
</p
>
122 <p
>As far as I can tell, a cell phone only show up on one of the
123 frequencies at the time, so if you are going to track and count every
124 cell phone around you, you need to listen to all the frequencies used.
125 To listen to several frequencies, use the --numrecv argument to
126 scan-and-livemon to use several receivers. Further, I am not sure if
127 phones using
3G or
4G will show as talking GSM to base stations, so
128 this approach might not see all phones around you. I typically see
129 0-
400 IMSI numbers an hour when looking around where I live.
</p
>
131 <p
>I
've tried to run the scanner on a
132 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
2 and
3
133 running Debian Buster
</a
>, but the grgsm_livemon_headless process seem
134 to be too CPU intensive to keep up. When GNU Radio print
'O
' to
135 stdout, I am told there it is caused by a buffer overflow between the
136 radio and GNU Radio, caused by the program being unable to read the
137 GSM data fast enough. If you see a stream of
'O
's from the terminal
138 where you started scan-and-livemon, you need a give the process more
139 CPU power. Perhaps someone are able to optimize the code to a point
140 where it become possible to set up RPi3 based GSM sniffers? I tried
141 using Raspbian instead of Debian, but there seem to be something wrong
142 with GNU Radio on raspbian, causing glibc to abort().
</p
>
147 <title>Datalagringsdirektivet kaster skygger over Høyre og Arbeiderpartiet
</title>
148 <link>http://people.skolelinux.org/pere/blog/Datalagringsdirektivet_kaster_skygger_over_H_yre_og_Arbeiderpartiet.html
</link>
149 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Datalagringsdirektivet_kaster_skygger_over_H_yre_og_Arbeiderpartiet.html
</guid>
150 <pubDate>Thu,
7 Sep
2017 21:
35:
00 +
0200</pubDate>
151 <description><p
>For noen dager siden publiserte Jon Wessel-Aas en bloggpost om
152 «
<a href=
"http://www.uhuru.biz/?p=
1821">Konklusjonen om datalagring som
153 EU-kommisjonen ikke ville at vi skulle få se
</a
>». Det er en
154 interessant gjennomgang av EU-domstolens syn på snurpenotovervåkning
155 av befolkningen, som er klar på at det er i strid med
156 EU-lovgivingen.
</p
>
158 <p
>Valgkampen går for fullt i Norge, og om noen få dager er siste
159 frist for å avgi stemme. En ting er sikkert, Høyre og Arbeiderpartiet
161 <a href=
"http://people.skolelinux.org/pere/blog/Datalagringsdirektivet_gj_r_at_Oslo_H_yre_og_Arbeiderparti_ikke_f_r_min_stemme_i__r.html
">denne
162 gangen heller
</a
>. Jeg har ikke glemt at de tvang igjennom loven som
163 skulle pålegge alle data- og teletjenesteleverandører å overvåke alle
164 sine kunder. En lov som er vedtatt, og aldri opphevet igjen.
</p
>
166 <p
>Det er tydelig fra diskusjonen rundt grenseløs digital overvåkning
167 (eller
"Digital Grenseforsvar
" som det kalles i Orvellisk nytale) at
168 hverken Høyre og Arbeiderpartiet har noen prinsipielle sperrer mot å
169 overvåke hele befolkningen, og diskusjonen så langt tyder på at flere
170 av de andre partiene heller ikke har det. Mange av
171 <a href=
"https://data.holderdeord.no/votes/
1301946411e
">de som stemte
172 for Datalagringsdirektivet i Stortinget
</a
> (
64 fra Arbeiderpartiet,
173 25 fra Høyre) er fortsatt aktive og argumenterer fortsatt for å radere
174 vekk mer av innbyggernes privatsfære.
</p
>
176 <p
>Når myndighetene demonstrerer sin mistillit til folket, tror jeg
177 folket selv bør legge litt innsats i å verne sitt privatliv, ved å ta
178 i bruk ende-til-ende-kryptert kommunikasjon med sine kjente og kjære,
179 og begrense hvor mye privat informasjon som deles med uvedkommende.
180 Det er jo ingenting som tyder på at myndighetene kommer til å være vår
182 <a href=
"http://people.skolelinux.org/pere/blog/How_to_talk_with_your_loved_ones_in_private.html
">Det
183 er mange muligheter
</a
>. Selv har jeg litt sans for
184 <a href=
"https://ring.cx/
">Ring
</a
>, som er basert på p2p-teknologi
185 uten sentral kontroll, er fri programvare, og støtter meldinger, tale
186 og video. Systemet er tilgjengelig ut av boksen fra
187 <a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> og
188 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, og det
189 finnes pakker for Android, MacOSX og Windows. Foreløpig er det få
190 brukere med Ring, slik at jeg også bruker
191 <a href=
"https://signal.org/
">Signal
</a
> som nettleserutvidelse.
</p
>
196 <title>Simpler recipe on how to make a simple $
7 IMSI Catcher using Debian
</title>
197 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</link>
198 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</guid>
199 <pubDate>Wed,
9 Aug
2017 23:
59:
00 +
0200</pubDate>
200 <description><p
>On friday, I came across an interesting article in the Norwegian
201 web based ICT news magazine digi.no on
202 <a href=
"https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-
60-kroner-na-kan-mobiler-kartlegges-av-alle/
398588">how
203 to collect the IMSI numbers of nearby cell phones
</a
> using the cheap
204 DVB-T software defined radios. The article refered to instructions
205 and
<a href=
"https://www.youtube.com/watch?v=UjwgNd_as30
">a recipe by
206 Keld Norman on Youtube on how to make a simple $
7 IMSI Catcher
</a
>, and I decided to test them out.
</p
>
208 <p
>The instructions said to use Ubuntu, install pip using apt (to
209 bypass apt), use pip to install pybombs (to bypass both apt and pip),
210 and the ask pybombs to fetch and build everything you need from
211 scratch. I wanted to see if I could do the same on the most recent
212 Debian packages, but this did not work because pybombs tried to build
213 stuff that no longer build with the most recent openssl library or
214 some other version skew problem. While trying to get this recipe
215 working, I learned that the apt-
>pip-
>pybombs route was a long detour,
216 and the only piece of software dependency missing in Debian was the
217 gr-gsm package. I also found out that the lead upstream developer of
218 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
219 Debian packages provided in an Ubuntu PPA repository. All I needed to
220 do was to dget the Debian source package and built it.
</p
>
222 <p
>The IMSI collector is a python script listening for packages on the
223 loopback network device and printing to the terminal some specific GSM
224 packages with IMSI numbers in them. The code is fairly short and easy
225 to understand. The reason this work is because gr-gsm include a tool
226 to read GSM data from a software defined radio like a DVB-T USB stick
227 and other software defined radios, decode them and inject them into a
228 network device on your Linux machine (using the loopback device by
229 default). This proved to work just fine, and I
've been testing the
230 collector for a few days now.
</p
>
232 <p
>The updated and simpler recipe is thus to
</p
>
236 <li
>start with a Debian machine running Stretch or newer,
</li
>
238 <li
>build and install the gr-gsm package available from
239 <a href=
"http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/
">http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/
</a
>,
</li
>
241 <li
>clone the git repostory from
<a href=
"https://github.com/Oros42/IMSI-catcher
">https://github.com/Oros42/IMSI-catcher
</a
>,
</li
>
243 <li
>run grgsm_livemon and adjust the frequency until the terminal
244 where it was started is filled with a stream of text (meaning you
245 found a GSM station).
</li
>
247 <li
>go into the IMSI-catcher directory and run
'sudo python simple_IMSI-catcher.py
' to extract the IMSI numbers.
</li
>
251 <p
>To make it even easier in the future to get this sniffer up and
252 running, I decided to package
253 <a href=
"https://github.com/ptrkrysik/gr-gsm/
">the gr-gsm project
</a
>
254 for Debian (
<a href=
"https://bugs.debian.org/
871055">WNPP
255 #
871055</a
>), and the package was uploaded into the NEW queue today.
256 Luckily the gnuradio maintainer has promised to help me, as I do not
257 know much about gnuradio stuff yet.
</p
>
259 <p
>I doubt this
"IMSI cacher
" is anywhere near as powerfull as
260 commercial tools like
261 <a href=
"https://www.thespyphone.com/portable-imsi-imei-catcher/
">The
262 Spy Phone Portable IMSI / IMEI Catcher
</a
> or the
263 <a href=
"https://en.wikipedia.org/wiki/Stingray_phone_tracker
">Harris
264 Stingray
</a
>, but I hope the existance of cheap alternatives can make
265 more people realise how their whereabouts when carrying a cell phone
266 is easily tracked. Seeing the data flow on the screen, realizing that
267 I live close to a police station and knowing that the police is also
268 wearing cell phones, I wonder how hard it would be for criminals to
269 track the position of the police officers to discover when there are
270 police near by, or for foreign military forces to track the location
271 of the Norwegian military forces, or for anyone to track the location
272 of government officials...
</p
>
274 <p
>It is worth noting that the data reported by the IMSI-catcher
275 script mentioned above is only a fraction of the data broadcasted on
276 the GSM network. It will only collect one frequency at the time,
277 while a typical phone will be using several frequencies, and not all
278 phones will be using the frequencies tracked by the grgsm_livemod
279 program. Also, there is a lot of radio chatter being ignored by the
280 simple_IMSI-catcher script, which would be collected by extending the
281 parser code. I wonder if gr-gsm can be set up to listen to more than
282 one frequency?
</p
>
287 <title>Norwegian Bokmål edition of Debian Administrator
's Handbook is now available
</title>
288 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</link>
289 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</guid>
290 <pubDate>Tue,
25 Jul
2017 21:
10:
00 +
0200</pubDate>
291 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2017-
07-
25-debian-handbook-nb-testprint.png
"/
></p
>
293 <p
>I finally received a copy of the Norwegian Bokmål edition of
294 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
295 Handbook
</a
>". This test copy arrived in the mail a few days ago, and
296 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
297 <a href=
"https://debian-handbook.info/get/#norwegian
">is available
298 from lulu.com
</a
>. If you buy it quickly, you save
25% on the list
299 price. The book is also available for download in electronic form as
300 PDF, EPUB and Mobipocket, as can be
301 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
302 as a web page
</a
>.
</p
>
304 <p
>This is the second book I publish (the first was the book
305 "<a href=
"http://free-culture.cc/
">Free Culture
</a
>" by Lawrence Lessig
307 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">English
</a
>,
308 <a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">French
</a
>
310 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Norwegian
311 Bokmål
</a
>), and I am very excited to finally wrap up this
313 "<a href=
"http://www.lulu.com/shop/rapha%C3%ABl-hertzog-and-roland-mas/h%C3%A5ndbok-for-debian-administratoren/paperback/product-
23262290.html
">Håndbok
314 for Debian-administratoren
</a
>" will be well received.
</p
>
319 <title>«Rapporten ser ikke på informasjonssikkerhet knyttet til personlig integritet»
</title>
320 <link>http://people.skolelinux.org/pere/blog/_Rapporten_ser_ikke_p__informasjonssikkerhet_knyttet_til_personlig_integritet_.html
</link>
321 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/_Rapporten_ser_ikke_p__informasjonssikkerhet_knyttet_til_personlig_integritet_.html
</guid>
322 <pubDate>Tue,
27 Jun
2017 17:
50:
00 +
0200</pubDate>
323 <description><p
>Jeg kom over teksten
324 «
<a href=
"https://freedom-to-tinker.com/
2017/
06/
21/killing-car-privacy-by-federal-mandate/
">Killing
325 car privacy by federal mandate
</a
>» av Leonid Reyzin på Freedom to
326 Tinker i dag, og det gleder meg å se en god gjennomgang om hvorfor det
327 er et urimelig inngrep i privatsfæren å la alle biler kringkaste sin
328 posisjon og bevegelse via radio. Det omtalte forslaget basert på
329 Dedicated Short Range Communication (DSRC) kalles Basic Safety Message
330 (BSM) i USA og Cooperative Awareness Message (CAM) i Europa, og det
331 norske Vegvesenet er en av de som ser ut til å kunne tenke seg å
332 pålegge alle biler å fjerne nok en bit av innbyggernes privatsfære.
333 Anbefaler alle å lese det som står der.
335 <p
>Mens jeg tittet litt på DSRC på biler i Norge kom jeg over et sitat
336 jeg synes er illustrativt for hvordan det offentlige Norge håndterer
337 problemstillinger rundt innbyggernes privatsfære i SINTEF-rapporten
338 «
<a href=
"https://www.sintef.no/publikasjoner/publikasjon/Download/?pubid=SINTEF+A23933
">Informasjonssikkerhet
339 i AutoPASS-brikker
</a
>» av Trond Foss:
</p
>
341 <p
><blockquote
>
342 «Rapporten ser ikke på informasjonssikkerhet knyttet til personlig
344 </blockquote
></p
>
346 <p
>Så enkelt kan det tydeligvis gjøres når en vurderer
347 informasjonssikkerheten. Det holder vel at folkene på toppen kan si
348 at «Personvernet er ivaretatt», som jo er den populære intetsigende
349 frasen som gjør at mange tror enkeltindividers integritet tas vare på.
350 Sitatet fikk meg til å undres på hvor ofte samme tilnærming, å bare se
351 bort fra behovet for personlig itegritet, blir valgt når en velger å
352 legge til rette for nok et inngrep i privatsfæren til personer i
353 Norge. Det er jo sjelden det får reaksjoner. Historien om
354 reaksjonene på Helse Sør-Østs tjenesteutsetting er jo sørgelig nok et
355 unntak og toppen av isfjellet, desverre. Tror jeg fortsatt takker nei
356 til både AutoPASS og holder meg så langt unna det norske helsevesenet
357 som jeg kan, inntil de har demonstrert og dokumentert at de verdsetter
358 individets privatsfære og personlige integritet høyere enn kortsiktig
359 gevist og samfunnsnytte.
</p
>
364 <title>Updated sales number for my Free Culture paper editions
</title>
365 <link>http://people.skolelinux.org/pere/blog/Updated_sales_number_for_my_Free_Culture_paper_editions.html
</link>
366 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Updated_sales_number_for_my_Free_Culture_paper_editions.html
</guid>
367 <pubDate>Mon,
12 Jun
2017 11:
40:
00 +
0200</pubDate>
368 <description><p
>It is pleasing to see that the work we put down in publishing new
369 editions of the classic
<a href=
"http://www.free-culture.cc/
">Free
370 Culture book
</a
> by the founder of the Creative Commons movement,
371 Lawrence Lessig, is still being appreciated. I had a look at the
372 latest sales numbers for the paper edition today. Not too impressive,
373 but happy to see some buyers still exist. All the revenue from the
374 books is sent to the
<a href=
"https://creativecommons.org/
">Creative
375 Commons Corporation
</a
>, and they receive the largest cut if you buy
376 directly from Lulu. Most books are sold via Amazon, with Ingram
377 second and only a small fraction directly from Lulu. The ebook
378 edition is available for free from
379 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">Github
</a
>.
</p
>
381 <table border=
"0">
382 <tr
><th rowspan=
"2" valign=
"bottom
">Title / language
</th
><th colspan=
"3">Quantity
</th
></tr
>
383 <tr
><th
>2016 jan-jun
</th
><th
>2016 jul-dec
</th
><th
>2017 jan-may
</th
></tr
>
386 <td
><a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">Culture Libre / French
</a
></td
>
387 <td align=
"right
">3</td
>
388 <td align=
"right
">6</td
>
389 <td align=
"right
">15</td
>
393 <td
><a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Fri kultur / Norwegian
</a
></td
>
394 <td align=
"right
">7</td
>
395 <td align=
"right
">1</td
>
396 <td align=
"right
">0</td
>
400 <td
><a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">Free Culture / English
</a
></td
>
401 <td align=
"right
">14</td
>
402 <td align=
"right
">27</td
>
403 <td align=
"right
">16</td
>
407 <td
>Total
</td
>
408 <td align=
"right
">24</td
>
409 <td align=
"right
">34</td
>
410 <td align=
"right
">31</td
>
415 <p
>A bit sad to see the low sales number on the Norwegian edition, and
416 a bit surprising the English edition still selling so well.
</p
>
418 <p
>If you would like to translate and publish the book in your native
419 language, I would be happy to help make it happen. Please get in
425 <title>Release
0.1.1 of free software archive system Nikita announced
</title>
426 <link>http://people.skolelinux.org/pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html
</link>
427 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html
</guid>
428 <pubDate>Sat,
10 Jun
2017 00:
40:
00 +
0200</pubDate>
429 <description><p
>I am very happy to report that the
430 <a href=
"https://github.com/hiOA-ABI/nikita-noark5-core
">Nikita Noark
5
431 core project
</a
> tagged its second release today. The free software
432 solution is an implementation of the Norwegian archive standard Noark
433 5 used by government offices in Norway. These were the changes in
434 version
0.1.1 since version
0.1.0 (from NEWS.md):
438 <li
>Continued work on the angularjs GUI, including document upload.
</li
>
439 <li
>Implemented correspondencepartPerson, correspondencepartUnit and
440 correspondencepartInternal
</li
>
441 <li
>Applied for coverity coverage and started submitting code on
442 regualr basis.
</li
>
443 <li
>Started fixing bugs reported by coverity
</li
>
444 <li
>Corrected and completed HATEOAS links to make sure entire API is
445 available via URLs in _links.
</li
>
446 <li
>Corrected all relation URLs to use trailing slash.
</li
>
447 <li
>Add initial support for storing data in ElasticSearch.
</li
>
448 <li
>Now able to receive and store uploaded files in the archive.
</li
>
449 <li
>Changed JSON output for object lists to have relations in _links.
</li
>
450 <li
>Improve JSON output for empty object lists.
</li
>
451 <li
>Now uses correct MIME type application/vnd.noark5-v4+json.
</li
>
452 <li
>Added support for docker container images.
</li
>
453 <li
>Added simple API browser implemented in JavaScript/Angular.
</li
>
454 <li
>Started on archive client implemented in JavaScript/Angular.
</li
>
455 <li
>Started on prototype to show the public mail journal.
</li
>
456 <li
>Improved performance by disabling Sprint FileWatcher.
</li
>
457 <li
>Added support for
'arkivskaper
',
'saksmappe
' and
'journalpost
'.
</li
>
458 <li
>Added support for some metadata codelists.
</li
>
459 <li
>Added support for Cross-origin resource sharing (CORS).
</li
>
460 <li
>Changed login method from Basic Auth to JSON Web Token (RFC
7519)
462 <li
>Added support for GET-ing ny-* URLs.
</li
>
463 <li
>Added support for modifying entities using PUT and eTag.
</li
>
464 <li
>Added support for returning XML output on request.
</li
>
465 <li
>Removed support for English field and class names, limiting ourself
466 to the official names.
</li
>
467 <li
>...
</li
>
471 <p
>If this sound interesting to you, please contact us on IRC (#nikita
472 on irc.freenode.net) or email
473 (
<a href=
"https://lists.nuug.no/mailman/listinfo/nikita-noark
">nikita-noark
474 mailing list).
</p
>
479 <title>Idea for storing trusted timestamps in a Noark
5 archive
</title>
480 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html
</link>
481 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html
</guid>
482 <pubDate>Wed,
7 Jun
2017 21:
40:
00 +
0200</pubDate>
483 <description><p
><em
>This is a copy of
484 <a href=
"https://lists.nuug.no/pipermail/nikita-noark/
2017-June/
000297.html
">an
485 email I posted to the nikita-noark mailing list
</a
>. Please follow up
486 there if you would like to discuss this topic. The background is that
487 we are making a free software archive system based on the Norwegian
488 <a href=
"https://www.arkivverket.no/forvaltning-og-utvikling/regelverk-og-standarder/noark-standarden
">Noark
489 5 standard
</a
> for government archives.
</em
></p
>
491 <p
>I
've been wondering a bit lately how trusted timestamps could be
493 <a href=
"https://en.wikipedia.org/wiki/Trusted_timestamping
">Trusted
494 timestamps
</a
> can be used to verify that some information
495 (document/file/checksum/metadata) have not been changed since a
496 specific time in the past. This is useful to verify the integrity of
497 the documents in the archive.
</p
>
499 <p
>Then it occured to me, perhaps the trusted timestamps could be
500 stored as dokument variants (ie dokumentobjekt referered to from
501 dokumentbeskrivelse) with the filename set to the hash it is
504 <p
>Given a
"dokumentbeskrivelse
" with an associated
"dokumentobjekt
",
505 a new dokumentobjekt is associated with
"dokumentbeskrivelse
" with the
506 same attributes as the stamped dokumentobjekt except these
507 attributes:
</p
>
511 <li
>format -
> "RFC3161
"
512 <li
>mimeType -
> "application/timestamp-reply
"
513 <li
>formatDetaljer -
> "&lt;source URL for timestamp service
&gt;
"
514 <li
>filenavn -
> "&lt;sjekksum
&gt;.tsr
"
518 <p
>This assume a service following
519 <a href=
"https://tools.ietf.org/html/rfc3161
">IETF RFC
3161</a
> is
520 used, which specifiy the given MIME type for replies and the .tsr file
521 ending for the content of such trusted timestamp. As far as I can
522 tell from the Noark
5 specifications, it is OK to have several
523 variants/renderings of a dokument attached to a given
524 dokumentbeskrivelse objekt. It might be stretching it a bit to make
525 some of these variants represent crypto-signatures useful for
526 verifying the document integrity instead of representing the dokument
529 <p
>Using the source of the service in formatDetaljer allow several
530 timestamping services to be used. This is useful to spread the risk
531 of key compromise over several organisations. It would only be a
532 problem to trust the timestamps if all of the organisations are
533 compromised.
</p
>
535 <p
>The following oneliner on Linux can be used to generate the tsr
536 file. $input is the path to the file to checksum, and $sha256 is the
537 SHA-
256 checksum of the file (ie the
"<sjekksum
>.tsr
" value mentioned
540 <p
><blockquote
><pre
>
541 openssl ts -query -data
"$inputfile
" -cert -sha256 -no_nonce \
542 | curl -s -H
"Content-Type: application/timestamp-query
" \
543 --data-binary
"@-
" http://zeitstempel.dfn.de
> $sha256.tsr
544 </pre
></blockquote
></p
>
546 <p
>To verify the timestamp, you first need to download the public key
547 of the trusted timestamp service, for example using this command:
</p
>
549 <p
><blockquote
><pre
>
550 wget -O ca-cert.txt \
551 https://pki.pca.dfn.de/global-services-ca/pub/cacert/chain.txt
552 </pre
></blockquote
></p
>
554 <p
>Note, the public key should be stored alongside the timestamps in
555 the archive to make sure it is also available
100 years from now. It
556 is probably a good idea to standardise how and were to store such
557 public keys, to make it easier to find for those trying to verify
558 documents
100 or
1000 years from now. :)
</p
>
560 <p
>The verification itself is a simple openssl command:
</p
>
562 <p
><blockquote
><pre
>
563 openssl ts -verify -data $inputfile -in $sha256.tsr \
564 -CAfile ca-cert.txt -text
565 </pre
></blockquote
></p
>
567 <p
>Is there any reason this approach would not work? Is it somehow against
568 the Noark
5 specification?
</p
>
573 <title>Når nynorskoversettelsen svikter til eksamen...
</title>
574 <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</link>
575 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</guid>
576 <pubDate>Sat,
3 Jun
2017 08:
20:
00 +
0200</pubDate>
577 <description><p
><a href=
"http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-
622459b.html
">Aftenposten
578 melder i dag
</a
> om feil i eksamensoppgavene for eksamen i politikk og
579 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
580 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
581 på om den fri oversetterløsningen
582 <a href=
"https://www.apertium.org/
">Apertium
</a
> ville gjort en bedre
583 jobb enn Utdanningsdirektoratet. Det kan se slik ut.
</p
>
585 <p
>Her er bokmålsoppgaven fra eksamenen:
</p
>
588 <p
>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
589 rolle og muligheter til å håndtere internasjonale utfordringer, som
590 for eksempel flykningekrisen.
</p
>
592 <p
>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
595 <li
>Flykningeregnskapet
2016, UNHCR og IDMC
596 <li
>«Grenseløst Europa for fall» A-Magasinet,
26. november
2015
601 <p
>Dette oversetter Apertium slik:
</p
>
604 <p
>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
605 andre aktørar og høve til å handtera internasjonale utfordringar, som
606 til dømes *flykningekrisen.
</p
>
608 <p
>Vedleggja er døme på tekster som kan gje relevante perspektiv på
612 <li
>*Flykningeregnskapet
2016, *UNHCR og *IDMC
</li
>
613 <li
>«*Grenseløst Europa for fall» A-Magasinet,
26. november
2015</li
>
618 <p
>Ord som ikke ble forstått er markert med stjerne (*), og trenger
619 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
620 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
621 "andre aktørers rolle og muligheter til ...
" burde vært oversatt til
622 "rolla til andre aktørar og deira høve til ...
" eller noe slikt, men
623 det er kanskje flisespikking. Det understreker vel bare at det alltid
624 trengs korrekturlesning etter automatisk oversettelse.
</p
>