So is it time to 100x key length on browsers yet or not?
Willow, Our Quantum Chip
361–370 of 557 posts
Re: Willow, Our Quantum Chip
#362> It lends credence to the notion that quantum computation occurs in many parallel universes, in line with the idea that we live in a multiverse I see the evidence, and I see the conclusion, but there's a lot of ellipses between the evidence and the conclusion. Do quantum computing folks really think that we are borrowing capacity from other universes for these calculations?
I don't understand the jump from: classical algorithm takes time A -> quantum algorithm takes time B -> (A - B) must be borrowed from a parallel universe. Maybe A wasn't the most efficient algorithm for this universe to begin with?
Right, and that's part of the argument against quantum computing being a proof (or disproof) of the many-worlds interpretation. Sure, "(A-B) was borrowed from parallel universes" is a possible explanation for why quantum computing can be so fast, but it's by far not the only possible explanation.
Re: Willow, Our Quantum Chip
#363More misleading random circuit sampling benchmarks. All it proves is that Google has built a quantum computer that does quantum things.
Re: Willow, Our Quantum Chip
#364Earlier quoted context omitted.
I agree that the scary scenario is stored SSL frames from 20 years of banking. That's nuclear meltdown scenarios.
To do what? Replay? Just curious on an attack vector.
Hopefully replay attacks will not be useful, but confidential information will be abundant. There will be actionable information mixed in there , and it will be a lot of data. Just imagine if everything whispered suddenly became shouted.
Re: Willow, Our Quantum Chip
#365>the more qubits we use in Willow, the more we reduce errors, and the more quantum the system becomes That's an EXTRAORDINARY claim and one that contradicts the experience of pretty much all other research and development in quantum error correction over the course of the history of quantum computing.
It's a categorically new experimental regime but it's exactly what was supposed to happen. I think it's an awesome result.
Re: Willow, Our Quantum Chip
#366what is this actually useful for?
Re: Willow, Our Quantum Chip
#367They opened the API for it and I'm sending requests but the response always comes back 300ms before I send the request, is there a way of handling that with try{} predestined{} blocks? Or do I need to use the Bootstrap Paradox library?
What happens when you don't send the request after receiving the response? Please try and report back.
Looks like we don't have a choice.
Re: Willow, Our Quantum Chip
#368Earlier quoted context omitted.
> quantum computers would be able to retroactively break any public keys that were stored Use a key exchange that offers perfect forward secrecy (e.g. diffie Hellman) and you don’t need to worry about your RSA private key eventually being discovered.
Perfect forward secrecy doesn't work that well when NSA motto is - store everything now decrypt later. If they intercept the ephemeral key exchange now they can decrypt the message 10 or 50 years later.
Something tells me that by the end of the century only the one-time pads will still be holding their secrets.
Re: Willow, Our Quantum Chip
#369Earlier quoted context omitted.
As if "thinking about it" will ever stop people from acting first. I'm far more scared when tech-bros like Musk land on Mars and contaminate stuff we might not even be able to detect yet.
i'm not even remotely 'far more scared' about that. i think you are insufficiently scared about crypto being broken
Quantum computer becoming available / powerful does not mean all cryptography will get broken. People who have actual knowledge and expertise are already busy working on various aspects of PQC.
Re: Willow, Our Quantum Chip
#370They opened the API for it and I'm sending requests but the response always comes back 300ms before I send the request, is there a way of handling that with try{} predestined{} blocks? Or do I need to use the Bootstrap Paradox library?
It think you are supposed to use a "past" object to get your results before calling the API.