> I think it's the same reason PGP never caught on. The learning curve is just too steep. This is what I always emphasise: usability first. If a solution is se

> I think it's the same reason PGP never caught on. The learning curve is just too steep. This is what I always emphasise: usability first. If a solution is secure on paper, but confusing to use, then it's not secure - the user can get confused and do the wrong thing. Defaults matter. > What it needs is something like a torrent client that 1) doesn't let you download unless you supply the expected SHA first, and perhaps 2) that it verifies that the hash came from the signed webpage where you got the torrent link. This is already a solved problem. Just provide a magnet link. You already have to trust the website to provide the checksum, so why not trust the link? As for packages, Debian experimented with a BitTorrent transport for apt a long while ago, but I suppose it didn't catch on. Perhaps this was before BitTorrent had HTTP fallback? Either way, this would be an interesting avenue for research.