- nexa - server-nexa.polito.it

Fwd: slides 14-01-2022 - Seminario GdF
by Andrea Trentini Jan. 19, 2022

Jan. 19, 2022

-------- Forwarded Message -------- Subject: slides 14-01-2022 - Seminario GdF Date: Wed, 19 Jan 2022 12:06:48 +0100 From: Andrea VISCONTI <Andrea.Visconti(a)unimi.it> To: AV <visconti(a)di.unimi.it> Buongiorno a tutti, come concordato, inoltro le slides del seminario del Col. Menegazzo. Arrivederci, Andrea Visconti --- ===================================================== Andrea VISCONTI Ph.D., Assistant Professor Dipartimento di Informatica “Giovanni degli Antoni” Università degli Studi di Milano via Celoria 18 - 20133 Milano - Italy Tel: +39 02 503.16233 (Office) Tel: +39 02 503.16361 (Lab) E-mail: andrea.visconti(a)unimi.it http://www.di.unimi.it/visconti http://www.club.di.unimi.it/ =====================================================

1 0

Agenzia Entrate... e sanzioni _AUTOMATICHE_.... (ambito vaccini over 50)
by Damiano Verzulli Jan. 19, 2022

Jan. 19, 2022

Un interessante articolo di Christian Bernieri - professionista in ambito Privacy -- che passa ai raggi X la recente evoluzione del quadro normativo che --come anticipato su questa stessa lista nei giorni scorsi-- consente ora all'Agenzia delle Entrate di sanzionare chi non adempie agli obblighi vaccinali (in un contesto che definirei "scivoloso" rispetto alla questione "privacy", in quanto è evidente che per erogare la sanzione è necessario accedere al dataset informativo [anagrafe vaccinale]). Interessante (dal mio punto di vista) il fatto che le sanzioni saranno _AUTOMATICHE_. L'articolo è questo: => Obbligo vaccino over 50, ecco le sanzioni automatiche: ma la privacy? https://www.cybersecurity360.it/legal/privacy-dati-personali/sanzioni-autom… Saluti, DV P.S.: A scanso di sgradevoli equivoci, evidenzio che il focus della discussione è legato unicamente al complesso intreccio fra "dati personali", "consenso al trattamento fornito ad una entità" (es.: Ministero Salute), "accesso a tali dati da parte di un terzo" (es.: Agenzia delle Entrate), "utilizzo di tali dati per irrorare una sanzione".... e nulla ha a che vedere con il tema "vaccini". -- Damiano Verzulli e-mail: damiano(a)verzulli.it --- possible?ok:while(!possible){open_mindedness++} --- "...I realized that free software would not generate the kind of income that was needed. Maybe in USA or Europe, you may be able to get a well paying job as a free software developer, but not here [in Africa]..." -- Guido Sohne - 1973-2008 http://ole.kenic.or.ke/pipermail/skunkworks/2008-April/005989.html

1 0

Re: [nexa] "German police under fire for misuse of COVID contact tracing app"
by Giuseppe Attardi Jan. 18, 2022

Jan. 18, 2022

Curioso che la gente abbia obiettato a soluzioni decentralizzate come quella ufficiale ‘Corona Warn’, e poi oltre 7 milioni di persone abbiano adottato una soluzione centralizzata e gestita da un’azienda privata, oltretutto complicata da usare, perché richiede di scandire un QR code all’entrata o uscita da un posto. Luca has a problematic centralised architecture, it is opaque and proprietary (it "creates a dependency on a single private company with the intention of making a profit as the operator of the system"), and its use is nonetheless "de facto compulsory," thus violating many of the privacy and rights-preserving principles established during the development of Germany's exposure notification app, 'Corona Warn'. — Beppe > On 18 Jan 2022, at 11:38, nexa-request(a)server-nexa.polito.it wrote: > > Date: Tue, 18 Jan 2022 09:40:05 +0100 > From: "J.C. DE MARTIN" <demartin(a)polito.it> > To: Nexa <nexa(a)server-nexa.polito.it> > Subject: [nexa] "German police under fire for misuse of COVID contact > tracing app" > Message-ID: <38a342a7-806e-b301-41fe-41d3fb699773(a)polito.it> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > *German police under fire for misuse of COVID contact tracing app** > */ > //German police used a contact tracing app to track down witnesses in a > local crime case. The scandal has data protection advocates up in arms, > with politicians warning that abuse of the app could undermine public > trust./ > > [...] > > continua qui: > https://www.dw.com/en/german-police-under-fire-for-misuse-of-covid-contact-…

2 1

Libro: "Digisprudence: Code as Law Rebooted" (open access)
by J.C. DE MARTIN Jan. 18, 2022

Jan. 18, 2022

*"Digisprudence: Code as Law Rebooted"* Laurence Diver Edinburgh University Press 276 pages Future Law Published December 2021 https://edinburghuniversitypress.com/book-digisprudence-code-as-law-reboote… *PDF disponibile in open access** * Reboots the debate on ‘code as law’ to present a new cross-disciplinary direction that sheds light on the fundamental issue of software legitimacy Reinvigorates the debate at the intersection of legal theory, philosophy of technology, STS and design practice Synthesises theories of legitimate legal rulemaking with practical knowledge of code production tools and practice Proposes a set of affordances that can legitimise code in line with an ecological view of legality Draws on contemporary technologies as case studies, examining blockchain applications and the Internet of Things Laurence Diver combines insight from legal theory, philosophy of technology and programming practice to develop a new theoretical and practical approach to the design of legitimate software. The book critically engages with the rule(s) of code, arguing that, like laws, these should exhibit certain formal characteristics if they are to be acceptable in a democracy. The resulting digisprudential affordances translate ideas of legitimacy from legal philosophy into the world of code design, to be realised through the ‘constitutional’ role played by programming languages, integrated development environments (IDEs), and agile development practice. The text interweaves theory and practice throughout, including many insights into real-world technologies, as well as case studies on blockchain applications and the Internet of Things (IoT). 1. Introduction The Structure of the Argument Rebooting ‘Code as Law’ Aspiring to Legitimacy in Code ‘Code as Law’, Code Versus Law, or Something Else? Concluding *Part I: Computational Legalism and the Rule(s) of Code* 2. A Design Perspective: Code Is More Than Law Affordance Infusing Code with Normativity 3. A Legal Philosophy Perspective: Code is Less Than Law What is Legalism? Computational Legalism Conclusion *Part II: What Makes a Good Rule?* 4. Criteria for Laws Normative Criteria for Law-Making: the Aspirations of Legality Conclusion 5. Criteria for Code Input and Output Legitimacy in Code Input Legitimacy Conclusion *Part III: Legitimating Code: Theory and Practice* 6. The Digisprudential Affordances Assessing Decisions, Or Assessing Design? Mapping the Criteria From Characteristics To Affordances Conclusion 7. Operationalising Digisprudence The Programmer of the Programmer Agile Development Integrated Development Environments Code and Natural Language Conclusion 8. Rebooting Code as Law: Conclusions and Next Steps The Contemporary Relevance of Digisprudence Next Steps? Concluding Thoughts

1 0

La connessione satellitare Starlink di Elon Musk deve fare i conti con una “minaccia” inaspettata: i gatti
by don Luca Peyron Jan. 18, 2022

Jan. 18, 2022

Per sorridere ogni tanto, ma in fondo... anche questa è cultura e società nella condizione digitale! Buona settimana dl https://www.greenme.it/tecno/gatti-provocano-problemi-connessione-satellita… _________________________ don Luca Peyron Direttore Ufficio per la Pastorale Universitaria Arcidiocesi di Torino www.universitari.to.it via XX settembre 83, Torino tel. 011 5156239

1 0

"German police under fire for misuse of COVID contact tracing app"
by J.C. DE MARTIN Jan. 18, 2022

Jan. 18, 2022

*German police under fire for misuse of COVID contact tracing app** */ //German police used a contact tracing app to track down witnesses in a local crime case. The scandal has data protection advocates up in arms, with politicians warning that abuse of the app could undermine public trust./ [...] continua qui: https://www.dw.com/en/german-police-under-fire-for-misuse-of-covid-contact-…

1 0

Enforcing the pyramid of Open Source | daniel.haxx.se
by Alberto Cammozzo Jan. 18, 2022

Jan. 18, 2022

<https://daniel.haxx.se/blog/2022/01/17/enforcing-the-pyramid-of-open-source/> The well-known log4j security vulnerability of December 2021 triggered a lot of renewed discussions around software supply chain security, and sometimes it has also been said to be an Open Source related issue. This was not the first software component to have a serious security flaw, and it will not be the last. What can we do about it? This is the 10,000 dollar question that is really hard to answer. In this post I hope to help putting some light on to why it is such a hard problem. This comes from my view as an Open Source author and contributor since almost three decades now. In this post I’m going to talk about security as in how we make our products have less bugs in the code we write and land on purpose. There is also a lot to be said about infrastructure problems such as consumers not verifying dependencies so that when malicious actors purposely destroy a component, users of that don’t notice the problem or supply chain security issues that risk letting bad actors insert malicious code into components. But those are not covered in this blog post! The OSS Pyramid I think we can view the world of software and open source as a pyramid, and I made this drawing to illustrate. The OSS pyramid, click for bigger version. Inside the pyramid there is a hierarchy where things using software are build on top of others, in layers. The higher up you go, the more you stand on the shoulders of open source components below you. At the very bottom of the pyramid are the foundational components. Operating systems and libraries. The stuff virtually everything runs or depends upon. The components you really don’t want to have serious security vulnerabilities. Going upwards In the left green arrow, I describe the trend if you look at software when climbing upwards the pyramid. Makes more direct money Shorter lifetimes, faster iterations Higher level languages Shrinking share of Open Source More end user facing At the top, there are a lot of things that are not Open Source. Proprietary shiny fronts with Open Source machines in the basement. Going downwards In the red arrow on the right, I describe the trend if you look at software when going downwards in the pyramid. Maintenance is more important than new fluff Longer lifetimes Bugs have larger impact and take longer to get deployed Lower level languages At the bottom, almost everything is Open Source. Each component in the bottom has countless users depending on them. It is in the bottom of the pyramid each serious bug has a risk of impacting the world in really vast and earth-shattering ways. That is where tightening things up may have the most positive outcomes. (Even if avoiding problems is mostly invisible unsexy work.) Zoom out to see the greater picture We can argue about specific details and placements within the pyramid, but I think largely people can agree with the greater picture. Skyscrapers using free bricks A little quote from my friend Stefan Eissing: As a manufacturer of skyscrapers, we decided to use the free bricks made available and then maybe something bad happened with them. Where is the problem in this scenario? Market economy drives “good enough” As long as it is possible to earn a lot of money without paying much for the “communal foundation” you stand on, there is very little incentive to invest in or pay for maintenance of something – that also incidentally benefits your competitors. As long as you make (a lot of) money, it is fine if it is “good enough”. Good enough software components will continue to have the occasional slip-ups (= horrible security flaws) and as long as those mistakes don’t truly hurt the moneymakers in this scenario, this world picture remains hard to change. However, if those flaws would have a notable negative impact on the mountains of cash in the vaults, then something could change. It would of course require something extraordinary for that to happen. What can bottom-dwellers do Our job, as makers of bricks in the very bottom of the pyramid, is to remind the top brass of the importance of a solid foundation. Our work is to convince a large enough share of software users higher up the stack that are relying on our functionality, that they are better off and can sleep better at night if they buy support and let us help them not fall into any hidden pitfalls going forward. Even if this also in fact indirectly helps their competitors who might rely on the very same components. Having support will at least put them in a better position than the ones who don’t have it, if something bad happens. Perhaps even make them avoid badness completely. Paying for maintenance of your dependencies help reduce the risk for future alarm calls far too early on a weekend morning. This convincing part is often much easier said than done. It is only human to not anticipate the problem ahead of time and rather react after the fact when the problem already occurred. “We have used this free product for years without problems, why would we pay for it now?” Software projects with sufficient funding to have engineer time spent on the code should be able to at least make serious software glitches rare. Remember that even the world’s most valuable company managed to ship the most ridiculous security flaw. Security is hard. (How we work to make sure curl is safe.) Components in higher levels can help All producers of code should make sure dependencies of theirs are of high quality. High quality here, does not only mean that the code as of right now is working, but they should also make sure that the dependencies are run in ways that are likely to continue to produce good output. This may require that you help out. Add resources. Provide funding. Run infrastructure. Whatever those projects may need to improve – if anything. The smallest are better off with helping hands I participate in a few small open source projects outside of curl. Small projects that produce libraries that are used widely. Not as widely as curl perhaps, but still millions and millions of users. Pyramid-bottom projects providing infrastructure for free for the moneymakers in the top. (I’m not naming them here because it doesn’t matter exactly which ones it is. As a reader I’m sure you know of several of this kind of projects.) This kind of projects don’t have anyone working on the project full-time and everyone participates out of personal interest. All-volunteer projects. Imagine that a company decides they want to help avoiding “the next log4j flaw” in such a project. How would that be done? In the slightly larger projects there might be a company involved to pay for support or an individual working on the project that you can hire or contract to do work. (In this aspect, curl would for example count as a “slightly larger” kind.) In these volunteers-only projects, all the main contributors work somewhere (else) and there is no established project related entity to throw money at to fix issues. In these projects, it is not necessarily easy for a contributor to take on a side project for a month or two – because they are employed to do something else during the days. Day-jobs have a habit of making it difficult to take a few weeks or months off for a side project. Helping hands would, eh… help Even the smallest projects tend to appreciate a good bug-fix and getting things from the TODO list worked on and landed. It also doesn’t add too much work load or requirements on the volunteers involved and it doesn’t introduce any money-problems (who would receive it, taxation, reporting, etc). For projects without any existing way setup or available method to pay for support or contract work, providing man power is for sure a good alternative to help out. In many cases the very best way. This of course then also moves the this is difficult part to the company that wants the improvement done (the user of it), as then they need to find that engineer with the correct skills and pay them for the allotted time for the job etc. The entity providing such helping hands to smaller projects could of course also be an organization or something dedicated for this, that is sponsored/funded by several companies. A general caution though: this creates the weird situation where the people running and maintaining the projects are still unpaid volunteers but people who show up contributing are getting paid to do it. It causes unbalances and might be cause for friction. Be aware. This needs to be done in close cooperating with the maintainers and existing contributors in these projects. Not the mythical man month Someone might object and ask what about this notion that adding manpower to a late software project makes it later? Sure, that’s often entirely correct for a project that already is staffed properly and has manpower to do its job. It is not valid for understaffed projects that most of all lack manpower. Grants are hard for small projects Doing grants is a popular (and easy from the giver’s perspective) way for some companies and organizations who want to help out. But for these all-volunteer projects, applying for grants and doing occasional short-term jobs is onerous and complicated. Again, the contributors work full-time somewhere, and landing and working short term on a project for a grant is then a very complicated thing to mix into your life. (And many employers actively would forbid employees to do it.) Should you be able to take time off your job, applying for grants is hard and time consuming work and you might not even get the grant. Estimating time and amount of work to complete the job is super hard. How much do you apply for and how long will it take? Some grant-givers even assume that you also will contribute so to speak, so the amount of money paid by the grant will not even cover your full-time wage. You are then, in effect, expected to improve the project by paying parts of the job yourself. I’m not saying this is always bad. If you are young, a student or early in your career that might still be perfect. If you are a family provider with a big mortgage, maybe less so. [...]

1 0

[REMINDER] WEBINAR GI-STS con F. Giannotti e G. Tamburrini: Intelligenza artificiale e sistemi d’arma autonomi - coordina G. Colombetti
by Diego.Latella Jan. 18, 2022

Jan. 18, 2022

[Con preghiera di diffusione] =========================== ANNUNCIO WEBINAR =========================== Intelligenza artificiale e sistemi d'arma autonomi Seminario on-line aperto al pubblico MERCOLEDÌ 19 Gennaio 2022 alle 16:00 (Official language: Italian) Coordina Giuliano Colombetti (CNR-IBF. GI-STS) 16:00 Saluti Istituzionali Antonello Provenzale (Presidente - Area della Ricerca di Pisa del CNR) 16:15 Stato dell'arte in Intelligenza Artificiale. Potenzialità e limiti delle tecnologie dell'Intelligenza Artificiale Fosca Giannotti (Scuola Normale Superiore, Pisa; CNR/ISTI) 16:45 La militarizzazione dell'Intelligenza Artificiale, le armi autonome e la pace internazionale Guglielmo Tamburrini (Università degli Studi di Napoli "Federico II") 17:15 Discussione Il webinar è organizzato dal Gruppo Interdisciplinare su Scienza, Tecnologia e Società (GI-STS) dell'Area della Ricerca di Pisa del CNR In cooperazione con Areaperta - Area della Ricerca CNR di Pisa Caffè della Scienza "N. Badaloni" - Livorno Centro Interdisciplinare Scienze per La Pace dell'Università di Pisa Istituto di Biofisica del CNR Istituto di Fisiologia Clinica del CNR Istituto di Informatica e Telematica del CNR Istituto di Scienza e Tecnologie dell'Informazione ``A. Faedo'' del CNR La Nuova Limonaia Laboratorio Informatica e Società del CINI Pugwash Conferences on Science and World Affairs Unione degli Scienziati Per Il Disarmo e con il patrocinio della Rete Università per la Pace Per ulteriori informazioni---incluso il link per la partecipazione all'evento---si rimanda alla pagina "Events" (http://gists.pi.cnr.it/events.html )del sito web del Gruppo Interdisciplinare su Scienza, Tecnologia e Società (GI-STS) dell'Area della Ricerca di Pisa del CNR,(http://gists.pi.cnr.it ). =========================== For more information---including the link for participation---please refer to the "Events" page (http://gists.pi.cnr.it/events.html ) in the web site of the Gruppo Interdisciplinare su Scienza, Tecnologia e Società (GI-STS) dell'Area della Ricerca di Pisa del CNR (http://gists.pi.cnr.it ). =========================== D. Latella -- Dott. Diego Latella - Senior Researcher CNR/ISTI, Via Moruzzi 1, 56124 Pisa, Italy (http:www.isti.cnr.it [1]) FM&&T Lab. (http://fmt.isti.cnr.it) CNR/GI-STS (http://gists.pi.cnr.it) https://www.isti.cnr.it/People/D.Latella - ph: +390506212982, fax: +390506212040 =================== I don't quite know whether it is especially computer science or its subdiscipline Artificial Intelligence that has such an enormous affection for euphemism. We speak so spectacularly and so readily of computer systems that understand, that see, decide, make judgments, and so on, without ourselves recognizing our own superficiality and immeasurable naivete with respect to these concepts. And, in the process of so speaking, we anesthetise our ability to evaluate the quality of our work and, what is more important, to identify and become conscious of its end use. […] One can't escape this state without asking, again and again: "What do I actually do? What is the final application and use of the products of my work?" and ultimately, "am I content or ashamed to have contributed to this use?" -- Prof. Joseph Weizenbaum ["Not without us", ACM SIGCAS 16(2-3) 2--7 - Aug. 1986] Links: ------ [1] http://www.isti.cnr.it

1 0

Ancora su Google Analytics
by Roberto Resoli Jan. 17, 2022

Jan. 17, 2022

... segnalo l'ottimo articolo di Bruno Saetta su Valigia Blu: https://www.valigiablu.it/google-analytics-illegale-europa/ rob

1 0

Re: [nexa] Wired: "Una mappa delle telecamere cinesi in uffici e luoghi pubblici d'Italia"
by Claudia Giulia Jan. 17, 2022

Jan. 17, 2022

Il lavoro aperto ad aprile da IlFogliomerita assolutamente attenzione. È certamente un bene che se ne dia seguito (rinfresco l’articolo iniziale dell’inchiesta x chi nn lo avesse letto allora) https://www.ilfoglio.it/esteri/2021/04/09/news/conte-e-la-videosorveglianza… Conte e la videosorveglianza cinese a Palazzo Chigi Che ci fanno le telecamere di una controversa società cinese all'ingresso del palazzo del governo? Il 30 settembre 2020, cioè in pieno governo Conte II, la Dahua Technology, la branca italiana di una delle più grandi società cinese di prodotti tech e di videosorveglianza, annuncia con un comunicato stampa di aver iniziato la videosorveglianza di un pezzo molto importante del nostro sistema democratico: Palazzo Chigi. Con tanto di titolo “La sicurezza Governa”, Dahua fa sapere https://www.dahuasecurity.com/it/newsEvents/pressRelease/4303 di aver messo a disposizione “delle alte cariche pubbliche e dei lavoratori di Palazzo Chigi, e delle altre strutture facenti capo alla Pcm e al Segretariato generale” ben diciannove termoscanner, che rilevano la temperatura di “ministri della Repubblica, funzionari, personale e visitatori in modo rapido, preciso e senza alcun contatto Non solo: questi terminali distribuiti in tutti gli ingressi del nostro palazzo di governo offrono anche “la funzione di riconoscimento facciale – con la possibilità di registrare i volti in liste Vip”. In pratica, chi entra a Palazzo Chigi deve guardare dentro a uno schermo che riconosce il suo volto – e rileva anche la temperatura. La Zhejiang Dahua Technology, società di Hangzhou quotata alla Borsa di Shenzhen, è una specie di colosso della videosorveglianza. Ha già da tempo diversi contratti con istituzioni ed enti italiani: dai Musei vaticani al Festival del cinema di Venezia, per citare i due menzionati anche dal loro comunicato stampa. Ma ci sono anche diversi supermercati e luoghi pubblici sorvegliati grazie alla sua tecnologia. Il salto di qualità in Italia è stato fatto nel 2018, quando è stata creata la filiale italiana Dahua Technology Italy con a capo il manager Pasquale Totaro. Il problema è che la società già da tempo è bandita negli Stati Uniti ed è sotto osservazione in numerosi paesi europei per via di diverse vicende. Tutto ha inizio nel 2017, quando una società di cybersecurity trova una backdoor nelle telecamere Dahua. La backdoor mandava dati a un “ignoto indirizzo IP in Cina”. Questo dimostrava non solo la vulnerabilità delle telecamere ma anche un uso piuttosto ambiguo, se non inquietante. L'anno dopo il governo americano ha proibito l'uso delle telecamere Dahua nei palazzi di governo. L'indagine sull'azienda è continuata. Nell'ottobre del 2019 la Dahua è stata messa nella lista nera americana per il suo ruolo nella videosorveglianza dello Xinjiang e delle minoranze etniche nella regione. Ci sono stati vari scandali successivi, per esempio quando Amazon ha acquistato quelle telecamere e quei termoscanner per i suoi stabilimenti. Più o meno nello stesso periodo in cui si installavano qui termoscanner a Palazzo Chigi, una società di cybersicurezza scopriva che nel software delle telecamere di Dahua c'era effettivamente un codice che serve a riconoscere automaticamente gli uiguri. Il codice poi è stato cancellato. Un'inchiesta pubblicata dal Los Angeles Times a inizio febbraio riportava che "il software di riconoscimento facciale sviluppato dalla cinese Dahua, uno dei maggiori produttori mondiali di tecnologia di videosorveglianza, rileva la razza degli individui ripresi dalla telecamera e avvisa la polizia quando identifica gli uiguri Alla luce di quanto emerso dalle ricerche sembra quantomeno azzardato che Palazzo Chigi, con Giuseppe Conte, abbia deciso di affidarsi alla Dahua per controllare il palazzo più importante che c'è. Le telecamere e i termoscanner di Palazzo Chigi sono stati l'oggetto di una interrogazione parlamentare proposta dal senatore della Lega Simone Bossi, presentata l'8 aprile, di cui si aspetta adesso la risposta scritta del governo. Interpellato dal Foglio, l'ufficio stampa di Palazzo Chigi non ha ancora risposto formalmente alla richiesta di informazioni sul contratto stipulato con Dahua. Inviato da iPhone > Il giorno 17 gen 2022, alle ore 11:50 AM, J.C. DE MARTIN <juancarlos.demartin(a)polito.it> ha scritto:

3 3