I do not like the idea of self-hosting VaultWarden because I generally do not like the idea of application software requiring so much random access memory for even the simplest tasks. So, my idea was to use something like pass[0] or passage[1] (pass[0] + age[2]) on a remote server, but the problem arises when Yubikeys come into play.
I am in no way, shape, or form, endorsing this PonyApp thingy and cannot vouch for it as I haven't audited it. But judging by what it says on the tin, it does appear like a candidate to solve the specific problem I have.
IMO Bitwarden really isn't that well engineered software, and I now use Keyguard on Android/Vaultwarden server instead. Reminds me of Subsonic, with many competing clients/servers. Hopefully someone will write a third party browser extension as the current one is quite slow/buggy.
It's all just slow and mediocre. The Windows desktop client is a massive almost 400MB-download behemoth (and is electron-based), and if you have SSH keys you want to store in it you have no choice but to use it. Oh and you can't log into the browser extension automatically from the desktop client.
Admittedly the mobile clients have since been rewritten to be native (they were _really_ slow before), but Keyguard is still much faster/lighter.
I started using 1Password at work and it's just a.. nicer experience? It does all this and more. Everything is fast, the browser extension is more proactive/recognises fields better (Bitwarden can't really do multi step logins), and the desktop client isn't a chore to use.
The best comparison I would give is comparing Immich and Jellyfin (if you've used these), they are miles apart in terms of end user experience/polish/efficient design. One is engineered, the other feels like it's been hacked together by hobbyists.
Same goes for the bitwarden cli (`bw`).
Its super slow and if you use it in scripts to pull multiple values (username, password), it takes ages. I personally switched to rbw (https://github.com/doy/rbw) and its day and night.
Syncing is iffy. Saving credentials associated to a shared org fails randomly. Rendering (x11/Firefox) sometimes fails completely, but is predictably slow. Auto fill can be buggy. Opening vaults on iOS can be remarkably slow.
Besides being slow, I found it buggy as hell. For instance, I wanted to log in with my Yubikey on my phone, and it flat out refused to let me in despite the master password and the PIN being 100% correct. There's even an open issue on Github about this, that they're doing absolutely nothing about, demonstrating the incompetence further at some really grand scales.
I mean, one of the most basic functionalities is missing: duplicate detection. This and the ability to just add a new domain to existing entry instead of a completely new one.
It's been requested for ages and they haven't delivered it yet.
Yup, instant nope here (That and not having a browser addon, passwords in the browser is 99% of my password-use).
All other stuff is mostly SSH keys / ssh-agent.
> They've got huge monetary losses, if you're ok with that
USA passed the CHIPS Act and is spending close to a trillion dollars to strategically re-home all of TSMC's most advanced fab technology to Arizona as a matter of national security. Monetary losses don't matter when the point is to not be reliant or China in the event of South China Sea conflict.
I think the point of this article, and the warnings from ASML, is that Europe is not making the same effort.
But that's sorta of hits to the heart of my comment, it's not particularly working well. TSMC has 2 fabs in China and yields+costs are a fraction of whats coming out of Arizona, let alone in Hsinchu.
Like are you really going to buy a chip that costs 70% more out of national pride? Might work on some but think that very few else will sign up for that.
70% extra on top of a trillion or two in investment is a relatively small price to pay when faced with the possibility of that being your only option at some point in the future.
I don't want to speak bad about them but it's just general demand for semiconductors at this point, everyone is just buying it all up because they can. The Arizona plant still doesn't seem to be pumping out and the self-sufficiency target for the US doesn't seem all there. Im sorry to be the bearer of bad news but honestly it's a culture that's hard to replicate and its how it somehow gets done in one country on Earth. The 2030 target for the states surely isn't happening, it's way too ambitious.
People really don't understand how this stuff is borderline magic turning silicon into these things. There's so much that can go wrong at every step, it's the most advanced manufacturing process on Earth.
Once upon a time chips went down in value but I don't think that's happening anymore, lot of other people seem aware of that. Not to mention the semiconductor talent is getting eaten up like pancakes everywhere.
Thanks! I noticed on one of my phones that RCS breaks once the Messages app is out of date by a certain amount of revisions. I hope this is an arbitrary decision by Google to invalidate older versions, given that the RCS protocol hasn't changed. I wouldn't want the Graphene team to have to keep up with each change Google makes with their Messages app, and instead is a security oversight Google has found in their own app.
We definitely will have to keep up with the changes. We already do in order to provide support for using RCS via Google Messages on GrapheneOS. Recently, they made a change which broke it on GrapheneOS and we had to quickly fix that in under a day.
Unbound is caching, not authoritative. Zones with dns records are served from authoritative DNS servers such as bind. Unbound asks authoritative servers for records and caches them locally, giving faster response and reducing load on authoritative servers.
reply