clojars

http://clojars.org discussion and “support”, see http://status.clojars.org for status.
micha 2016-09-11T22:26:13.000007Z

seems to me that the fundamental problem is that our customers trust us with their data, and we implicitly trust the dependencies we use not to do anything bad

micha 2016-09-11T22:27:48.000008Z

maybe something like IPFS really is all we need

micha 2016-09-11T22:28:06.000009Z

and not even sign jars at all

danielcompton 2016-09-11T22:39:03.000010Z

There’s a few trust issues I think: 1. How do we verify that JARs we download from an untrusted source like Clojars haven’t been tampered with? 2. How do we verify that dependencies don’t do anything bad? 2. Seems to come down to auditing JAR updates before updating deps, I’m not sure how else you can verify that a dependency isn’t doing anything bad. 1. seems a little more tractable, by defining a mechanism for trusting a developer and therefore trusting their releases

micha 2016-09-11T22:54:49.000014Z

you could go the other way i suppose

micha 2016-09-11T22:55:07.000015Z

and just care about whether you have used those jars before in the past

micha 2016-09-11T22:55:28.000016Z

and you don't do any verification of gpg signatures or anything

micha 2016-09-11T22:56:08.000017Z

maybe IPFS provides such a mechanism

danielcompton 2016-09-11T23:41:48.000018Z

something like https://github.com/WhisperSystems/gradle-witness ?