Agreed, I don't want to get into any trouble.
What about storing a hash of the ime. Then I am unable to identify
the actual ime that was used but I am still able validate.
On Nov 23, 10:53 pm, Fred Grott(Android Expert,
http://mobilebytes.wordpress.com)
fred.gr...@gmail.com wrote:
I agree
Do you guys think that asking user to enter Order number is going to
be too much hustle?
On Dec 6, 7:00 am, jax jackma...@gmail.com wrote:
Agreed, I don't want to get into any trouble.
What about storing a hash of the ime. Then I am unable to identify
the actual ime that was used but I am
I am still trying to get my head around this.
How would I go about generating the hash code? I am intending on
using the ime.
Do I need public private keys?
confused...
On Nov 15, 3:39 am, Pooper code...@gmail.com wrote:
What you can do is make your user enter serial #, the serial number
How do you get hold of the users google account from your app?
On Nov 17, 10:03 pm, Streets Of Boston flyingdutc...@gmail.com
wrote:
What would happen if someone gets a new android phone? The app's
authentication will fail.
You should hash/key on the user's google-account, the same key that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jax wrote:
[...]
How would I go about generating the hash code? I am intending on
using the ime.
If you're in the UK and you want to keep track of customers' IMEIs, you
may need to get legal advice --- there's a good chance you'll be liable
under
I agree getting IMEI to store on a server not in telecoms control bad
idea..both security wise and legally..
Fred Grott
Android Developer | http://mobilebytes.wordpess.com |
http://twitter.com/sharemefg | http://www.linkedin.com/in/shareme |
gtalk: fred.grott | skype: fred.grott | googlewave:
Unless I missed it above, no one has published a method to check
whether an app was downloaded and not refunded by Google Checkout.
Without this check, none of the above code will be of any value.
Google please provide us with something we can use - devs work hard to
improve the platform. Pirates
What would happen if someone gets a new android phone? The app's
authentication will fail.
You should hash/key on the user's google-account, the same key that is
used by Android Market (you can download paid apps as often as you
want - once you paid for them - based on your google-account)
On
I've sure seen a lot of posts lately about piracy and protection, and
really IMO I think the anxiety about this is a little too high at the
moment.
The fact is no matter what you do, you will have piracy. If you spend
all of your time fretting about it you are never going to get
anywhere. Also,
Disagree. The problem with Android Market is that it doesn't even
attempt to solve the piracy issue. I agree that 100% protection is
impossible but devs right now have 0% protection.
Don't believe me? Search for any popular Android app on google - you
will find as many links to pirated apk's for
If your looking at it from this perspective, then maybe you shouldn't
continue developing?
Unless your developing a program that is SaaS where data is kept
primarily on a server, your /not/ going to keep your program from
being pirated.
I don't agree with people who are pirating apps, but I also
No anti-piracy system is perfect. Thats why I said 100% protection was
unachievable.
What I am saying is we need some way to get over the hump of 0%
protection. Even if we just had a shared system where we had the level
of protection of apps, e.g. MyBackup and CoPilot currently have, then
at
You know the piracy rate of MyBackup and CoPilot are probably much
higher than 4:1 right?
I'm not sure where your get your statistics from, but while you notice
apk files are easy to fine - amoung the easier are those exact apps
that you think have a good level of security.
The point is they
By reducing the number of pirated copies, you are not necessarily
increasing your paid copies.
I'd rather see it go from 4:1 to 4:4 or even 4:1 to 1:4. Just
saying... :)
I'm going to go do some developing now. :)
On Nov 17, 10:20 am, admin.androidsl...@googlemail.com
Using the unique ID (hash) of the phone, register it with your web
service on install.
Then employ PKI to authenticate your app on each launch.
On your web service sign a string containing the hash, timestamp, and
a short expiration timestamp.
Then have your app use your public key (in the app) to
What you can do is make your user enter serial #, the serial number
could
be a hashing function that you come up with that takes the device id
(could be the imei number)
the application could then check if the serial/hash code matches for
that device. This would
require your customer to send you
We (AndAppStore) already have a system available which you can find
details of at http://andappstore.com/AndroidApplications/licensing.jsp
It's not tied to our purchasing system, so you can use it to generate
licenses from your own site if you wish.
We always welcome feedback so if you have any
What u want to do is to tie your app to one device
How u do it up to u
On Nov 14, 7:12 am, jax jackma...@gmail.com wrote:
I am wondering how I might go about securing a paid app on Android.
I am thinking of selling the application from my own website via
PayPal, however, how will I stop
Yes, that is why I have posted the question because I don't know how
to do it.
Has anyone done this before or know of a method for achieving this?
On Nov 14, 10:23 pm, Andrei gml...@gmail.com wrote:
What u want to do is to tie your app to one device
How u do it up to u
On Nov 14, 7:12 am,
TelephonyManager telManager = (TelephonyManager)
context.getSystemService(Context.TELEPHONY_SERVICE);
telManager.getDeviceId() will give you the device ID (IMEI for cell
phones). This is how you can tie your application to the device. The
rest (license generation, your program - server
20 matches
Mail list logo
