Comment by dingaling911
8 days ago
I just got a LLM to write a user script that blocks pass key requests:
(() => {
// Sites check `window.PublicKeyCredential` to decide whether to offer passkeys.
try { delete window.PublicKeyCredential; } catch (e) {}
// Block passkey requests from sites that skip the check. Password/federated credentials still work.
const creds = navigator.credentials;
if (!creds) return;
const refuse = () => Promise.reject(new DOMException("Passkeys are disabled.", "NotAllowedError"));
const origGet = creds.get.bind(creds);
const origCreate = creds.create.bind(creds);
creds.get = (opts) => (opts && opts.publicKey ? refuse() : origGet(opts));
creds.create = (opts) => (opts && opts.publicKey ? refuse() : origCreate(opts));
})();
This disables more than just passkeys Also second factors and all of webauthn.
I just want to use passwords, so it's fine.
The LLM should have suggested where you find the browser setting to disable it - they all have one. Can you explain why you're leaving the setting enabled, and using a user-script to disable it instead? Most browsers even offer per-site permissions.
Because the setting in brave doesn't actually work.