X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/6b0c1fa519b278178825b3b550343129140b2ca7..ed339a38453ed95dfb25e4ade1b05e3d3772a102:/blog/index.rss diff --git a/blog/index.rss b/blog/index.rss index d2a8c98f0b..c85c7f822a 100644 --- a/blog/index.rss +++ b/blog/index.rss @@ -7,767 +7,538 @@ - Some notes on fault tolerant storage systems - http://people.skolelinux.org/pere/blog/Some_notes_on_fault_tolerant_storage_systems.html - http://people.skolelinux.org/pere/blog/Some_notes_on_fault_tolerant_storage_systems.html - Wed, 1 Nov 2017 15:35:00 +0100 - <p>If you care about how fault tolerant your storage is, you might -find these articles and papers interesting. They have formed how I -think of when designing a storage system.</p> - -<ul> - -<li>USENIX :login; <a -href="https://www.usenix.org/publications/login/summer2017/ganesan">Redundancy -Does Not Imply Fault Tolerance. Analysis of Distributed Storage -Reactions to Single Errors and Corruptions</a> by Aishwarya Ganesan, -Ramnatthan Alagappan, Andrea C. Arpaci-Dusseau, and Remzi -H. Arpaci-Dusseau</li> - -<li>ZDNet -<a href="http://www.zdnet.com/article/why-raid-5-stops-working-in-2009/">Why -RAID 5 stops working in 2009</a> by Robin Harris</li> - -<li>ZDNet -<a href="http://www.zdnet.com/article/why-raid-6-stops-working-in-2019/">Why -RAID 6 stops working in 2019</a> by Robin Harris</li> - -<li>USENIX FAST'07 -<a href="http://research.google.com/archive/disk_failures.pdf">Failure -Trends in a Large Disk Drive Population</a> by Eduardo Pinheiro, -Wolf-Dietrich Weber and Luiz André Barroso</li> - -<li>USENIX ;login: <a -href="https://www.usenix.org/system/files/login/articles/hughes12-04.pdf">Data -Integrity. Finding Truth in a World of Guesses and Lies</a> by Doug -Hughes</li> - -<li>USENIX FAST'08 -<a href="https://www.usenix.org/events/fast08/tech/full_papers/bairavasundaram/bairavasundaram_html/">An -cAnalysis of Data Corruption in the Storage Stack</a> - -L. N. Bairavasundaram, G. R. Goodson, B. Schroeder, A. C. -Arpaci-Dusseau, and R. H. Arpaci-Dusseau</li> - -<li>USENIX FAST'07 <a -href="https://www.usenix.org/legacy/events/fast07/tech/schroeder/schroeder_html/">Disk -failures in the real world: what does an MTTF of 1,000,000 hours mean -to you?</a> by B. Schroeder and G. A. Gibson.</li> - -<li>USENIX ;login: <a -href="https://www.usenix.org/events/fast08/tech/full_papers/jiang/jiang_html/">Are -Disks the Dominant Contributor for Storage Failures? A Comprehensive -Study of Storage Subsystem Failure Characteristics</a> by Weihang -Jiang, Chongfeng Hu, Yuanyuan Zhou, and Arkady Kanevsky</li> - -<li>SIGMETRICS 2007 -<a href="http://research.cs.wisc.edu/adsl/Publications/latent-sigmetrics07.pdf">An -analysis of latent sector errors in disk drives</a> - -L. N. Bairavasundaram, G. R. Goodson, S. Pasupathy, and J. Schindler</li> - -</ul> - -<p>Several of these research papers are based on data collected from -hundred thousands or millions of disk, and their findings are eye -opening. The short story is simply do not implicitly trust RAID or -redundant storage systems. Details matter. And unfortunately there -are few options on Linux addressing all the identified issues. Both -ZFS and Btrfs are doing a fairly good job, but have legal and -practical issues on their own. I wonder how cluster file systems like -Ceph do in this regard.</p> - -<p>Just remember, in the end, it do not matter how redundant, or how -fault tolerant your storage is, if you do not continuously monitor its -status to detect and replace failed disks.</p> + En grunn til å takke nei til usikker digital post + http://people.skolelinux.org/pere/blog/En_grunn_til___takke_nei_til_usikker_digital_post.html + http://people.skolelinux.org/pere/blog/En_grunn_til___takke_nei_til_usikker_digital_post.html + Mon, 2 Apr 2018 13:30:00 +0200 + <p>Brevpost er beskyttet av straffelovens bestemmelse som gjør det +kriminelt å åpne andres brev. Dette følger av (ny) straffelovs +<a href="https://lovdata.no/dokument/NL/lov/2005-05-20-28/§205">§ 205 +(Krenkelse av retten til privat kommunikasjon)</a>, som sier at «Med +bot eller fengsel inntil 2 år straffes den som uberettiget ... c) +åpner brev eller annen lukket skriftlig meddelelse som er adressert +til en annen, eller på annen måte skaffer seg uberettiget tilgang til +innholdet.» Dette gjelder såvel postbud som alle andre som har +befatning med brevet etter at avsender har befatning med et lukket +brev. Tilsvarende står også tidligere utgaver av den norske +straffeloven.</p> + +<p>Når en registrerer seg på usikre digitale postkasseløsningene, som +f.eks. Digipost og e-Boks, og slik tar disse i bruk, så gir en de som +står bak løsningene tillatelse til å åpne sine brev. Dette er +nødvendig for at innholdet i digital post skal kunne vises frem til +mottaker via tjenestens websider. Dermed gjelder ikke straffelovens +paragraf om forbud mot å åpne brev, da tilgangen ikke lenger er +uberetiget. En gir altså fremmede tilgang til å lese sin +korrespondanse. I tillegg vil bruk av slike usikre digitale +postbokser føre til at det blir registrert når du leser brevene, hvor +du befinner deg (vha. tilkoblingens IP-adresse), hvilket utstyr du +bruker og en rekke annen personlig informasjon som ikke er +tilgjengelig når papirpost brukes. Jeg foretrekker at det er +lovmessig beskyttelse av min korrespondanse, som jo inneholder privat +og personlig informasjon. Det bidrar til litt bedre vern av personlig +integritet i dagens norske samfunn.</p> - Web services for writing academic LaTeX papers as a team - http://people.skolelinux.org/pere/blog/Web_services_for_writing_academic_LaTeX_papers_as_a_team.html - http://people.skolelinux.org/pere/blog/Web_services_for_writing_academic_LaTeX_papers_as_a_team.html - Tue, 31 Oct 2017 21:00:00 +0100 - <p>I was surprised today to learn that a friend in academia did not -know there are easily available web services available for writing -LaTeX documents as a team. I thought it was common knowledge, but to -make sure at least my readers are aware of it, I would like to mention -these useful services for writing LaTeX documents. Some of them even -provide a WYSIWYG editor to ease writing even further.</p> - -<p>There are two commercial services available, -<a href="https://sharelatex.com">ShareLaTeX</a> and -<a href="https://overleaf.com">Overleaf</a>. They are very easy to -use. Just start a new document, select which publisher to write for -(ie which LaTeX style to use), and start writing. Note, these two -have announced their intention to join forces, so soon it will only be -one joint service. I've used both for different documents, and they -work just fine. While -<a href="https://github.com/sharelatex/sharelatex">ShareLaTeX is free -software</a>, while the latter is not. According to <a -href="https://www.overleaf.com/help/17-is-overleaf-open-source">a -announcement from Overleaf</a>, they plan to keep the ShareLaTeX code -base maintained as free software.</p> - -But these two are not the only alternatives. -<a href="https://app.fiduswriter.org/">Fidus Writer</a> is another free -software solution with <a href="https://github.com/fiduswriter">the -source available on github</a>. I have not used it myself. Several -others can be found on the nice -<a href="https://alternativeto.net/software/sharelatex/">alterntiveTo -web service</a>. - -<p>If you like Google Docs or Etherpad, but would like to write -documents in LaTeX, you should check out these services. You can even -host your own, if you want to. :)</p> - + Self-appointed leaders of the Free World + http://people.skolelinux.org/pere/blog/Self_appointed_leaders_of_the_Free_World.html + http://people.skolelinux.org/pere/blog/Self_appointed_leaders_of_the_Free_World.html + Thu, 22 Mar 2018 11:00:00 +0100 + <p>The leaders of the worlds have started to congratulate the +re-elected Russian head of state, and this causes some criticism. I +am though a little fascinated by a comment from USA senator John McCain, +<a href="http://thehill.com/homenews/senate/379339-mccain-rips-trumps-congratulatory-call-to-putin-as-insult-to-russian-people">sited +by The Hill and others</a>: + +<p><blockquote> +<p>"An American president does not lead the Free World by +congratulating dictators on winning sham elections."</p> +</blockquote></p> + +<p>While I totally agree with the senator here, the way the quote is +phrased make me suspect that he is unaware of the simple fact that USA +have not lead the Free World since at least before its government +<a href="https://en.wikipedia.org/wiki/Maher_Arar">kidnapped a +completely innocent Canadian citizen in transit on his way home to +Canada via John F. Kennedy International Airport in September 2002 and +sent him to be tortured in Syria for a year</a>.</p> + +<p>USA might be running ahead, but the path they are taking is not the +one taken by any Free World.</p> - Locating IMDB IDs of movies in the Internet Archive using Wikidata - http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html - http://people.skolelinux.org/pere/blog/Locating_IMDB_IDs_of_movies_in_the_Internet_Archive_using_Wikidata.html - Wed, 25 Oct 2017 12:20:00 +0200 - <p>Recently, I needed to automatically check the copyright status of a -set of <a href="http://www.imdb.com/">The Internet Movie database -(IMDB)</a> entries, to figure out which one of the movies they refer -to can be freely distributed on the Internet. This proved to be -harder than it sounds. IMDB for sure list movies without any -copyright protection, where the copyright protection has expired or -where the movie is lisenced using a permissive license like one from -Creative Commons. These are mixed with copyright protected movies, -and there seem to be no way to separate these classes of movies using -the information in IMDB.</p> - -<p>First I tried to look up entries manually in IMDB, -<a href="https://www.wikipedia.org/">Wikipedia</a> and -<a href="https://www.archive.org/">The Internet Archive</a>, to get a -feel how to do this. It is hard to know for sure using these sources, -but it should be possible to be reasonable confident a movie is "out -of copyright" with a few hours work per movie. As I needed to check -almost 20,000 entries, this approach was not sustainable. I simply -can not work around the clock for about 6 years to check this data -set.</p> - -<p>I asked the people behind The Internet Archive if they could -introduce a new metadata field in their metadata XML for IMDB ID, but -was told that they leave it completely to the uploaders to update the -metadata. Some of the metadata entries had IMDB links in the -description, but I found no way to download all metadata files in bulk -to locate those ones and put that approach aside.</p> - -<p>In the process I noticed several Wikipedia articles about movies -had links to both IMDB and The Internet Archive, and it occured to me -that I could use the Wikipedia RDF data set to locate entries with -both, to at least get a lower bound on the number of movies on The -Internet Archive with a IMDB ID. This is useful based on the -assumption that movies distributed by The Internet Archive can be -legally distributed on the Internet. With some help from the RDF -community (thank you DanC), I was able to come up with this query to -pass to <a href="https://query.wikidata.org/">the SPARQL interface on -Wikidata</a>: - -<p><pre> -SELECT ?work ?imdb ?ia ?when ?label -WHERE -{ - ?work wdt:P31/wdt:P279* wd:Q11424. - ?work wdt:P345 ?imdb. - ?work wdt:P724 ?ia. - OPTIONAL { - ?work wdt:P577 ?when. - ?work rdfs:label ?label. - FILTER(LANG(?label) = "en"). - } -} -</pre></p> - -<p>If I understand the query right, for every film entry anywhere in -Wikpedia, it will return the IMDB ID and The Internet Archive ID, and -when the movie was released and its English title, if either or both -of the latter two are available. At the moment the result set contain -2338 entries. Of course, it depend on volunteers including both -correct IMDB and The Internet Archive IDs in the wikipedia articles -for the movie. It should be noted that the result will include -duplicates if the movie have entries in several languages. There are -some bogus entries, either because The Internet Archive ID contain a -typo or because the movie is not available from The Internet Archive. -I did not verify the IMDB IDs, as I am unsure how to do that -automatically.</p> - -<p>I wrote a small python script to extract the data set from Wikidata -and check if the XML metadata for the movie is available from The -Internet Archive, and after around 1.5 hour it produced a list of 2097 -free movies and their IMDB ID. In total, 171 entries in Wikidata lack -the refered Internet Archive entry. I assume the 70 "disappearing" -entries (ie 2338-2097-171) are duplicate entries.</p> - -<p>This is not too bad, given that The Internet Archive report to -contain <a href="https://archive.org/details/feature_films">5331 -feature films</a> at the moment, but it also mean more than 3000 -movies are missing on Wikipedia or are missing the pair of references -on Wikipedia.</p> - -<p>I was curious about the distribution by release year, and made a -little graph to show how the amount of free movies is spread over the -years:<p> - -<p><img src="http://people.skolelinux.org/pere/blog/images/2017-10-25-verk-i-det-fri-filmer.png"></p> - -<p>I expect the relative distribution of the remaining 3000 movies to -be similar.</p> - -<p>If you want to help, and want to ensure Wikipedia can be used to -cross reference The Internet Archive and The Internet Movie Database, -please make sure entries like this are listed under the "External -links" heading on the Wikipedia article for the movie:</p> - -<p><pre> -* {{Internet Archive film|id=FightingLady}} -* {{IMDb title|id=0036823|title=The Fighting Lady}} -</pre></p> - -<p>Please verify the links on the final page, to make sure you did not -introduce a typo.</p> - -<p>Here is the complete list, if you want to correct the 171 -identified Wikipedia entries with broken links to The Internet -Archive: <a href="http://www.wikidata.org/entity/Q1140317">Q1140317</a>, -<a href="http://www.wikidata.org/entity/Q458656">Q458656</a>, -<a href="http://www.wikidata.org/entity/Q458656">Q458656</a>, -<a href="http://www.wikidata.org/entity/Q470560">Q470560</a>, -<a href="http://www.wikidata.org/entity/Q743340">Q743340</a>, -<a href="http://www.wikidata.org/entity/Q822580">Q822580</a>, -<a href="http://www.wikidata.org/entity/Q480696">Q480696</a>, -<a href="http://www.wikidata.org/entity/Q128761">Q128761</a>, -<a href="http://www.wikidata.org/entity/Q1307059">Q1307059</a>, -<a href="http://www.wikidata.org/entity/Q1335091">Q1335091</a>, -<a href="http://www.wikidata.org/entity/Q1537166">Q1537166</a>, -<a href="http://www.wikidata.org/entity/Q1438334">Q1438334</a>, -<a href="http://www.wikidata.org/entity/Q1479751">Q1479751</a>, -<a href="http://www.wikidata.org/entity/Q1497200">Q1497200</a>, -<a href="http://www.wikidata.org/entity/Q1498122">Q1498122</a>, -<a href="http://www.wikidata.org/entity/Q865973">Q865973</a>, -<a href="http://www.wikidata.org/entity/Q834269">Q834269</a>, -<a href="http://www.wikidata.org/entity/Q841781">Q841781</a>, -<a href="http://www.wikidata.org/entity/Q841781">Q841781</a>, -<a href="http://www.wikidata.org/entity/Q1548193">Q1548193</a>, -<a href="http://www.wikidata.org/entity/Q499031">Q499031</a>, -<a href="http://www.wikidata.org/entity/Q1564769">Q1564769</a>, -<a href="http://www.wikidata.org/entity/Q1585239">Q1585239</a>, -<a href="http://www.wikidata.org/entity/Q1585569">Q1585569</a>, -<a href="http://www.wikidata.org/entity/Q1624236">Q1624236</a>, -<a href="http://www.wikidata.org/entity/Q4796595">Q4796595</a>, -<a href="http://www.wikidata.org/entity/Q4853469">Q4853469</a>, -<a href="http://www.wikidata.org/entity/Q4873046">Q4873046</a>, -<a href="http://www.wikidata.org/entity/Q915016">Q915016</a>, -<a href="http://www.wikidata.org/entity/Q4660396">Q4660396</a>, -<a href="http://www.wikidata.org/entity/Q4677708">Q4677708</a>, -<a href="http://www.wikidata.org/entity/Q4738449">Q4738449</a>, -<a href="http://www.wikidata.org/entity/Q4756096">Q4756096</a>, -<a href="http://www.wikidata.org/entity/Q4766785">Q4766785</a>, -<a href="http://www.wikidata.org/entity/Q880357">Q880357</a>, -<a href="http://www.wikidata.org/entity/Q882066">Q882066</a>, -<a href="http://www.wikidata.org/entity/Q882066">Q882066</a>, -<a href="http://www.wikidata.org/entity/Q204191">Q204191</a>, -<a href="http://www.wikidata.org/entity/Q204191">Q204191</a>, -<a href="http://www.wikidata.org/entity/Q1194170">Q1194170</a>, -<a href="http://www.wikidata.org/entity/Q940014">Q940014</a>, -<a href="http://www.wikidata.org/entity/Q946863">Q946863</a>, -<a href="http://www.wikidata.org/entity/Q172837">Q172837</a>, -<a href="http://www.wikidata.org/entity/Q573077">Q573077</a>, -<a href="http://www.wikidata.org/entity/Q1219005">Q1219005</a>, -<a href="http://www.wikidata.org/entity/Q1219599">Q1219599</a>, -<a href="http://www.wikidata.org/entity/Q1643798">Q1643798</a>, -<a href="http://www.wikidata.org/entity/Q1656352">Q1656352</a>, -<a href="http://www.wikidata.org/entity/Q1659549">Q1659549</a>, -<a href="http://www.wikidata.org/entity/Q1660007">Q1660007</a>, -<a href="http://www.wikidata.org/entity/Q1698154">Q1698154</a>, -<a href="http://www.wikidata.org/entity/Q1737980">Q1737980</a>, -<a href="http://www.wikidata.org/entity/Q1877284">Q1877284</a>, -<a href="http://www.wikidata.org/entity/Q1199354">Q1199354</a>, -<a href="http://www.wikidata.org/entity/Q1199354">Q1199354</a>, -<a href="http://www.wikidata.org/entity/Q1199451">Q1199451</a>, -<a href="http://www.wikidata.org/entity/Q1211871">Q1211871</a>, -<a href="http://www.wikidata.org/entity/Q1212179">Q1212179</a>, -<a href="http://www.wikidata.org/entity/Q1238382">Q1238382</a>, -<a href="http://www.wikidata.org/entity/Q4906454">Q4906454</a>, -<a href="http://www.wikidata.org/entity/Q320219">Q320219</a>, -<a href="http://www.wikidata.org/entity/Q1148649">Q1148649</a>, -<a href="http://www.wikidata.org/entity/Q645094">Q645094</a>, -<a href="http://www.wikidata.org/entity/Q5050350">Q5050350</a>, -<a href="http://www.wikidata.org/entity/Q5166548">Q5166548</a>, -<a href="http://www.wikidata.org/entity/Q2677926">Q2677926</a>, -<a href="http://www.wikidata.org/entity/Q2698139">Q2698139</a>, -<a href="http://www.wikidata.org/entity/Q2707305">Q2707305</a>, -<a href="http://www.wikidata.org/entity/Q2740725">Q2740725</a>, -<a href="http://www.wikidata.org/entity/Q2024780">Q2024780</a>, -<a href="http://www.wikidata.org/entity/Q2117418">Q2117418</a>, -<a href="http://www.wikidata.org/entity/Q2138984">Q2138984</a>, -<a href="http://www.wikidata.org/entity/Q1127992">Q1127992</a>, -<a href="http://www.wikidata.org/entity/Q1058087">Q1058087</a>, -<a href="http://www.wikidata.org/entity/Q1070484">Q1070484</a>, -<a href="http://www.wikidata.org/entity/Q1080080">Q1080080</a>, -<a href="http://www.wikidata.org/entity/Q1090813">Q1090813</a>, -<a href="http://www.wikidata.org/entity/Q1251918">Q1251918</a>, -<a href="http://www.wikidata.org/entity/Q1254110">Q1254110</a>, -<a href="http://www.wikidata.org/entity/Q1257070">Q1257070</a>, -<a href="http://www.wikidata.org/entity/Q1257079">Q1257079</a>, -<a href="http://www.wikidata.org/entity/Q1197410">Q1197410</a>, -<a href="http://www.wikidata.org/entity/Q1198423">Q1198423</a>, -<a href="http://www.wikidata.org/entity/Q706951">Q706951</a>, -<a href="http://www.wikidata.org/entity/Q723239">Q723239</a>, -<a href="http://www.wikidata.org/entity/Q2079261">Q2079261</a>, -<a href="http://www.wikidata.org/entity/Q1171364">Q1171364</a>, -<a href="http://www.wikidata.org/entity/Q617858">Q617858</a>, -<a href="http://www.wikidata.org/entity/Q5166611">Q5166611</a>, -<a href="http://www.wikidata.org/entity/Q5166611">Q5166611</a>, -<a href="http://www.wikidata.org/entity/Q324513">Q324513</a>, -<a href="http://www.wikidata.org/entity/Q374172">Q374172</a>, -<a href="http://www.wikidata.org/entity/Q7533269">Q7533269</a>, -<a href="http://www.wikidata.org/entity/Q970386">Q970386</a>, -<a href="http://www.wikidata.org/entity/Q976849">Q976849</a>, -<a href="http://www.wikidata.org/entity/Q7458614">Q7458614</a>, -<a href="http://www.wikidata.org/entity/Q5347416">Q5347416</a>, -<a href="http://www.wikidata.org/entity/Q5460005">Q5460005</a>, -<a href="http://www.wikidata.org/entity/Q5463392">Q5463392</a>, -<a href="http://www.wikidata.org/entity/Q3038555">Q3038555</a>, -<a href="http://www.wikidata.org/entity/Q5288458">Q5288458</a>, -<a href="http://www.wikidata.org/entity/Q2346516">Q2346516</a>, -<a href="http://www.wikidata.org/entity/Q5183645">Q5183645</a>, -<a href="http://www.wikidata.org/entity/Q5185497">Q5185497</a>, -<a href="http://www.wikidata.org/entity/Q5216127">Q5216127</a>, -<a href="http://www.wikidata.org/entity/Q5223127">Q5223127</a>, -<a href="http://www.wikidata.org/entity/Q5261159">Q5261159</a>, -<a href="http://www.wikidata.org/entity/Q1300759">Q1300759</a>, -<a href="http://www.wikidata.org/entity/Q5521241">Q5521241</a>, -<a href="http://www.wikidata.org/entity/Q7733434">Q7733434</a>, -<a href="http://www.wikidata.org/entity/Q7736264">Q7736264</a>, -<a href="http://www.wikidata.org/entity/Q7737032">Q7737032</a>, -<a href="http://www.wikidata.org/entity/Q7882671">Q7882671</a>, -<a href="http://www.wikidata.org/entity/Q7719427">Q7719427</a>, -<a href="http://www.wikidata.org/entity/Q7719444">Q7719444</a>, -<a href="http://www.wikidata.org/entity/Q7722575">Q7722575</a>, -<a href="http://www.wikidata.org/entity/Q2629763">Q2629763</a>, -<a href="http://www.wikidata.org/entity/Q2640346">Q2640346</a>, -<a href="http://www.wikidata.org/entity/Q2649671">Q2649671</a>, -<a href="http://www.wikidata.org/entity/Q7703851">Q7703851</a>, -<a href="http://www.wikidata.org/entity/Q7747041">Q7747041</a>, -<a href="http://www.wikidata.org/entity/Q6544949">Q6544949</a>, -<a href="http://www.wikidata.org/entity/Q6672759">Q6672759</a>, -<a href="http://www.wikidata.org/entity/Q2445896">Q2445896</a>, -<a href="http://www.wikidata.org/entity/Q12124891">Q12124891</a>, -<a href="http://www.wikidata.org/entity/Q3127044">Q3127044</a>, -<a href="http://www.wikidata.org/entity/Q2511262">Q2511262</a>, -<a href="http://www.wikidata.org/entity/Q2517672">Q2517672</a>, -<a href="http://www.wikidata.org/entity/Q2543165">Q2543165</a>, -<a href="http://www.wikidata.org/entity/Q426628">Q426628</a>, -<a href="http://www.wikidata.org/entity/Q426628">Q426628</a>, -<a href="http://www.wikidata.org/entity/Q12126890">Q12126890</a>, -<a href="http://www.wikidata.org/entity/Q13359969">Q13359969</a>, -<a href="http://www.wikidata.org/entity/Q13359969">Q13359969</a>, -<a href="http://www.wikidata.org/entity/Q2294295">Q2294295</a>, -<a href="http://www.wikidata.org/entity/Q2294295">Q2294295</a>, -<a href="http://www.wikidata.org/entity/Q2559509">Q2559509</a>, -<a href="http://www.wikidata.org/entity/Q2559912">Q2559912</a>, -<a href="http://www.wikidata.org/entity/Q7760469">Q7760469</a>, -<a href="http://www.wikidata.org/entity/Q6703974">Q6703974</a>, -<a href="http://www.wikidata.org/entity/Q4744">Q4744</a>, -<a href="http://www.wikidata.org/entity/Q7766962">Q7766962</a>, -<a href="http://www.wikidata.org/entity/Q7768516">Q7768516</a>, -<a href="http://www.wikidata.org/entity/Q7769205">Q7769205</a>, -<a href="http://www.wikidata.org/entity/Q7769988">Q7769988</a>, -<a href="http://www.wikidata.org/entity/Q2946945">Q2946945</a>, -<a href="http://www.wikidata.org/entity/Q3212086">Q3212086</a>, -<a href="http://www.wikidata.org/entity/Q3212086">Q3212086</a>, -<a href="http://www.wikidata.org/entity/Q18218448">Q18218448</a>, -<a href="http://www.wikidata.org/entity/Q18218448">Q18218448</a>, -<a href="http://www.wikidata.org/entity/Q18218448">Q18218448</a>, -<a href="http://www.wikidata.org/entity/Q6909175">Q6909175</a>, -<a href="http://www.wikidata.org/entity/Q7405709">Q7405709</a>, -<a href="http://www.wikidata.org/entity/Q7416149">Q7416149</a>, -<a href="http://www.wikidata.org/entity/Q7239952">Q7239952</a>, -<a href="http://www.wikidata.org/entity/Q7317332">Q7317332</a>, -<a href="http://www.wikidata.org/entity/Q7783674">Q7783674</a>, -<a href="http://www.wikidata.org/entity/Q7783704">Q7783704</a>, -<a href="http://www.wikidata.org/entity/Q7857590">Q7857590</a>, -<a href="http://www.wikidata.org/entity/Q3372526">Q3372526</a>, -<a href="http://www.wikidata.org/entity/Q3372642">Q3372642</a>, -<a href="http://www.wikidata.org/entity/Q3372816">Q3372816</a>, -<a href="http://www.wikidata.org/entity/Q3372909">Q3372909</a>, -<a href="http://www.wikidata.org/entity/Q7959649">Q7959649</a>, -<a href="http://www.wikidata.org/entity/Q7977485">Q7977485</a>, -<a href="http://www.wikidata.org/entity/Q7992684">Q7992684</a>, -<a href="http://www.wikidata.org/entity/Q3817966">Q3817966</a>, -<a href="http://www.wikidata.org/entity/Q3821852">Q3821852</a>, -<a href="http://www.wikidata.org/entity/Q3420907">Q3420907</a>, -<a href="http://www.wikidata.org/entity/Q3429733">Q3429733</a>, -<a href="http://www.wikidata.org/entity/Q774474">Q774474</a></p> + Facebooks ability to sell your personal information is the real Cambridge Analytica scandal + http://people.skolelinux.org/pere/blog/Facebooks_ability_to_sell_your_personal_information_is_the_real_Cambridge_Analytica_scandal.html + http://people.skolelinux.org/pere/blog/Facebooks_ability_to_sell_your_personal_information_is_the_real_Cambridge_Analytica_scandal.html + Wed, 21 Mar 2018 16:30:00 +0100 + <p>So, Cambridge Analytica is getting some well deserved criticism for +(mis)using information it got from Facebook about 50 million people, +mostly in the USA. What I find a bit surprising, is how little +criticism Facebook is getting for handing the information over to +Cambridge Analytica and others in the first place. And what about the +people handing their private and personal information to Facebook? +And last, but not least, what about the government offices who are +handing information about the visitors of their web pages to Facebook? +No-one who looked at the terms of use of Facebook should be surprised +that information about peoples interests, political views, personal +lifes and whereabouts would be sold by Facebook.</p> + +<p>What I find to be the real scandal is the fact that Facebook is +selling your personal information, not that one of the buyers used it +in a way Facebook did not approve when exposed. It is well known that +Facebook is selling out their users privacy, but a scandal +nevertheless. Of course the information provided to them by Facebook +would be misused by one of the parties given access to personal +information about the millions of Facebook users. Collected +information will be misused sooner or later. The only way to avoid +such misuse, is to not collect the information in the first place. If +you do not want Facebook to hand out information about yourself for +the use and misuse of its customers, do not give Facebook the +information.</p> + +<p>Personally, I would recommend to completely remove your Facebook +account, and take back some control of your personal information. +<a href="https://www.theguardian.com/technology/2018/mar/19/how-to-protect-your-facebook-privacy-or-delete-yourself-completely">According +to The Guardian</a>, it is a bit hard to find out how to request +account removal (and not just 'disabling'). You need to +<a href="https://www.facebook.com/help/224562897555674?helpref=faq_content">visit +a specific Facebook page</a> and click on 'let us know' on that page +to get to <a href="https://www.facebook.com/help/delete_account">the +real account deletion screen</a>. Perhaps something to consider? I +would not trust the information to really be deleted (who knows, +perhaps NSA, GCHQ and FRA already got a copy), but it might reduce the +exposure a bit.</p> + +<p>If you want to learn more about the capabilities of Cambridge +Analytica, I recommend to see the video recording of the one hour talk +Paul-Olivier Dehaye gave to <a href="">NUUG</a> last april about +<a href="https://www.nuug.no/aktiviteter/20170404-big-data-psychometric/"> +Data collection, psychometric profiling and their impact on +politics</a>.</p> + +<p>And if you want to communicate with your friends and loved ones, +use some end-to-end encrypted method like +<a href="https://www.signal.org/">Signal</a> or +<a href="https://ring.cx/">Ring</a>, and stop sharing your private +messages with strangers like Facebook and Google.</p> - A one-way wall on the border? - http://people.skolelinux.org/pere/blog/A_one_way_wall_on_the_border_.html - http://people.skolelinux.org/pere/blog/A_one_way_wall_on_the_border_.html - Sat, 14 Oct 2017 22:10:00 +0200 - <p>I find it fascinating how many of the people being locked inside -the proposed border wall between USA and Mexico support the idea. The -proposal to keep Mexicans out reminds me of -<a href="http://www.history.com/news/10-things-you-may-not-know-about-the-berlin-wall">the -propaganda twist from the East Germany government</a> calling the wall -the “Antifascist Bulwark” after erecting the Berlin Wall, claiming -that the wall was erected to keep enemies from creeping into East -Germany, while it was obvious to the people locked inside it that it -was erected to keep the people from escaping.</p> - -<p>Do the people in USA supporting this wall really believe it is a -one way wall, only keeping people on the outside from getting in, -while not keeping people in the inside from getting out?</p> + H, Ap, Frp og Venstre går for DNA-innsamling av hele befolkningen + http://people.skolelinux.org/pere/blog/H__Ap__Frp_og_Venstre_g_r_for_DNA_innsamling_av_hele_befolkningen.html + http://people.skolelinux.org/pere/blog/H__Ap__Frp_og_Venstre_g_r_for_DNA_innsamling_av_hele_befolkningen.html + Wed, 14 Mar 2018 14:15:00 +0100 + <p>I går kom det nok et argument for å holde seg unna det norske +helsevesenet. Da annonserte et stortingsflertall, bestående av Høyre, +Arbeiderpartiet, Fremskrittspartiet og Venstre, at de går inn for å +samle inn og lagre DNA-prøver fra hele befolkningen i Norge til evig +tid. Endringen gjelder innsamlede blodprøver fra nyfødte i Norge. +Det vil dermed ta litt tid før en har hele befolkningen, men det er +dit vi havner gitt nok tid. I dag er det nesten hundre prosent +oppslutning om undersøkelsen som gjøres like etter fødselen, på +bakgrunn av blodprøven det er snakk om å lagre, for å oppdage endel +medfødte sykdommer. Blodprøven lagres i dag i inntil seks år. +<a href="https://www.stortinget.no/no/Saker-og-publikasjoner/Publikasjoner/Innstillinger/Stortinget/2017-2018/inns-201718-182l/?all=true">Stortingets +flertallsinnstilling</a> er at tidsbegrensingen skal fjernes, og mener +at tidsubegrenset lagring ikke vil påvirke oppslutningen om +undersøkelsen.</p> + +<p>Datatilsynet har ikke akkurat applaudert forslaget:</p> + +<p><blockquote> + + <p>«Datatilsynet mener forslaget ikke i tilstrekkelig grad + synliggjør hvilke etiske og personvernmessige utfordringer som må + diskuteres før en etablerer en nasjonal biobank med blodprøver fra + hele befolkningen.»</p> + +</blockquote></p> + +<p>Det er flere historier om hvordan innsamlet biologisk materiale har +blitt brukt til andre formål enn de ble innsamlet til, og historien om +<a href="https://www.aftenposten.no/norge/i/Ql0WR/Na-ma-Folkehelsa-slette-uskyldiges-DNA-info">folkehelseinstituttets +lagring på vegne av politiet (Kripos) av innsamlet biologisk materiale +og DNA-informasjon i strid med loven</a> viser at en ikke kan være +trygg på at lover og intensjoner beskytter de som blir berørt mot +misbruk av slik privat og personlig informasjon.</p> + +<p>Det er verdt å merke seg at det kan forskes på de innsamlede +blodprøvene uten samtykke fra den det gjelder (eller foreldre når det +gjelder barn), etter en lovendring for en stund tilbake, med mindre +det er sendt inn skjema der en reserverer seg mot forskning uten +samtykke. Skjemaet er tilgjengelig fra +<a href="https://www.fhi.no/arkiv/publikasjoner/for-pasienter-skjema-for-reservasjo/">folkehelseinstituttets +websider</a>, og jeg anbefaler, uavhengig av denne saken, varmt alle å +sende inn skjemaet for å dokumentere hvor mange som ikke synes det er +greit å fjerne krav om samtykke.</p> + +<p>I tillegg bør en kreve destruering av alt biologisk materiale som +er samlet inn om en selv, for å redusere eventuelle negative +konsekvenser i fremtiden når materialet kommer på avveie eller blir +brukt uten samtykke, men det er så vidt jeg vet ikke noe system for +dette i dag.</p> + +<p>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til +det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner +til min adresse +<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p> - Generating 3D prints in Debian using Cura and Slic3r(-prusa) - http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html - http://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html - Mon, 9 Oct 2017 10:50:00 +0200 - <p>At my nearby maker space, -<a href="http://sonen.ifi.uio.no/">Sonen</a>, I heard the story that it -was easier to generate gcode files for theyr 3D printers (Ultimake 2+) -on Windows and MacOS X than Linux, because the software involved had -to be manually compiled and set up on Linux while premade packages -worked out of the box on Windows and MacOS X. I found this annoying, -as the software involved, -<a href="https://github.com/Ultimaker/Cura">Cura</a>, is free software -and should be trivial to get up and running on Linux if someone took -the time to package it for the relevant distributions. I even found -<a href="https://bugs.debian.org/706656">a request for adding into -Debian</a> from 2013, which had seem some activity over the years but -never resulted in the software showing up in Debian. So a few days -ago I offered my help to try to improve the situation.</p> - -<p>Now I am very happy to see that all the packages required by a -working Cura in Debian are uploaded into Debian and waiting in the NEW -queue for the ftpmasters to have a look. You can track the progress -on -<a href="https://qa.debian.org/developer.php?email=3dprinter-general%40lists.alioth.debian.org">the -status page for the 3D printer team</a>.</p> - -<p>The uploaded packages are a bit behind upstream, and was uploaded -now to get slots in <a href="https://ftp-master.debian.org/new.html">the NEW -queue</a> while we work up updating the packages to the latest -upstream version.</p> - -<p>On a related note, two competitors for Cura, which I found harder -to use and was unable to configure correctly for Ultimaker 2+ in the -short time I spent on it, are already in Debian. If you are looking -for 3D printer "slicers" and want something already available in -Debian, check out -<a href="https://tracker.debian.org/pkg/slic3r">slic3r</a> and -<a href="https://tracker.debian.org/pkg/slic3r-prusa">slic3r-prusa</a>. -The latter is a fork of the former.</p> + First rough draft Norwegian and Spanish edition of the book Made with Creative Commons + http://people.skolelinux.org/pere/blog/First_rough_draft_Norwegian_and_Spanish_edition_of_the_book_Made_with_Creative_Commons.html + http://people.skolelinux.org/pere/blog/First_rough_draft_Norwegian_and_Spanish_edition_of_the_book_Made_with_Creative_Commons.html + Tue, 13 Mar 2018 13:00:00 +0100 + <p>I am working on publishing yet another book related to Creative +Commons. This time it is a book filled with interviews and histories +from those around the globe making a living using Creative +Commons.</p> + +<p>Yesterday, after many months of hard work by several volunteer +translators, the first draft of a Norwegian Bokmål edition of the book +<a href="https://madewith.cc">Made with Creative Commons from 2017</a> +was complete. The Spanish translation is also complete, while the +Dutch, Polish, German and Ukraine edition need a lot of work. Get in +touch if you want to help make those happen, or would like to +translate into your mother tongue.</p> + +<p>The whole book project started when +<a href="http://gwolf.org/node/4102">Gunnar Wolf announced</a> that he +was going to make a Spanish edition of the book. I noticed, and +offered some input on how to make a book, based on my experience with +translating the +<a href="https://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">Free +Culture</a> and +<a href="https://debian-handbook.info/get/#norwegian">The Debian +Administrator's Handbook</a> books to Norwegian Bokmål. To make a +long story short, we ended up working on a Bokmål edition, and now the +first rough translation is complete, thanks to the hard work of +Ole-Erik Yrvin, Ingrid Yrvin, Allan Nordhøy and myself. The first +proof reading is almost done, and only the second and third proof +reading remains. We will also need to translate the 14 figures and +create a book cover. Once it is done we will publish the book on +paper, as well as in PDF, ePub and possibly Mobi formats.</p> + +<p>The book itself originates as a manuscript on Google Docs, is +downloaded as ODT from there and converted to Markdown using pandoc. +The Markdown is modified by a script before is converted to DocBook +using pandoc. The DocBook is modified again using a script before it +is used to create a Gettext POT file for translators. The translated +PO file is then combined with the earlier mentioned DocBook file to +create a translated DocBook file, which finally is given to dblatex to +create the final PDF. The end result is a set of editions of the +manuscript, one English and one for each of the translations.</p> + +<p>The translation is conducted using +<a href="https://hosted.weblate.org/projects/madewithcc/translation/">the +Weblate web based translation system</a>. Please have a look there +and get in touch if you would like to help out with proof +reading. :)</p> + +<p>As usual, if you use Bitcoin and want to show your support of my +activities, please send Bitcoin donations to my address +<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p> - Mangler du en skrue, eller har du en skrue løs? - http://people.skolelinux.org/pere/blog/Mangler_du_en_skrue__eller_har_du_en_skrue_l_s_.html - http://people.skolelinux.org/pere/blog/Mangler_du_en_skrue__eller_har_du_en_skrue_l_s_.html - Wed, 4 Oct 2017 09:40:00 +0200 - Når jeg holder på med ulike prosjekter, så trenger jeg stadig ulike -skruer. Det siste prosjektet jeg holder på med er å lage -<a href="https://www.thingiverse.com/thing:676916">en boks til en -HDMI-touch-skjerm</a> som skal brukes med Raspberry Pi. Boksen settes -sammen med skruer og bolter, og jeg har vært i tvil om hvor jeg kan -få tak i de riktige skruene. Clas Ohlson og Jernia i nærheten har -sjelden hatt det jeg trenger. Men her om dagen fikk jeg et fantastisk -tips for oss som bor i Oslo. -<a href="http://www.zachskruer.no/">Zachariassen Jernvare AS</a> i -<a href="http://www.openstreetmap.org/?mlat=59.93421&mlon=10.76795#map=19/59.93421/10.76795">Hegermannsgate -23A på Torshov</a> har et fantastisk utvalg, og åpent mellom 09:00 og -17:00. De selger skruer, muttere, bolter, skiver etc i løs vekt, og -så langt har jeg fått alt jeg har lett etter. De har i tillegg det -meste av annen jernvare, som verktøy, lamper, ledninger, etc. Jeg -håper de har nok kunder til å holde det gående lenge, da dette er en -butikk jeg kommer til å besøke ofte. Butikken er et funn å ha i -nabolaget for oss som liker å bygge litt selv. :)</p> + Debian used in the subway info screens in Oslo, Norway + http://people.skolelinux.org/pere/blog/Debian_used_in_the_subway_info_screens_in_Oslo__Norway.html + http://people.skolelinux.org/pere/blog/Debian_used_in_the_subway_info_screens_in_Oslo__Norway.html + Fri, 2 Mar 2018 13:10:00 +0100 + <p>Today I was pleasantly surprised to discover my operating system of +choice, Debian, was used in the info screens on the subway stations. +While passing Nydalen subway station in Oslo, Norway, I discovered the +info screen booting with some text scrolling. I was not quick enough +with my camera to be able to record a video of the scrolling boot +screen, but I did get a photo from when the boot got stuck with a +corrupt file system: + +<p align="center"><a href="http://people.skolelinux.org/pere/blog/images/2018-03-02-ruter-debian-lenny.jpeg"><img align="center" width="40%" src="http://people.skolelinux.org/pere/blog/images/2018-03-02-ruter-debian-lenny.jpeg" alt="[photo of subway info screen]"></a></p> + +<p>While I am happy to see Debian used more places, some details of the +content on the screen worries me.</p> + +<p>The image show the version booting is 'Debian GNU/Linux lenny/sid', +indicating that this is based on code taken from Debian Unstable/Sid +after Debian Etch (version 4) was released 2007-04-08 and before +Debian Lenny (version 5) was released 2009-02-14. Since Lenny Debian +has released version 6 (Squeeze) 2011-02-06, 7 (Wheezy) 2013-05-04, 8 +(Jessie) 2015-04-25 and 9 (Stretch) 2017-06-15, according to +<a href="https://en.wikipedia.org/wiki/Debian_version_history">a Debian +version history on Wikpedia</a>. This mean the system is running +around 10 year old code, with no security fixes from the vendor for +many years.</p> + +<p>This is not the first time I discover the Oslo subway company, +Ruter, running outdated software. In 2012, +<a href="http://people.skolelinux.org/pere/blog/Er_billettautomatene_til_kollektivtrafikken_i_Oslo_uten_sikkerhetsoppdateringer_.html">I +discovered the ticket vending machines were running Windows 2000</a>, +and this was +<a href="http://people.skolelinux.org/pere/blog/Fortsatt_ingen_sikkerhetsoppdateringer_for_billettautomatene_til_kollektivtrafikken_i_Oslo_.html">still +the case in 2016</a>. Given the response from the responsible people +in 2016, I would assume the machines are still running unpatched +Windows 2000. Thus, an unpatched Debian setup come as no surprise.</p> + +<p>The photo is made available under the license terms +<a href="http://creativecommons.org/licenses/by/4.0/">Creative Commons +4.0 Attribution International (CC BY 4.0)</a>.</p> + +<p>As usual, if you use Bitcoin and want to show your support of my +activities, please send Bitcoin donations to my address +<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p> - Visualizing GSM radio chatter using gr-gsm and Hopglass - http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html - http://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html - Fri, 29 Sep 2017 10:30:00 +0200 - <p>Every mobile phone announce its existence over radio to the nearby -mobile cell towers. And this radio chatter is available for anyone -with a radio receiver capable of receiving them. Details about the -mobile phones with very good accuracy is of course collected by the -phone companies, but this is not the topic of this blog post. The -mobile phone radio chatter make it possible to figure out when a cell -phone is nearby, as it include the SIM card ID (IMSI). By paying -attention over time, one can see when a phone arrive and when it leave -an area. I believe it would be nice to make this information more -available to the general public, to make more people aware of how -their phones are announcing their whereabouts to anyone that care to -listen.</p> - -<p>I am very happy to report that we managed to get something -visualizing this information up and running for -<a href="http://norwaymakers.org/osf17">Oslo Skaperfestival 2017</a> -(Oslo Makers Festival) taking place today and tomorrow at Deichmanske -library. The solution is based on the -<a href="http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html">simple -recipe for listening to GSM chatter</a> I posted a few days ago, and -will show up at the stand of <a href="http://sonen.ifi.uio.no/">Åpen -Sone from the Computer Science department of the University of -Oslo</a>. The presentation will show the nearby mobile phones (aka -IMSIs) as dots in a web browser graph, with lines to the dot -representing mobile base station it is talking to. It was working in -the lab yesterday, and was moved into place this morning.</p> - -<p>We set up a fairly powerful desktop machine using Debian -Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers -connected and visualize the visible cell phone towers using an -<a href="https://github.com/marlow925/hopglass">English version of -Hopglass</a>. A fairly powerfull machine is needed as the -grgsm_livemon_headless processes from -<a href="https://tracker.debian.org/pkg/gr-gsm">gr-gsm</a> converting -the radio signal to data packages is quite CPU intensive.</p> - -<p>The frequencies to listen to, are identified using a slightly -patched scan-and-livemon (to set the --args values for each receiver), -and the Hopglass data is generated using the -<a href="https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output">patches -in my meshviewer-output branch</a>. For some reason we could not get -more than four SDRs working. There is also a geographical map trying -to show the location of the base stations, but I believe their -coordinates are hardcoded to some random location in Germany, I -believe. The code should be replaced with code to look up location in -a text file, a sqlite database or one of the online databases -mentioned in -<a href="https://github.com/Oros42/IMSI-catcher/issues/14">the github -issue for the topic</a>. - -<p>If this sound interesting, visit the stand at the festival!</p> + The SysVinit upstream project just migrated to git + http://people.skolelinux.org/pere/blog/The_SysVinit_upstream_project_just_migrated_to_git.html + http://people.skolelinux.org/pere/blog/The_SysVinit_upstream_project_just_migrated_to_git.html + Sun, 18 Feb 2018 09:20:00 +0100 + <p>Surprising as it might sound, there are still computers using the +traditional Sys V init system, and there probably will be until +systemd start working on Hurd and FreeBSD. +<a href="https://savannah.nongnu.org/projects/sysvinit">The upstream +project still exist</a>, though, and up until today, the upstream +source was available from Savannah via subversion. I am happy to +report that this just changed.</p> + +<p>The upstream source is now in Git, and consist of three +repositories:</p> + +<ul> + +<li><a href="http://git.savannah.nongnu.org/cgit/sysvinit.git">sysvinit</a></li> +<li><a href="http://git.savannah.nongnu.org/cgit/sysvinit/insserv.git">insserv</a></li> +<li><a href="http://git.savannah.nongnu.org/cgit/sysvinit/startpar.git">startpar</a></li> + +</ul> + +<p>I do not really spend much time on the project these days, and I +has mostly retired, but found it best to migrate the source to a good +version control system to help those willing to move it forward.</p> + +<p>As usual, if you use Bitcoin and want to show your support of my +activities, please send Bitcoin donations to my address +<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p> - Easier recipe to observe the cell phones around you - http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html - http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html - Sun, 24 Sep 2017 08:30:00 +0200 - <p>A little more than a month ago I wrote -<a href="http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html">how -to observe the SIM card ID (aka IMSI number) of mobile phones talking -to nearby mobile phone base stations using Debian GNU/Linux and a -cheap USB software defined radio</a>, and thus being able to pinpoint -the location of people and equipment (like cars and trains) with an -accuracy of a few kilometer. Since then we have worked to make the -procedure even simpler, and it is now possible to do this without any -manual frequency tuning and without building your own packages.</p> - -<p>The <a href="https://tracker.debian.org/pkg/gr-gsm">gr-gsm</a> -package is now included in Debian testing and unstable, and the -IMSI-catcher code no longer require root access to fetch and decode -the GSM data collected using gr-gsm.</p> - -<p>Here is an updated recipe, using packages built by Debian and a git -clone of two python scripts:</p> - -<ol> - -<li>Start with a Debian machine running the Buster version (aka - testing).</li> - -<li>Run '<tt>apt install gr-gsm python-numpy python-scipy - python-scapy</tt>' as root to install required packages.</li> - -<li>Fetch the code decoding GSM packages using '<tt>git clone - github.com/Oros42/IMSI-catcher.git</tt>'.</li> - -<li>Insert USB software defined radio supported by GNU Radio.</li> - -<li>Enter the IMSI-catcher directory and run '<tt>python - scan-and-livemon</tt>' to locate the frequency of nearby base - stations and start listening for GSM packages on one of them.</li> - -<li>Enter the IMSI-catcher directory and run '<tt>python - simple_IMSI-catcher.py</tt>' to display the collected information.</li> - -</ol> - -<p>Note, due to a bug somewhere the scan-and-livemon program (actually -<a href="https://github.com/ptrkrysik/gr-gsm/issues/336">its underlying -program grgsm_scanner</a>) do not work with the HackRF radio. It does -work with RTL 8232 and other similar USB radio receivers you can get -very cheaply -(<a href="https://www.ebay.com/sch/items/?_nkw=rtl+2832">for example -from ebay</a>), so for now the solution is to scan using the RTL radio -and only use HackRF for fetching GSM data.</p> - -<p>As far as I can tell, a cell phone only show up on one of the -frequencies at the time, so if you are going to track and count every -cell phone around you, you need to listen to all the frequencies used. -To listen to several frequencies, use the --numrecv argument to -scan-and-livemon to use several receivers. Further, I am not sure if -phones using 3G or 4G will show as talking GSM to base stations, so -this approach might not see all phones around you. I typically see -0-400 IMSI numbers an hour when looking around where I live.</p> - -<p>I've tried to run the scanner on a -<a href="https://wiki.debian.org/RaspberryPi">Raspberry Pi 2 and 3 -running Debian Buster</a>, but the grgsm_livemon_headless process seem -to be too CPU intensive to keep up. When GNU Radio print 'O' to -stdout, I am told there it is caused by a buffer overflow between the -radio and GNU Radio, caused by the program being unable to read the -GSM data fast enough. If you see a stream of 'O's from the terminal -where you started scan-and-livemon, you need a give the process more -CPU power. Perhaps someone are able to optimize the code to a point -where it become possible to set up RPi3 based GSM sniffers? I tried -using Raspbian instead of Debian, but there seem to be something wrong -with GNU Radio on raspbian, causing glibc to abort().</p> + Using VLC to stream bittorrent sources + http://people.skolelinux.org/pere/blog/Using_VLC_to_stream_bittorrent_sources.html + http://people.skolelinux.org/pere/blog/Using_VLC_to_stream_bittorrent_sources.html + Wed, 14 Feb 2018 08:00:00 +0100 + <p>A few days ago, a new major version of +<a href="https://www.videolan.org/">VLC</a> was announced, and I +decided to check out if it now supported streaming over +<a href="http://bittorrent.org/">bittorrent</a> and +<a href="https://webtorrent.io">webtorrent</a>. Bittorrent is one of +the most efficient ways to distribute large files on the Internet, and +Webtorrent is a variant of Bittorrent using +<a href="https://webrtc.org">WebRTC</a> as its transport channel, +allowing web pages to stream and share files using the same technique. +The network protocols are similar but not identical, so a client +supporting one of them can not talk to a client supporting the other. +I was a bit surprised with what I discovered when I started to look. +Looking at +<a href="https://www.videolan.org/vlc/releases/3.0.0.html">the release +notes</a> did not help answering this question, so I started searching +the web. I found several news articles from 2013, most of them +tracing the news from Torrentfreak +("<a href=https://torrentfreak.com/open-source-giant-vlc-mulls-bittorrent-support-130211/">Open +Source Giant VLC Mulls BitTorrent Streaming Support</a>"), about a +initiative to pay someone to create a VLC patch for bittorrent +support. To figure out what happend with this initiative, I headed +over to the #videolan IRC channel and asked if there were some bug or +feature request tickets tracking such feature. I got an answer from +lead developer Jean-Babtiste Kempf, telling me that there was a patch +but neither he nor anyone else knew where it was. So I searched a bit +more, and came across an independent +<a href="https://github.com/johang/vlc-bittorrent">VLC plugin to add +bittorrent support</a>, created by Johan Gunnarsson in 2016/2017. +Again according to Jean-Babtiste, this is not the patch he was talking +about.</p> + +<p>Anyway, to test the plugin, I made a working Debian package from +the git repository, with some modifications. After installing this +package, I could stream videos from +<a href="https://www.archive.org/">The Internet Archive</a> using VLC +commands like this:</p> + +<p><blockquote><pre> +vlc https://archive.org/download/LoveNest/LoveNest_archive.torrent +</pre></blockquote></p> + +<p>The plugin is supposed to handle magnet links too, but since The +Internet Archive do not have magnet links and I did not want to spend +time tracking down another source, I have not tested it. It can take +quite a while before the video start playing without any indication of +what is going on from VLC. It took 10-20 seconds when I measured it. +Some times the plugin seem unable to find the correct video file to +play, and show the metadata XML file name in the VLC status line. I +have no idea why.</p> + +<p>I have created a <a href="https://bugs.debian.org/890360">request for +a new package in Debian (RFP)</a> and +<a href="https://github.com/johang/vlc-bittorrent/issues/1">asked if +the upstream author is willing to help make this happen</a>. Now we +wait to see what come out of this. I do not want to maintain a +package that is not maintained upstream, nor do I really have time to +maintain more packages myself, so I might leave it at this. But I +really hope someone step up to do the packaging, and hope upstream is +still maintaining the source. If you want to help, please update the +RFP request or the upstream issue.</p> + +<p>I have not found any traces of webtorrent support for VLC.</p> + +<p>As usual, if you use Bitcoin and want to show your support of my +activities, please send Bitcoin donations to my address +<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p> - Datalagringsdirektivet kaster skygger over Høyre og Arbeiderpartiet - http://people.skolelinux.org/pere/blog/Datalagringsdirektivet_kaster_skygger_over_H_yre_og_Arbeiderpartiet.html - http://people.skolelinux.org/pere/blog/Datalagringsdirektivet_kaster_skygger_over_H_yre_og_Arbeiderpartiet.html - Thu, 7 Sep 2017 21:35:00 +0200 - <p>For noen dager siden publiserte Jon Wessel-Aas en bloggpost om -«<a href="http://www.uhuru.biz/?p=1821">Konklusjonen om datalagring som -EU-kommisjonen ikke ville at vi skulle få se</a>». Det er en -interessant gjennomgang av EU-domstolens syn på snurpenotovervåkning -av befolkningen, som er klar på at det er i strid med -EU-lovgivingen.</p> - -<p>Valgkampen går for fullt i Norge, og om noen få dager er siste -frist for å avgi stemme. En ting er sikkert, Høyre og Arbeiderpartiet -får ikke min stemme -<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 -gangen heller</a>. Jeg har ikke glemt at de tvang igjennom loven som -skulle pålegge alle data- og teletjenesteleverandører å overvåke alle -sine kunder. En lov som er vedtatt, og aldri opphevet igjen.</p> - -<p>Det er tydelig fra diskusjonen rundt grenseløs digital overvåkning -(eller "Digital Grenseforsvar" som det kalles i Orvellisk nytale) at -hverken Høyre og Arbeiderpartiet har noen prinsipielle sperrer mot å -overvåke hele befolkningen, og diskusjonen så langt tyder på at flere -av de andre partiene heller ikke har det. Mange av -<a href="https://data.holderdeord.no/votes/1301946411e">de som stemte -for Datalagringsdirektivet i Stortinget</a> (64 fra Arbeiderpartiet, -25 fra Høyre) er fortsatt aktive og argumenterer fortsatt for å radere -vekk mer av innbyggernes privatsfære.</p> - -<p>Når myndighetene demonstrerer sin mistillit til folket, tror jeg -folket selv bør legge litt innsats i å verne sitt privatliv, ved å ta -i bruk ende-til-ende-kryptert kommunikasjon med sine kjente og kjære, -og begrense hvor mye privat informasjon som deles med uvedkommende. -Det er jo ingenting som tyder på at myndighetene kommer til å være vår -privatsfære. -<a href="http://people.skolelinux.org/pere/blog/How_to_talk_with_your_loved_ones_in_private.html">Det -er mange muligheter</a>. Selv har jeg litt sans for -<a href="https://ring.cx/">Ring</a>, som er basert på p2p-teknologi -uten sentral kontroll, er fri programvare, og støtter meldinger, tale -og video. Systemet er tilgjengelig ut av boksen fra -<a href="https://tracker.debian.org/pkg/ring">Debian</a> og -<a href="https://launchpad.net/ubuntu/+source/ring">Ubuntu</a>, og det -finnes pakker for Android, MacOSX og Windows. Foreløpig er det få -brukere med Ring, slik at jeg også bruker -<a href="https://signal.org/">Signal</a> som nettleserutvidelse.</p> + Version 3.1 of Cura, the 3D print slicer, is now in Debian + http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html + http://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html + Tue, 13 Feb 2018 06:20:00 +0100 + <p>A new version of the +<a href="https://tracker.debian.org/pkg/cura">3D printer slicer +software Cura</a>, version 3.1.0, is now available in Debian Testing +(aka Buster) and Debian Unstable (aka Sid). I hope you find it +useful. It was uploaded the last few days, and the last update will +enter testing tomorrow. See the +<a href="https://ultimaker.com/en/products/cura-software/release-notes">release +notes</a> for the list of bug fixes and new features. Version 3.2 +was announced 6 days ago. We will try to get it into Debian as +well.</p> + +<p>More information related to 3D printing is available on the +<a href="https://wiki.debian.org/3DPrinting">3D printing</a> and +<a href="https://wiki.debian.org/3D-printer">3D printer</a> wiki pages +in Debian.</p> + +<p>As usual, if you use Bitcoin and want to show your support of my +activities, please send Bitcoin donations to my address +<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p> - Simpler recipe on how to make a simple $7 IMSI Catcher using Debian - http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html - http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html - Wed, 9 Aug 2017 23:59:00 +0200 - <p>On friday, I came across an interesting article in the Norwegian -web based ICT news magazine digi.no on -<a href="https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-60-kroner-na-kan-mobiler-kartlegges-av-alle/398588">how -to collect the IMSI numbers of nearby cell phones</a> using the cheap -DVB-T software defined radios. The article refered to instructions -and <a href="https://www.youtube.com/watch?v=UjwgNd_as30">a recipe by -Keld Norman on Youtube on how to make a simple $7 IMSI Catcher</a>, and I decided to test them out.</p> - -<p>The instructions said to use Ubuntu, install pip using apt (to -bypass apt), use pip to install pybombs (to bypass both apt and pip), -and the ask pybombs to fetch and build everything you need from -scratch. I wanted to see if I could do the same on the most recent -Debian packages, but this did not work because pybombs tried to build -stuff that no longer build with the most recent openssl library or -some other version skew problem. While trying to get this recipe -working, I learned that the apt->pip->pybombs route was a long detour, -and the only piece of software dependency missing in Debian was the -gr-gsm package. I also found out that the lead upstream developer of -gr-gsm (the name stand for GNU Radio GSM) project already had a set of -Debian packages provided in an Ubuntu PPA repository. All I needed to -do was to dget the Debian source package and built it.</p> - -<p>The IMSI collector is a python script listening for packages on the -loopback network device and printing to the terminal some specific GSM -packages with IMSI numbers in them. The code is fairly short and easy -to understand. The reason this work is because gr-gsm include a tool -to read GSM data from a software defined radio like a DVB-T USB stick -and other software defined radios, decode them and inject them into a -network device on your Linux machine (using the loopback device by -default). This proved to work just fine, and I've been testing the -collector for a few days now.</p> - -<p>The updated and simpler recipe is thus to</p> - -<ol> - -<li>start with a Debian machine running Stretch or newer,</li> - -<li>build and install the gr-gsm package available from -<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> - -<li>clone the git repostory from <a href="https://github.com/Oros42/IMSI-catcher">https://github.com/Oros42/IMSI-catcher</a>,</li> - -<li>run grgsm_livemon and adjust the frequency until the terminal -where it was started is filled with a stream of text (meaning you -found a GSM station).</li> - -<li>go into the IMSI-catcher directory and run 'sudo python simple_IMSI-catcher.py' to extract the IMSI numbers.</li> - -</ol> - -<p>To make it even easier in the future to get this sniffer up and -running, I decided to package -<a href="https://github.com/ptrkrysik/gr-gsm/">the gr-gsm project</a> -for Debian (<a href="https://bugs.debian.org/871055">WNPP -#871055</a>), and the package was uploaded into the NEW queue today. -Luckily the gnuradio maintainer has promised to help me, as I do not -know much about gnuradio stuff yet.</p> - -<p>I doubt this "IMSI cacher" is anywhere near as powerfull as -commercial tools like -<a href="https://www.thespyphone.com/portable-imsi-imei-catcher/">The -Spy Phone Portable IMSI / IMEI Catcher</a> or the -<a href="https://en.wikipedia.org/wiki/Stingray_phone_tracker">Harris -Stingray</a>, but I hope the existance of cheap alternatives can make -more people realise how their whereabouts when carrying a cell phone -is easily tracked. Seeing the data flow on the screen, realizing that -I live close to a police station and knowing that the police is also -wearing cell phones, I wonder how hard it would be for criminals to -track the position of the police officers to discover when there are -police near by, or for foreign military forces to track the location -of the Norwegian military forces, or for anyone to track the location -of government officials...</p> - -<p>It is worth noting that the data reported by the IMSI-catcher -script mentioned above is only a fraction of the data broadcasted on -the GSM network. It will only collect one frequency at the time, -while a typical phone will be using several frequencies, and not all -phones will be using the frequencies tracked by the grgsm_livemod -program. Also, there is a lot of radio chatter being ignored by the -simple_IMSI-catcher script, which would be collected by extending the -parser code. I wonder if gr-gsm can be set up to listen to more than -one frequency?</p> + Overvåkning i Kina vs. Norge + http://people.skolelinux.org/pere/blog/Overv_kning_i_Kina_vs__Norge.html + http://people.skolelinux.org/pere/blog/Overv_kning_i_Kina_vs__Norge.html + Mon, 12 Feb 2018 09:40:00 +0100 + <p>Jeg lar meg fascinere av en artikkel +<a href="https://www.dagbladet.no/kultur/terroristene-star-pa-dora/69436116">i +Dagbladet om Kinas håndtering av Xinjiang</a>, spesielt følgende +utsnitt:</p> + +<p><blockquote> + +<p>«I den sørvestlige byen Kashgar nærmere grensa til +Sentral-Asia meldes det nå at 120.000 uigurer er internert i såkalte +omskoleringsleirer. Samtidig er det innført et omfattende +helsesjekk-program med innsamling og lagring av DNA-prøver fra +absolutt alle innbyggerne. De mest avanserte overvåkingsmetodene +testes ut her. Programmer for å gjenkjenne ansikter og stemmer er på +plass i regionen. Der har de lokale myndighetene begynt å installere +GPS-systemer i alle kjøretøy og egne sporingsapper i +mobiltelefoner.</p> + +<p>Politimetodene griper så dypt inn i folks dagligliv at motstanden +mot Beijing-regimet øker.»</p> + +</blockquote></p> + +<p>Beskrivelsen avviker jo desverre ikke så veldig mye fra tilstanden +her i Norge.</p> + +<table> +<tr> +<th>Dataregistrering</th> +<th>Kina</th> +<th>Norge</th> + +<tr> +<td>Innsamling og lagring av DNA-prøver fra befolkningen</td> +<td>Ja</td> +<td>Delvis, planlagt for alle nyfødte.</td> +</tr> + +<tr> +<td>Ansiktsgjenkjenning</td> +<td>Ja</td> +<td>Ja</td> +</tr> + +<tr> +<td>Stemmegjenkjenning</td> +<td>Ja</td> +<td>Nei</td> +</tr> + +<tr> +<td>Posisjons-sporing av mobiltelefoner</td> +<td>Ja</td> +<td>Ja</td> +</tr> + +<tr> +<td>Posisjons-sporing av biler</td> +<td>Ja</td> +<td>Ja</td> +</tr> + +</table> + +<p>I Norge har jo situasjonen rundt Folkehelseinstituttets lagring av +DNA-informasjon på vegne av politiet, der de nektet å slette +informasjon politiet ikke hadde lov til å ta vare på, gjort det klart +at DNA tar vare på ganske lenge. I tillegg finnes det utallige +biobanker som lagres til evig tid, og det er planer om å innføre +<a href="https://www.aftenposten.no/norge/i/75E9/4-av-10-mener-staten-bor-lagre-DNA-profiler-pa-alle-nyfodte">evig +lagring av DNA-materiale fra alle spebarn som fødes</a> (med mulighet +for å be om sletting).</p> + +<p>I Norge er det system på plass for ansiktsgjenkjenning, som +<a href="https://www.nrk.no/norge/kun-gardermoen-har-teknologi-for-ansiktsgjenkjenning-i-norge-1.12719461">en +NRK-artikkel fra 2015</a> forteller er aktiv på Gardermoen, samt +<a href="https://www.dagbladet.no/nyheter/inntil-27-000-bor-i-norge-under-falsk-id/60500781">brukes +til å analysere bilder innsamlet av myndighetene</a>. Brukes det også +flere plasser? Det er tett med overvåkningskamera kontrollert av +politi og andre myndigheter i for eksempel Oslo sentrum.</p> + +<p>Jeg er ikke kjent med at Norge har noe system for identifisering av +personer ved hjelp av stemmegjenkjenning.</p> + +<p>Posisjons-sporing av mobiltelefoner er ruinemessig tilgjengelig for +blant annet politi, NAV og Finanstilsynet, i tråd med krav i +telefonselskapenes konsesjon. I tillegg rapporterer smarttelefoner +sin posisjon til utviklerne av utallige mobil-apper, der myndigheter +og andre kan hente ut informasjon ved behov. Det er intet behov for +noen egen app for dette.</p> + +<p>Posisjons-sporing av biler er rutinemessig tilgjengelig via et tett +nett av målepunkter på veiene (automatiske bomstasjoner, +køfribrikke-registrering, automatiske fartsmålere og andre veikamera). +Det er i tillegg vedtatt at alle nye biler skal selges med utstyr for +GPS-sporing (eCall).</p> + +<p>Det er jammen godt vi lever i et liberalt demokrati, og ikke en +overvåkningsstat, eller?</p> + +<p>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til +det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner +til min adresse +<b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>