Guardian Project @guardianproject@librem.one

The F-droid app is undergoing major changes: Faster and smaller updates thanks to a new repository format.

For this, we needed to change the entire app database. To ensure that there are no regression we need your help: Please install the latest alpha version of F-Droid 1.16 and report anything unusual.

🗓️ This Saturday we will join @fosdem to introduce the work of 🇪🇺 Open Source Program Office (@EC_OSPO)

With over 750 lecturers and 8000 participants, FOSDEM is the largest conference in Europe that promotes the use of free and open source software.

Learn more ➡️ bit.ly/3DH70M7

You still have time to register for today's VIRTUAL #PublicDomainDay celebration!
⏰ 1pm PT / 4pm ET
🎟️ https://www.eventbrite.com/e/public-domain-day-virtual-party-tickets-477668177377

#FDroid in an #EU "Pilot project — De-monopolized access to EU applications"... "The focus of the pilot project includes EU institutions releasing their apps on existing alternative app stores, including f-droid that aims at promoting apps released under open source licenses"

https://data.consilium.europa.eu/doc/document/ST-14783-2022-ADD-5/en/pdf

This level of vigilance is hard, so we have added another layer of defense in the upcoming #FDroid client v1.16 release, currently in beta. We've moved the database to be based on #Room and its built-in #security measures, then had that new code audited https://f-droid.org/2022/12/22/third-audit-results.html 2/2

If you want to see a real world attempt at adding a #SQL #injection #vulnerability to an #Android app via merge request, take a look at https://gitlab.com/fdroid/fdroidclient/-/merge_requests/889#note_506478642 1/2

#DRM isn't just an annoyance -- it's a violation of your right to use the items you own as you see fit. Learn more about our Defective by Design campaign at http://defectivebydesign.org, and follow our campaign account at @endDRM

The release of subfolders for iOS is experiencing a short delay. Apparently, Apple doesn't take kindly to referencing other "mobile devices" in the What's New section of an update.

To be clear, we included no mention of Android in this submission.

This type of overly restrictive behavior is unacceptable and is a clear example of why open source software is important. A single company should not have this kind of market control.

#Debian and #FDroid require signature verification, and #FDroid is built on top of #Android's APK signing. This improves things a lot but does not mean they are immune. Debian and F-Droid repos can still override packages lower priority repos. It could make sense to have a "no overrides allowed" setting, but that would restrict useful features. Maybe F-Droid could implement "no new signing keys when overriding" rule by default, I wonder how much that would break what people are doing now? 2/2

#Decentralized #software repository systems like #npm #maven #rubygems #pypi etc have key issues that make them hard to decentralize properly: solid verification is optional, one repo can override packages from another, and the tooling makes it hard to see which repo was actually used. #MavenCentral has additional measures which make it more trustworthy, but if devs add repos, those can still override it. #Gradle verification helps a lot when using Maven repos but does not solve everything 1/2

We are organizing an “Edit A Thon” event (in Persian). The goal is to create wiki pages for the political prisoners in Iran who are at the immediate risk of execution. We collect information about them and putting it in one place to make it easy for Human Right groups to work on their case.
If you like to join, please register here:

https://www.all4iran.com/event-details/wikipedia-edit-a-thon-for-political-prisoners-in-iran-at-risk-of-execution

#MahsaAmini
#StopExecutionInIran
#WomanLifeFreedom

“Imagine if you use a phone for twice as long…that means you only have to produce half the amount of phones and you have half the amount of waste”. 🌍 💚 #Fairphone Founder, @basvanabel@twitter.com, spoke to the team at @WhatDesignCanDo@twitter.com: https://youtu.be/LYhQji59dGY

EU countries are stepping up the fight for digital sovereignty for their citizens, in their schools, and in government.

See how France, Denmark, the Netherlands, and Germany do this in our blog!

https://nextcloud.com/blog/europe-steps-up-fight-for-digital-sovereignty-bans-365-and-workspace-in-more-places/

People from all over Europe want the right to install any software on any device! New signatures to our open letter:

🇮🇹 Italy

Wikimedia Italia @wikimediaitalia

LinuxTrent @linuxtrent

🇩🇪 Germany

Do-FOSS @do_foss

Werkkooperative der TechnikfreundInnen @HackerGeno@chaos.socia

🇪🇸 Spain

Pangea @pangea_org

🇳🇱 Netherlands

Open Nederland @opennl

🇫🇷 France

Fédération des Fournisseurs d'Accès Internet Associatifs @ffdn_channel

Sign now! https://fsfe.org/activities/upcyclingandroid/openletter.html

#righttorepair #UpcyclingAndroid #freesoftware

@Gargron is providing a shining example of the new breed of "startup" culture that is arising. We want impact in the public interest, and just to make a living doing it. Getting rich is besides the point, and it is certainly not a reason to compromise the goals of the project. I believe #FDroid is another example of this.

https://arstechnica.com/tech-policy/2022/12/twitter-rival-mastodon-rejects-funding-to-preserve-nonprofit-status/

What a neat little christmas surprise 🤶 🎄 Oneplus 6 running #postmarketOS 🎉 Bye bye Apple, welcome #Linux 👋

I recently wrote a post detailing the recent #LastPass breach from a #password cracker's perspective, and for the most part it was well-received and widely boosted. However, a good number of people questioned why I recommend ditching LastPass and expressed concern with me recommending people jump ship simply because they suffered a breach. Even more are questioning why I recommend #Bitwarden and #1Password, what advantages they hold over LastPass, and why would I dare recommend yet another cloud-based password manager (because obviously the problem is the entire #cloud, not a particular company.)

So, here are my responses to all of these concerns!

Let me start by saying I used to support LastPass. I recommended it for years and defended it publicly in the media. If you search Google for "jeremi gosney" + "lastpass" you'll find hundreds of articles where I've defended and/or pimped LastPass (including in Consumer Reports magazine). I defended it even in the face of vulnerabilities and breaches, because it had superior UX and still seemed like the best option for the masses despite its glaring flaws. And it still has a somewhat special place in my heart, being the password manager that actually turned me on to password managers. It set the bar for what I required from a password manager, and for a while it was unrivaled.

But things change, and in recent years I found myself unable to defend LastPass. I can't recall if there was a particular straw that broke the camel's back, but I do know that I stopped recommending it in 2017 and fully migrated away from it in 2019. Below is an unordered list of the reasons why I lost all faith in LastPass:

- LastPass's claim of "zero knowledge" is a bald-faced lie. They have about as much knowledge as a password manager can possibly get away with. Every time you login to a site, an event is generated and sent to LastPass for the sole purpose of tracking what sites you are logging into. You can disable telemetry, except disabling it doesn't do anything - it still phones home to LastPass every time you authenticate somewhere. Moreover, nearly everything in your LastPass vault is unencrypted. I think most people envision their vault as a sort of encrypted database where the entire file is protected, but no -- with LastPass, your vault is a plaintext file and only a few select fields are encrypted. The only thing that would be worse is if...

- LastPass uses shit #encryption (or "encraption", as @sc00bz calls it). Padding oracle vulnerabilities, use of ECB mode (leaks information about password length and which passwords in the vault are similar/the same. recently switched to unauthenticated CBC, which isn't much better, plus old entries will still be encrypted with ECB mode), vault key uses AES256 but key is derived from only 128 bits of entropy, encryption key leaked through webui, silent KDF downgrade, KDF hash leaked in log files, they even roll their own version of AES - they essentially commit every "crypto 101" sin. All of these are trivial to identify (and fix!) by anyone with even basic familiarity with cryptography, and it's frankly appalling that an alleged security company whose product hinges on cryptography would have such glaring errors. The only thing that would be worse is if...

- LastPass has terrible secrets management. Your vault encryption key always resident in memory and never wiped, and not only that, but the entire vault is decrypted once and stored entirely in memory. If that wasn't enough, the vault recovery key and dOTP are stored on each device in plain text and can be read without root/admin access, rendering the master password rather useless. The only thing that would be worse is if...

- LastPass's browser extensions are garbage. Just pure, unadulterated garbage. Tavis Ormandy went on a hunting spree a few years back and found just about every possible bug -- including credential theft and RCE -- present in LastPass's browser extensions. They also render your browser's sandbox mostly ineffective. Again, for an alleged security company, the sheer amount of high and critical severity bugs was beyond unconscionable. All easy to identify, all easy to fix. Their presence can only be explained by apathy and negligence. The only thing that would be worse is if...

- LastPass's API is also garbage. Server-can-attack-client vulns (server can request encryption key from the client, server can instruct client to inject any javascript it wants on every web page, including code to steal plaintext credentials), JWT issues, HTTP verb confusion, account recovery links can be easily forged, the list goes on. Most of these are possibly low-risk, except in the event that LastPass loses control of its servers. The only thing that would be worse is if...

- LastPass has suffered 7 major #security breaches (malicious actors active on the internal network) in the last 10 years. I don't know what the threshold of "number of major breaches users should tolerate before they lose all faith in the service" is, but surely it's less than 7. So all those "this is only an issue if LastPass loses control of its servers" vulns are actually pretty damn plausible. The only thing that would be worse is if...

- LastPass has a history of ignoring security researchers and vuln reports, and does not participate in the infosec community nor the password cracking community. Vuln reports go unacknowledged and unresolved for months, if not years, if not ever. For a while, they even had an incorrect contact listed for their security team. Bugcrowd fields vulns for them now, and most if not all vuln reports are handled directly by Bugcrowd and not by LastPass. If you try to report a vulnerability to LastPass support, they will pretend they do not understand and will not escalate your ticket to the security team. Now, Tavis Ormandy has praised LastPass for their rapid response to vuln reports, but I have a feeling this is simply because it's Tavis / Project Zero reporting them as this is not the experience that most researchers have had.

You see, I'm not simply recommending that users bail on LastPass because of this latest breach. I'm recommending you run as far way as possible from LastPass due to its long history of incompetence, apathy, and negligence. It's abundantly clear that they do not care about their own security, and much less about your security.

So, why do I recommend Bitwarden and 1Password? It's quite simple:

- I personally know the people who architect 1Password and I can attest that not only are they extremely competent and very talented, but they also actively engage with the password cracking community and have a deep, *deep* desire to do everything in the most correct manner possible. Do they still get some things wrong? Sure. But they strive for continuous improvement and sincerely care about security.

- Bitwarden is 100% open source. I have not done a thorough code review, but I have taken a fairly long glance at the code and I am mostly pleased with what I've seen. I'm less thrilled about it being written in a garbage collected language and there are some tradeoffs that are made there, but overall Bitwarden is a solid product. I also prefer Bitwarden's UX. I've also considered crowdfunding a formal audit of Bitwarden, much in the way the Open Crypto Audit Project raised the funds to properly audit TrueCrypt. The community would greatly benefit from this.

Is the cloud the problem? No. The vast majority of issues LastPass has had have nothing to do with the fact that it is a cloud-based solution. Further, consider the fact that the threat model for a cloud-based password management solution should *start* with the vault being compromised. In fact, if password management is done correctly, I should be able to host my vault anywhere, even openly downloadable (open S3 bucket, unauthenticated HTTPS, etc.) without concern. I wouldn't do that, of course, but the point is the vault should be just that -- a vault, not a lockbox.

I hope this clarifies things! As always, if you found this useful, please boost for reach and give me a follow for more password insights!

@matthew_d_green The solution to the problem posed in that piece is referenced in it: #FBI got #Signal messages when they had a legitimate reason to have them. End-to-end encryption stops mass surveillance, but clearly did not stop the Jan 6th investigations. I think its pretty clear that phones should be treated like one's house in terms of search and seizure. Courts can compel people to give info, and can compel people to unlock their phones. My guess is that's how FBI got info from Signal.

Today’s social media status quo isn’t cutting it, so Mozilla is exploring an alternative here on Mastodon. In early 2023, Mozilla will be testing a publicly accessible instance in the Fediverse at Mozilla.Social. We will keep you updated, but for now learn more here: mzl.la/3BNXQMQ