Malware from Google Market menaces Android users Google has yanked more than two-dozen mobile apps from its Android Market after security researchers reported they were laced with malicious code that transferred user data to servers controlled by attackers. As many as 120,000 Android users downloaded the trojans before they were detected, according to Tim Wyatt, a researcher …
In the past two months, many of my users are getting these same types of trojans just from clicking on the top responses to Google Searches let alone many of the banner ads right on the top of the Google page!
Granted, I wish my users "supervisors" would actually discipline their employees for recreational web browsing on company computers, but that is another topic that doesn't involve the content that Google is providing to the world!
Are you actually using a WP7? I am currently using iPhone, Android, and WP7. Out of the three I far prefer the interface and experience of the WP7, the app store and hardware of the iPhone, and just about nothing about the Android experience...yet. I will give the Android a fair shake before writing it off. Perhaps having an App ask me for access to my Contacts sort of soured me early.
As for SSH client? I personally do that where I can hammer a keyboard...and then no client is needed, just the ability to type quickly...which with mini touch keyboards is not it. Are you logging in to see if a process is finished or actually doing terminal work?
A friend of mine blasted away iOS and is running uPhone. Maybe you ought to check it out.
.........refusing or restricting apps (free or paid for) that demand permissions that are totally unnecessary for the function that they allegedly perform. For example, why do so many wallpaper apps or ringtones need/demand permissions that mean they in practice would own your phone's arse? Those types of apps do not need administrator and/or communications permissions. Devs submitting apps that make such demands where there is no obvious functional need for the app to have that degree of system access should, at the very least, be facing some very blunt questions from Mountain View.
What does an Android developer do if they want their app to behave nicely when a phonecall is received whilst the app is running? Judging by the permissions required by many in the Market I think their only option is to
"READ PHONE STATE AND IDENTITY
Allows the application to access the phone features of the device. An application with this permission can determine the phone number and serial number of this phone, whether a call is active, the number that call is connected to and the like."
I have no way of knowing if an app will ever read the serial number or use its permission to determine who I call and who calls me! Wouldn't it have been better to design the OS so that apps could register to be alerted when the phone rings, rather than having to listen for it themselves? That way they would not need to request any unnecessary privileges.
Having lots of option for telling the user what "features" are used when there is little knowledge on the end user side of what each option really means. This is a perfect case where less really is more. Google needs to look at what features they "warn" about and limit it to 2-3 options. No more.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
