-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Reproducible builds #326
Comments
Hey @xrviv, Thanks for reviewing our project! We will create a BUILD.md files with build instructions and keep you posted. |
Thanks for your interest. This is an important issue for us. We will make sure to prioritize it before we move out of Beta. |
I was able to build 0.3.2, with this Dockerfile:Proof of Build https://asciinema.org/a/677360
The build had the following diffs:
|
Thank you for creating that Dockerfile. I will add it to the repo and as we make progress I will update it. So AndroidManifest.xml is the first differing file; which I am not sure why. I took a look at the existing AndroidManifest.xml file and there doesnt seem to be anything specific to the system building the project that is being added. Any ideas on what this could be about? Regarding the libraries we are using; we had a bounty which a dev is working on and he found that if you use a different version of cargo as what we have used, the resulting binary differ. I am building our android apks on a system running I assume we would also need a way of stripping the signature data from the binary. I unfortunately am swamped with work at the moment to dig into the details but you've given me a great starting point. Thanks again! |
Hello @i5hi, thank you for the attentive and quick reply! I apologize for the late reply, as we've been handling several issues at the moment. I actually would not know how this came to differ unless we ran a diffoscope on it. We can derive clues from various providers though, For Bitkey's AndroidManifest.xml: They also mentioned something about the resources.arsc mismatch here:
As for the reasoning for the other files, they're WiP |
Hello @xrviv, I've tried your Dockerfile without success, here are the changes I did :
I have one remaining issue, the If you want to take a look, you can check the branch I wonder how your environment let you use flutter commands as a root user, while flutter throw an error if you attempt it. |
removing
solved the JAVA_HOME error |
Hi apologies, currently have my plate filled. Will get to this as soon as I can. |
Don't bother, I reworked the Dockerfile and created PR #411 which seems to work for the Android apk. We will merge it once more people have tested it. |
Okay, I'm free now. Will proceed with this. Documenting my current attempts:
Diffs:
2025-01-09
|
Hello team bullbitcoin! 😃
I'm Danny, and I work with WalletScrutiny.com.
We have reviewed over 6500+ Bitcoin Android apps and firmware.
You can read about our methodology here.
We'd love to work with your team on verifying the reproducibility of your app, with appID com.bullbitcoin.mobile
To get there, may we suggest the following:
Hoping to hear from you again soon!
Kind Regards,
Danny
The text was updated successfully, but these errors were encountered: