I've upgrade to the beta on an 88u. The GUI is noticeably faster. This is especially evident when I pull up a list of connected clients. That used to take a significant amount of time. Now it is very fast.
I have noticed that chrome now says it is not a secure link when I sign on to the GUI. I get an i with a circle instead of a padlock. Does that mean it is really insecure, or that it needs a new certificate? Is this anything that will be fixed in future software builds?
Are you using HTTPS(you probably have to enter sth like x.x.x.x
:8443 or router.asus.com
:8443, number can be different)? If so, follow the second post on this
link.
However, I think what you are getting is Google's attempt to make website owners change from their websites from using insecure HTTP to HTTPS(sorry, can't find blog for you). Normally your router WebUI uses HTTP by default, which make google chrome reports that it as insecure. HTTP is insecure as it sends packets without encryption which means your information(router's password and settings) could be monitored by someone else in LOCAL NETWORK(if you
disable Web Access form WAN). I'm not sure how it can be done, but it is possible that if one of your devices in local network is infected, it can be used to gather your information that you send to your router. However, you don't think you will ever have an infected device and you have Web Access from WAN turned off, HTTP should be quite safe.
HTTPS, on the other hand, is more secure version of HTTP. It can be set by going to Administration -> Authentication Method -> Both or HTTPS -> apply -> access your router with the same link as before but with ":8443" at the back. Yet, this will cause Google Chrome to report even more as insecure. This is because the key(TLS) used to encrypt data is self-signed(instead of being signed by trusted company); however, it is way safer than HTTP. Then you have to follow this
link same as above link. This will stop Google Chrome reporting that it is unsafe.
I don't know that much about security, but HTTPS is way safer than HTTP, but HTTP is safe enough for many cases. I personally use HTTPS to be sure. And the reason Google Chrome is doing this is mostly likely related to some websites that ask for personal information(such as credit info), but use insecure HTTP protocol which can be easily spied through internet.