Hey #Google, cool you're adding a bit of #BinaryTransparency. Unfortunately, it doesn't mean much without #FreeSoftware #OpenSource and #ReproducibleBuilds. When can we expect you to adopt those practices?

https://blog.google/security/bringing-binary-transparency-to-the-android-ecosystem/

For the record #FDroid has offered binary transparency since 2017 https://gitlab.com/fdroid/fdroidserver/-/merge_requests/226

And we even offer binary transparency for your #Gradle and #AndroidSDK binaries
https://f-droid.org/2021/02/05/apis-for-all-the-things.html#binary-transparency-logs

How about expanding your logging to all your binaries?

Evolving Verifiable Trust: Bringing Binary Transparency to the Android Ecosystem

Google is expanding Binary Transparency on Android to help you verify that your Google apps are genuine and authorized for release.

Google

Google Bolsters Android App Security with Public Verification Ledger

Google is stepping up its game to keep your Android apps safe with a new public verification ledger that ensures the Google apps on your device are genuine and exactly as intended. This move builds on its Pixel Binary Transparency feature, now expanding it to all Android production apps.

https://osintsights.com/google-bolsters-android-app-security-with-public-verification-ledger?utm_source=mastodon&utm_medium=social

#AndroidAppSecurity #PixelBinaryTransparency #BinaryTransparency #Google #SupplyChain

Google Bolsters Android App Security with Public Verification Ledger

Learn how Google's Public Verification Ledger enhances Android app security with verifiable mechanisms, ensuring Google apps are authentic and trustworthy - read more now.

OSINTSights
Add new hash 44e978970ac5a511d4ba83364a76d81041ccd71129e57cdd8384cd460ff9bd35 for theName (theVersion) for theArchitecture #debian #binarytransparency
Add new hash 2b4247be96a1911c3a6278cb888b3742497a8901319118221f041bb1fc4c2066 for intel-microcode (3.20250812.0ubuntu0.22.04.1) for amd64 #debian #binarytransparency
Add new hash aa833951a9b8bfa004fa814b990961a8c515f03ae8bd93349b8e00a0c975feb3 for gitlab-runner (18.2.0-1) for amd64 #debian #binarytransparency
Add new hash 584d2b03e41e6bc4031330263a9305fe76646be0490348b4e3c73f35c9bffa4a for python3-systemd (235-1b2) for amd64 #debian #binarytransparency
Da endlich mal Zeit ist zwischen den Jahren, gibt es updates zu @bintra #binarytransparency zu den vielen Verbesserungen und Tickets im #NodeJs die sich so aufstauen. Einfach mal für sich selbst was programmieren ist pure Entspannung im Vergleich zu Kundenprojekten. #ITnerd

#WhatsApp implementing #KeyTransparency is pretty nice, and definitely an excellent step in the right direction against shadow accounts and the service provider trust problem. However, without the client being #OpenSource, it is not that meaningful. Yes, of course somebody could implement an independent monitor for the transparency log to check keys registered for an identity, but what percentage of the user base will actually do that when the only realistic way to use the service is to rely on the #proprietary client, which can still be used to maliciously target (groups of) users to break #E2EE?

Secure messenger clients should both use identity security protections like #KeyTransparency and have a *default* implementation that is #OpenSource and, ideally, be distributed with #BinaryTransparency and verified through #ReproducibleBuilds. Oh, and allow other identifiers than just phone numbers (still looking at you, @signalapp - which is otherwise ticking a lot of the right checkboxes).

Add new hash 223b4c3eafd3edf44d9b8153f834c24aface03ea7585db4ccb0292e582fd6345 for gitlab-ce (15.10.0-ce.0) for amd64 #debian #binarytransparency
Add new hash 91c1ae6c5a02d25f901917a1f944b07ab9d7bd8033e3d10a8e714de4c3f5eef4 for libcurl3-gnutls (7.68.0-1ubuntu2.16) for amd64 #debian #binarytransparency