when trying different combinations of malware.testing.google.test/
testing/malware/, we never succeed.
Last replier told he could get a match malware.testing.google.test/
testing/malware/ with md5 dc5178cc1a0820bc434c83d2f089f105
We can see that md5 in our database, but none of the strings we tested
had dc5178cc1a0820bc434c83d2f089f105 for md5. So, when testing safe
browsing with http://malware.testing.google.test/testing/malware/ , do
you succeed in matching a hash of the wire format. And with with
string and md5 do you succeed ?
thanks
> We've implemented google safe browsing protection api v1 in our
> client, and we're looking for urls to test it.
>
> when trying different combinations of malware.testing.google.test/
> testing/malware/, we never succeed.
Did you implement URL canonicalization in your client as specified by
the "Developer's Guide" at
http://code.google.com/apis/safebrowsing/developers_guide.html#Canonicalization
>
> Last replier told he could get a match malware.testing.google.test/
> testing/malware/ with md5 dc5178cc1a0820bc434c83d2f089f105
> We can see that md5 in our database, but none of the strings we tested
> had dc5178cc1a0820bc434c83d2f089f105 for md5.
MD5 is cryptographic hash function. Ideally you'll get a unique has
for every unique input. Technically it's mapping space is 128-bits so
have the chance to have collisions but again ideally you won't. That
being said, you cannot expect another input to give the same MD5 hash.
That's why __you need to canonicalize the URL and try iterations of
it__. Read the sections "Performing Lookups" and "Canonicalization" in
Developer's Guide and implement your code as specified.