Over the weekend news that the newest version of the popular Nexus 7 does not have official Google Wallet support. When purchasers of the tablet went to download Wallet from the Play Store they found the download not compatible with their tablet. Now before anyone suggests that this has something to do with Android 4.3 Google’s own Director of Product Management for Google Wallet, Peter Hazlehurst told the folks over at Android Police that it’s because the tablet doesn’t have a secure element. This is needed in order for Google Wallet to protect your information. Here’s what he said:
“Hi folks, there is no Secure Element in the new Nexus 7 (or the HTC One Play Edition) which is why Google Wallet isn’t supported.”
Pretty simple and straight forward. Basically without this secure element to store your credit card and billing information safely, having the app on there isn’t safe. Whether or not this has anything to do with the LTE version coming to carriers or not is anyone’s guess. Does this mean that Google’s attempt at paying via NFC is going to go the way of Google Reader? We’re not sure. Regardless, those of you buying the newest generation of the Nexus 7 in hopes of using it as a way to pay, will sadly be disappointed.
source: Android Police
Security wasn’t really a big part of Google’s Android 4.3 announcement, which might sound odd considering how big of a deal device security has been in these past few weeks. However, that doesn’t mean Google hasn’t done anything to target malicious apps; instead of loading up Android 4.3 with beefy security features, they took those security features and implemented them into Google’s Play services application that’s updated separately from Android versions.
Android users are familiar with the idea of app permissions since installing or updating apps triggers a notice about what permissions an app requires. However, just knowing what permissions an app requires can be limiting since users have to accept all or none of the permissions. Android 4.3 appears to have changed that as users have found a “hidden through obscurity” setting that gives users the ability to turn individual permissions on and off for an app.
We all thought the SIM card was un-hackable, but think again. German cryptographer Karsten Nohl is going to present some interesting findings at the Black Hat security conference in Las Vegas on July 31. He found encryption and software flaws that could affect millions of SIM cards. His team tested approximately 1,000 SIM cards for vulnerabilities and found that hackers can remotely infect a SIM with a virus that sends premium text messages. That’s not all, they can redirect or record calls and possibly commit payment system fraud. “Give me any phone number and there is some chance I will, a few minutes later, be able to remotely control this SIM card and even make a copy of it,” Nohl says.
Now it doesn’t look like this affects all SIM cards. It all comes down to the encryption standards chosen by different countries. Noel said, “Different shipments of SIM cards either have [the bug] or not, it’s very random.” Noel did find about 25% of the cards he tested to be hackable, but figures about an eighth of the world’s SIM cards to be vulnerable. That’s about a half a billion mobile devices.
It looks like the NSA is about to have a rival in the spying business— good old Mom and Pops.
Got a feeling your kids are up to no good? Want to monitor your kids’ data usage? Need to lock your son out of his phone because he won’t do his homework?
Good news for you— Verizon has announced “FamilyBase,” which will let parents (or account administrators) monitor and limit calling, texting, app usage, app purchases, as well as set time restrictions and review contact lists. The feature to remotely lock their devices on demand is also available.
Big Red is making the service available for $5/month for up to 10 lines— it’s only for Android devices running 2.1 or higher. (So pretty much all of you can use it.) To set it up, parents can visit familybase.vzw.com, or by calling SAFE, or by texting SAFE to #7233. The apps are also available in the Play store.
Check out the press release after the break for more info.
After all the commotion about the latest major security vulnerability to Android devices, you would think things on the security side of the platform would quiet down for a bit. However, that’s not the case, as a Chinese site has posted details about an application exploit similar to Bluebox’s earlier revealed loophole that would allow apps to avoid signature verification to run malicious code on an Android device. However, the vulnerability was found in older code that was replaced with a security fix, so Google was already aware of the problem and has patched it up as soon as they were made aware of it. It may take awhile for that type of security patch to hit devices in the wild, but like the Bluebox vulnerability, Google has done all they can to take care of things on their end.
If you want to read up on the specifics of the vulnerability, hit the links below. It’s a pretty small, complicated vulnerability that would be pretty tricky for malware to pull off on most devices, but it’s interesting nonetheless.
source: Sina Blog
via: Android Police
Once again, the CyanogenMod team seems to be on top of things, as they just released version 10.1.1 of their famed firmware. A post on their blog today issued a follow-up to the general release. They pointed out that the CM 10.1.1 build is simply a security bug-fix release on top of their previous release, the 10.1.0.x code-base. Check out the full blog post after the break for more details.
Last week we told you about a new security threat that was uncovered by Bluebox. It was actually uncovered several months ago and Google was informed about it in February. At the time of the posting, Google didn’t make a comment, but it appears Google did indeed patch the hole back in March.
Gina Scigliano, Google’s Android Communications Manager, did “confirm that a patch has been provided to our partners – some OEMs, like Samsung, are already shipping the fix to the Android devices.”
There is only one problem. The patch is in the hands of the OEMs and it’s up to them to update devices. Anyone want to take a guess as to how long it will take for all Android devices to receive the update? Have no fear because there hasn’t been one case of the exploit taking place. Google regularly scans the Play Store for such things and nothing has popped up.