this post was submitted on 06 Feb 2024
1052 points (99.0% liked)

Microblog Memes

5793 readers
2746 users here now

A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.

Created as an evolution of White People Twitter and other tweet-capture subreddits.

Rules:

  1. Please put at least one word relevant to the post in the post title.
  2. Be nice.
  3. No advertising, brand promotion or guerilla marketing.
  4. Posters are encouraged to link to the toot or tweet etc in the description of posts.

Related communities:

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 9 months ago

Plus, if the app supports reproducible build, fdorid will just delivers the app to you via the developer's signature. So it is just a additional verification without adding any trusted party. App signing section https://f-droid.org/docs/Security_Model/

fdroid also manually inspect the source to make sure nothing funky is going on. But of course that cannot be absolutely through, because the time and workforce constraint.

Finally, fdroid has updated to index v2 which improves the security of index v1, specifically:

  • As of index-v2, files from the repo are verified based on SHA-256, including icons, screenshots, etc.
  • index-v2 uses any algorithm supported by apksigner and android-23 and newer, and relies on OpenJDK’s and Google’s maintenance of the currently valid signing algorithms. When index-v2 was launched, the signature algorithm in use was SHA256withRSA and the digest algorithm was SHA-256. index-v1 is signed by SHA1withRSA. As of this writing, SHA1 are still considered strong against second pre-image attacks, which is what is relevant for index JARs.

https://f-droid.org/docs/Security_Model/