Sandboxes have often been represented as a security feature, but it seems there are always ways out, e.g. there are always jailbreaks available for iOS. Sandboxes still make sense for restricting non-malware apps from accessing private info. For security, its more important to avoid targeted exploits, e.g. reducing identifiability, to force the use 0days into broader targets, which is then more likely to burn that 0day. Users of 0day exploits are rarely willing to burn one to target one person
@rogermcnamee on top of that, each affected Facebook user has been allocated about $2.25. Yup, two dollars and change. A classic example of the problems of class action lawsuits. The firm gets to cash out with $181 million, but the actual settlement for the affected parties is not worth the time to do the paperwork.
@filippo Cloudflare will tell you about it: https://blog.cloudflare.com/icloud-private-relay/ It is based on the #IETF #MASQUE standard for proxying over UDP/QUIC.
@mozilla here's the link, I think https://blog.mozilla.org/en/mozilla/mozilla-launch-fediverse-instance-social-media-alternative/
"A passionate and bipartisan legislative effort to rein in the country’s largest technology companies collapsed this week, the victim of an epic lobbying campaign by Amazon, Apple, Google and Meta"
https://www.bloomberg.com/news/articles/2022-12-20/big-tech-divided-and-conquered-to-block-key-bipartisan-bills
@somegirlprivacy@mstdn.asprivacy.com I'm not saying it should not be updated, we welcome contributions there. I would love to see F-Droid working well everywhere, I can't do it all, and the dev team for #FDroid is small. We can make it work well for a lot more people if there are more contributors.
Tech giants are now spending hundreds of millions to systematically shape policy across the world, including donations and funding to policymakers, civil society orgs, media orgs and academia.
A decade ago, this may not have been clear to everyone. Now it really should be.
We welcome help for bumping the #targetSdkVersionfor #FDroid and have mapped out what needs to be done:
* https://gitlab.com/fdroid/fdroidclient/-/issues/2037
* https://gitlab.com/fdroid/fdroidclient/-/issues/1440
Given our limited resources, I have chosen to focus my time on concrete improvements for #FreeSoftware. The only thing I'm opposed to in all this is removing functionality in order to bump targetSdkVersion. Google's recent changes there have removed functionality that many rely on.
When #FDroid is built into a #FreeSoftware ROM, like #CalyxOS, #lineageos for #microg, etc there is no popup warning with fdroidclient. That comes from "Play Protect", which is #Google proprietary software that flags things based on automated rules, it does not point to real world security concerns for apps like #FDroid. I have nothing against the #targetSdkVersion sandbox, I just think it is important to note what it is good for, and what it cannot do well 2/2
As lead maintainer of the official #FDroid client, I hear a lot of criticism that #targetSdkVersion is still at 25. fdroidclient is #FreeSoftware, publicly audited, with #ReproducibleBuilds, written in memory safe languages, with a proven record of respecting #privacy and delivering #security. The source and binaries also receive human and machine review. #targetSdkVersion is designed around untrusted proprietary software with non-memory safe code where the binary only gets machine review. 1/2
@guardianproject @lauren And of course #ReproducibleBuilds is a key part of this whole picture, allowing anyone to confirm that the exact binary that is running on their device matches the source code as published and audited.
@lauren #FreeSoftware and audits are the only way to provide trustworthy #E2EE. Apps like #DeltaChat, #Matrix with #Olm/#Megolm, #XMPP with #OMEMO, #Signal, #Threema provide trustworthy E2EE because they are built on open standards, free software, and have been publicly audited. That is the standard all services should be held to in order to be labeled trustworthy. Anything else just means you have to trust the service operator. 2/2
@lauren It is important to describe the limitations here. E2EE here would be useful when emailing with third parties. Since #Gmail is proprietary software, users just have to trust #Google to do the right thing. Technically, it is easy to build E2EE where the service can get the private keys and decrypt as they like. Given participation in #PRISM etc, proprietary Gmail cannot provide trustworthy E2EE, especially considering most emails stay within Gmail 1/2
People rocking up on this platform and expecting it to be as rich and diverse and mature as their carefully nurtured Twitter feed, fine-tuned over a decade to reflect their interests and values, maybe give it a few weeks of actually investing in finding the accounts that interest you before writing the whole thing off as a howling wasteland.
Why curation and #decentralization is better than millions of #apps.
Happy to have our last version of "The Android Platform Security Model" now included in the official August 2021 edition of ACM Transactions on Privacy and Security: https://dl.acm.org/doi/10.1145/3448609.
Fully open access - download, read, share, feel free to use however it's helpful ;-)
@n8fr8 @vitriolix I would have liked a content warning on that 😜 At least this web client handles GIFs well, only starting when I click it, easy to stop, etc. Element kills me because the GIFs just keep going and going.