android - Google Licensing Service - Understanding the concept -
I do not understand the concept of Google's licensing service
Scenario: User buys an app on A Device X. A user then installs the Android Market through his other device to install the app and does not pay the other device because he uses the same account on both devices.
The app requests a license check that is stored on random data or device generated during installation on specific data or device of the device.
As far as I understand that the additional data will vary on device X and Y, the request for licensing check is different for the same user and app but it is still valid.
During the download from the Android Market, additional request data is also collected on the user / app / device per licensing server?
User A can not copy from Device X to Device Y, License test may fail because the device or installation specific data is stored only on the server when installing app from Android Market?
Some information is saved locally for example: Due to being finally locally stored, you are encouraged to obscure local data (otherwise a forbidden user can enter their local data, which is licensed Is valid in the form) and the An abbuscator which uses AES to encrypt the data. When you create ServerManagedPolicy last Response, Validity stays the timestamp, until maximum retries and retries in the form of local-device data.
AESObfusceter class has been provided as such:
AESObfuscator , you provide a
byte [] salt, string app id, string device id . The password is based on
applicationId and
deviceId (you can see it in the source code).
ANDROID_ID to
deviceId . How secure it is to rely on your discretion - it can be as simple as secure value in your app
(new string (byte)] ((byte) 75, (byte) 12}) ANDROID_ID) or some other cryptography scheme (whose discussion may be more appropriate for cryptography forums).
Comments
Post a Comment