Im trying to see how to set a limit on .apk installations. Not so much concerned with end user piracy as I have ways of doing that. The key server-side-authentication is a good suggestion, however not fully understanding how they actually go about "embed the app" has me kinda blind as to the methods or "practical steps" I can enforce on them.
So far Im Mcguyvering my own server-side-auth-token activation system. I know Im just being lazy and wanted google to give a feature like "hey after this date the .apk is null, and after these many installations its dead too, and a way to assign an OEM a specific OEM KEY associated with a given signed app" I'll look into the 4.1+ features you mentioned. Anywho, thnx for your response, really appreciated it! On Monday, July 30, 2012 8:15:44 AM UTC-7, seattleandrew wrote: > > No, I don't believe so. Are you trying to protect your app from piracy? If > so, you may want to use the Google Play Store's encrypt .apk feature for > Android 4.1+. This will prevent a user from taking an .apk and distributing > it easily. If you're looking to limit the number of installs you could > easily go with a server-side authentication method. i.e. hand out the .apk > but also email a key that can only be used 10,000 times. This way the > distribution is easy and you can limit the number of instances that it is > installed. > > tl;dr android 4.1 provides .apk encryption to protect against piracy, or > you could setup a server-side authentication system to "license" the app. > > Hope that helps. > > On Friday, July 27, 2012 12:54:51 PM UTC-7, markcorv wrote: >> >> Yeah, but what if the limit was 10,000 installs or 50,000 for a one-time >> batch installation run. >> >> On Thursday, July 26, 2012 7:03:13 AM UTC-7, RichardC wrote: >>> >>> copy >>> install >>> copy >>> install >>> .. >>> .. >>> .. >>> >>> On Thursday, July 26, 2012 2:45:51 PM UTC+1, markcorv wrote: >>>> >>>> Hi guys is there a way to limit the number os times an app can be >>>> installed from an .apk. >>>> Something similar to the time-stamp, but instead of time-stamp to limit >>>> the time left , a sorta "install-stamp" for installations left. >>>> >>>> thnx >>>> >>> -- You received this message because you are subscribed to the Google Groups "Android Security Discussions" group. To view this discussion on the web visit https://groups.google.com/d/msg/android-security-discuss/-/06UlVz4SzjsJ. 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-security-discuss?hl=en.
