Correction: Claude found a plausible way these curve points were generated. And “plausible” is carrying a metric fuckton of weight here.
It found PRNG settings that could theoretically generate the same values, but the fact that it requires thousands of iterations makes me think this is more of a coincidence than anything. Especially given that the NSA employee remembered something completely different.
As a product reveal, this is nothing short of blatant fraud. I guarantee there was nothing inside that shell but gas tanks and thrusters.
They posted this here once already and then deleted it, I guess because they expected people to actually give a shit.
Kofi has clearly never had a girl sleep over at his place in nothing but one of his shirts.
All the messaging about fast charging speed is focused on the wrong thing. EV drivers should be able to do the vast majority of their charging at home or at their destination. The messaging should be about getting chargers in more homes, apartment complexes and workplaces. Speed doesn’t matter as much if you’re going to be parked for half the day or overnight.
Fast charging stations should only be necessary for road trips, where you should be taking a break every so often anyways.
If I bite into what looks like a chocolate chip cookie and get spam, I’m going to kill everyone in the room and then myself.
What, you don’t want to go to a restaurant where the only things on the menu are fairy bread and cans of VB?
I’m guessing Outback Steakhouse doesn’t really count lol
Still a better drummer than Lars Ulrich
You should cross post this to /c/THE_PACK
That’s what CSRF mitigations are for.
Do you actually understand how any of the modern web works or does your knowledge stop at W3Schools tutorials from the mid-2000s?
Bitwarden lets you store passkeys in its vault, which I think is what you’re asking for? It’s mentioned in the post too.
No. I’m talking about using the password to directly derive the passkey. This would eliminate the need to store them in something like BitWarden.
In the scheme I’m proposing, the password never gets sent to the server.
The issue of password reuse is the password getting sent to the site, because the prevailing approach is to hash the password server-side. Passwords leak because they get stored in plaintext, or hashed using outdated algorithms, or get logged with request metadata–bottom line, they end up stored somewhere that an attacker can get their grubby little paws on them, or in a way they can reasonably recover them.
Using a master password to derive a passkey client-side isn’t any different than using a master password to unlock a password manager. It just cuts out the middle step.
I feel like there’s some potential in password-derived passkeys, which would get around the storage and hardware lock-in issues. It’d essentially be a master password like for BitWarden, but instead of needing an app to store a bunch of generated passwords, the master password could be all you need to authenticate.
Most of the sources of compromise for regular users would be eliminated because the password never leaves the client.
I’d love to have a backyard someday private enough to try this, not for any new age healing reason, I just wanna know what the warmth of the sun on my taint would feel like
Irish jokes never left
Fire Department Chronicles on YouTube has some really funny skits, but the complete lack of respect for the 180 degree rule or any sort of consistent blocking/sightlines can be really distracting: watching this, I have no idea where each of these characters are standing relative to each other.
Really? No one’s posted this yet?
Relevant XKCD: https://xkcd.com/908/
If I’m interpreting it correctly, that’s the probability that this particular PRNG with those particular seeds produces those particular outputs. That’s a strawman argument; a PRNG with uniform output should eventually produce any value.
It’s perfectly believable that a known broken PRNG from 40+ years ago could be backsolved. The part I doubt is the sensationalized part, that the LLM found the exact method with which it was calculated. It’s just a plausible choice for a random oracle. It’s a local minimum the LLM settled into.
That’s the thing with random oracles, there’s likely so many plausible combinations of candidate algorithms and inputs/seed values that the actual truth is almost certainly lost to history.