[tor-talk] Deterministic Builds - was: Bridge Communities?

[Gregory Disney]

So the PKI method that bitcoin uses is a sha256 encoding + sha1 decoding.
The OR provides a PKI key (sha256) with hidden services, so the solution
may be switches that run openCL or CUDA to authenticate the key to the node
(parallel computing is still the fastest way to compute) . If the node key
does not match the node could be isolated from the network.


On Sun, Apr 14, 2013 at 12:46 AM, Gregory Maxwell <gmaxwell at gmail.com>wrote:

> On Sat, Apr 13, 2013 at 8:44 PM, adrelanos <adrelanos at riseup.net> wrote:
> > I assume you're the Gregory Disney who is also one builder of those
> > Bitcoin deterministic builds? Since you're involved in Tor as well, I
> > seems to me you could be a great help by providing some information
> > about the Bitcoin build process.
>
> There is no Gregory Disney involved with Bitcoin as far as I know.
>
> > Where are the instructions how I (or someone else) not involved in
> > Bitcoin development can produce bit identical builds of Bitcoin to match
> > the hash sums which are also distribiuted on sourceforge? If there are
> > none, could you provide them please?
>
> They're included with the source:
>
> https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.txt
> and
> https://github.com/bitcoin/bitcoin/tree/master/contrib/gitian-descriptors
>
> > Can their system be applied for Tor as well or are there any differences?
>
> Yes. It may take a little jiggling to get the builds to actually be
> deterministic for any particular package, but they should be
> applicable to anything.
> _______________________________________________
> tor-talk mailing list
> tor-talk at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
>