And this is why I won't be buying Google Wifi. Really poor design that it reverts to factory defaults on something like this.
Not to mention the trust issues with Google.
"
Sounds like you do not understand the Google WiFi (GW) and why it is a major step forward. This is a bump on the journey. Google has built in the Google WiFi a hardware token that is tied to the boot image. The boot image is then tied to your Google account.
Early this week a major security issue was discovered with Cloudflare. Ironically the security issue was discovered by Google. This is a huge issue as many, many companies used Cloudflare for Internet security. Very private data was leaking. In response the Cloudflare certs were revoked causing people to re login into their accounts including Google but also notice wife was knocked out of her FB account.
The Google WiFi security is built to stop use if the chain of integrity is broken. I do think Google needs to think what should happen when integrity is broken. In some ways I get the wipe when integrity breaks down. You do NOT know if a port forwarding command was executed on the GW illegally. But probably needs some middle ground.
The GW is a device that comes with a service in many ways. I think of it more like Google and what they did to spam with Gmail. Google basically ended spam by building perdictive models for spam and blocked. It is similar here.
The major DDOS attacks of late have been coming from regular people inside their homes with their iOT they just do NOT realize it. I assume the GW goal is to end.
I replaced an Airport with the GW. I believe the old model of network routers just does not scale with our new world. It is just too complicated and now we have huge risk as we have our smoke detectors, thermostat, cams, etc all on the Internet and needs to be secured.
In security it is easy to open the door. Someone is having trouble getting to a site or something well just open the door and no complaints. I believe Google is creating a far better closed door but with it there are hiccups and this was one.
Would love to say the Cloudflare issue is unusual and started to type exactly that. But to be honest it is not. Ironically Google also released a proof of concept on breaking SHA1 THIS week. SHA1 is a foundational hashing algorithm. Sites like GIT for example are heavy users of SHA1.
Google posted two PDFs with the exact same signature but the two documents are different! This is why we must move to a better network security model then the past.
BTW, another example is CA transparency. On this one Google became their own CA root. Non of the other platform companies have gone this route. But this makes 100% sense. It limits the attack surface for Google. It allows them to control security and not be dependent on anyone else.
My home security is important to me and I do not believe anyone is in a better position to protect then Google.
If curious here is some additional info on a couple of the subjects I shared.
"Google Just Discovered A Massive Web Leak... And You Might Want To Change All Your Passwords"
https://www.forbes.com/sites/thomas...nt-to-change-all-your-passwords/#702de3a23ca3
"Google just cracked one of the building blocks of web encryption (but don’t worry)"
http://www.theverge.com/2017/2/23/14712118/google-sha1-collision-broken-web-encryption-shattered
"Google launches root certificate authority"
https://www.theregister.co.uk/2017/01/27/google_root_ca/
The root cert authority (CA) is really,really important. Otherwise security is reliant on other CA roots which can be an issue. The cert is what assures you that a site is what they say they are. So if you go to
www.amazon.com and enter your credit card you really want to be sure it is really Amazon. To make that work we allows different roots and if root is ok then anything else under the root is assumed to be real. But EVERY company on this planet was dependent on the integrity of the roots until now.
Google is the only one of the platform companies that can assure the integrity of their certs because they are the root provider and would assume will allow no others.
There has been a push for transparency so when a rogue root issues a cert say to disney.com it has to be shared. That is good but we had one of these root CAs issued a illegal cert and nobody noticed for 24 hours! It just takes less than a second to be hacked.
"What is Certificate Transparency? How It helps Detect Fake SSL Certificates"
http://thehackernews.com/2016/04/ssl-certificate-transparency.html
I heavily prefer for it to ONLY be in Google's hands. So here is for example in Firefox what each of the major sites and who is the root. The root for these has to be trusted. Google now the two are the same as Google is their own root.
https://mozillacaprogram.secure.force.com/CA/CACertificatesInFirefoxReport
BTW, as you can see Amazon is also a root.
[doublepost=1488113109][/doublepost]
>Google said the issue with its Google Accounts engine also caused some Google Wifi and OnHub devices to automatically revert to factory settings.
This is a bit disturbing to be honest. A local device should NEVER lose its configuration because of an issue on the network. ESPECIALLY a networking device
This is NOT true! If there is a security issue the network device should absoultely shutdown! Please do not write things so wrong as you are giving very poor advice.
You are ONLY looking at your Internet working. The other side is your Internet working securely. What happened is Cloudflare had a HUGE security issue discovered this week. Certs were revoked and why you had to relogin in Google account and FB account and others.
The Google WiFi is implementing the next generation of security which we need. It has a hardware token inside locked ot the boot image to the running image to your Google account. If this chain of integrity breaks down the device should stop!
This problem is soon to be in the past as Google has taken the unusual step of becoming their own CA root. This means they are no longer subject to third parties security problems.
"Google launches root certificate authority
Cutting out the middle man"
https://www.theregister.co.uk/2017/01/27/google_root_ca/
"Google Just Discovered A Massive Web Leak... And You Might Want To Change All Your Passwords"
https://www.forbes.com/sites/thomas...nt-to-change-all-your-passwords/#26b5d8223ca3