security - Is this plan for preventing iPhone app client spoofing sound? -
I am preparing an iPhone app that communicates with more servers than HTTP.
I just want the app to be able to POST for some URLs on the server, not arbitrary HTTP client. Therefore I will set the server to validate only those posts, which includes the secret token, and set up the app to include that secret token. All requests that include all tokens will only be sent over one HTTPS connection, so that it can not be smeared.
Are you seeing any flaw with this argument? For example, is it possible to exclude the token from the compiled app using "string", hex editor, etc.? I'm definitely one. Will not store this token in Plist or other plain-text format
Suggestions for alternative design are welcome.
What exactly is the key that is trying to get the keys, and sells the product with a demographic objective, which are not encouraged to steal. The price of your product is so much that it is cheaper to buy than it is to find the key. Provide good service to your customers. These are all marketing and legal issues rather than technical.
If you embed a key, use a method, which requires each customer to search for himself, as each customer requires a different key. Do not want to find an attacker key and publish it, everyone can use it.
This tool or device can help hide the mystery for better and worse than the owner of the device. But, anything is brittle.
Comments
Post a Comment