Software distribution: new points of failure In a censored world

by Alexander E. Patrakov
At: FOSDEM 2020
video.fosdem.o...
There is a multitude of software or code ecosystems: Linux distribution packages, language-specific (e.g. Python or node.js) modules, third-party desktop themes, git repositories, and recently also Flatpak and Snap. Users thus obtain software and code mainly from the network. This talk explores what can go wrong in such code delivery mechanisms, and what actually went wrong when a new threat has materialized: networks in certain countries started to be unreliable "thanks" to the governments (classical example: isitblockedinr... == true). And what technical steps can be done in order for the said ecosystems to survive when censorship and overblocking spreads over the globe even more. The focus will be on how mirror networks and CDNs operate (and what's the difference and why it matters), illustrated by examples of Debian mirrors and NPM. Both availability and integrity concerns regarding code delivery will be discussed.
Room: K.3.201
Scheduled start: 2020-02-02 10:30:00

[@23poiuz]

very interesting talk. also, great talk structure and examples. thanks for sharing your insights! one Q: for robust file hosting and distribution with no single point of failure, that is neither technical nor administrative, how would you compare CDNs and classis mirror (eg Debian) to Blockchain, eg Ethereum IPFS and ENS? as in: the latter is also censorship (governments and corporate) resistant (unlike CDNs). because it is decentralized (no SPOV administratively), not only distributed (no SPOV technically). what do you think?