]> pere.pagekite.me Git - homepage.git/blob - blog/index.rss
Generated.
[homepage.git] / blog / index.rss
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">
3 <channel>
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" />
8
9 <item>
10 <title>Some notes on fault tolerant storage systems</title>
11 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_fault_tolerant_storage_systems.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_fault_tolerant_storage_systems.html</guid>
13 <pubDate>Wed, 1 Nov 2017 15:35:00 +0100</pubDate>
14 <description>&lt;p&gt;If you care about how fault tolerant your storage is, you might
15 find these articles and papers interesting. They have formed how I
16 think of when designing a storage system.&lt;/p&gt;
17
18 &lt;ul&gt;
19
20 &lt;li&gt;USENIX :login; &lt;a
21 href=&quot;https://www.usenix.org/publications/login/summer2017/ganesan&quot;&gt;Redundancy
22 Does Not Imply Fault Tolerance. Analysis of Distributed Storage
23 Reactions to Single Errors and Corruptions&lt;/a&gt; by Aishwarya Ganesan,
24 Ramnatthan Alagappan, Andrea C. Arpaci-Dusseau, and Remzi
25 H. Arpaci-Dusseau&lt;/li&gt;
26
27 &lt;li&gt;ZDNet
28 &lt;a href=&quot;http://www.zdnet.com/article/why-raid-5-stops-working-in-2009/&quot;&gt;Why
29 RAID 5 stops working in 2009&lt;/a&gt; by Robin Harris&lt;/li&gt;
30
31 &lt;li&gt;ZDNet
32 &lt;a href=&quot;http://www.zdnet.com/article/why-raid-6-stops-working-in-2019/&quot;&gt;Why
33 RAID 6 stops working in 2019&lt;/a&gt; by Robin Harris&lt;/li&gt;
34
35 &lt;li&gt;USENIX FAST&#39;07
36 &lt;a href=&quot;http://research.google.com/archive/disk_failures.pdf&quot;&gt;Failure
37 Trends in a Large Disk Drive Population&lt;/a&gt; by Eduardo Pinheiro,
38 Wolf-Dietrich Weber and Luiz André Barroso&lt;/li&gt;
39
40 &lt;li&gt;USENIX ;login: &lt;a
41 href=&quot;https://www.usenix.org/system/files/login/articles/hughes12-04.pdf&quot;&gt;Data
42 Integrity. Finding Truth in a World of Guesses and Lies&lt;/a&gt; by Doug
43 Hughes&lt;/li&gt;
44
45 &lt;li&gt;USENIX FAST&#39;08
46 &lt;a href=&quot;https://www.usenix.org/events/fast08/tech/full_papers/bairavasundaram/bairavasundaram_html/&quot;&gt;An
47 Analysis of Data Corruption in the Storage Stack&lt;/a&gt; by
48 L. N. Bairavasundaram, G. R. Goodson, B. Schroeder, A. C.
49 Arpaci-Dusseau, and R. H. Arpaci-Dusseau&lt;/li&gt;
50
51 &lt;li&gt;USENIX FAST&#39;07 &lt;a
52 href=&quot;https://www.usenix.org/legacy/events/fast07/tech/schroeder/schroeder_html/&quot;&gt;Disk
53 failures in the real world: what does an MTTF of 1,000,000 hours mean
54 to you?&lt;/a&gt; by B. Schroeder and G. A. Gibson.&lt;/li&gt;
55
56 &lt;li&gt;USENIX ;login: &lt;a
57 href=&quot;https://www.usenix.org/events/fast08/tech/full_papers/jiang/jiang_html/&quot;&gt;Are
58 Disks the Dominant Contributor for Storage Failures? A Comprehensive
59 Study of Storage Subsystem Failure Characteristics&lt;/a&gt; by Weihang
60 Jiang, Chongfeng Hu, Yuanyuan Zhou, and Arkady Kanevsky&lt;/li&gt;
61
62 &lt;li&gt;SIGMETRICS 2007
63 &lt;a href=&quot;http://research.cs.wisc.edu/adsl/Publications/latent-sigmetrics07.pdf&quot;&gt;An
64 analysis of latent sector errors in disk drives&lt;/a&gt; by
65 L. N. Bairavasundaram, G. R. Goodson, S. Pasupathy, and J. Schindler&lt;/li&gt;
66
67 &lt;/ul&gt;
68
69 &lt;p&gt;Several of these research papers are based on data collected from
70 hundred thousands or millions of disk, and their findings are eye
71 opening. The short story is simply do not implicitly trust RAID or
72 redundant storage systems. Details matter. And unfortunately there
73 are few options on Linux addressing all the identified issues. Both
74 ZFS and Btrfs are doing a fairly good job, but have legal and
75 practical issues on their own. I wonder how cluster file systems like
76 Ceph do in this regard. After all, there is an old saying, you know
77 you have a distributed system when the crash of a computer you have
78 never heard of stops you from getting any work done. The same holds
79 true if fault tolerance do not work.&lt;/p&gt;
80
81 &lt;p&gt;Just remember, in the end, it do not matter how redundant, or how
82 fault tolerant your storage is, if you do not continuously monitor its
83 status to detect and replace failed disks.&lt;/p&gt;
84 </description>
85 </item>
86
87 <item>
88 <title>Web services for writing academic LaTeX papers as a team</title>
89 <link>http://people.skolelinux.org/pere/blog/Web_services_for_writing_academic_LaTeX_papers_as_a_team.html</link>
90 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Web_services_for_writing_academic_LaTeX_papers_as_a_team.html</guid>
91 <pubDate>Tue, 31 Oct 2017 21:00:00 +0100</pubDate>
92 <description>&lt;p&gt;I was surprised today to learn that a friend in academia did not
93 know there are easily available web services available for writing
94 LaTeX documents as a team. I thought it was common knowledge, but to
95 make sure at least my readers are aware of it, I would like to mention
96 these useful services for writing LaTeX documents. Some of them even
97 provide a WYSIWYG editor to ease writing even further.&lt;/p&gt;
98
99 &lt;p&gt;There are two commercial services available,
100 &lt;a href=&quot;https://sharelatex.com&quot;&gt;ShareLaTeX&lt;/a&gt; and
101 &lt;a href=&quot;https://overleaf.com&quot;&gt;Overleaf&lt;/a&gt;. They are very easy to
102 use. Just start a new document, select which publisher to write for
103 (ie which LaTeX style to use), and start writing. Note, these two
104 have announced their intention to join forces, so soon it will only be
105 one joint service. I&#39;ve used both for different documents, and they
106 work just fine. While
107 &lt;a href=&quot;https://github.com/sharelatex/sharelatex&quot;&gt;ShareLaTeX is free
108 software&lt;/a&gt;, while the latter is not. According to &lt;a
109 href=&quot;https://www.overleaf.com/help/17-is-overleaf-open-source&quot;&gt;a
110 announcement from Overleaf&lt;/a&gt;, they plan to keep the ShareLaTeX code
111 base maintained as free software.&lt;/p&gt;
112
113 But these two are not the only alternatives.
114 &lt;a href=&quot;https://app.fiduswriter.org/&quot;&gt;Fidus Writer&lt;/a&gt; is another free
115 software solution with &lt;a href=&quot;https://github.com/fiduswriter&quot;&gt;the
116 source available on github&lt;/a&gt;. I have not used it myself. Several
117 others can be found on the nice
118 &lt;a href=&quot;https://alternativeto.net/software/sharelatex/&quot;&gt;alterntiveTo
119 web service&lt;/a&gt;.
120
121 &lt;p&gt;If you like Google Docs or Etherpad, but would like to write
122 documents in LaTeX, you should check out these services. You can even
123 host your own, if you want to. :)&lt;/p&gt;
124
125 </description>
126 </item>
127
128 <item>
129 <title>Locating IMDB IDs of movies in the Internet Archive using Wikidata</title>
130 <link>http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html</link>
131 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html</guid>
132 <pubDate>Wed, 25 Oct 2017 12:20:00 +0200</pubDate>
133 <description>&lt;p&gt;Recently, I needed to automatically check the copyright status of a
134 set of &lt;a href=&quot;http://www.imdb.com/&quot;&gt;The Internet Movie database
135 (IMDB)&lt;/a&gt; entries, to figure out which one of the movies they refer
136 to can be freely distributed on the Internet. This proved to be
137 harder than it sounds. IMDB for sure list movies without any
138 copyright protection, where the copyright protection has expired or
139 where the movie is lisenced using a permissive license like one from
140 Creative Commons. These are mixed with copyright protected movies,
141 and there seem to be no way to separate these classes of movies using
142 the information in IMDB.&lt;/p&gt;
143
144 &lt;p&gt;First I tried to look up entries manually in IMDB,
145 &lt;a href=&quot;https://www.wikipedia.org/&quot;&gt;Wikipedia&lt;/a&gt; and
146 &lt;a href=&quot;https://www.archive.org/&quot;&gt;The Internet Archive&lt;/a&gt;, to get a
147 feel how to do this. It is hard to know for sure using these sources,
148 but it should be possible to be reasonable confident a movie is &quot;out
149 of copyright&quot; with a few hours work per movie. As I needed to check
150 almost 20,000 entries, this approach was not sustainable. I simply
151 can not work around the clock for about 6 years to check this data
152 set.&lt;/p&gt;
153
154 &lt;p&gt;I asked the people behind The Internet Archive if they could
155 introduce a new metadata field in their metadata XML for IMDB ID, but
156 was told that they leave it completely to the uploaders to update the
157 metadata. Some of the metadata entries had IMDB links in the
158 description, but I found no way to download all metadata files in bulk
159 to locate those ones and put that approach aside.&lt;/p&gt;
160
161 &lt;p&gt;In the process I noticed several Wikipedia articles about movies
162 had links to both IMDB and The Internet Archive, and it occured to me
163 that I could use the Wikipedia RDF data set to locate entries with
164 both, to at least get a lower bound on the number of movies on The
165 Internet Archive with a IMDB ID. This is useful based on the
166 assumption that movies distributed by The Internet Archive can be
167 legally distributed on the Internet. With some help from the RDF
168 community (thank you DanC), I was able to come up with this query to
169 pass to &lt;a href=&quot;https://query.wikidata.org/&quot;&gt;the SPARQL interface on
170 Wikidata&lt;/a&gt;:
171
172 &lt;p&gt;&lt;pre&gt;
173 SELECT ?work ?imdb ?ia ?when ?label
174 WHERE
175 {
176 ?work wdt:P31/wdt:P279* wd:Q11424.
177 ?work wdt:P345 ?imdb.
178 ?work wdt:P724 ?ia.
179 OPTIONAL {
180 ?work wdt:P577 ?when.
181 ?work rdfs:label ?label.
182 FILTER(LANG(?label) = &quot;en&quot;).
183 }
184 }
185 &lt;/pre&gt;&lt;/p&gt;
186
187 &lt;p&gt;If I understand the query right, for every film entry anywhere in
188 Wikpedia, it will return the IMDB ID and The Internet Archive ID, and
189 when the movie was released and its English title, if either or both
190 of the latter two are available. At the moment the result set contain
191 2338 entries. Of course, it depend on volunteers including both
192 correct IMDB and The Internet Archive IDs in the wikipedia articles
193 for the movie. It should be noted that the result will include
194 duplicates if the movie have entries in several languages. There are
195 some bogus entries, either because The Internet Archive ID contain a
196 typo or because the movie is not available from The Internet Archive.
197 I did not verify the IMDB IDs, as I am unsure how to do that
198 automatically.&lt;/p&gt;
199
200 &lt;p&gt;I wrote a small python script to extract the data set from Wikidata
201 and check if the XML metadata for the movie is available from The
202 Internet Archive, and after around 1.5 hour it produced a list of 2097
203 free movies and their IMDB ID. In total, 171 entries in Wikidata lack
204 the refered Internet Archive entry. I assume the 70 &quot;disappearing&quot;
205 entries (ie 2338-2097-171) are duplicate entries.&lt;/p&gt;
206
207 &lt;p&gt;This is not too bad, given that The Internet Archive report to
208 contain &lt;a href=&quot;https://archive.org/details/feature_films&quot;&gt;5331
209 feature films&lt;/a&gt; at the moment, but it also mean more than 3000
210 movies are missing on Wikipedia or are missing the pair of references
211 on Wikipedia.&lt;/p&gt;
212
213 &lt;p&gt;I was curious about the distribution by release year, and made a
214 little graph to show how the amount of free movies is spread over the
215 years:&lt;p&gt;
216
217 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2017-10-25-verk-i-det-fri-filmer.png&quot;&gt;&lt;/p&gt;
218
219 &lt;p&gt;I expect the relative distribution of the remaining 3000 movies to
220 be similar.&lt;/p&gt;
221
222 &lt;p&gt;If you want to help, and want to ensure Wikipedia can be used to
223 cross reference The Internet Archive and The Internet Movie Database,
224 please make sure entries like this are listed under the &quot;External
225 links&quot; heading on the Wikipedia article for the movie:&lt;/p&gt;
226
227 &lt;p&gt;&lt;pre&gt;
228 * {{Internet Archive film|id=FightingLady}}
229 * {{IMDb title|id=0036823|title=The Fighting Lady}}
230 &lt;/pre&gt;&lt;/p&gt;
231
232 &lt;p&gt;Please verify the links on the final page, to make sure you did not
233 introduce a typo.&lt;/p&gt;
234
235 &lt;p&gt;Here is the complete list, if you want to correct the 171
236 identified Wikipedia entries with broken links to The Internet
237 Archive: &lt;a href=&quot;http://www.wikidata.org/entity/Q1140317&quot;&gt;Q1140317&lt;/a&gt;,
238 &lt;a href=&quot;http://www.wikidata.org/entity/Q458656&quot;&gt;Q458656&lt;/a&gt;,
239 &lt;a href=&quot;http://www.wikidata.org/entity/Q458656&quot;&gt;Q458656&lt;/a&gt;,
240 &lt;a href=&quot;http://www.wikidata.org/entity/Q470560&quot;&gt;Q470560&lt;/a&gt;,
241 &lt;a href=&quot;http://www.wikidata.org/entity/Q743340&quot;&gt;Q743340&lt;/a&gt;,
242 &lt;a href=&quot;http://www.wikidata.org/entity/Q822580&quot;&gt;Q822580&lt;/a&gt;,
243 &lt;a href=&quot;http://www.wikidata.org/entity/Q480696&quot;&gt;Q480696&lt;/a&gt;,
244 &lt;a href=&quot;http://www.wikidata.org/entity/Q128761&quot;&gt;Q128761&lt;/a&gt;,
245 &lt;a href=&quot;http://www.wikidata.org/entity/Q1307059&quot;&gt;Q1307059&lt;/a&gt;,
246 &lt;a href=&quot;http://www.wikidata.org/entity/Q1335091&quot;&gt;Q1335091&lt;/a&gt;,
247 &lt;a href=&quot;http://www.wikidata.org/entity/Q1537166&quot;&gt;Q1537166&lt;/a&gt;,
248 &lt;a href=&quot;http://www.wikidata.org/entity/Q1438334&quot;&gt;Q1438334&lt;/a&gt;,
249 &lt;a href=&quot;http://www.wikidata.org/entity/Q1479751&quot;&gt;Q1479751&lt;/a&gt;,
250 &lt;a href=&quot;http://www.wikidata.org/entity/Q1497200&quot;&gt;Q1497200&lt;/a&gt;,
251 &lt;a href=&quot;http://www.wikidata.org/entity/Q1498122&quot;&gt;Q1498122&lt;/a&gt;,
252 &lt;a href=&quot;http://www.wikidata.org/entity/Q865973&quot;&gt;Q865973&lt;/a&gt;,
253 &lt;a href=&quot;http://www.wikidata.org/entity/Q834269&quot;&gt;Q834269&lt;/a&gt;,
254 &lt;a href=&quot;http://www.wikidata.org/entity/Q841781&quot;&gt;Q841781&lt;/a&gt;,
255 &lt;a href=&quot;http://www.wikidata.org/entity/Q841781&quot;&gt;Q841781&lt;/a&gt;,
256 &lt;a href=&quot;http://www.wikidata.org/entity/Q1548193&quot;&gt;Q1548193&lt;/a&gt;,
257 &lt;a href=&quot;http://www.wikidata.org/entity/Q499031&quot;&gt;Q499031&lt;/a&gt;,
258 &lt;a href=&quot;http://www.wikidata.org/entity/Q1564769&quot;&gt;Q1564769&lt;/a&gt;,
259 &lt;a href=&quot;http://www.wikidata.org/entity/Q1585239&quot;&gt;Q1585239&lt;/a&gt;,
260 &lt;a href=&quot;http://www.wikidata.org/entity/Q1585569&quot;&gt;Q1585569&lt;/a&gt;,
261 &lt;a href=&quot;http://www.wikidata.org/entity/Q1624236&quot;&gt;Q1624236&lt;/a&gt;,
262 &lt;a href=&quot;http://www.wikidata.org/entity/Q4796595&quot;&gt;Q4796595&lt;/a&gt;,
263 &lt;a href=&quot;http://www.wikidata.org/entity/Q4853469&quot;&gt;Q4853469&lt;/a&gt;,
264 &lt;a href=&quot;http://www.wikidata.org/entity/Q4873046&quot;&gt;Q4873046&lt;/a&gt;,
265 &lt;a href=&quot;http://www.wikidata.org/entity/Q915016&quot;&gt;Q915016&lt;/a&gt;,
266 &lt;a href=&quot;http://www.wikidata.org/entity/Q4660396&quot;&gt;Q4660396&lt;/a&gt;,
267 &lt;a href=&quot;http://www.wikidata.org/entity/Q4677708&quot;&gt;Q4677708&lt;/a&gt;,
268 &lt;a href=&quot;http://www.wikidata.org/entity/Q4738449&quot;&gt;Q4738449&lt;/a&gt;,
269 &lt;a href=&quot;http://www.wikidata.org/entity/Q4756096&quot;&gt;Q4756096&lt;/a&gt;,
270 &lt;a href=&quot;http://www.wikidata.org/entity/Q4766785&quot;&gt;Q4766785&lt;/a&gt;,
271 &lt;a href=&quot;http://www.wikidata.org/entity/Q880357&quot;&gt;Q880357&lt;/a&gt;,
272 &lt;a href=&quot;http://www.wikidata.org/entity/Q882066&quot;&gt;Q882066&lt;/a&gt;,
273 &lt;a href=&quot;http://www.wikidata.org/entity/Q882066&quot;&gt;Q882066&lt;/a&gt;,
274 &lt;a href=&quot;http://www.wikidata.org/entity/Q204191&quot;&gt;Q204191&lt;/a&gt;,
275 &lt;a href=&quot;http://www.wikidata.org/entity/Q204191&quot;&gt;Q204191&lt;/a&gt;,
276 &lt;a href=&quot;http://www.wikidata.org/entity/Q1194170&quot;&gt;Q1194170&lt;/a&gt;,
277 &lt;a href=&quot;http://www.wikidata.org/entity/Q940014&quot;&gt;Q940014&lt;/a&gt;,
278 &lt;a href=&quot;http://www.wikidata.org/entity/Q946863&quot;&gt;Q946863&lt;/a&gt;,
279 &lt;a href=&quot;http://www.wikidata.org/entity/Q172837&quot;&gt;Q172837&lt;/a&gt;,
280 &lt;a href=&quot;http://www.wikidata.org/entity/Q573077&quot;&gt;Q573077&lt;/a&gt;,
281 &lt;a href=&quot;http://www.wikidata.org/entity/Q1219005&quot;&gt;Q1219005&lt;/a&gt;,
282 &lt;a href=&quot;http://www.wikidata.org/entity/Q1219599&quot;&gt;Q1219599&lt;/a&gt;,
283 &lt;a href=&quot;http://www.wikidata.org/entity/Q1643798&quot;&gt;Q1643798&lt;/a&gt;,
284 &lt;a href=&quot;http://www.wikidata.org/entity/Q1656352&quot;&gt;Q1656352&lt;/a&gt;,
285 &lt;a href=&quot;http://www.wikidata.org/entity/Q1659549&quot;&gt;Q1659549&lt;/a&gt;,
286 &lt;a href=&quot;http://www.wikidata.org/entity/Q1660007&quot;&gt;Q1660007&lt;/a&gt;,
287 &lt;a href=&quot;http://www.wikidata.org/entity/Q1698154&quot;&gt;Q1698154&lt;/a&gt;,
288 &lt;a href=&quot;http://www.wikidata.org/entity/Q1737980&quot;&gt;Q1737980&lt;/a&gt;,
289 &lt;a href=&quot;http://www.wikidata.org/entity/Q1877284&quot;&gt;Q1877284&lt;/a&gt;,
290 &lt;a href=&quot;http://www.wikidata.org/entity/Q1199354&quot;&gt;Q1199354&lt;/a&gt;,
291 &lt;a href=&quot;http://www.wikidata.org/entity/Q1199354&quot;&gt;Q1199354&lt;/a&gt;,
292 &lt;a href=&quot;http://www.wikidata.org/entity/Q1199451&quot;&gt;Q1199451&lt;/a&gt;,
293 &lt;a href=&quot;http://www.wikidata.org/entity/Q1211871&quot;&gt;Q1211871&lt;/a&gt;,
294 &lt;a href=&quot;http://www.wikidata.org/entity/Q1212179&quot;&gt;Q1212179&lt;/a&gt;,
295 &lt;a href=&quot;http://www.wikidata.org/entity/Q1238382&quot;&gt;Q1238382&lt;/a&gt;,
296 &lt;a href=&quot;http://www.wikidata.org/entity/Q4906454&quot;&gt;Q4906454&lt;/a&gt;,
297 &lt;a href=&quot;http://www.wikidata.org/entity/Q320219&quot;&gt;Q320219&lt;/a&gt;,
298 &lt;a href=&quot;http://www.wikidata.org/entity/Q1148649&quot;&gt;Q1148649&lt;/a&gt;,
299 &lt;a href=&quot;http://www.wikidata.org/entity/Q645094&quot;&gt;Q645094&lt;/a&gt;,
300 &lt;a href=&quot;http://www.wikidata.org/entity/Q5050350&quot;&gt;Q5050350&lt;/a&gt;,
301 &lt;a href=&quot;http://www.wikidata.org/entity/Q5166548&quot;&gt;Q5166548&lt;/a&gt;,
302 &lt;a href=&quot;http://www.wikidata.org/entity/Q2677926&quot;&gt;Q2677926&lt;/a&gt;,
303 &lt;a href=&quot;http://www.wikidata.org/entity/Q2698139&quot;&gt;Q2698139&lt;/a&gt;,
304 &lt;a href=&quot;http://www.wikidata.org/entity/Q2707305&quot;&gt;Q2707305&lt;/a&gt;,
305 &lt;a href=&quot;http://www.wikidata.org/entity/Q2740725&quot;&gt;Q2740725&lt;/a&gt;,
306 &lt;a href=&quot;http://www.wikidata.org/entity/Q2024780&quot;&gt;Q2024780&lt;/a&gt;,
307 &lt;a href=&quot;http://www.wikidata.org/entity/Q2117418&quot;&gt;Q2117418&lt;/a&gt;,
308 &lt;a href=&quot;http://www.wikidata.org/entity/Q2138984&quot;&gt;Q2138984&lt;/a&gt;,
309 &lt;a href=&quot;http://www.wikidata.org/entity/Q1127992&quot;&gt;Q1127992&lt;/a&gt;,
310 &lt;a href=&quot;http://www.wikidata.org/entity/Q1058087&quot;&gt;Q1058087&lt;/a&gt;,
311 &lt;a href=&quot;http://www.wikidata.org/entity/Q1070484&quot;&gt;Q1070484&lt;/a&gt;,
312 &lt;a href=&quot;http://www.wikidata.org/entity/Q1080080&quot;&gt;Q1080080&lt;/a&gt;,
313 &lt;a href=&quot;http://www.wikidata.org/entity/Q1090813&quot;&gt;Q1090813&lt;/a&gt;,
314 &lt;a href=&quot;http://www.wikidata.org/entity/Q1251918&quot;&gt;Q1251918&lt;/a&gt;,
315 &lt;a href=&quot;http://www.wikidata.org/entity/Q1254110&quot;&gt;Q1254110&lt;/a&gt;,
316 &lt;a href=&quot;http://www.wikidata.org/entity/Q1257070&quot;&gt;Q1257070&lt;/a&gt;,
317 &lt;a href=&quot;http://www.wikidata.org/entity/Q1257079&quot;&gt;Q1257079&lt;/a&gt;,
318 &lt;a href=&quot;http://www.wikidata.org/entity/Q1197410&quot;&gt;Q1197410&lt;/a&gt;,
319 &lt;a href=&quot;http://www.wikidata.org/entity/Q1198423&quot;&gt;Q1198423&lt;/a&gt;,
320 &lt;a href=&quot;http://www.wikidata.org/entity/Q706951&quot;&gt;Q706951&lt;/a&gt;,
321 &lt;a href=&quot;http://www.wikidata.org/entity/Q723239&quot;&gt;Q723239&lt;/a&gt;,
322 &lt;a href=&quot;http://www.wikidata.org/entity/Q2079261&quot;&gt;Q2079261&lt;/a&gt;,
323 &lt;a href=&quot;http://www.wikidata.org/entity/Q1171364&quot;&gt;Q1171364&lt;/a&gt;,
324 &lt;a href=&quot;http://www.wikidata.org/entity/Q617858&quot;&gt;Q617858&lt;/a&gt;,
325 &lt;a href=&quot;http://www.wikidata.org/entity/Q5166611&quot;&gt;Q5166611&lt;/a&gt;,
326 &lt;a href=&quot;http://www.wikidata.org/entity/Q5166611&quot;&gt;Q5166611&lt;/a&gt;,
327 &lt;a href=&quot;http://www.wikidata.org/entity/Q324513&quot;&gt;Q324513&lt;/a&gt;,
328 &lt;a href=&quot;http://www.wikidata.org/entity/Q374172&quot;&gt;Q374172&lt;/a&gt;,
329 &lt;a href=&quot;http://www.wikidata.org/entity/Q7533269&quot;&gt;Q7533269&lt;/a&gt;,
330 &lt;a href=&quot;http://www.wikidata.org/entity/Q970386&quot;&gt;Q970386&lt;/a&gt;,
331 &lt;a href=&quot;http://www.wikidata.org/entity/Q976849&quot;&gt;Q976849&lt;/a&gt;,
332 &lt;a href=&quot;http://www.wikidata.org/entity/Q7458614&quot;&gt;Q7458614&lt;/a&gt;,
333 &lt;a href=&quot;http://www.wikidata.org/entity/Q5347416&quot;&gt;Q5347416&lt;/a&gt;,
334 &lt;a href=&quot;http://www.wikidata.org/entity/Q5460005&quot;&gt;Q5460005&lt;/a&gt;,
335 &lt;a href=&quot;http://www.wikidata.org/entity/Q5463392&quot;&gt;Q5463392&lt;/a&gt;,
336 &lt;a href=&quot;http://www.wikidata.org/entity/Q3038555&quot;&gt;Q3038555&lt;/a&gt;,
337 &lt;a href=&quot;http://www.wikidata.org/entity/Q5288458&quot;&gt;Q5288458&lt;/a&gt;,
338 &lt;a href=&quot;http://www.wikidata.org/entity/Q2346516&quot;&gt;Q2346516&lt;/a&gt;,
339 &lt;a href=&quot;http://www.wikidata.org/entity/Q5183645&quot;&gt;Q5183645&lt;/a&gt;,
340 &lt;a href=&quot;http://www.wikidata.org/entity/Q5185497&quot;&gt;Q5185497&lt;/a&gt;,
341 &lt;a href=&quot;http://www.wikidata.org/entity/Q5216127&quot;&gt;Q5216127&lt;/a&gt;,
342 &lt;a href=&quot;http://www.wikidata.org/entity/Q5223127&quot;&gt;Q5223127&lt;/a&gt;,
343 &lt;a href=&quot;http://www.wikidata.org/entity/Q5261159&quot;&gt;Q5261159&lt;/a&gt;,
344 &lt;a href=&quot;http://www.wikidata.org/entity/Q1300759&quot;&gt;Q1300759&lt;/a&gt;,
345 &lt;a href=&quot;http://www.wikidata.org/entity/Q5521241&quot;&gt;Q5521241&lt;/a&gt;,
346 &lt;a href=&quot;http://www.wikidata.org/entity/Q7733434&quot;&gt;Q7733434&lt;/a&gt;,
347 &lt;a href=&quot;http://www.wikidata.org/entity/Q7736264&quot;&gt;Q7736264&lt;/a&gt;,
348 &lt;a href=&quot;http://www.wikidata.org/entity/Q7737032&quot;&gt;Q7737032&lt;/a&gt;,
349 &lt;a href=&quot;http://www.wikidata.org/entity/Q7882671&quot;&gt;Q7882671&lt;/a&gt;,
350 &lt;a href=&quot;http://www.wikidata.org/entity/Q7719427&quot;&gt;Q7719427&lt;/a&gt;,
351 &lt;a href=&quot;http://www.wikidata.org/entity/Q7719444&quot;&gt;Q7719444&lt;/a&gt;,
352 &lt;a href=&quot;http://www.wikidata.org/entity/Q7722575&quot;&gt;Q7722575&lt;/a&gt;,
353 &lt;a href=&quot;http://www.wikidata.org/entity/Q2629763&quot;&gt;Q2629763&lt;/a&gt;,
354 &lt;a href=&quot;http://www.wikidata.org/entity/Q2640346&quot;&gt;Q2640346&lt;/a&gt;,
355 &lt;a href=&quot;http://www.wikidata.org/entity/Q2649671&quot;&gt;Q2649671&lt;/a&gt;,
356 &lt;a href=&quot;http://www.wikidata.org/entity/Q7703851&quot;&gt;Q7703851&lt;/a&gt;,
357 &lt;a href=&quot;http://www.wikidata.org/entity/Q7747041&quot;&gt;Q7747041&lt;/a&gt;,
358 &lt;a href=&quot;http://www.wikidata.org/entity/Q6544949&quot;&gt;Q6544949&lt;/a&gt;,
359 &lt;a href=&quot;http://www.wikidata.org/entity/Q6672759&quot;&gt;Q6672759&lt;/a&gt;,
360 &lt;a href=&quot;http://www.wikidata.org/entity/Q2445896&quot;&gt;Q2445896&lt;/a&gt;,
361 &lt;a href=&quot;http://www.wikidata.org/entity/Q12124891&quot;&gt;Q12124891&lt;/a&gt;,
362 &lt;a href=&quot;http://www.wikidata.org/entity/Q3127044&quot;&gt;Q3127044&lt;/a&gt;,
363 &lt;a href=&quot;http://www.wikidata.org/entity/Q2511262&quot;&gt;Q2511262&lt;/a&gt;,
364 &lt;a href=&quot;http://www.wikidata.org/entity/Q2517672&quot;&gt;Q2517672&lt;/a&gt;,
365 &lt;a href=&quot;http://www.wikidata.org/entity/Q2543165&quot;&gt;Q2543165&lt;/a&gt;,
366 &lt;a href=&quot;http://www.wikidata.org/entity/Q426628&quot;&gt;Q426628&lt;/a&gt;,
367 &lt;a href=&quot;http://www.wikidata.org/entity/Q426628&quot;&gt;Q426628&lt;/a&gt;,
368 &lt;a href=&quot;http://www.wikidata.org/entity/Q12126890&quot;&gt;Q12126890&lt;/a&gt;,
369 &lt;a href=&quot;http://www.wikidata.org/entity/Q13359969&quot;&gt;Q13359969&lt;/a&gt;,
370 &lt;a href=&quot;http://www.wikidata.org/entity/Q13359969&quot;&gt;Q13359969&lt;/a&gt;,
371 &lt;a href=&quot;http://www.wikidata.org/entity/Q2294295&quot;&gt;Q2294295&lt;/a&gt;,
372 &lt;a href=&quot;http://www.wikidata.org/entity/Q2294295&quot;&gt;Q2294295&lt;/a&gt;,
373 &lt;a href=&quot;http://www.wikidata.org/entity/Q2559509&quot;&gt;Q2559509&lt;/a&gt;,
374 &lt;a href=&quot;http://www.wikidata.org/entity/Q2559912&quot;&gt;Q2559912&lt;/a&gt;,
375 &lt;a href=&quot;http://www.wikidata.org/entity/Q7760469&quot;&gt;Q7760469&lt;/a&gt;,
376 &lt;a href=&quot;http://www.wikidata.org/entity/Q6703974&quot;&gt;Q6703974&lt;/a&gt;,
377 &lt;a href=&quot;http://www.wikidata.org/entity/Q4744&quot;&gt;Q4744&lt;/a&gt;,
378 &lt;a href=&quot;http://www.wikidata.org/entity/Q7766962&quot;&gt;Q7766962&lt;/a&gt;,
379 &lt;a href=&quot;http://www.wikidata.org/entity/Q7768516&quot;&gt;Q7768516&lt;/a&gt;,
380 &lt;a href=&quot;http://www.wikidata.org/entity/Q7769205&quot;&gt;Q7769205&lt;/a&gt;,
381 &lt;a href=&quot;http://www.wikidata.org/entity/Q7769988&quot;&gt;Q7769988&lt;/a&gt;,
382 &lt;a href=&quot;http://www.wikidata.org/entity/Q2946945&quot;&gt;Q2946945&lt;/a&gt;,
383 &lt;a href=&quot;http://www.wikidata.org/entity/Q3212086&quot;&gt;Q3212086&lt;/a&gt;,
384 &lt;a href=&quot;http://www.wikidata.org/entity/Q3212086&quot;&gt;Q3212086&lt;/a&gt;,
385 &lt;a href=&quot;http://www.wikidata.org/entity/Q18218448&quot;&gt;Q18218448&lt;/a&gt;,
386 &lt;a href=&quot;http://www.wikidata.org/entity/Q18218448&quot;&gt;Q18218448&lt;/a&gt;,
387 &lt;a href=&quot;http://www.wikidata.org/entity/Q18218448&quot;&gt;Q18218448&lt;/a&gt;,
388 &lt;a href=&quot;http://www.wikidata.org/entity/Q6909175&quot;&gt;Q6909175&lt;/a&gt;,
389 &lt;a href=&quot;http://www.wikidata.org/entity/Q7405709&quot;&gt;Q7405709&lt;/a&gt;,
390 &lt;a href=&quot;http://www.wikidata.org/entity/Q7416149&quot;&gt;Q7416149&lt;/a&gt;,
391 &lt;a href=&quot;http://www.wikidata.org/entity/Q7239952&quot;&gt;Q7239952&lt;/a&gt;,
392 &lt;a href=&quot;http://www.wikidata.org/entity/Q7317332&quot;&gt;Q7317332&lt;/a&gt;,
393 &lt;a href=&quot;http://www.wikidata.org/entity/Q7783674&quot;&gt;Q7783674&lt;/a&gt;,
394 &lt;a href=&quot;http://www.wikidata.org/entity/Q7783704&quot;&gt;Q7783704&lt;/a&gt;,
395 &lt;a href=&quot;http://www.wikidata.org/entity/Q7857590&quot;&gt;Q7857590&lt;/a&gt;,
396 &lt;a href=&quot;http://www.wikidata.org/entity/Q3372526&quot;&gt;Q3372526&lt;/a&gt;,
397 &lt;a href=&quot;http://www.wikidata.org/entity/Q3372642&quot;&gt;Q3372642&lt;/a&gt;,
398 &lt;a href=&quot;http://www.wikidata.org/entity/Q3372816&quot;&gt;Q3372816&lt;/a&gt;,
399 &lt;a href=&quot;http://www.wikidata.org/entity/Q3372909&quot;&gt;Q3372909&lt;/a&gt;,
400 &lt;a href=&quot;http://www.wikidata.org/entity/Q7959649&quot;&gt;Q7959649&lt;/a&gt;,
401 &lt;a href=&quot;http://www.wikidata.org/entity/Q7977485&quot;&gt;Q7977485&lt;/a&gt;,
402 &lt;a href=&quot;http://www.wikidata.org/entity/Q7992684&quot;&gt;Q7992684&lt;/a&gt;,
403 &lt;a href=&quot;http://www.wikidata.org/entity/Q3817966&quot;&gt;Q3817966&lt;/a&gt;,
404 &lt;a href=&quot;http://www.wikidata.org/entity/Q3821852&quot;&gt;Q3821852&lt;/a&gt;,
405 &lt;a href=&quot;http://www.wikidata.org/entity/Q3420907&quot;&gt;Q3420907&lt;/a&gt;,
406 &lt;a href=&quot;http://www.wikidata.org/entity/Q3429733&quot;&gt;Q3429733&lt;/a&gt;,
407 &lt;a href=&quot;http://www.wikidata.org/entity/Q774474&quot;&gt;Q774474&lt;/a&gt;&lt;/p&gt;
408 </description>
409 </item>
410
411 <item>
412 <title>A one-way wall on the border?</title>
413 <link>http://people.skolelinux.org/pere/blog/A_one_way_wall_on_the_border_.html</link>
414 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_one_way_wall_on_the_border_.html</guid>
415 <pubDate>Sat, 14 Oct 2017 22:10:00 +0200</pubDate>
416 <description>&lt;p&gt;I find it fascinating how many of the people being locked inside
417 the proposed border wall between USA and Mexico support the idea. The
418 proposal to keep Mexicans out reminds me of
419 &lt;a href=&quot;http://www.history.com/news/10-things-you-may-not-know-about-the-berlin-wall&quot;&gt;the
420 propaganda twist from the East Germany government&lt;/a&gt; calling the wall
421 the “Antifascist Bulwark” after erecting the Berlin Wall, claiming
422 that the wall was erected to keep enemies from creeping into East
423 Germany, while it was obvious to the people locked inside it that it
424 was erected to keep the people from escaping.&lt;/p&gt;
425
426 &lt;p&gt;Do the people in USA supporting this wall really believe it is a
427 one way wall, only keeping people on the outside from getting in,
428 while not keeping people in the inside from getting out?&lt;/p&gt;
429 </description>
430 </item>
431
432 <item>
433 <title>Generating 3D prints in Debian using Cura and Slic3r(-prusa)</title>
434 <link>http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</link>
435 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</guid>
436 <pubDate>Mon, 9 Oct 2017 10:50:00 +0200</pubDate>
437 <description>&lt;p&gt;At my nearby maker space,
438 &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Sonen&lt;/a&gt;, I heard the story that it
439 was easier to generate gcode files for theyr 3D printers (Ultimake 2+)
440 on Windows and MacOS X than Linux, because the software involved had
441 to be manually compiled and set up on Linux while premade packages
442 worked out of the box on Windows and MacOS X. I found this annoying,
443 as the software involved,
444 &lt;a href=&quot;https://github.com/Ultimaker/Cura&quot;&gt;Cura&lt;/a&gt;, is free software
445 and should be trivial to get up and running on Linux if someone took
446 the time to package it for the relevant distributions. I even found
447 &lt;a href=&quot;https://bugs.debian.org/706656&quot;&gt;a request for adding into
448 Debian&lt;/a&gt; from 2013, which had seem some activity over the years but
449 never resulted in the software showing up in Debian. So a few days
450 ago I offered my help to try to improve the situation.&lt;/p&gt;
451
452 &lt;p&gt;Now I am very happy to see that all the packages required by a
453 working Cura in Debian are uploaded into Debian and waiting in the NEW
454 queue for the ftpmasters to have a look. You can track the progress
455 on
456 &lt;a href=&quot;https://qa.debian.org/developer.php?email=3dprinter-general%40lists.alioth.debian.org&quot;&gt;the
457 status page for the 3D printer team&lt;/a&gt;.&lt;/p&gt;
458
459 &lt;p&gt;The uploaded packages are a bit behind upstream, and was uploaded
460 now to get slots in &lt;a href=&quot;https://ftp-master.debian.org/new.html&quot;&gt;the NEW
461 queue&lt;/a&gt; while we work up updating the packages to the latest
462 upstream version.&lt;/p&gt;
463
464 &lt;p&gt;On a related note, two competitors for Cura, which I found harder
465 to use and was unable to configure correctly for Ultimaker 2+ in the
466 short time I spent on it, are already in Debian. If you are looking
467 for 3D printer &quot;slicers&quot; and want something already available in
468 Debian, check out
469 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r&quot;&gt;slic3r&lt;/a&gt; and
470 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r-prusa&quot;&gt;slic3r-prusa&lt;/a&gt;.
471 The latter is a fork of the former.&lt;/p&gt;
472 </description>
473 </item>
474
475 <item>
476 <title>Mangler du en skrue, eller har du en skrue løs?</title>
477 <link>http://people.skolelinux.org/pere/blog/Mangler_du_en_skrue__eller_har_du_en_skrue_l_s_.html</link>
478 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Mangler_du_en_skrue__eller_har_du_en_skrue_l_s_.html</guid>
479 <pubDate>Wed, 4 Oct 2017 09:40:00 +0200</pubDate>
480 <description>Når jeg holder på med ulike prosjekter, så trenger jeg stadig ulike
481 skruer. Det siste prosjektet jeg holder på med er å lage
482 &lt;a href=&quot;https://www.thingiverse.com/thing:676916&quot;&gt;en boks til en
483 HDMI-touch-skjerm&lt;/a&gt; som skal brukes med Raspberry Pi. Boksen settes
484 sammen med skruer og bolter, og jeg har vært i tvil om hvor jeg kan
485 få tak i de riktige skruene. Clas Ohlson og Jernia i nærheten har
486 sjelden hatt det jeg trenger. Men her om dagen fikk jeg et fantastisk
487 tips for oss som bor i Oslo.
488 &lt;a href=&quot;http://www.zachskruer.no/&quot;&gt;Zachariassen Jernvare AS&lt;/a&gt; i
489 &lt;a href=&quot;http://www.openstreetmap.org/?mlat=59.93421&amp;mlon=10.76795#map=19/59.93421/10.76795&quot;&gt;Hegermannsgate
490 23A på Torshov&lt;/a&gt; har et fantastisk utvalg, og åpent mellom 09:00 og
491 17:00. De selger skruer, muttere, bolter, skiver etc i løs vekt, og
492 så langt har jeg fått alt jeg har lett etter. De har i tillegg det
493 meste av annen jernvare, som verktøy, lamper, ledninger, etc. Jeg
494 håper de har nok kunder til å holde det gående lenge, da dette er en
495 butikk jeg kommer til å besøke ofte. Butikken er et funn å ha i
496 nabolaget for oss som liker å bygge litt selv. :)&lt;/p&gt;
497 </description>
498 </item>
499
500 <item>
501 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass</title>
502 <link>http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</link>
503 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</guid>
504 <pubDate>Fri, 29 Sep 2017 10:30:00 +0200</pubDate>
505 <description>&lt;p&gt;Every mobile phone announce its existence over radio to the nearby
506 mobile cell towers. And this radio chatter is available for anyone
507 with a radio receiver capable of receiving them. Details about the
508 mobile phones with very good accuracy is of course collected by the
509 phone companies, but this is not the topic of this blog post. The
510 mobile phone radio chatter make it possible to figure out when a cell
511 phone is nearby, as it include the SIM card ID (IMSI). By paying
512 attention over time, one can see when a phone arrive and when it leave
513 an area. I believe it would be nice to make this information more
514 available to the general public, to make more people aware of how
515 their phones are announcing their whereabouts to anyone that care to
516 listen.&lt;/p&gt;
517
518 &lt;p&gt;I am very happy to report that we managed to get something
519 visualizing this information up and running for
520 &lt;a href=&quot;http://norwaymakers.org/osf17&quot;&gt;Oslo Skaperfestival 2017&lt;/a&gt;
521 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
522 library. The solution is based on the
523 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html&quot;&gt;simple
524 recipe for listening to GSM chatter&lt;/a&gt; I posted a few days ago, and
525 will show up at the stand of &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Åpen
526 Sone from the Computer Science department of the University of
527 Oslo&lt;/a&gt;. The presentation will show the nearby mobile phones (aka
528 IMSIs) as dots in a web browser graph, with lines to the dot
529 representing mobile base station it is talking to. It was working in
530 the lab yesterday, and was moved into place this morning.&lt;/p&gt;
531
532 &lt;p&gt;We set up a fairly powerful desktop machine using Debian
533 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
534 connected and visualize the visible cell phone towers using an
535 &lt;a href=&quot;https://github.com/marlow925/hopglass&quot;&gt;English version of
536 Hopglass&lt;/a&gt;. A fairly powerfull machine is needed as the
537 grgsm_livemon_headless processes from
538 &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt; converting
539 the radio signal to data packages is quite CPU intensive.&lt;/p&gt;
540
541 &lt;p&gt;The frequencies to listen to, are identified using a slightly
542 patched scan-and-livemon (to set the --args values for each receiver),
543 and the Hopglass data is generated using the
544 &lt;a href=&quot;https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output&quot;&gt;patches
545 in my meshviewer-output branch&lt;/a&gt;. For some reason we could not get
546 more than four SDRs working. There is also a geographical map trying
547 to show the location of the base stations, but I believe their
548 coordinates are hardcoded to some random location in Germany, I
549 believe. The code should be replaced with code to look up location in
550 a text file, a sqlite database or one of the online databases
551 mentioned in
552 &lt;a href=&quot;https://github.com/Oros42/IMSI-catcher/issues/14&quot;&gt;the github
553 issue for the topic&lt;/a&gt;.
554
555 &lt;p&gt;If this sound interesting, visit the stand at the festival!&lt;/p&gt;
556 </description>
557 </item>
558
559 <item>
560 <title>Easier recipe to observe the cell phones around you</title>
561 <link>http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</link>
562 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</guid>
563 <pubDate>Sun, 24 Sep 2017 08:30:00 +0200</pubDate>
564 <description>&lt;p&gt;A little more than a month ago I wrote
565 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html&quot;&gt;how
566 to observe the SIM card ID (aka IMSI number) of mobile phones talking
567 to nearby mobile phone base stations using Debian GNU/Linux and a
568 cheap USB software defined radio&lt;/a&gt;, and thus being able to pinpoint
569 the location of people and equipment (like cars and trains) with an
570 accuracy of a few kilometer. Since then we have worked to make the
571 procedure even simpler, and it is now possible to do this without any
572 manual frequency tuning and without building your own packages.&lt;/p&gt;
573
574 &lt;p&gt;The &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt;
575 package is now included in Debian testing and unstable, and the
576 IMSI-catcher code no longer require root access to fetch and decode
577 the GSM data collected using gr-gsm.&lt;/p&gt;
578
579 &lt;p&gt;Here is an updated recipe, using packages built by Debian and a git
580 clone of two python scripts:&lt;/p&gt;
581
582 &lt;ol&gt;
583
584 &lt;li&gt;Start with a Debian machine running the Buster version (aka
585 testing).&lt;/li&gt;
586
587 &lt;li&gt;Run &#39;&lt;tt&gt;apt install gr-gsm python-numpy python-scipy
588 python-scapy&lt;/tt&gt;&#39; as root to install required packages.&lt;/li&gt;
589
590 &lt;li&gt;Fetch the code decoding GSM packages using &#39;&lt;tt&gt;git clone
591 github.com/Oros42/IMSI-catcher.git&lt;/tt&gt;&#39;.&lt;/li&gt;
592
593 &lt;li&gt;Insert USB software defined radio supported by GNU Radio.&lt;/li&gt;
594
595 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
596 scan-and-livemon&lt;/tt&gt;&#39; to locate the frequency of nearby base
597 stations and start listening for GSM packages on one of them.&lt;/li&gt;
598
599 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
600 simple_IMSI-catcher.py&lt;/tt&gt;&#39; to display the collected information.&lt;/li&gt;
601
602 &lt;/ol&gt;
603
604 &lt;p&gt;Note, due to a bug somewhere the scan-and-livemon program (actually
605 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/issues/336&quot;&gt;its underlying
606 program grgsm_scanner&lt;/a&gt;) do not work with the HackRF radio. It does
607 work with RTL 8232 and other similar USB radio receivers you can get
608 very cheaply
609 (&lt;a href=&quot;https://www.ebay.com/sch/items/?_nkw=rtl+2832&quot;&gt;for example
610 from ebay&lt;/a&gt;), so for now the solution is to scan using the RTL radio
611 and only use HackRF for fetching GSM data.&lt;/p&gt;
612
613 &lt;p&gt;As far as I can tell, a cell phone only show up on one of the
614 frequencies at the time, so if you are going to track and count every
615 cell phone around you, you need to listen to all the frequencies used.
616 To listen to several frequencies, use the --numrecv argument to
617 scan-and-livemon to use several receivers. Further, I am not sure if
618 phones using 3G or 4G will show as talking GSM to base stations, so
619 this approach might not see all phones around you. I typically see
620 0-400 IMSI numbers an hour when looking around where I live.&lt;/p&gt;
621
622 &lt;p&gt;I&#39;ve tried to run the scanner on a
623 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi 2 and 3
624 running Debian Buster&lt;/a&gt;, but the grgsm_livemon_headless process seem
625 to be too CPU intensive to keep up. When GNU Radio print &#39;O&#39; to
626 stdout, I am told there it is caused by a buffer overflow between the
627 radio and GNU Radio, caused by the program being unable to read the
628 GSM data fast enough. If you see a stream of &#39;O&#39;s from the terminal
629 where you started scan-and-livemon, you need a give the process more
630 CPU power. Perhaps someone are able to optimize the code to a point
631 where it become possible to set up RPi3 based GSM sniffers? I tried
632 using Raspbian instead of Debian, but there seem to be something wrong
633 with GNU Radio on raspbian, causing glibc to abort().&lt;/p&gt;
634 </description>
635 </item>
636
637 <item>
638 <title>Datalagringsdirektivet kaster skygger over Høyre og Arbeiderpartiet</title>
639 <link>http://people.skolelinux.org/pere/blog/Datalagringsdirektivet_kaster_skygger_over_H_yre_og_Arbeiderpartiet.html</link>
640 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Datalagringsdirektivet_kaster_skygger_over_H_yre_og_Arbeiderpartiet.html</guid>
641 <pubDate>Thu, 7 Sep 2017 21:35:00 +0200</pubDate>
642 <description>&lt;p&gt;For noen dager siden publiserte Jon Wessel-Aas en bloggpost om
643 «&lt;a href=&quot;http://www.uhuru.biz/?p=1821&quot;&gt;Konklusjonen om datalagring som
644 EU-kommisjonen ikke ville at vi skulle få se&lt;/a&gt;». Det er en
645 interessant gjennomgang av EU-domstolens syn på snurpenotovervåkning
646 av befolkningen, som er klar på at det er i strid med
647 EU-lovgivingen.&lt;/p&gt;
648
649 &lt;p&gt;Valgkampen går for fullt i Norge, og om noen få dager er siste
650 frist for å avgi stemme. En ting er sikkert, Høyre og Arbeiderpartiet
651 får ikke min stemme
652 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Datalagringsdirektivet_gj_r_at_Oslo_H_yre_og_Arbeiderparti_ikke_f_r_min_stemme_i__r.html&quot;&gt;denne
653 gangen heller&lt;/a&gt;. Jeg har ikke glemt at de tvang igjennom loven som
654 skulle pålegge alle data- og teletjenesteleverandører å overvåke alle
655 sine kunder. En lov som er vedtatt, og aldri opphevet igjen.&lt;/p&gt;
656
657 &lt;p&gt;Det er tydelig fra diskusjonen rundt grenseløs digital overvåkning
658 (eller &quot;Digital Grenseforsvar&quot; som det kalles i Orvellisk nytale) at
659 hverken Høyre og Arbeiderpartiet har noen prinsipielle sperrer mot å
660 overvåke hele befolkningen, og diskusjonen så langt tyder på at flere
661 av de andre partiene heller ikke har det. Mange av
662 &lt;a href=&quot;https://data.holderdeord.no/votes/1301946411e&quot;&gt;de som stemte
663 for Datalagringsdirektivet i Stortinget&lt;/a&gt; (64 fra Arbeiderpartiet,
664 25 fra Høyre) er fortsatt aktive og argumenterer fortsatt for å radere
665 vekk mer av innbyggernes privatsfære.&lt;/p&gt;
666
667 &lt;p&gt;Når myndighetene demonstrerer sin mistillit til folket, tror jeg
668 folket selv bør legge litt innsats i å verne sitt privatliv, ved å ta
669 i bruk ende-til-ende-kryptert kommunikasjon med sine kjente og kjære,
670 og begrense hvor mye privat informasjon som deles med uvedkommende.
671 Det er jo ingenting som tyder på at myndighetene kommer til å være vår
672 privatsfære.
673 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/How_to_talk_with_your_loved_ones_in_private.html&quot;&gt;Det
674 er mange muligheter&lt;/a&gt;. Selv har jeg litt sans for
675 &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;, som er basert på p2p-teknologi
676 uten sentral kontroll, er fri programvare, og støtter meldinger, tale
677 og video. Systemet er tilgjengelig ut av boksen fra
678 &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; og
679 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, og det
680 finnes pakker for Android, MacOSX og Windows. Foreløpig er det få
681 brukere med Ring, slik at jeg også bruker
682 &lt;a href=&quot;https://signal.org/&quot;&gt;Signal&lt;/a&gt; som nettleserutvidelse.&lt;/p&gt;
683 </description>
684 </item>
685
686 <item>
687 <title>Simpler recipe on how to make a simple $7 IMSI Catcher using Debian</title>
688 <link>http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</link>
689 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</guid>
690 <pubDate>Wed, 9 Aug 2017 23:59:00 +0200</pubDate>
691 <description>&lt;p&gt;On friday, I came across an interesting article in the Norwegian
692 web based ICT news magazine digi.no on
693 &lt;a href=&quot;https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-60-kroner-na-kan-mobiler-kartlegges-av-alle/398588&quot;&gt;how
694 to collect the IMSI numbers of nearby cell phones&lt;/a&gt; using the cheap
695 DVB-T software defined radios. The article refered to instructions
696 and &lt;a href=&quot;https://www.youtube.com/watch?v=UjwgNd_as30&quot;&gt;a recipe by
697 Keld Norman on Youtube on how to make a simple $7 IMSI Catcher&lt;/a&gt;, and I decided to test them out.&lt;/p&gt;
698
699 &lt;p&gt;The instructions said to use Ubuntu, install pip using apt (to
700 bypass apt), use pip to install pybombs (to bypass both apt and pip),
701 and the ask pybombs to fetch and build everything you need from
702 scratch. I wanted to see if I could do the same on the most recent
703 Debian packages, but this did not work because pybombs tried to build
704 stuff that no longer build with the most recent openssl library or
705 some other version skew problem. While trying to get this recipe
706 working, I learned that the apt-&gt;pip-&gt;pybombs route was a long detour,
707 and the only piece of software dependency missing in Debian was the
708 gr-gsm package. I also found out that the lead upstream developer of
709 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
710 Debian packages provided in an Ubuntu PPA repository. All I needed to
711 do was to dget the Debian source package and built it.&lt;/p&gt;
712
713 &lt;p&gt;The IMSI collector is a python script listening for packages on the
714 loopback network device and printing to the terminal some specific GSM
715 packages with IMSI numbers in them. The code is fairly short and easy
716 to understand. The reason this work is because gr-gsm include a tool
717 to read GSM data from a software defined radio like a DVB-T USB stick
718 and other software defined radios, decode them and inject them into a
719 network device on your Linux machine (using the loopback device by
720 default). This proved to work just fine, and I&#39;ve been testing the
721 collector for a few days now.&lt;/p&gt;
722
723 &lt;p&gt;The updated and simpler recipe is thus to&lt;/p&gt;
724
725 &lt;ol&gt;
726
727 &lt;li&gt;start with a Debian machine running Stretch or newer,&lt;/li&gt;
728
729 &lt;li&gt;build and install the gr-gsm package available from
730 &lt;a href=&quot;http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/&quot;&gt;http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/&lt;/a&gt;,&lt;/li&gt;
731
732 &lt;li&gt;clone the git repostory from &lt;a href=&quot;https://github.com/Oros42/IMSI-catcher&quot;&gt;https://github.com/Oros42/IMSI-catcher&lt;/a&gt;,&lt;/li&gt;
733
734 &lt;li&gt;run grgsm_livemon and adjust the frequency until the terminal
735 where it was started is filled with a stream of text (meaning you
736 found a GSM station).&lt;/li&gt;
737
738 &lt;li&gt;go into the IMSI-catcher directory and run &#39;sudo python simple_IMSI-catcher.py&#39; to extract the IMSI numbers.&lt;/li&gt;
739
740 &lt;/ol&gt;
741
742 &lt;p&gt;To make it even easier in the future to get this sniffer up and
743 running, I decided to package
744 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/&quot;&gt;the gr-gsm project&lt;/a&gt;
745 for Debian (&lt;a href=&quot;https://bugs.debian.org/871055&quot;&gt;WNPP
746 #871055&lt;/a&gt;), and the package was uploaded into the NEW queue today.
747 Luckily the gnuradio maintainer has promised to help me, as I do not
748 know much about gnuradio stuff yet.&lt;/p&gt;
749
750 &lt;p&gt;I doubt this &quot;IMSI cacher&quot; is anywhere near as powerfull as
751 commercial tools like
752 &lt;a href=&quot;https://www.thespyphone.com/portable-imsi-imei-catcher/&quot;&gt;The
753 Spy Phone Portable IMSI / IMEI Catcher&lt;/a&gt; or the
754 &lt;a href=&quot;https://en.wikipedia.org/wiki/Stingray_phone_tracker&quot;&gt;Harris
755 Stingray&lt;/a&gt;, but I hope the existance of cheap alternatives can make
756 more people realise how their whereabouts when carrying a cell phone
757 is easily tracked. Seeing the data flow on the screen, realizing that
758 I live close to a police station and knowing that the police is also
759 wearing cell phones, I wonder how hard it would be for criminals to
760 track the position of the police officers to discover when there are
761 police near by, or for foreign military forces to track the location
762 of the Norwegian military forces, or for anyone to track the location
763 of government officials...&lt;/p&gt;
764
765 &lt;p&gt;It is worth noting that the data reported by the IMSI-catcher
766 script mentioned above is only a fraction of the data broadcasted on
767 the GSM network. It will only collect one frequency at the time,
768 while a typical phone will be using several frequencies, and not all
769 phones will be using the frequencies tracked by the grgsm_livemod
770 program. Also, there is a lot of radio chatter being ignored by the
771 simple_IMSI-catcher script, which would be collected by extending the
772 parser code. I wonder if gr-gsm can be set up to listen to more than
773 one frequency?&lt;/p&gt;
774 </description>
775 </item>
776
777 </channel>
778 </rss>