Archive for January 20, 2017

Microsoft Goes After Chrome Users With A Pop-Up Ad

Posted in Commentary with tags on January 20, 2017 by itnerd

Microsoft since Windows 10 appeared have done some really invasive things to collect data. And despite some privacy related changes that are coming soon, they seem to want to expand upon how invasive they are. Exhibit A on that front is the news that Google Chrome users on Windows 10 are apparently being treated to a new experience: a pop-up ad. Here’s the details via PC Magazine:

If you have Chrome installed and the icon present on the Windows Taskbar, chances are you’re going to start seeing a pop-up advert appear suggesting you install Microsoft’s Personal Shopping Assistant Chrome extension. Microsoft touts it as “Your smart shopping cart across the web.” Opting to install the extension results in Microsoft monitoring which products you’ve searched for and viewed while using Chrome, and then offering to compare those products to find the best price. There’s also alerts when prices change, and the ability to track products across all your devices. Of course, Microsoft will make money if you opt to purchase any products using the Assistant.

Well. Isn’t that special. I’m sure that Microsoft things this is a great idea, but users sure don’t. I guess that whatever data Microsoft collects is worth annoying their user base.

Viral Chinese Selfie App Meitu Phones Home

Posted in Commentary with tags , on January 20, 2017 by itnerd

The Meitu selfie app that is the app to have on your phone at the moment aggressively your personal data researchers say. Said researchers have discovered that the app harvests information about the devices on which it runs, includes invasive advertising tracking features and is just badly coded overall:

Meitu, a Chinese production, includes in its code up to three checks to determine if an iPhone handset is jailbroken, according to respected forensics man Jonathan Zdziarski, a function to grab mobile provider information, and various analytics capabilities. Zdziarski says the app also appears to build a unique device profile based in part on a handset’s MAC address. “Meitu is a throw-together of multiple analytics and marketing/ad tracking packages, with something cute to get people to use it,” Zdziarski says. Unique phone IMEI numbers are shipped to dozens of Chinese servers, malware researcher FourOctets found.

Well, that’s pretty bad. My advice is to pull it from your phone. Like right now. Clearly this is an app that cannot be trusted. Oh by the way, this is a perfect example as to why you should never jailbreak your phone because the fact that the app checks for that is really really bad.

 

Security Researchers Call On The Guardian To Retract WhatsApp Story

Posted in Commentary with tags on January 20, 2017 by itnerd

You’ll recall that I posted a story that detailed a story from The Guardian on what it called a “backdoor” in WhatsApp. Some security researchers have called out The Guardian for what they concluded was irresponsible journalism and misleading story. Over three dozen security researchers including Matthew Green and Bruce Schneier (as well as some from companies such as Google, Mozilla, Cloudflare, and EFF) have signed a long editorial post, pointing out where The Guardian’s report fell short, and also asking the publication to retract the story.

So, is this a backdoor or not? The lack of a definitive answer on this leaves users in limbo. Maybe both sides should work together to clear the air on this. And for bonus points, maybe Facebook who owns WhatsApp should get involved as well?

Rogers DOCSIS 3.1 Rollout Hitting Snags Because Of Modem Issues

Posted in Commentary with tags on January 20, 2017 by itnerd

You might recall that I recently got a new modem/router from Rogers as part of their rollout of DOCSIS 3.1 which when completed, will enable Rogers to offer faster speeds for their Internet offering. But there appear to be significant signs that all is not right with this rollout. To get the most accurate idea of what is going on, I have been monitoring Rogers own community forums, Red Flag Deals, and DSLReports, and cross referencing info with sources that I have within Rogers both at the retail level and within Rogers corporate that speak to me “off the record.” Here’s what seems to be going on.

The version of the Rogers modem/router that I have seems to have an issue where the 2.4 GHz WiFi band causes slower speeds. This link has the details. This was mitigated to a degree via a firmware update to the modem/router for some. Also, having the modem/router 6 feet away from any other router that you might be using helps with this as well. But this didn’t help some users. There was also an issue getting gigabit speeds if you put the modem/router into bridge mode which again was mitigated with a firmware update. But at some point, it must have been determined that there was a hardware issue as well. Thus Rogers apparently released a newer version of this modem where there is a black dot on the packaging and the modem itself so that you (or more likely Rogers employees) can tell the difference between the original modem and the black dot version. This new modem apparently had extra shielding to mitigate the issues with the 2.4 GHz band. But now it seems that there is some sort of “recall” on that modem. The quotes are around the word “recall” because that is what people are using in places like DSLReports, but it is not quite correct. A post on the Rogers community forums which I confirmed with my sources both at the retail level and corporate level of Rogers indicates that there is additional testing going on of these modems. As a result, fully tested modems are replacing modems that are already in store stock. For people who have modems in service, there is no need to swap the modem unless you have an issue. Thus this isn’t a “recall” as such.

Now, the issue that Rogers seems to be having with the Hitron modem/router is clearly going to have a downstream effect in terms of getting DOCSIS 3.1 and IPv6 rolled out. My sources inside Rogers have confirmed that. But that’s not going to be the thing that Rogers has to worry about most. If you look at Red Flag Deals, DSLReports, and Rogers community forums, there is a fair amount of frustration out there that beyond the modem issues. The most common thing appears to be that people aren’t getting the speeds that they are paying for and resolution to their issues doesn’t seem to be anywhere in sight. This is something that I experienced when I had my issues with Rogers Ignite Gigabit Internet which were ultimately solved, likely because of the fact that I am a blogger with a significant following. If I were Rogers, that is what I would worry about more. Yes they need to get their modem/router issues sorted as the optics of that are not good. But the customer perception that Rogers can’t roll out new tech without it going sideways is likely going to make Bell Canada lick their lips because these problems open up the opportunity for them to steal customers from Rogers.

I will be keeping an eye on this and reporting back on any new developments as clearly this is an evolving story.

UPDATE: There’s a page on the Rogers community forum that lists the outstanding issues with the modem/router referred to in this story.

Oh The Irony: Windows 10 IPv6 Bug Stops Microsoft’s IPv6 Rollout

Posted in Commentary with tags on January 20, 2017 by itnerd

Microsoft is apparently moving from the IPv4 standard of network addressing to the much more modern IPv6 standard. But the rollout has hit a snag. According to Marcus Keane via a blog post, a bug in Windows 10 is one item of many that is putting the brakes on this rollout:

The second issue slowing us down was a DHCPv6 bug in Windows 10. This affected both stateful and stateless schemes. Needless to say, IPv6-only expansion was impossible until we resolved this issue. We have reported it to the product group, and they are duly working on a fix.

So in effect, one part of Microsoft is waiting on another part of Microsoft to fix an issue with a Microsoft product. That’s incredibly ironic.

But this does bring up a few discussion points aside from the fact that Microsoft can’t get it’s own OS working with IPv6 properly. Many companies are going to have to go to IPv6 at some point in the near future. Consumers will as well. The fact that one of the biggest software companies in the world is struggling with this, what hope do the rest of us have? Another point, IPv6 is not backwards compatible. That means that the complexity to pull off this transition skyrockets. Perhaps if it were backwards compatible, there would be less pain experienced by those who want to make the switch? In any case, watching how Microsoft navigates this will be an interesting case study for anyone who is thinking of making this switch.