router.asus.com vs 192.168.50.1

andyross

Occasional Visitor
Just an update that in bugzilla, they are considering simply removing asus.com from that list in FF 105 as a temporary fix.
 

drinkingbird

Senior Member
Just an update that in bugzilla, they are considering simply removing asus.com from that list in FF 105 as a temporary fix.

In the meantime you could enable https access to the router (set it to HTTPS or BOTH). You can use the default 8443 port or change it to 443 for ease. Technically more secure anyway. Of course then you may get the "this site is not secure" and you'll need to install the certificate if you don't want to see that screen every time.
 

andyross

Occasional Visitor
When you change the mode, does it require a router reboot, or does it take effect as soon as you log out?
 

andyross

Occasional Visitor
According to someone who downloaded the latest Firefox 105 (should be available through internal update soon), it does have the quick patch for the router.asus.com issue.
 

andyross

Occasional Visitor
In the latest Bugzilla update, they added code to explicitly exclude asus.com no matter what the HSTS list has. But someone also posted that it seems as if Asus removed their entry from the latest version of the list.
 

andyross

Occasional Visitor
It looks like Asus has formally removed their submission and Google is updating the list to prevent issues with Chrome and related browsers.
Hi all, we received confirmation from Asus Security to proceed with manually removing their HSTS preload list entry at this time, and landed that removal in https://chromium-review.googlesource.com/c/chromium/src/+/3910704. We're merging that removal back to Chrome 106 and 107 ahead of releases next week to hopefully prevent any breakage for Chrome clients. For downstream consumers of the HSTS preload list this means that you should be able to stop manually patching out this entry soon, once you pull in the latest version.
Asus will separately stop serving the dynamic HSTS header soon; meanwhile there may still be some clients that visit the bare asus.com domain and pick up the dynamic entry. Such clients may continue to have issues with the router subdomain, but from what I've read this case seems rare (which may be why it didn't serve as an early breakage signal before Asus requested preloading).
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top