August 2018 - nexa - server-nexa.polito.it

Re: [nexa] Is coding style personal data?

by Giacomo Tesio

In effetti anche i riferimenti dell'articolo sono molto interessanti. Ho seguito alcuni dei riferimenti per trovare il paper in cui si indicano le caratteristiche del codice utilizzate per identificare i programmatori. https://www.usenix.org/system/files/conference/usenixsecurity15/sec15-paper… Va sicuramente notato che in certi linguaggi il layout è determinato piuttosto rigidamente (e.g. Haskell, Python e in un certo senso anche Go) anche se non sempre vincolati a livello di compilatore/interprete. D'altro canto è ragionevole pensare che un linguaggio più complesso (i paper si basano su C++) determini un maggior numero di possibili stili come combinazione delle feature rindondanti. In questa ottica sarebbe molto interessante vedere lo stesso studio applicato ad un linguaggio semplice ed elegante come Oberon-07, che il Professor Wirth continua a perfezionare *rimuovendo* features. Detto questo, non so se si possa utilizzare queste tecniche come prova perché uno stile può essere facilmente imitato da un programmatore esperto: è una cosa che facciamo di continuo (con vari gradi di successo) quando studiamo ed estendiamo un software esistente o quando correggiamo un problema ed intendiamo condividere la modifica con gli autori originali. Giacomo Il Ven 17 Ago 2018 08:20 Diego Giorio <dgiorio(a)hotmail.com> ha scritto: > Molto interessante, grazie per la segnalazione. > > > In realtà il discorso dello stile, che rende identificabile una persona, è > molto più ampio: uno stile pittorico, un modo di scrivere, un approccio > personale al disegno possono rendere identificabile una persona tanto > quanto lo stile di programmazione. > > > Buon agosto a tutti > > > D. > > > ------------------------------ > *From:* nexa <nexa-bounces(a)server-nexa.polito.it> on behalf of Giovanni > Battista Gallus <g.gallus(a)gmail.com> > *Sent:* Thursday, August 16, 2018 6:28 AM > *To:* nexa(a)server-nexa.polito.it > *Subject:* [nexa] Is coding style personal data? > > Identifying Programmers by their Coding Style > > *[2018.08.13]* > <https://www.schneier.com/blog/archives/2018/08/identifying_pro.html> > Fascinating research > <https://www.wired.com/story/machine-learning-identify-anonymous-code/> de-anonymizing > code -- from either source code or compiled code: > > Rachel Greenstadt, an associate professor of computer science at Drexel > University, and Aylin Caliskan, Greenstadt's former PhD student and now an > assistant professor at George Washington University, have found that code, > like other forms of stylistic expression, are not anonymous. At the DefCon > hacking conference Friday, the pair will present a number of studies > they've conducted using machine learning techniques to de-anonymize the > authors of code samples. Their work could be useful in a plagiarism > dispute, for instance, but it also has privacy implications, especially for > the thousands of developers who contribute open source code to the world. > > > Una prospettiva molto interessante, segnalata sull'ultimo Cryptogram ( > https://www.schneier.com/crypto-gram/archives/2018/0815.html#cg29) > > Buone riflessioni agostane. > > G.Battista Gallus > > _______________________________________________ > nexa mailing list > nexa(a)server-nexa.polito.it > https://server-nexa.polito.it/cgi-bin/mailman/listinfo/nexa >

Aug. 20, 2018

How Royal Mail saved home mover marketing from the GDPR graveyard

by Luigi Scorca

https://www-computerworlduk-com.cdn.ampproject.org/c/s/www.computerworlduk.…

Aug. 20, 2018

Botched CIA Communications System Helped Blow Cover of Chinese Agents

by Alberto Cammozzo

<https://foreignpolicy.com/2018/08/15/botched-cia-communications-system-help…># t was considered one of the CIA’s worst failures in decades: Over a two-year period starting in late 2010, Chinese authorities systematically dismantled the agency’s network of agents across the country, executing dozens of suspected U.S. spies. But since then, a question has loomed over the entire debacle. How were the Chinese able to roll up the network? Now, nearly eight years later, it appears that the agency botched the communication system it used to interact with its sources, according to five current and former intelligence officials. The CIA had imported the system from its Middle East operations, where the online environment was considerably less hazardous, and apparently underestimated China’s ability to penetrate it. “The attitude was that we’ve got this, we’re untouchable,” said one of the officials who, like the others, declined to be named discussing sensitive information. The former official described the attitude of those in the agency who worked on China at the time as “invincible.” [] When CIA officers begin working with a new source, they often use an interim covert communications system—in case the person turns out to be a double agent. The communications system used in China during this period was internet-based and accessible from laptop or desktop computers, two of the former officials said. This interim, or “throwaway,” system, an encrypted digital program, allows for remote communication between an intelligence officer and a source, but it is also separated from the main communications system used with vetted sources, reducing the risk if an asset goes bad. Although they used some of the same coding, the interim system and the main covert communication platform used in China at this time were supposed to be clearly separated. In theory, if the interim system were discovered or turned over to Chinese intelligence, people using the main system would still be protected—and there would be no way to trace the communication back to the CIA. But the CIA’s interim system contained a technical error: It connected back architecturally to the CIA’s main covert communications platform. When the compromise was suspected, the FBI and NSA both ran “penetration tests” to determine the security of the interim system. They found that cyber experts with access to the interim system could also access the broader covert communications system the agency was using to interact with its vetted sources, according to the former officials. In the words of one of the former officials, the CIA had “fucked up the firewall” between the two systems. [...]

Aug. 20, 2018

This company embeds microchips in its employees, and they love it

by Guido Noto La Diega

Last August, 50 employees at Three Square Market got RFID chips in their hands. Now 80 have them https://www.technologyreview.com/s/611884/this-company-embeds-microchips-in… -- Guido Dr Guido Noto La Diega Senior Lecturer / European Research Partnerships Coordinator @ Northumbria Law School Director @italiot | Fellow @nexacenter | Co-convenor @NINSOrig | Co-founder @DPA2018 Northumbria Law School City Campus East, Newcastle upon Tyne NE1 8ST noto.la.diega(a)gmail.com +44(0)191 349 5562 You can access my papers on Academia.edu <http://northumbria.academia.edu/GuidoNotoLaDiega> and on the Social Science Research Network (SSRN <https://papers.ssrn.com/sol3/cf_dev/AbsByAuth.cfm?per_id=1794950>) This e-mail and any attachment hereto are strictly confidential and are exclusively intended for the person above identified. Without intended recipient’s entitlement, use, copy and dissemination of this e-mail is prohibited. If you have received it in error, please advice us immediately by telephone and return the documents received to the above address, deleting the files. Thank you. Unless necessary, please do not print this e-mail.

Aug. 19, 2018

Gli algoritmi del copyright censurano articoli contro la censura- BrunoSaetta.it

by J.C. DE MARTIN

https://brunosaetta.it/diritto-autore/algoritmi-copyright-censurano-articol… Gli algoritmi del copyright censurano articoli contro la censura (Sent from my wireless device; please excuse brevity and typos (if any))

Aug. 17, 2018

Re: [nexa] Is coding style personal data?

by Diego Giorio

Molto interessante, grazie per la segnalazione. In realtà il discorso dello stile, che rende identificabile una persona, è molto più ampio: uno stile pittorico, un modo di scrivere, un approccio personale al disegno possono rendere identificabile una persona tanto quanto lo stile di programmazione. Buon agosto a tutti D. ________________________________ From: nexa <nexa-bounces(a)server-nexa.polito.it> on behalf of Giovanni Battista Gallus <g.gallus(a)gmail.com> Sent: Thursday, August 16, 2018 6:28 AM To: nexa(a)server-nexa.polito.it Subject: [nexa] Is coding style personal data? Identifying Programmers by their Coding Style [2018.08.13]<https://www.schneier.com/blog/archives/2018/08/identifying_pro.html> Fascinating research<https://www.wired.com/story/machine-learning-identify-anonymous-code/> de-anonymizing code -- from either source code or compiled code: Rachel Greenstadt, an associate professor of computer science at Drexel University, and Aylin Caliskan, Greenstadt's former PhD student and now an assistant professor at George Washington University, have found that code, like other forms of stylistic expression, are not anonymous. At the DefCon hacking conference Friday, the pair will present a number of studies they've conducted using machine learning techniques to de-anonymize the authors of code samples. Their work could be useful in a plagiarism dispute, for instance, but it also has privacy implications, especially for the thousands of developers who contribute open source code to the world. Una prospettiva molto interessante, segnalata sull'ultimo Cryptogram (https://www.schneier.com/crypto-gram/archives/2018/0815.html#cg29) Buone riflessioni agostane. G.Battista Gallus

Aug. 17, 2018

Re: [nexa] Interesting and relevant paper

by Stefano Quintarelli

molto molto interessante, grazie. ho sfiorato il punto nel mio articolo "intermediati di tutto il mondo, unitevi!" dove ho accennato che, per gli utenti, la proprieta' privata online non esiste. piu' che alle cryptocurrencies personalmente guardo con interesse alle possibili applicazioni di crittografia e registri pubblici per la potenzialita' di rendere le informazioni rivali ed escludibili, consentendo quindi di ridare la proprieta' dei dati agli utenti. mi sembra di leggere sempre piu' cose su questo argomento e non e' un caso che shapiro abbia detto di recente che i dati sono non rivali e solo parzialmente escludibili (mi verrebbe da pensare che intedesse "quando li custodisce qualcuno" (tipo google)) IMHO IPFS potrebbe essere rilevante in questa ipotesi ciao!, s. On 16/08/2018 13:39, Roberto Dolci wrote: > Segnalo questo articolo che prende un approccio economico interessante > sul controllo e possesso dei dati, concentrandosi sul concetto di (non) > rivalita’. > > Buona lettura > > Rob > > http://christophertonetti.com/files/papers/JonesTonetti_DataNonrivalry.pdf > > > > _______________________________________________ > nexa mailing list > nexa(a)server-nexa.polito.it > https://server-nexa.polito.it/cgi-bin/mailman/listinfo/nexa >

Aug. 16, 2018

Interesting and relevant paper

by Roberto Dolci

Segnalo questo articolo che prende un approccio economico interessante sul controllo e possesso dei dati, concentrandosi sul concetto di (non) rivalita’. Buona lettura Rob http://christophertonetti.com/files/papers/JonesTonetti_DataNonrivalry.pdf

Aug. 16, 2018

To Catch A Robber, The FBI Attempted An Unprecedented Grab For Google Location Data

by J.C. DE MARTIN

https://www.forbes.com/sites/thomasbrewster/2018/08/15/to-catch-a-robber-th… To Catch A Robber, The FBI Attempted An Unprecedented Grab For Google Location Data Thomas Fox-Brewster (Sent from my wireless device; please excuse brevity and typos (if any))

Aug. 16, 2018

Is coding style personal data?

by Giovanni Battista Gallus

Identifying Programmers by their Coding Style *[2018.08.13]* <https://www.schneier.com/blog/archives/2018/08/identifying_pro.html> Fascinating research <https://www.wired.com/story/machine-learning-identify-anonymous-code/> de-anonymizing code -- from either source code or compiled code: Rachel Greenstadt, an associate professor of computer science at Drexel University, and Aylin Caliskan, Greenstadt's former PhD student and now an assistant professor at George Washington University, have found that code, like other forms of stylistic expression, are not anonymous. At the DefCon hacking conference Friday, the pair will present a number of studies they've conducted using machine learning techniques to de-anonymize the authors of code samples. Their work could be useful in a plagiarism dispute, for instance, but it also has privacy implications, especially for the thousands of developers who contribute open source code to the world. Una prospettiva molto interessante, segnalata sull'ultimo Cryptogram ( https://www.schneier.com/crypto-gram/archives/2018/0815.html#cg29) Buone riflessioni agostane. G.Battista Gallus

Aug. 16, 2018