A good example of why a MAC after encryption is also needed. And blocking length extension attacks.
When AES(☢) = ☠ – a crypto-binary trick
11–20 of 36 posts
Re: When AES(☢) = ☠ – a crypto-binary trick
#12Earlier quoted context omitted.
I guess I'm not following your logic. If there is a salted, hashed password in a db, allowing arbitrary length passwords shouldn't matter? HMACs and KDFs work very differently from symetric-crypto primatives.
The point is that it makes it easier for an attacker to find a hash collision. It's much easier to construct data which hashes to a given value if it can be of arbitrary length. I don't immediately see the connection with this article however.
Re: When AES(☢) = ☠ – a crypto-binary trick
#13Does anyone know where I can download the src to have a look through?
Edit: found it https://code.google.com/p/corkami/source/browse/#svn%2Ftrunk...
Re: When AES(☢) = ☠ – a crypto-binary trick
#14Re: When AES(☢) = ☠ – a crypto-binary trick
#15Re: When AES(☢) = ☠ – a crypto-binary trick
#16That was a great read. I saw the title and figured it would quickly go over my head but it's all pretty understandable. Does anyone know where I can download the src to have a look through? Edit: found it https://code.google.com/p/corkami/source/browse/#svn%2Ftrunk...
Re: When AES(☢) = ☠ – a crypto-binary trick
#17Does any one know the name of the hex editor used in these slides, the one showing the PNG chunks and JPEG information?
Re: When AES(☢) = ☠ – a crypto-binary trick
#18I love the "HexII" hex-dump format he links to, it's so much less cluttered than the traditional one. I'm definitely going to have to try that out the next time I'm picking apart some binary file.