hi Mark, so we should not use MODE_WORLD_READABLE in a content provider implementation? can you provide a link to the outline you mentioned.
On Fri, Jan 14, 2011 at 7:16 AM, Mark Murphy <[email protected]> wrote: > On Thu, Jan 13, 2011 at 10:05 PM, John Lussmyer <[email protected]> > wrote: >> So, all the documentation about making things "World Writeable" is a flat >> out lie? > > No. > > MODE_WORLD_WRITEABLE is available for a handful of methods on Context > (e.g., openFileOutput()) and for ParcelFileDescriptor (mostly used by > content providers, AFAIK). Ideally, there would be an equivalent > operation for standard Java file I/O within the area demarcated by > getFilesDir() -- I can only guess as to why setWritable() was dropped. > > MODE_WORLD_WRITEABLE on a file is a really bad idea, for the same > security reasons that world-writable files are a bad idea in any > operating system. > > Use any of the mechanisms that I outlined in a previous thread of > yours for inter-process communication on Android. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://github.com/commonsguy > http://commonsware.com/blog | http://twitter.com/commonsguy > > Android App Developer 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 -- 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
