Dieser Bereich kann Inhalte enthalten, die nicht für alle Nutzer geeignet sind. Dazu können unter anderem Texte, Medien oder Diskussionen gehören, die als beleidigend, extremistisch, gewaltbezogen oder anderweitig belastend empfunden werden. Wenn du solche Inhalte nicht sehen möchtest, nutze bitte die jeweiligen Filter- und Meldeoptionen der Plattform oder meide entsprechende Threads/Communities.
I wouldn’t agree HTTPS was unproblematic before Let’s Encrypt existed, so I’m not sure where you are going with this. The average person doesn’t need a HTTPS cert issued, which I would say is comparable to the average citizen using a passkey. If only some spaces, e.g. enterprise, use them then it’s not a real problem. But that’s why it seems problematic to me once passkeys are pushed for general use.
I don’t think that I did, but my apologies if that is the case.
no, i was saying Let’s Encrypt solved HTTPS’s problems. before it HTTPS had the problems people claim passkeys’ attestation certificate chain has. it is very possible an authority equivalent to Let’s Encrypt will come about within the 16 years after 2021.
the average person doesn’t need an passkeys certificate issued either. using a passkey is the equivalent of HTTPS’s TLS packets, not making a new certificate.
So why shouldn’t we tell people to boycott the tech until then? Even then, that doesn’t solve the threat of a hardware attestation toggle.
I disagree.
because attestation the conspiracy to use attestation has not activated and i believe the damage is too small even if it did; i’ve argued how TPM reliance would be impossible for a very long time.
just like how Let’s Encrypt made acquiring certs (essentially a requirement for new websites now thanks to HTTPS, just like what you say passkey attestation is) extremely easy, the equivalent for passkeys would make new attestation providers quite easy, since the equivalent authority would be trusted
Why so? What about passkey attestation requires each user to issue a certificate?