Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #37302
| From | Daniel James <daniel@me.invalid> |
|---|---|
| Newsgroups | comp.mobile.android |
| Subject | Re: Android 6 |
| Date | 2017-01-04 13:40 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <VA.00000c25.19a8c3d6@me.invalid> (permalink) |
| References | (6 earlier) <449f715e-6c60-7051-98a5-bed4624d9a68@arnowelzel.de> <VA.00000c21.0051986f@me.invalid> <98f471b5-835a-7fd5-698a-cdc0e88929c2@arnowelzel.de> <VA.00000c23.0503f1e5@me.invalid> <60f194ae-3c1d-5179-2ade-25c34f5528ee@arnowelzel.de> |
In article <60f194ae-3c1d-5179-2ade-25c34f5528ee@arnowelzel.de>, Arno Welzel wrote: >> However, I'd say that some of an app's data is internal in nature, >> but some is external, and in that latter case the app developer >> *should* give the user the option to store it on external media. > > The problem is once again - security. > > As soon as you allow to store *any* data on an SD card this also > means that it is readable by *anyone* and not only the app involved. Yes, of course ... but we're talking about a removable SD card, here. There is NO POINT in trying to implement security within Android when the user can take the card out and mount it in a PC and read/write everything anyway. If you care about security in that case you simply encrypt the data. > Of course one could say, that it is the users responsibility to deal > with this. But how many people do really understand the implication of > putting data on a media which can be read by any app with storage > permission? I think that the fact that the card is removable sends a pretty strong signal to anyone who understands anything about data. >> In the (special) case of the camera app there will be settings -- >> e.g. the flash on/off/auto setting -- that apply to that app on >> that device and don't need to be accessed by anything else, but >> there are also the actual photographs that other apps might >> want/need to read. > > That's the reason why camera apps usually allow to store photos on > the SD card as well (or the "internal" media storage) so other apps > like "gallery" apps or e-mail apps can read them. Your comment seems a little confused ... Android apps can access the images in the DCIM directory in internal storage without any special permission, but can only access images in the DCIM directory on an SD card if they have permission to read external storage. My point, again, is that the files on external storage can always be read by mounting that storage on another device (PC, etc) so requiring special permission for that is daft. Files in internal storage can only be read by Android apps, so there would be some point in requiring permission for that, but ironically none is needed. >> An Android device's internal memory is a finite resource, and >> should be used sparingly. Apps should make sure that where an SD >> card is available they make provision for using it. > > No - only if it makes sense. Putting *everyhing* on an SD card just > because it is there, makes no sense. If you need this, then format the > SD card in Android as "internal memory" - then it is also protected > agains unauthorized access BTW. I wrote "make provision for using it", not "force the user to use it all the time". My point is that only the user knows what meets his own requirements, and the user should be in a position to decide how the available storage should be used. That requires app writers to write their apps so that they give the user the choice. Formatting the SD card as "internal" storage is not the answer if the user wants to be able to transfer data by removing the card and reading it in another device. It's not an everyday event, but when my first Android phone failed (the screen suddenly decided to display an intricate pattern of many colours, instead of text) I was very grateful for the fact that all my data were on an SD card because (a) some data had not yet been backed up, and (b) I could return the phone for repair without worrying too much about personal data being left in memory (it was impossible to do a factory reset without being able to read the screen). -- Cheers, Daniel.
Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Android 6 Bill <Billaboard@gmail.com> - 2016-12-22 17:21 +0000
Re: Android 6 The Real Bev <bashley101@gmail.com> - 2016-12-22 10:00 -0800
Re: Android 6 Bill <Billaboard@gmail.com> - 2016-12-23 00:23 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-22 19:30 -0500
Re: Android 6 Bill <Billaboard@gmail.com> - 2016-12-23 12:42 +0000
Re: Android 6 tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2016-12-23 11:58 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-29 13:43 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2016-12-30 15:34 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-30 22:33 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2016-12-31 13:27 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-04 08:59 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-04 13:40 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-11 09:00 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-15 18:23 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-15 21:20 +0100
Re: Android 6 AL <45364747@invalid.com> - 2017-01-04 10:06 -0700
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-11 09:00 +0100
Re: Android 6 tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-05 01:34 -0500
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-07 14:14 +0000
Re: Android 6 tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-07 13:09 -0500
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-08 18:18 +0000
Re: Android 6 tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-08 15:42 -0500
Re: Android 6 The Real Bev <bashley101@gmail.com> - 2017-01-08 17:11 -0800
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-08 20:19 -0500
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-09 23:55 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-11 18:07 +0100
Re: Android 6 Frank Slootweg <this@ddress.is.invalid> - 2017-01-08 21:34 +0000
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-09 23:55 +0000
Re: Android 6 Joerg Lorenz <hugybear@gmx.ch> - 2016-12-24 10:49 +0100
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-22 23:55 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-22 19:15 -0500
Re: Android 6 Joerg Lorenz <hugybear@gmx.ch> - 2016-12-23 05:46 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-23 00:15 -0500
Re: Android 6 Dave Higton <dave@davehigton.me.uk> - 2016-12-23 17:11 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-23 12:43 -0500
Re: Android 6 Dave Higton <dave@davehigton.me.uk> - 2016-12-23 21:22 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-24 14:29 -0500
Re: Android 6 Dave Higton <dave@davehigton.me.uk> - 2016-12-25 11:10 +0000
Re: Android 6 Piet <www.godfatherof.nl/@opt-in.invalid> - 2016-12-25 12:37 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-25 11:18 -0500
Re: Android 6 Dave Higton <dave@davehigton.me.uk> - 2016-12-25 20:28 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-29 12:02 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-29 23:45 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-29 18:02 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-30 22:24 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-31 11:55 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-04 09:04 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-04 10:14 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-11 18:11 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-11 13:05 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-13 17:23 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-16 15:35 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-17 05:39 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2016-12-30 15:34 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-30 22:26 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2016-12-31 13:27 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-31 11:55 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-04 09:11 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-04 13:40 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-04 10:14 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-11 18:12 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-11 13:05 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-13 17:24 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-15 18:23 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-15 21:30 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-16 15:42 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-16 15:35 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-17 05:44 +0100
Re: Android 6 Daniel James <daniel@me.invalid> - 2017-01-17 17:47 +0000
Re: Android 6 Bill <Billaboard@gmail.com> - 2017-01-01 01:05 +0000
Re: Android 6 tlvp <mPiOsUcB.EtLlLvEp@att.net> - 2017-01-02 02:08 -0500
Re: Android 6 David Taylor <david-taylor@blueyonder.co.uk.invalid> - 2017-01-02 08:01 +0000
Re: Android 6 nospam <nospam@nospam.invalid> - 2017-01-02 08:51 -0500
Re: Android 6 Bill <Billaboard@gmail.com> - 2017-01-02 20:41 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-04 09:18 +0100
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2017-01-04 09:14 +0100
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-29 14:05 +0100
Re: Android 6 nospam <nospam@nospam.invalid> - 2016-12-29 12:02 -0500
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-29 23:46 +0100
Re: Android 6 Dave Higton <dave@davehigton.me.uk> - 2016-12-31 20:18 +0000
Re: Android 6 Arno Welzel <usenet@arnowelzel.de> - 2016-12-29 13:47 +0100
csiph-web