NIST Asks Public For Help With Quantum-Proof Cryptography (securityledger.com) 138
chicksdaddy quotes a report from The Security Ledger: With functional, quantum computers on the (distant?) horizon, The National Institute of Standards and Technology (NIST) is asking the public for help heading off what it calls "a looming threat to information security:" powerful quantum computers capable of breaking even the strongest encryption codes used to protect the privacy of digital information. In a statement Tuesday, NIST asked the public to submit ideas for "post-quantum cryptography" algorithms that will be "less susceptible to a quantum computer's attack." NIST formally announced its quest in a publication on The Federal Register. Dustin Moody, a mathematician at NIST said the Institute's main focus is developing new public key cryptography algorithms, which are used today to protect both stored and transmitted information. "We're looking to replace three NIST cryptographic standards and guidelines that would be the most vulnerable to quantum computers," Moody said. They are FIPS 186-4, NIST SP 800-56A and NIST SP 800-56B. Researchers have until November, 2017 to submit their ideas. After the deadline, NIST will review the submissions. Proposals that meet the "post-quantum crypto" standards set up by NIST will be invited to present their algorithms at an open workshop in early 2018.
Oxy-morons (Score:1)
So, they want a code less vulnerable to math... good luck with that.
Re: (Score:2)
Solution: One time pad; "mathematically unbreakable encryption",
Re: (Score:2)
Especially since Quantum Computing only breaks current public key encryption, not even some current shared key algorithms, and keys are much easier to exchange than giant pads.
Re: (Score:3)
Especially since Quantum Computing only breaks current public key encryption, not even some current shared key algorithms, and keys are much easier to exchange than giant pads.
OK. First off, "giant pads" is at best a clumsy phrase, so let's not beat around the bush, just call them MaxiPads.
Once that is done it should be no problem getting replenishment from a 7-11 "Flirtey drone".
Re: (Score:3, Interesting)
How does it handle counterfeit or lost messages? Not so well, I bet. Why would I want to spend more time securely obtaining one time pads than actually communicating?
I think it would work like this:
You go to your bank to open an account. While you are filling out paperwork and supplying a thumb-print (thank you 9/11 terrorist - NOT!) the bank generates a very long one-time pad that should provide enough coverage for several year's worth of communications. They keep a copy and they give you a copy. The pad is probably signed with the bank's public key so you know it is really from the bank.
To detect lost messages, every communication will include either an index into
Re: Oxy-morons (Score:4, Informative)
Also, to avoid pad exhaustion, the pad would probably be used to generate temporary/ephemeral symmetric keys and for some other things like the initial setup of the communication. The actual "meat" of the communication would be encrypted with the ephemeral, symmetric keys.
And oops! It's no longer a one-time pad. As soon as you start using an algorithm, by its very nature, you're now leaking a very slight amount of information, because the output is no longer actually random either. This exactly why a one-time pad isn't practical for most applications. It's only effective if it's the same length as the message being encrypted. Any attempt to "cheat" and you compromise the encryption integrity.
Besides, modern ciphers actually DO use true random numbers to generate the initial symmetric keys, typically using Diffie-Hellman key exchange [wikipedia.org], in which it's impossible for anyone to intercept the key even if they listen to the entire exchange. So you might as well skip the one-time pad, and you get the exact same effect.
Re: (Score:3)
The point is, that it's the Diffie-Hellman which is going to be broken by quantum computing, presumably. So you might want to be careful with that 'impossible' - this is exactly what the article is about.
Re: (Score:3)
Re: (Score:2)
Re: (Score:2)
Re: (Score:1)
That's what has enabled the modern spy infrastructure
Not just the modern spy infrastructure, but most "spy infrastructures" throughout history.
Fear: Either on the part of the public, demanding the government protect them (e.g. 1933 Germany, 2001 USA), or on the part of a tyrannical regime, to protect them from rebellion (e.g. Communist Eastern Europe excluding Russia, Japan-occupied China and Korea in the decades before 1945, the occupied parts of the Confederacy during the last parts of the American Civil War and former Confederate states in the years after
Re: (Score:3)
Solution: One time pad; "mathematically unbreakable encryption",
A concept born in 1882, and yet NIST is still looking for a solution in 2017.
Hmmm...
Re: (Score:2)
Your pad is as big as the original message, so how do you send the pad to someone in a secure manner? One time pads are very secure but don't solve many real world problems.
Re: (Score:2)
That's more or less what we have now, until quantum computing is real. You don't need a quantum computer to use post-quantum cryptography [wikipedia.org].
What I haven't seen is how quantum simulators [phys.org] rate as a threat.
Re: (Score:2)
Of QC ever gets real. Strikes me a lot like "AI", which looks these days as it may actually be impossible in this universe if you want something at least as smart as a human moron. Quantum factoring has gone from 4 bits to 16 bits in 25 years or so. Even if it continues to scale like that (which it will not, there is indication it scales inverse-exponentially, so 30-100 bits or so may be the absolute upper limit), it will not be a threat to modern encryption for 50-100 years, and that is only if we continue
Re: (Score:2)
which looks these days as it may actually be impossible in this universe if you want something at least as smart as a human moron
The progress has indeed been hyped, but that does not suggest in any way that it is impossible.
Machine intelligence will progress in the future, sometimes quickly but mostly slow. Nobody has a clue as to how far it will go.
Re: (Score:2)
There are some rather strong indications it will not go very far at all. They are not reliable proof, sure, but proving a negative is notoriously hard. One is that at this time, after half a century of research into it, there still is no credible theory how intelligence could be generated artificially. The only thing we have that can mimic some aspects of intelligence is automated theorem proving, and that cannot scale up to what a smart human can do in this universe, not enough matter and energy available.
Re: (Score:2)
Most insight-less comment of the day. No wonder you post as AC.
Not Hard (Score:1, Interesting)
This is a bad idea. We're in a weapons race, and so long as we keep playing the game, successive generations of crypto will be subject to attack. We need an end-run around the problem, which means changing how we think about encryption and data security.
Encryption should begin with a physical exchange of one-time pads. If you open a bank account, you should get a key to it. The key is an exhaustible one-time pad you use to encrypt transmissions to and from the bank. You plug it into a machine which runs pac
Re: Not Hard (Score:5, Insightful)
Ffs..
So.. You will personally go and visit each and every web site you want to access privately?
Physically visit every inline store you want to deal with?
Then secure all that data carefully! Remember.. If anyone gets a copy.. All security is give.. At either end!
You need to think about things for more than 30 seconds.
Or perhaps you should accept that armchair 'experts' like you who think this is so easy are actually a big part of the problem?
Good crypto is hard.. QC proof crypto will be harder.. Such is life.
The major historical mistake to avoid is over complex 'standards' that are therefore never implemented or used correctly (I am looking at you ipsec..)
Re: (Score:2)
So.. You will personally go and visit each and every web site you want to access privately?
The obvious solution, if you could trust your government, would be to have them handle the issuance of one-time pads. Since you can't, you can still use the technology for banking, dealing with social security, or for several other purposes without undue inconvenience.
Re: (Score:3)
Ffs..
So.. You will personally go and visit each and every web site you want to access privately?
Physically visit every inline store you want to deal with?
Then secure all that data carefully! Remember.. If anyone gets a copy.. All security is give.. At either end!
You need to think about things for more than 30 seconds.
Or perhaps you should accept that armchair 'experts' like you who think this is so easy are actually a big part of the problem?
Good crypto is hard.. QC proof crypto will be harder.. Such is life.
The major historical mistake to avoid is over complex 'standards' that are therefore never implemented or used correctly (I am looking at you ipsec..)
Of course not. You build an infrastructure based on the premise of physical distribution of one-time pads. That doesn't mean you personally visit every web site you interact with; it means you assume that encryption of a website is breakable and you make the important sites uncrackable by using one-time pads. There are lots of ways to play around with the model and lots of weak points in bad implementations, but fundamentally any encryption algorithm other than that is breakable eventually. It's a much bett
Re: (Score:1)
You know when laypeople that read about court cases have an opinion about how easy caselaw is if only lawyers would do this one thing they just made up? You are giving that cringy feeling to everyone here that deals in infosec.
Re: (Score:2)
The crypto-morons that think everything is easy and they of course understand the questions that takes an actual expert a decade or so to really get will never die out. They are a close cousin to the morons that think coding is easy.
Re: (Score:3)
Re: (Score:2)
Well, to be fair, if a scaling QC ever materializes, AES-128 may be just barely vulnerable (2^64 effort). But AES-256 will still have a very comfortable security margin.
Re: (Score:2)
Your argument is not internally consistent. You are assuming that AES ciphertext will be encrypted with a password-derived key but DES will use a uniformly random one. That's not a fair comparison. Anyways, your whole premise is flawed for two reasons:
1) Password security is an orthogonal issue to encryption. You can have the strongest encryption in the world and if you use a weak password to derive a key you will not get the full benefit of that strength. Attacking a ciphertext you break either the pa
Re: (Score:3)
Yes let us now compare the packed files you have seen personally vs the entire volume of HTTPS traffic that goes across the internet every day. I am betting that the second one is a teensy bit bigger. And yes TrueCrypt and VeraCrypt don't use enclave chips, but only a handful of enthusiasts use those programs. You know what programs do use enclaves and therefore uniformly random keys? iOS encryption (over 1 billion iOS devices), Android encryption (lots of those too), Microsoft BitLocker, Apple Filevaul
Re: (Score:2)
Indeed. On the plus side, we already have QC-proof symmetric encryption today. It just gives you a square-root improvement, so AES-256 is proof against a QC. The moron above probably does not know that, as a one-time pad is symmetrical encryption and hence does not improve against AES-256 in the presence og working, scaling QC in actual reality.
That works in some contexts (Score:1)
Banking with your local bank branch, fine.
Sending in an online application to a graduate school a thousand miles away, not so much.
Okay, I take that back: Physical "in person" key exchange could be done if you did your key exchange "in person" with agents acting on the other party's behalf, with the key sealed in a tamper-evident packaging and optionally encrypted with your public key. Oh way, scratch that optional part, or we will be reasoning in circles.
Besides, one-time pads can be compromised.
I do agr
One time pad is a time machine, not a crpto algori (Score:2)
Suppose that that Bob and Alice have a secure channel now, that they will not have in the future. They will have an insecure channel in the future. A OTP allows them to exchange messages now, that have not been written yet! A OTP is a message time machine. It allows you to securely exchange a message now, that you intend to write in the future.
After they exchange a
Re: One time pad is a time machine, not a crpto al (Score:1)
I found Bob and murdered him. I have the codes, now what? Can I get your data?
Re: (Score:1)
Re: (Score:2)
Protip: If anybody in an encryption-debate brings up the one-time pad, then they have just outed themselves as clueless amateurs.
Post backdoor (Score:3, Interesting)
NIST are hardly credible at this point, they previously were involved in the Dual EC fake random number generator, and now they're an agency under the Executive of Russian puppet leader, Trump. No credibility, means no trust.
FBI has demanded backdoors, Trump has said he'll give them their backdoors. NIST are the backdoor implementers.
Re:Post backdoor (Score:5, Interesting)
One should not trust NIST, but that doesn't stop NIST from providing a forum where trustworthy theoreticians can spar, and that's a helpful thing for them to do. It's not like they are entirely evil, just their decisions should not be trusted, but rather reviewed by the cryptomath community and either endorsed or criticized.
Basically any government entity is going to be torn between wanting to break crypto (for cointel) and wanting to use it (for their own security or for the fact that it is pretty damn essential to a continuing economy.) They'll do some good things, and they'll do some bad things, but at least they'll do something, rather than just sitting on their hands.
Re: (Score:1)
Please implement your own encryption without any of our nasty backdoor review process! We're totally sure that it will be perfectly secure because we didn't put in a backdoor! NO REALLY!
-- The NSA
Re: (Score:2)
Re: (Score:2)
So this wikipedia page [wikipedia.org] is wrong? It says there were multiple warning before NIST ratified the standard and that is how I remember it at the time.
Re: (Score:1)
there is going to be lag between when Quantum Computers can decrypt classical based algorithms and when Quantum Cryptography can be used. They must think it's long enough to find more robust classical algorithms. Probably not going to help
The two concepts are related but not identical.
Practical quantum cryptography means sending quantum messages over long distances - anything less than halfway across the world leaves room for improvement - while quantum computing, which includes fast description of classical encryption algorithms - is typically done in one location.
I expect well-funded parties will be able to routinely decript 512-bit-and-smaller factor-based algorithms in a reasonable amount of time (less than a year) and cost (less than $1
Re: (Score:3)
Done (Score:1)
They can write me a check.
The NSA!? (Score:1)
They are the sheeps in the wolves clothing here. They well not allow anything they can't break.
Re: (Score:1)
They are the sheeps in the wolves clothing here.
I think the NSA re-worded your message for you. Did you mean carnivors dressing up as herbivors by any chance?
they couldn't explain 911 (Score:1)
Re: they couldn't explain 911 (Score:2, Funny)
For a good explanation of 911 see:
https://en.m.wikipedia.org/wiki/911_(number)
Post Quantum Cryptography (Score:5, Informative)
Ask a perl programmer (Score:1, Offtopic)
"Falken: W.P.O.R.: (Score:2, Offtopic)
A strange game. The only winning move is not to play." ~ War Games - 1983
Encryption is not the solution; it's the problem.
Quantum computers can't do a goddam thing better than what we already do except faster.
The best new approach is to change paradigms.
I'm not 16 anymore and I don't have enough time left to figure it out.
That's the way to go, though.
The problem with security today is the fucking DNA of the first computer ever built.
The first automobile should have had seat belts.
Re: (Score:2)
It was WOPR, not WPOR.
Re: (Score:2)
You are correct. Thank you for the correction.
Re: (Score:3)
Re: (Score:2)
That's what I said. We have to fight the problem of speed if we stick to the current paradigm.
We need to change the rules so computers can't play.
--
TRUE STORY
I got a chess game for my Tandy 2000 back in the very early 80s. I had a hard time beating it because it would make a test move; predict my next move; make a test move based on that; rinse repeat,
I won a lot after I figured out what was going on.
My friends thought I was really good at chess.
Not true.
I fucked that computer over by making illogical moves
Re: (Score:2)
Re: (Score:2)
You are not an editor, so I'm sorry you missed the digression markup, "--" that signals a change of subject.
My bad.
--
I've been in this business since Moby Dick was a minnow and I also grok quantum theory and the emergence of the computers.
I also understand that when a problem is solved, a way to sabotage the process is to change the problem but not the solution.
That, in a nutshell, is encryption.
The NIST is looking for an elephant gun to kill a piss ant.
Instead, we need to provide a solution where piss ants
D-Wave can't run Shor's algorithm, but... (Score:2)
Re:D-Wave can't run Shor's algorithm, but... (Score:5, Informative)
This is a really big increase in efficiency, say going from a month worth of computation to solve a problem down to just an hour. But it is not anywhere near enough to break factoring since it would hypothetically take thousands of years to break on a classical computer. In fact, the best classical algorithm is actually slightly faster than quantum annealing because we happen to know that factoring is a problem that requires sub-exponential time to solve, O(N^(1/3)) on a classical computer vs O(N^(1/2)) on a D-Wave.
I am not a Cryptographer... (Score:2)
I'm not up on cryptography but from what I understand most encryption standards have a way to tell if a data set is decrypted correctly. Correct?
So couldn't you implement a cypher that has no way to verify the result -- put in a key, any key, get an output file. If the proper key is used the output file is an encrypted file that can be decoded using another key, and a different encryption system that does a check for correctness.
Wouldn't that greatly increase the difficulty in cracking the code? The file wo
You've simply doubled the length of the key. Good (Score:2)
It sounds to me like you've simply doubled the length of the key. Actually slightly worse than that due to collisions. You'd be more secure encrypting 128 bit blocks with a 128 bit key than encrypting a 64 bit block with a 64 bit key, then with another 64 bit key.
It should be noted that making the key twice as long does NOT make it twice as hard to decrypt. Rather it SQUARES the time required. A 129 bit key takes twice as long as a 128 bit key (assuming blocks are long enough etc.) So your idea DOES ma
Three reasons (Score:2)
There are three reasons to have an integrity checksum, to verify that it decrypted correctly. One issue you didn't mention is that it's always possible for an attacker to change the cipher text without decrypting it, and sometimes they can make interesting changes. You want to know if the data has been modified.
> Maybe a machine learning algorithm could pick it out, but otherwise it's a needle hiding in a huge haystack...
It's not hard for an attacker to notice whether or not the plaintext looks like:
GE
Good point (Score:2)
Thanks for pointing that out.
Re: (Score:3)
A few suggestions and questions? (Score:1)
As a mathematician who occasionally works on cryptography problems, I read the statement, provided in the link, at the Federal Register, some thoughts:
1) Quantum computers are a distant reality. From my understanding, they are still mostly theoretical. Those that do function, can only perform basic arithmetic -- or the equivalent -- or aren't considered fully quantum. So, it would have helped to define what quantum cryptography is. Presently, a key size, from my understanding, that's needed to prevent birth
Re: (Score:3)
1) Because of Grover's algorithm, even encryption which is "secure" against quantum computers still needs twice the key length to have the same level of security as against classical computers. This is because Grover's algorithm lets you brute force a space of N possibilities in time O(sqrt(N)) instead of O(N). So if 90 bits is secure today, you would want 180 bits to be secure against quantum attacks.
2) They can. AES goes up to 256 bits and there is no reason we couldn't make larger block ciphers if we
One time pad (Score:2)
If you want unbreakable crypto... One time pad.
and here someone says "but MOOOOOM its hard!"... no it isn't.
How many gigs of communication do you need to secure per device? Lets presume that there are LEVELS of security that can be secured with varying levels of security.
Naturally it is impractical to secure everything with the one time pad type encryption. Which to be clear would be a very large file stored on the sender and receiver and the data being encrypted would use only a portion of that seed data t
Re: (Score:2)
Re: (Score:2)
"NIST Asks Public For Help With Quantum-Proof Cryptography" ...
Re: (Score:2)
Re: (Score:2)
Doesn't address the quantum aspect of the query. Define the danger of quantum cracking?
Do you know how that is supposed to work? If you think your 256 bit key is going to hold against what that promises to be then maybe you should look that up.
That said, I haven't seen any practical evidence of it actually working. So maybe it doesn't matter.
Your sad dive into rudeness however is unfortunate. Why is your ego so small that when your obvious autism is revealed you have to lash out.
Calm down, dude. You're auti
Re: (Score:2)
Re: (Score:2)
The air is let out of your pretensions and this is all you're left with...
Sad.
Re: (Score:2)
Re: (Score:2)
Still no response to the quantum bit that made you run away like a kicked dog. Pretension... I call you out on it and you claim a PhD... Irony.
Re: (Score:2)
Re: (Score:2)
How do I secure my one-time pads? WIth more one-time pads? Is it one-time pads all the way down?
Re: (Score:2)
... It is assumed that the opposition doesn't have physical access to your system or the target system. Rather the assumption is that the encryption is required any other system besides the origin and destination of the message. If you need to secure things so that your own system isn't compromised then you're basically fucked via the first rule of computer security...
Physical security. You either have that or kill yourself.
Re: (Score:2)
You update the code as you exhaust it.
For the highest level security you can physically deliver new codes. Thus meaning the code will only be compromised if intercepted. And if it is intercepted... physically... you just invalidate the new code and deploy another one.
Again this is used for the highest level security already. Nuclear launch codes work this way. You can't crack them. If I told you what all the past launch codes were, you'd have no idea what the new launch codes are. The codes don't repeat. On
Guess verification (Score:2)
if you want to crack encryption with a powerful computer, you need a means to algorithmically verify your guesses. This is what you need to make hard. Essentially you need a way of encoding messages such that there are many many plausible decryptions. As such, if you took a dictionary of the most common 5000 English words, and forced all communications to use those, and only standard English grammar, you could algorithmically map strings of integers to English words and phrases. There are many ways to do th
Re: (Score:3)
Re: (Score:2)
Maybe too early to worry (Score:1)
Re: (Score:2)
I think you are thinking of the D-Wave computer, which is not actually a quantum computer in the most general sense. The great thing about quantum computers is that they actually break some complexity barriers that exist for classical computers, factoring being one of them. If we ever get a quantum computer that can handle a few hundred qubits then it would be able to instantly factor existing RSA moduli, compared to hundreds or thousands of years for a classical computer. Right now I think the record is
To hell with that! (Score:2)
If I have an idea for creating encryption that's invulnerable(or extremely resistant) to attack by quantum computers, I'm going to the patent office not NIST.
Another gov org not helping or doing much (Score:1)
Do we the tax payers have to pay the government to make free (and probably bloated, not working) versions of everything?
I don't see why anyone uses NIST outside the government. Almost no one does unless they have huge budgets not requiring profit.
An Old Parable (Score:2)
Re: (Score:2)
Radial Lock (Score:2)
There Came An Echo, anyone?
Re: (Score:2)
The number of key bits is still the metric for quantum resistant encryption. You just need to base your scheme on a problem that is not solvable in polynomial time by a quantum computer. There are no great ways to do this except to find a problem that seems like it is hard for a quantum computer, conjecture that it is hard, and then wait for people to try to break your conjecture. You cannot prove that something is hard to solve because we still don't know if P = NP, maybe all problems are easy and we ju