You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I didn't check if that matches the binary that end users download from TestFlight, or whether Apple injects some signature magic.
Because the binary is signed by me, it's not possible for someone else to reproduce the exact same binary. However perhaps it's possible to generate a binary, strip the signature data and then perform the comparison.
The v0.0.1 release uses a temporary branch of upstream libwally-core and libwally-swift. These commits won't exist anymore after a while, at least Github won't serve them. This is a temporary issue; by the time this app is ready for the App Store I plan to use only tagged releases for dependencies; those should remain available on Github.
The text was updated successfully, but these errors were encountered:
I'd like to be able to prove that the TestFlight and App Store binaries are actually derived from this source code.
As a first step I've uploaded the binary to the release tag: https://github.com/Sjors/nthkey-ios/releases/tag/v0.0.1
I didn't check if that matches the binary that end users download from TestFlight, or whether Apple injects some signature magic.
Because the binary is signed by me, it's not possible for someone else to reproduce the exact same binary. However perhaps it's possible to generate a binary, strip the signature data and then perform the comparison.
The v0.0.1 release uses a temporary branch of upstream libwally-core and libwally-swift. These commits won't exist anymore after a while, at least Github won't serve them. This is a temporary issue; by the time this app is ready for the App Store I plan to use only tagged releases for dependencies; those should remain available on Github.
The text was updated successfully, but these errors were encountered: