Is AES-256 Vulnerable?

Source:  The Conversation and InfoWorld

Happened across a couple articles today, that I found interesting, is AES-256 vulnerable to attack? After reading the articles (IANAM – I am not a mathematician), it seems like the answer is no, for now. Should we be worried? – I don’t think so, we are constantly working on new encryption algorithms, and to say that we are going to be on AES-256 for the next 25-50 years is a little absurd.

So, yes, scientists have found a way, no matter what difficulty they have, and what hardware they have,they have found that they can “break” AES-256 3 to 5 times quicker than was thought, or that was able to do before. Just to bring you back down to Earth on this idea. The current stats of time required to break AES-256 (calculated before these current scientists gave their information, with a 256-bit key) is 3.31 x 10^56. Just using purely rough numbers, that means that it would take billions of years to crack a single key. Then, with the current details, that the scientist provides, if you divide that time, by 5, you come up with 6.6 x 10^55, which is still billions of years.

It is safe to say, at this stage in the game we are safe. We must continue to develop new encryption standards, and new encryption schemes, but not to completely freak out, and lose our minds right now, with this newly released information about AES-256. The other thing, that I’m also taking into consideration; if scientists found a way to reduce the amount of time to compute a key by 5, it is likely that sometime in the future, additional scientists will find a way to reduce the amount of time to compute, by even more. Regardless, at this time, we are safe, and as long as we keep working on new encryption standards, we will still be safe, even when AES-256 is down to hundreds of years to crack.

Don’t freak out now, but keep urging people to continue working on encryption standards to improve on current schemes.

Short URL: http://bit.ly/1Mjbuat

Leave a Reply

Your email address will not be published. Required fields are marked *