> Google don't provide a key-to-url facility. It would be rather good if > they did, because queries about keys here could be answered far more > quickly if we could find out what url a key was actually created for. My experience shows that the GoogleAPI key is kind of hash and/or encrypt, and thus unable to be reversed to the initial string except brute-forcing (see http://www.insidepro.com/hashes.php?lang=eng) Am I right? Someone got any ideas - how Google working on the given "domain" string + existing "user" value + date of the key creation, exactly?
On the general, the key is: ABQIAA AA EEdfDFSDdsfsdfsdEB RSFDCsdwesdfCXXSDFFSDB RWEdsFweFSDSrewSD43dfsdFFSDdw, where: ServiceID (6 bytes) + ServicePort (2 bytes) + account (22 bytes) + domain (28 bytes) + creation date (28 bytes) All values are hashed and/or encrypted. Any ideas are highly welcome - the case is really interesting to me too, and might be considered as "Private data (domain name) reversing and protection, and Google's streghts and weaknesses on this". --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
