If there was some sort of insane scenario where you had to reconstruct a complete 1GB block from a single MD5 hash... (ie, "here's an MD5 hash. Give me a sequence of 1073741824 bytes to make it") well it's technically possible, though the electric bill for your server farm may piss off more than a few treehuggers.
If this would be true, you'd have found a very space-efficient datacompression algoritm. The truth is, however, if you map all integers representing 1 GB of data to the integers representing 16 bytes of MD5, your map cannot be bijective.
That way any measurement of the entangled photon would cause an immediate change to its twin (The twin photon - of entangled pair)would presumably be archived on the alien world bouncing back and forth in a cavity (not unlike the cavities we use today - only presumably far more advanced.) So, once change is observed, an immeditae alarm bell is triggered.
I believe the first measurement (in order to observe change) of the archived photon will destroy the entanglement. So the photons are no longer twins...
Slashdot Mirror
But your a.out still contains symbols, try running strip and (in my case) the size of a.out went down from 626K to 554K. Still large, though.
If there was some sort of insane scenario where you had to reconstruct a complete 1GB block from a single MD5 hash... (ie, "here's an MD5 hash. Give me a sequence of 1073741824 bytes to make it") well it's technically possible, though the electric bill for your server farm may piss off more than a few treehuggers.
If this would be true, you'd have found a very space-efficient datacompression algoritm. The truth is, however, if you map all integers representing 1 GB of data to the integers representing 16 bytes of MD5, your map cannot be bijective.