The in-app billing docs says this:
http://developer.android.com/guide/market/billing/billing_best_practices.html
To keep your public key safe from malicious users and hackers, do not
embed it in any code as a literal string. Instead, construct the
string at runtime from pieces or use bit manipulation (for example,
XOR with some other string) to hide the actual key. The key itself is
not secret information, but you do not want to make it easy for a
hacker or malicious user to replace the public key with another key.
The server signs its responses, and I believe the idea is to make it
more difficult for hackers to inject their own response that would pass
the signature check in the application. They'd have to use their own
private key to sign their injected response, and thus need to replace
the public key embedded in the application so they match. Embedding the
key as a one-piece Base64 string makes it really easy to find and replace.
Same logic should apply to the LVL, but I haven't used it and don't see
a direct mention in the docs.
-- Kostya
29.04.2011 23:19, Ted Hopp пишет:
Thanks, Kostya. I'm curious why the (public) publisher account key
would need to be obfuscated. What vulnerability would there be if the
key were publicly known?
--
You received this message because you are subscribed to the Google
Groups "Android Developers" 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/android-developers?hl=en
--
Kostya Vasilyev -- http://kmansoft.wordpress.com
--
You received this message because you are subscribed to the Google
Groups "Android Developers" 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/android-developers?hl=en