PackageManager pm = context.getPackageManager();
try
{
PackageInfo info = pm.getPackageInfo( xxx.xxx.xxx.xxx,
PackageManager.GET_SIGNATURES );
Signature[] sig = info.signatures;
String sigstring = new String( sig[0].toChars() );
// Compare this
On Tuesday, January 15, 2013 2:56:20 AM UTC-7, b0b wrote:
Note that this is not super useful to do that, as all automated cracking
tools will detect your call with PackageManager.GET_SIGNATURES, and patch
it out.
We think we have a mechanism that makes this fairly difficult. It is
Hopefully you understand how to write such a tool: it seems that most
people who try to write these tools do not, and security by obscurity
sounds good until you get someone who pulls out a decompiler on your
app.
To be clear: the way to circumvent this will entail some degree of
static analysis,
By the way: this doesn't belong on android-developers, it belongs on
android-security-discuss. You'll probably get more publicity there
from people who know things about Android security (into which this
conversation has delved).
Kris
On Tue, Jan 15, 2013 at 1:05 PM, Kristopher Micinski
How does your anti-piracy mechanism deal with people who just copy the APK
around but don't actually modify it?
This seems like it would be the most common case anyhow.
On Monday, January 14, 2013 12:28:23 PM UTC-6, btschumy wrote:
We've recently implemented anti-piracy code in the
5 matches
Mail list logo
