Thanks for your responses, Mark. I understand your reasoning. I guess I'm just confused how there are so many "app protector" applications in the Market if this isn't officially supported. Are they all using security holes to listen for application launches and protect them via password?
On Oct 26, 2:01 am, Mark Murphy <[email protected]> wrote: > On Tue, Oct 26, 2010 at 1:58 AM, Mark Murphy <[email protected]> wrote: > > And if you are able to pull that off, you are exploiting a security > > hole. Somebody else could create an app that does what you propose, > > but the only way to get the password is to pay a ransom. > > To clarify: I don't have a problem with the aims of your app. However, > that strikes me as something that should be more tightly integrated > with the operating system (e.g., part of the device admin APIs), with > appropriate permissions or something so users understand that > installing this application may lock them out of app access. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://github.com/commonsguyhttp://commonsware.com/blog|http://twitter.com/commonsguy > > Android 2.2 Programming Books:http://commonsware.com/books -- You received this message because you are subscribed to the Google Groups "Android Developers" group. 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-developers?hl=en
