One quick comment from glancing: use --frozen in your invocation of
cargo to prohibit network access and sort of "test" that the
dependencies were vendored correctly. I was pretty satisfied when
looking at trust-rust before. Obviously the non-determinism sucks, but
given how much the rust compiler
Sorry to hear you were sick. Vitamin D FTW.
On Mon, Jan 8, 2018 at 10:40 AM Sean Bowe wrote:
> I've been quite busy with holidays, work and being sick. :( I'd like
> to get around to writing some instructions for the ceremony that
> encourage people to
It looks like the result is pretty far from deterministic. In fact, I see
20,000+ lines of difference in diffoscope.
So it looks like each participant will have to build their own toolchain.
On Tue, Dec 5, 2017 at 4:44 PM Sean Bowe wrote:
> That would be nice!
> What other
That would be nice!
What other obstacles are there for fully deterministic builds? It
seems like it would be a good idea to toss a few features in (like
that one) and make some kind of "release" binaries for people to use
which have been scrutinized and built in this reproducible way.
Verification passed (in fact, new_challenge was identical).
BTW, would be nice if `compute` had a flag to only take entropy from STDIN,
so that we can check for any differences in the response.
On Tue, Dec 5, 2017 at 12:48 PM Devrandom wrote:
> Thank you. Will do
Thank you. Will do the verification shortly.
Also, I've updated the instructions in
use the cargo built by mrustc. This required vendoring of the dependencies.
On Tue, Dec 5, 2017 at 11:24 AM Sean Bowe
Excellent work! :)
new, compute, verify_transform is a good demonstration. I would
verify_transform with a binary compiled with the normal Rust compiler
On Tue, Dec 5, 2017 at 11:59 AM, Devrandom wrote:
> Hi all,
> I was able to build rustc