This project is about reverse engineering the firmware blobs. It states that they do not want to create a distribution like postmarketOS or other projects do.
If you wanted to create an ebook from scratch, how would you do this? Would you write plain html. Would you write markdown, and convert it? What tools would you use?
Imho as everywhere in this field there are tradeoffs to choose for improving this problem: Complexity (rust, formal proofs), runtime overhead (GC), etc.
Hare tries to be simple, so that it's easier to reason about the code and hence maybe find/avoid such bugs more easily.
Yes you need to trust the software. But unless you don't store it on your computer, you need to trust software. The hard part is to figure out which software and whom to trust.
I would definitely use the browser password manager, if I could choose where to sync the data to. I think it's possible with firefox, but it's not straight forward.
I personally trust pfp, because the creator is doing audits of browser addons and publishes them on his blog. They are very well explained.
Also the code is quite compact compared to the other password managers. LastPass, 1Password and Bitwarden have more than 100,000 lines of code, including many third party dependencies. So an audit of PfP is more feasible.
It's still in the works and unfortunately I've written it in German. If you're still interested I'll share a link as soon as it's released. Should be sometime this summer.
Pfp puts the icon in the browser bar, to counter such action. So the pop-up can only be opened this way and the pop up is in a different context than the website itself.
Yes the pop-up could be faked, but not the button.
Actually Tavis Ormandy found a lot of security breaches in password managers that loaded GUI elements into the website. Not only that you can fake it, but also they are susceptible to clickjacking.
I would NOT recommend the chrome password manager. If you sync your passwords, they will not be stored encrypted at the google side. You need to specifically set password encryption in the settings.
I've also spend a lot of time with understanding password managers in my master thesis. What I can recommend is: https://pfp.works/
The creator was auditing password managers like LastPass, found a lot of issues, and used his knowledge to create pfp, which does it right imho.
I'm using e.foundation for a while now on my Moto G3 (osprey) and it's working ok despite a few camera/gallery crashes here and there.
The only thing I'm not really fond of, is that the apps come from an opaque source (https://info.cleanapk.org/). I also found no information on how those apps are signed, and how this is checked. Upon asking them, someone pointed me to a git commit where an outdated public key of F-Droid was used.