Just for the sake of argument, what do you think is the worst thing that a malicious app can do if one of its classes is loaded into another app that is using this technique? I understand there could be problems if you call methods on a loaded class and happen to pass it a reference to something sensitive. But just loading a class?
Doug On Thursday, March 10, 2011 11:32:31 AM UTC-8, Shri wrote: > > With Context.createPackageContext, you can use the > CONTEXT_IGNORE_SECURITY flag along with CONTEXT_INCLUDE_CODE to load > the code in the apk. You will then need to do your own security > checks, which is probably making sure that the .apk you are loading is > signed with the same certificate as your own. Yup, you do need to be > careful here to avoid creating security bugs. > <http://commonsware.com/training> -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
