News for hackers. Stuff that matters.
Re:Caddy 0.10.10 Released Along with New Pricing Structure by vog on Monday October 09, 2017 @09:40AM (#15433662)
Assuming that one day there will reproducible builds, how will they ever tell apart the legal use from the illegal use of the (bit-for-bit identical) binary?
Re:Caddy 0.10.10 Released Along with New Pricing Structure by dln_eintr on Monday October 09, 2017 @10:07AM (#15433866)
By ensuring the proprietary builds are NOT the same.
Re:Caddy 0.10.10 Released Along with New Pricing Structure by vog on Tuesday October 10, 2017 @03:46AM (#15440062)
Ouch! Then we have the choice between a community-provided binary that is cross-validated by multiple build servers of multiple distros, and a vendor-provided binary which is deliberately different and has legal restrictions. Which one would we consider to be more trustworthy?
Re:Caddy 0.10.10 Released Along with New Pricing Structure by giancarlostoro on Monday October 09, 2017 @09:43AM (#15433677)
Code signing maybe? Not entirely sure otherwise.
Re:Caddy 0.10.10 Released Along with New Pricing Structure by vog on Monday October 09, 2017 @09:46AM (#15433701)
How would that work? The signature of the official binary would be also valid for the "other" binaries.
Re:Caddy 0.10.10 Released Along with New Pricing Structure by giancarlostoro on Monday October 09, 2017 @09:53AM (#15433772)
Code signing involves attaching a certificate from the author which nobody else can reproduce unless a CA is compromised. Think SSL certs to some degree. This only proves identity of person signing it. This would differentiate the binary enough I would think.
Re:Caddy 0.10.10 Released Along with New Pricing Structure by StavrosK on Monday October 09, 2017 @10:44AM (#15434189)
If the rest of the binary is bit-for-bit identical, you can just tack the signature on to the OSS binary.