News for hackers. Stuff that matters.
Re:MEGAChat now includes end-to-end encryption by alkonaut on Saturday January 23, 2016 @08:25AM (#10958301)
Aren't builds typically reproducible? What makes builds non-reproducible? I know the Debian folks are very enthusiastic about reproducible builds, and for a huge system I can see that things can vary -- but what tends to be varying in the case of individual components? If I build a library from the same revision of a source tree I expect the exact bits to come out, if the same compiler version was used? When does it not?

Is it a problem with C/C++ in particular, where toolchains are complex? Or would non-reproducible also be a problem e.g for a Java library?

Googling reproducible builds mainly gets you Debian info, not a general description of the issue

Re:MEGAChat now includes end-to-end encryption by wila on Saturday January 23, 2016 @09:09AM (#10958431)
No builds are not easy to reproduce bit by bit as there are much more factors as the actual source.

For example:

  - compiler version used
  - date / timestamps at the time of compile
  - build id's
A good article on this can be found here: https://blogs.kde.org/2013/06/19/really-source-code-software
Re:MEGAChat now includes end-to-end encryption by sandworm101 on Saturday January 23, 2016 @08:30AM (#10958318)
A build is not reproducible where it incorporates both open and closed code. A company may "open source" some important stuff (encryption algorithms) but keep enough code closed that the final build cannot be duplicated from the "open" code. It is therefore difficult to judge whether the open code has actually been adopted properly, or whether any closed code hasn't created new bugs.