Linked by David Adams on Thu 24th Jun 2010 16:22 UTC, submitted by Governa
Privacy, Security, Encryption About 20 percent of third-party apps available through the Android marketplace allow third-party access to sensitive data, and can do things like make calls and send texts without the owners' knowledge, according to a recent security report from security firm SMobile Systems. There's no indication that any of the highlighted apps is malicious, but the report does underscore the inherent risks of a more open ecosystem as opposed to Apple's oppressive yet more controlled environment, with every app being vetted before availability.
Thread beginning with comment 431341
To read all comments associated with this story, please click here.
From a security firm
by Ikshaar on Thu 24th Jun 2010 16:52 UTC
Ikshaar
Member since:
2005-07-14

Shocking news at 11... PEBKAC.

At least they agree this is not an Android problem per se, just a common problem... there is users. lol.

Reply Score: 1

RE: From a security firm
by Kroc on Thu 24th Jun 2010 23:00 in reply to "From a security firm"
Kroc Member since:
2005-11-10

PEWTD - Problem Exists With The Designer. Security is a process, not a feature, and the user should remain safe and in control should the worse happen because the system is designed as such. You could blame the user for causing a car crash, but you shouldn’t blame them if the car’s engineering fails to protect them; that’s down to the design of the car, not the user.

Reply Parent Score: 2

RE[2]: From a security firm
by aesiamun on Fri 25th Jun 2010 03:10 in reply to "RE: From a security firm"
aesiamun Member since:
2005-06-29

The user chooses to install an application and is given a list of what the app has access to. The user has the choice, if they choose to continue then that is their decision.

Reply Parent Score: 2

RE[2]: From a security firm
by kaiwai on Fri 25th Jun 2010 05:25 in reply to "RE: From a security firm"
kaiwai Member since:
2005-07-06

PEWTD - Problem Exists With The Designer. Security is a process, not a feature, and the user should remain safe and in control should the worse happen because the system is designed as such. You could blame the user for causing a car crash, but you shouldn’t blame them if the car’s engineering fails to protect them; that’s down to the design of the car, not the user.


But how much is too much when it comes to an application giving off warnings before an end user does something? or how restrictive should it be where there is a weighing up between keeping the individual safe and giving maximum flexibility? at some point one has to take off the training wheels and allow the user to stay upright on the bike - and yes that might mean going into the gutter or straying into the road and getting hit by a car.

There is a thing called personal responsibility that is sorely lacking these days - time that end users exercised that instead of being mindless click and drool mouth breathers.

Reply Parent Score: 2