reginald78
Joined 2 years ago
Joined 2 years ago
https://github.com/keepassxreboot/keepassxc/issues/10407
Of course, they might just block you for not being on a whitelist of approved providers anyway.
This thread is one of the guys from FIDO threatening to blacklist keypass for doing just that, using the spec'd passkey attestation feature as the tool to do so. Just because the attestation feature isn't widely used as a weapon just this second doesn't mean that is not the intended endgame, in fact I'd argue the hand was tipped in that very thread.
I think the dance is all for naught though, they'll end up locked out as non-standard once uptake is high enough IMO.
Perhaps your dad simply expected to scrollbars to be visible like they initially were.
I believe Steam did support bitcoin at one point but decided to end usage over because the price fluctuations made it to unpredictable on their end. Maybe the landscape has changed though.
This also reminds me of those Japanese temples where in order to preserve the institutional knowledge of how to rebuild the temple in case of disaster the monks tear it down and rebuild it from scratch every 30-40 years assuring the next generation has experience.
My impression is unraid developers have kind of ignored enhancing the core feature of their product to much. They seem to have put a lot of effort into ZFS support which isn't that easy to integrate as it isn't part of the kernel, when ZFS isn't really the core draw of their product in the first place.
> To be very honest here, you risk having KeePassXC blocked by relying parties (similar to #10406).
From the linked https://github.com/keepassxreboot/keepassxc/issues/10406 > | no signed stamp of approval from on high > see above. Once certification and attestation goes live, there will be a minimum functional and security bar for providers.
> | RP's blocking arbitrary AAGUIDs doesn't seem like a thing that's going to happen or that can even make a difference > It does happen and will continue to happen because of non-spec compliant implementations and authenticators with poor security posture.
Is your argument that despite being doused with gasoline I can't complain because I'm not currently on fire?