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>Generating
3D prints in Debian using Cura and Slic3r(-prusa)
</title>
11 <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</guid>
13 <pubDate>Mon,
9 Oct
2017 10:
50:
00 +
0200</pubDate>
14 <description><p
>At my nearby maker space,
15 <a href=
"http://sonen.ifi.uio.no/
">Sonen
</a
>, I heard the story that it
16 was easier to generate gcode files for theyr
3D printers (Ultimake
2+)
17 on Windows and MacOS X than Linux, because the software involved had
18 to be manually compiled and set up on Linux while premade packages
19 worked out of the box on Windows and MacOS X. I found this annoying,
20 as the software involved,
21 <a href=
"https://github.com/Ultimaker/Cura
">Cura
</a
>, is free software
22 and should be trivial to get up and running on Linux if someone took
23 the time to package it for the relevant distributions. I even found
24 <a href=
"https://bugs.debian.org/
706656">a request for adding into
25 Debian
</a
> from
2013, which had seem some activity over the years but
26 never resulted in the software showing up in Debian. So a few days
27 ago I offered my help to try to improve the situation.
</p
>
29 <p
>Now I am very happy to see that all the packages required by a
30 working Cura in Debian are uploaded into Debian and waiting in the NEW
31 queue for the ftpmasters to have a look. You can track the progress
33 <a href=
"https://qa.debian.org/developer.php?email=
3dprinter-general%
40lists.alioth.debian.org
">the
34 status page for the
3D printer team
</a
>.
</p
>
36 <p
>The uploaded packages are a bit behind upstream, and was uploaded
37 now to get slots in
<a href=
"https://ftp-master.debian.org/new.html
">the NEW
38 queue
</a
> while we work up updating the packages to the latest
39 upstream version.
</p
>
41 <p
>On a related note, two competitors for Cura, which I found harder
42 to use and was unable to configure correctly for Ultimaker
2+ in the
43 short time I spent on it, are already in Debian. If you are looking
44 for
3D printer
"slicers
" and want something already available in
46 <a href=
"https://tracker.debian.org/pkg/slic3r
">slic3r
</a
> and
47 <a href=
"https://tracker.debian.org/pkg/slic3r-prusa
">slic3r-prusa
</a
>.
48 The latter is a fork of the former.
</p
>
53 <title>Mangler du en skrue, eller har du en skrue løs?
</title>
54 <link>http://people.skolelinux.org/pere/blog/Mangler_du_en_skrue__eller_har_du_en_skrue_l_s_.html
</link>
55 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Mangler_du_en_skrue__eller_har_du_en_skrue_l_s_.html
</guid>
56 <pubDate>Wed,
4 Oct
2017 09:
40:
00 +
0200</pubDate>
57 <description>Når jeg holder på med ulike prosjekter, så trenger jeg stadig ulike
58 skruer. Det siste prosjektet jeg holder på med er å lage
59 <a href=
"https://www.thingiverse.com/thing:
676916">en boks til en
60 HDMI-touch-skjerm
</a
> som skal brukes med Raspberry Pi. Boksen settes
61 sammen med skruer og bolter, og jeg har vært i tvil om hvor jeg kan
62 få tak i de riktige skruene. Clas Ohlson og Jernia i nærheten har
63 sjelden hatt det jeg trenger. Men her om dagen fikk jeg et fantastisk
64 tips for oss som bor i Oslo.
65 <a href=
"http://www.zachskruer.no/
">Zachariassen Jernvare AS
</a
> i
66 <a href=
"http://www.openstreetmap.org/?mlat=
59.93421&mlon=
10.76795#map=
19/
59.93421/
10.76795">Hegermannsgate
67 23A på Torshov
</a
> har et fantastisk utvalg, og åpent mellom
09:
00 og
68 17:
00. De selger skruer, muttere, bolter, skiver etc i løs vekt, og
69 så langt har jeg fått alt jeg har lett etter. De har i tillegg det
70 meste av annen jernvare, som verktøy, lamper, ledninger, etc. Jeg
71 håper de har nok kunder til å holde det gående lenge, da dette er en
72 butikk jeg kommer til å besøke ofte. Butikken er et funn å ha i
73 nabolaget for oss som liker å bygge litt selv. :)
</p
>
78 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass
</title>
79 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</link>
80 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</guid>
81 <pubDate>Fri,
29 Sep
2017 10:
30:
00 +
0200</pubDate>
82 <description><p
>Every mobile phone announce its existence over radio to the nearby
83 mobile cell towers. And this radio chatter is available for anyone
84 with a radio receiver capable of receiving them. Details about the
85 mobile phones with very good accuracy is of course collected by the
86 phone companies, but this is not the topic of this blog post. The
87 mobile phone radio chatter make it possible to figure out when a cell
88 phone is nearby, as it include the SIM card ID (IMSI). By paying
89 attention over time, one can see when a phone arrive and when it leave
90 an area. I believe it would be nice to make this information more
91 available to the general public, to make more people aware of how
92 their phones are announcing their whereabouts to anyone that care to
95 <p
>I am very happy to report that we managed to get something
96 visualizing this information up and running for
97 <a href=
"http://norwaymakers.org/osf17
">Oslo Skaperfestival
2017</a
>
98 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
99 library. The solution is based on the
100 <a href=
"http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
">simple
101 recipe for listening to GSM chatter
</a
> I posted a few days ago, and
102 will show up at the stand of
<a href=
"http://sonen.ifi.uio.no/
">Åpen
103 Sone from the Computer Science department of the University of
104 Oslo
</a
>. The presentation will show the nearby mobile phones (aka
105 IMSIs) as dots in a web browser graph, with lines to the dot
106 representing mobile base station it is talking to. It was working in
107 the lab yesterday, and was moved into place this morning.
</p
>
109 <p
>We set up a fairly powerful desktop machine using Debian
110 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
111 connected and visualize the visible cell phone towers using an
112 <a href=
"https://github.com/marlow925/hopglass
">English version of
113 Hopglass
</a
>. A fairly powerfull machine is needed as the
114 grgsm_livemon_headless processes from
115 <a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
> converting
116 the radio signal to data packages is quite CPU intensive.
</p
>
118 <p
>The frequencies to listen to, are identified using a slightly
119 patched scan-and-livemon (to set the --args values for each receiver),
120 and the Hopglass data is generated using the
121 <a href=
"https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output
">patches
122 in my meshviewer-output branch
</a
>. For some reason we could not get
123 more than four SDRs working. There is also a geographical map trying
124 to show the location of the base stations, but I believe their
125 coordinates are hardcoded to some random location in Germany, I
126 believe. The code should be replaced with code to look up location in
127 a text file, a sqlite database or one of the online databases
129 <a href=
"https://github.com/Oros42/IMSI-catcher/issues/
14">the github
130 issue for the topic
</a
>.
132 <p
>If this sound interesting, visit the stand at the festival!
</p
>
137 <title>Easier recipe to observe the cell phones around you
</title>
138 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</link>
139 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</guid>
140 <pubDate>Sun,
24 Sep
2017 08:
30:
00 +
0200</pubDate>
141 <description><p
>A little more than a month ago I wrote
142 <a href=
"http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
">how
143 to observe the SIM card ID (aka IMSI number) of mobile phones talking
144 to nearby mobile phone base stations using Debian GNU/Linux and a
145 cheap USB software defined radio
</a
>, and thus being able to pinpoint
146 the location of people and equipment (like cars and trains) with an
147 accuracy of a few kilometer. Since then we have worked to make the
148 procedure even simpler, and it is now possible to do this without any
149 manual frequency tuning and without building your own packages.
</p
>
151 <p
>The
<a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
>
152 package is now included in Debian testing and unstable, and the
153 IMSI-catcher code no longer require root access to fetch and decode
154 the GSM data collected using gr-gsm.
</p
>
156 <p
>Here is an updated recipe, using packages built by Debian and a git
157 clone of two python scripts:
</p
>
161 <li
>Start with a Debian machine running the Buster version (aka
164 <li
>Run
'<tt
>apt install gr-gsm python-numpy python-scipy
165 python-scapy
</tt
>' as root to install required packages.
</li
>
167 <li
>Fetch the code decoding GSM packages using
'<tt
>git clone
168 github.com/Oros42/IMSI-catcher.git
</tt
>'.
</li
>
170 <li
>Insert USB software defined radio supported by GNU Radio.
</li
>
172 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
173 scan-and-livemon
</tt
>' to locate the frequency of nearby base
174 stations and start listening for GSM packages on one of them.
</li
>
176 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
177 simple_IMSI-catcher.py
</tt
>' to display the collected information.
</li
>
181 <p
>Note, due to a bug somewhere the scan-and-livemon program (actually
182 <a href=
"https://github.com/ptrkrysik/gr-gsm/issues/
336">its underlying
183 program grgsm_scanner
</a
>) do not work with the HackRF radio. It does
184 work with RTL
8232 and other similar USB radio receivers you can get
186 (
<a href=
"https://www.ebay.com/sch/items/?_nkw=rtl+
2832">for example
187 from ebay
</a
>), so for now the solution is to scan using the RTL radio
188 and only use HackRF for fetching GSM data.
</p
>
190 <p
>As far as I can tell, a cell phone only show up on one of the
191 frequencies at the time, so if you are going to track and count every
192 cell phone around you, you need to listen to all the frequencies used.
193 To listen to several frequencies, use the --numrecv argument to
194 scan-and-livemon to use several receivers. Further, I am not sure if
195 phones using
3G or
4G will show as talking GSM to base stations, so
196 this approach might not see all phones around you. I typically see
197 0-
400 IMSI numbers an hour when looking around where I live.
</p
>
199 <p
>I
've tried to run the scanner on a
200 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
2 and
3
201 running Debian Buster
</a
>, but the grgsm_livemon_headless process seem
202 to be too CPU intensive to keep up. When GNU Radio print
'O
' to
203 stdout, I am told there it is caused by a buffer overflow between the
204 radio and GNU Radio, caused by the program being unable to read the
205 GSM data fast enough. If you see a stream of
'O
's from the terminal
206 where you started scan-and-livemon, you need a give the process more
207 CPU power. Perhaps someone are able to optimize the code to a point
208 where it become possible to set up RPi3 based GSM sniffers? I tried
209 using Raspbian instead of Debian, but there seem to be something wrong
210 with GNU Radio on raspbian, causing glibc to abort().
</p
>
215 <title>Datalagringsdirektivet kaster skygger over Høyre og Arbeiderpartiet
</title>
216 <link>http://people.skolelinux.org/pere/blog/Datalagringsdirektivet_kaster_skygger_over_H_yre_og_Arbeiderpartiet.html
</link>
217 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Datalagringsdirektivet_kaster_skygger_over_H_yre_og_Arbeiderpartiet.html
</guid>
218 <pubDate>Thu,
7 Sep
2017 21:
35:
00 +
0200</pubDate>
219 <description><p
>For noen dager siden publiserte Jon Wessel-Aas en bloggpost om
220 «
<a href=
"http://www.uhuru.biz/?p=
1821">Konklusjonen om datalagring som
221 EU-kommisjonen ikke ville at vi skulle få se
</a
>». Det er en
222 interessant gjennomgang av EU-domstolens syn på snurpenotovervåkning
223 av befolkningen, som er klar på at det er i strid med
224 EU-lovgivingen.
</p
>
226 <p
>Valgkampen går for fullt i Norge, og om noen få dager er siste
227 frist for å avgi stemme. En ting er sikkert, Høyre og Arbeiderpartiet
229 <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
230 gangen heller
</a
>. Jeg har ikke glemt at de tvang igjennom loven som
231 skulle pålegge alle data- og teletjenesteleverandører å overvåke alle
232 sine kunder. En lov som er vedtatt, og aldri opphevet igjen.
</p
>
234 <p
>Det er tydelig fra diskusjonen rundt grenseløs digital overvåkning
235 (eller
"Digital Grenseforsvar
" som det kalles i Orvellisk nytale) at
236 hverken Høyre og Arbeiderpartiet har noen prinsipielle sperrer mot å
237 overvåke hele befolkningen, og diskusjonen så langt tyder på at flere
238 av de andre partiene heller ikke har det. Mange av
239 <a href=
"https://data.holderdeord.no/votes/
1301946411e
">de som stemte
240 for Datalagringsdirektivet i Stortinget
</a
> (
64 fra Arbeiderpartiet,
241 25 fra Høyre) er fortsatt aktive og argumenterer fortsatt for å radere
242 vekk mer av innbyggernes privatsfære.
</p
>
244 <p
>Når myndighetene demonstrerer sin mistillit til folket, tror jeg
245 folket selv bør legge litt innsats i å verne sitt privatliv, ved å ta
246 i bruk ende-til-ende-kryptert kommunikasjon med sine kjente og kjære,
247 og begrense hvor mye privat informasjon som deles med uvedkommende.
248 Det er jo ingenting som tyder på at myndighetene kommer til å være vår
250 <a href=
"http://people.skolelinux.org/pere/blog/How_to_talk_with_your_loved_ones_in_private.html
">Det
251 er mange muligheter
</a
>. Selv har jeg litt sans for
252 <a href=
"https://ring.cx/
">Ring
</a
>, som er basert på p2p-teknologi
253 uten sentral kontroll, er fri programvare, og støtter meldinger, tale
254 og video. Systemet er tilgjengelig ut av boksen fra
255 <a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> og
256 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, og det
257 finnes pakker for Android, MacOSX og Windows. Foreløpig er det få
258 brukere med Ring, slik at jeg også bruker
259 <a href=
"https://signal.org/
">Signal
</a
> som nettleserutvidelse.
</p
>
264 <title>Simpler recipe on how to make a simple $
7 IMSI Catcher using Debian
</title>
265 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</link>
266 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</guid>
267 <pubDate>Wed,
9 Aug
2017 23:
59:
00 +
0200</pubDate>
268 <description><p
>On friday, I came across an interesting article in the Norwegian
269 web based ICT news magazine digi.no on
270 <a href=
"https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-
60-kroner-na-kan-mobiler-kartlegges-av-alle/
398588">how
271 to collect the IMSI numbers of nearby cell phones
</a
> using the cheap
272 DVB-T software defined radios. The article refered to instructions
273 and
<a href=
"https://www.youtube.com/watch?v=UjwgNd_as30
">a recipe by
274 Keld Norman on Youtube on how to make a simple $
7 IMSI Catcher
</a
>, and I decided to test them out.
</p
>
276 <p
>The instructions said to use Ubuntu, install pip using apt (to
277 bypass apt), use pip to install pybombs (to bypass both apt and pip),
278 and the ask pybombs to fetch and build everything you need from
279 scratch. I wanted to see if I could do the same on the most recent
280 Debian packages, but this did not work because pybombs tried to build
281 stuff that no longer build with the most recent openssl library or
282 some other version skew problem. While trying to get this recipe
283 working, I learned that the apt-
>pip-
>pybombs route was a long detour,
284 and the only piece of software dependency missing in Debian was the
285 gr-gsm package. I also found out that the lead upstream developer of
286 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
287 Debian packages provided in an Ubuntu PPA repository. All I needed to
288 do was to dget the Debian source package and built it.
</p
>
290 <p
>The IMSI collector is a python script listening for packages on the
291 loopback network device and printing to the terminal some specific GSM
292 packages with IMSI numbers in them. The code is fairly short and easy
293 to understand. The reason this work is because gr-gsm include a tool
294 to read GSM data from a software defined radio like a DVB-T USB stick
295 and other software defined radios, decode them and inject them into a
296 network device on your Linux machine (using the loopback device by
297 default). This proved to work just fine, and I
've been testing the
298 collector for a few days now.
</p
>
300 <p
>The updated and simpler recipe is thus to
</p
>
304 <li
>start with a Debian machine running Stretch or newer,
</li
>
306 <li
>build and install the gr-gsm package available from
307 <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
>
309 <li
>clone the git repostory from
<a href=
"https://github.com/Oros42/IMSI-catcher
">https://github.com/Oros42/IMSI-catcher
</a
>,
</li
>
311 <li
>run grgsm_livemon and adjust the frequency until the terminal
312 where it was started is filled with a stream of text (meaning you
313 found a GSM station).
</li
>
315 <li
>go into the IMSI-catcher directory and run
'sudo python simple_IMSI-catcher.py
' to extract the IMSI numbers.
</li
>
319 <p
>To make it even easier in the future to get this sniffer up and
320 running, I decided to package
321 <a href=
"https://github.com/ptrkrysik/gr-gsm/
">the gr-gsm project
</a
>
322 for Debian (
<a href=
"https://bugs.debian.org/
871055">WNPP
323 #
871055</a
>), and the package was uploaded into the NEW queue today.
324 Luckily the gnuradio maintainer has promised to help me, as I do not
325 know much about gnuradio stuff yet.
</p
>
327 <p
>I doubt this
"IMSI cacher
" is anywhere near as powerfull as
328 commercial tools like
329 <a href=
"https://www.thespyphone.com/portable-imsi-imei-catcher/
">The
330 Spy Phone Portable IMSI / IMEI Catcher
</a
> or the
331 <a href=
"https://en.wikipedia.org/wiki/Stingray_phone_tracker
">Harris
332 Stingray
</a
>, but I hope the existance of cheap alternatives can make
333 more people realise how their whereabouts when carrying a cell phone
334 is easily tracked. Seeing the data flow on the screen, realizing that
335 I live close to a police station and knowing that the police is also
336 wearing cell phones, I wonder how hard it would be for criminals to
337 track the position of the police officers to discover when there are
338 police near by, or for foreign military forces to track the location
339 of the Norwegian military forces, or for anyone to track the location
340 of government officials...
</p
>
342 <p
>It is worth noting that the data reported by the IMSI-catcher
343 script mentioned above is only a fraction of the data broadcasted on
344 the GSM network. It will only collect one frequency at the time,
345 while a typical phone will be using several frequencies, and not all
346 phones will be using the frequencies tracked by the grgsm_livemod
347 program. Also, there is a lot of radio chatter being ignored by the
348 simple_IMSI-catcher script, which would be collected by extending the
349 parser code. I wonder if gr-gsm can be set up to listen to more than
350 one frequency?
</p
>
355 <title>Norwegian Bokmål edition of Debian Administrator
's Handbook is now available
</title>
356 <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</link>
357 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</guid>
358 <pubDate>Tue,
25 Jul
2017 21:
10:
00 +
0200</pubDate>
359 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2017-
07-
25-debian-handbook-nb-testprint.png
"/
></p
>
361 <p
>I finally received a copy of the Norwegian Bokmål edition of
362 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
363 Handbook
</a
>". This test copy arrived in the mail a few days ago, and
364 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
365 <a href=
"https://debian-handbook.info/get/#norwegian
">is available
366 from lulu.com
</a
>. If you buy it quickly, you save
25% on the list
367 price. The book is also available for download in electronic form as
368 PDF, EPUB and Mobipocket, as can be
369 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
370 as a web page
</a
>.
</p
>
372 <p
>This is the second book I publish (the first was the book
373 "<a href=
"http://free-culture.cc/
">Free Culture
</a
>" by Lawrence Lessig
375 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">English
</a
>,
376 <a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">French
</a
>
378 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Norwegian
379 Bokmål
</a
>), and I am very excited to finally wrap up this
381 "<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
382 for Debian-administratoren
</a
>" will be well received.
</p
>
387 <title>«Rapporten ser ikke på informasjonssikkerhet knyttet til personlig integritet»
</title>
388 <link>http://people.skolelinux.org/pere/blog/_Rapporten_ser_ikke_p__informasjonssikkerhet_knyttet_til_personlig_integritet_.html
</link>
389 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/_Rapporten_ser_ikke_p__informasjonssikkerhet_knyttet_til_personlig_integritet_.html
</guid>
390 <pubDate>Tue,
27 Jun
2017 17:
50:
00 +
0200</pubDate>
391 <description><p
>Jeg kom over teksten
392 «
<a href=
"https://freedom-to-tinker.com/
2017/
06/
21/killing-car-privacy-by-federal-mandate/
">Killing
393 car privacy by federal mandate
</a
>» av Leonid Reyzin på Freedom to
394 Tinker i dag, og det gleder meg å se en god gjennomgang om hvorfor det
395 er et urimelig inngrep i privatsfæren å la alle biler kringkaste sin
396 posisjon og bevegelse via radio. Det omtalte forslaget basert på
397 Dedicated Short Range Communication (DSRC) kalles Basic Safety Message
398 (BSM) i USA og Cooperative Awareness Message (CAM) i Europa, og det
399 norske Vegvesenet er en av de som ser ut til å kunne tenke seg å
400 pålegge alle biler å fjerne nok en bit av innbyggernes privatsfære.
401 Anbefaler alle å lese det som står der.
403 <p
>Mens jeg tittet litt på DSRC på biler i Norge kom jeg over et sitat
404 jeg synes er illustrativt for hvordan det offentlige Norge håndterer
405 problemstillinger rundt innbyggernes privatsfære i SINTEF-rapporten
406 «
<a href=
"https://www.sintef.no/publikasjoner/publikasjon/Download/?pubid=SINTEF+A23933
">Informasjonssikkerhet
407 i AutoPASS-brikker
</a
>» av Trond Foss:
</p
>
409 <p
><blockquote
>
410 «Rapporten ser ikke på informasjonssikkerhet knyttet til personlig
412 </blockquote
></p
>
414 <p
>Så enkelt kan det tydeligvis gjøres når en vurderer
415 informasjonssikkerheten. Det holder vel at folkene på toppen kan si
416 at «Personvernet er ivaretatt», som jo er den populære intetsigende
417 frasen som gjør at mange tror enkeltindividers integritet tas vare på.
418 Sitatet fikk meg til å undres på hvor ofte samme tilnærming, å bare se
419 bort fra behovet for personlig itegritet, blir valgt når en velger å
420 legge til rette for nok et inngrep i privatsfæren til personer i
421 Norge. Det er jo sjelden det får reaksjoner. Historien om
422 reaksjonene på Helse Sør-Østs tjenesteutsetting er jo sørgelig nok et
423 unntak og toppen av isfjellet, desverre. Tror jeg fortsatt takker nei
424 til både AutoPASS og holder meg så langt unna det norske helsevesenet
425 som jeg kan, inntil de har demonstrert og dokumentert at de verdsetter
426 individets privatsfære og personlige integritet høyere enn kortsiktig
427 gevist og samfunnsnytte.
</p
>
432 <title>Updated sales number for my Free Culture paper editions
</title>
433 <link>http://people.skolelinux.org/pere/blog/Updated_sales_number_for_my_Free_Culture_paper_editions.html
</link>
434 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Updated_sales_number_for_my_Free_Culture_paper_editions.html
</guid>
435 <pubDate>Mon,
12 Jun
2017 11:
40:
00 +
0200</pubDate>
436 <description><p
>It is pleasing to see that the work we put down in publishing new
437 editions of the classic
<a href=
"http://www.free-culture.cc/
">Free
438 Culture book
</a
> by the founder of the Creative Commons movement,
439 Lawrence Lessig, is still being appreciated. I had a look at the
440 latest sales numbers for the paper edition today. Not too impressive,
441 but happy to see some buyers still exist. All the revenue from the
442 books is sent to the
<a href=
"https://creativecommons.org/
">Creative
443 Commons Corporation
</a
>, and they receive the largest cut if you buy
444 directly from Lulu. Most books are sold via Amazon, with Ingram
445 second and only a small fraction directly from Lulu. The ebook
446 edition is available for free from
447 <a href=
"https://github.com/petterreinholdtsen/free-culture-lessig
">Github
</a
>.
</p
>
449 <table border=
"0">
450 <tr
><th rowspan=
"2" valign=
"bottom
">Title / language
</th
><th colspan=
"3">Quantity
</th
></tr
>
451 <tr
><th
>2016 jan-jun
</th
><th
>2016 jul-dec
</th
><th
>2017 jan-may
</th
></tr
>
454 <td
><a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">Culture Libre / French
</a
></td
>
455 <td align=
"right
">3</td
>
456 <td align=
"right
">6</td
>
457 <td align=
"right
">15</td
>
461 <td
><a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Fri kultur / Norwegian
</a
></td
>
462 <td align=
"right
">7</td
>
463 <td align=
"right
">1</td
>
464 <td align=
"right
">0</td
>
468 <td
><a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">Free Culture / English
</a
></td
>
469 <td align=
"right
">14</td
>
470 <td align=
"right
">27</td
>
471 <td align=
"right
">16</td
>
475 <td
>Total
</td
>
476 <td align=
"right
">24</td
>
477 <td align=
"right
">34</td
>
478 <td align=
"right
">31</td
>
483 <p
>A bit sad to see the low sales number on the Norwegian edition, and
484 a bit surprising the English edition still selling so well.
</p
>
486 <p
>If you would like to translate and publish the book in your native
487 language, I would be happy to help make it happen. Please get in
493 <title>Release
0.1.1 of free software archive system Nikita announced
</title>
494 <link>http://people.skolelinux.org/pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html
</link>
495 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html
</guid>
496 <pubDate>Sat,
10 Jun
2017 00:
40:
00 +
0200</pubDate>
497 <description><p
>I am very happy to report that the
498 <a href=
"https://github.com/hiOA-ABI/nikita-noark5-core
">Nikita Noark
5
499 core project
</a
> tagged its second release today. The free software
500 solution is an implementation of the Norwegian archive standard Noark
501 5 used by government offices in Norway. These were the changes in
502 version
0.1.1 since version
0.1.0 (from NEWS.md):
506 <li
>Continued work on the angularjs GUI, including document upload.
</li
>
507 <li
>Implemented correspondencepartPerson, correspondencepartUnit and
508 correspondencepartInternal
</li
>
509 <li
>Applied for coverity coverage and started submitting code on
510 regualr basis.
</li
>
511 <li
>Started fixing bugs reported by coverity
</li
>
512 <li
>Corrected and completed HATEOAS links to make sure entire API is
513 available via URLs in _links.
</li
>
514 <li
>Corrected all relation URLs to use trailing slash.
</li
>
515 <li
>Add initial support for storing data in ElasticSearch.
</li
>
516 <li
>Now able to receive and store uploaded files in the archive.
</li
>
517 <li
>Changed JSON output for object lists to have relations in _links.
</li
>
518 <li
>Improve JSON output for empty object lists.
</li
>
519 <li
>Now uses correct MIME type application/vnd.noark5-v4+json.
</li
>
520 <li
>Added support for docker container images.
</li
>
521 <li
>Added simple API browser implemented in JavaScript/Angular.
</li
>
522 <li
>Started on archive client implemented in JavaScript/Angular.
</li
>
523 <li
>Started on prototype to show the public mail journal.
</li
>
524 <li
>Improved performance by disabling Sprint FileWatcher.
</li
>
525 <li
>Added support for
'arkivskaper
',
'saksmappe
' and
'journalpost
'.
</li
>
526 <li
>Added support for some metadata codelists.
</li
>
527 <li
>Added support for Cross-origin resource sharing (CORS).
</li
>
528 <li
>Changed login method from Basic Auth to JSON Web Token (RFC
7519)
530 <li
>Added support for GET-ing ny-* URLs.
</li
>
531 <li
>Added support for modifying entities using PUT and eTag.
</li
>
532 <li
>Added support for returning XML output on request.
</li
>
533 <li
>Removed support for English field and class names, limiting ourself
534 to the official names.
</li
>
535 <li
>...
</li
>
539 <p
>If this sound interesting to you, please contact us on IRC (#nikita
540 on irc.freenode.net) or email
541 (
<a href=
"https://lists.nuug.no/mailman/listinfo/nikita-noark
">nikita-noark
542 mailing list).
</p
>