Collaborate Disseminate
The MD5 hashing algorithm is a one-way cryptographic function that accepts a message of any length as input and returns as output a fixed-length digest value to be used for authenticating the original message.The MD5 hash fun… Continue reading Can i use Honey Encryption in place of MD5?
This question already has an answer here:
How to determine what type of encoding/encryption has been used?
8 answers
I ha… Continue reading Help me decrypt this base64 string [duplicate]
I read on Wikipedia, that at first MD6 had some problems with a buffer overflow, and a lack of proof of resilience against differential attacks; however, the article also says that that was fixed.
Yet, I struggle to find muc… Continue reading What happened to MD6?
Why is it unsafe to use the DNSSEC algorithm RSA/MD5? In practical terms, how is DNSSEC weakened by the use of an algorithm such as MD5, which has a known weakness of collisions?
RFC 6944 states, under chapter 2.3 DNSSEC Im… Continue reading What are the implications of using an "unsafe" DNSSEC algorithm like RSA/MD5?
I am trying to crack one of multiple MD5 hashes that have been created from numerical input.
I have a sample of 1000 MD5 hashes that are generated from numerical input. I know that the input is somewhere between 10^6 and 10^… Continue reading Cracking a MD5 hash from numerical input
I’m reviewing API documentation from a potential supplier.
In order to gain access to the useful parts of the API, we have to send a GET or POST request to a particular endpoint passing two parameters – our organization name… Continue reading API hash-based authentication
Suppose I’ve got a list of “passwords” that are hashed using the same suffix, so basically what we do is hash = md5_digest(prefix+suffix), with suffix being a constant.
Now, if I know a single prefix and hash pair, I can tri… Continue reading Is MD5 particularly vulnerable when given multiple MD5 hashes using a common, secret suffix?
So as of this morning any SHA-1 hash can officially be collided for as little as $110k in GPU power on Amazon.
http://shattered.it/
https://arstechnica.com/security/2017/02/at-deaths-door-for-years-widely-used-sha1-function… Continue reading All hash algos shatter… so why not switch from golden bullet to scatter shot?
A team from Google and CWI Amsterdam just announced it: they produced the first SHA-1 hash collision. The attack required over 9,223,372,036,854,775,808 SHA-1 computations, the equivalent processing power as 6,500 years of single-CPU computations and 110 years of single-GPU computations. While this may seem overwhelming, this is a practical attack if you are, lets say, a state-sponsored attacker. Or if you control a large enough botnet. Or if you are just able to spend some serious money on cloud computing. It’s doable. Make no mistake, this is not a brute-force attack, that would take around 12,000,000 single-GPU years to complete. …read more
Algorithm underpinning Internet security falls to first-known collision attack. Continue reading At death’s door for years, widely used SHA1 function is now dead
