So I just got my RT-N66U today (replacement for a faulty one), set it up, and now it's up and working on my home network.
There were several annoying glitches in the firmware (.108), as people have noticed.
One I noticed that probably isn't that worrisome, but is notable, is that when you "log out" of the router admin page, it says you're logged out. However, if you go back there with the same browser, you're not really logged out.
I figured it must be storing my password in a cookie (or just a "trusted host" cookie, perhaps), and not making me log in each time. Logging out doesn't seem to actually DO anything... a good, secure router would clear that cookie.
Anyway, I did a before/after check to see if there was a new cookie set after visiting the router page, and there wasn't.
However, if I exit all instances of my browser, then restart the browser, then go to the router page, I'm asked for my password again. Rather curious... I wonder how the router is storing my logged-in state such that I'd see this effect.
I'm probably missing something ridiculously obvious - anyone know why a login session would be tied to a browser instance running, and I'd see no new cookie created by the router admin page?
- Tim
There were several annoying glitches in the firmware (.108), as people have noticed.
One I noticed that probably isn't that worrisome, but is notable, is that when you "log out" of the router admin page, it says you're logged out. However, if you go back there with the same browser, you're not really logged out.
I figured it must be storing my password in a cookie (or just a "trusted host" cookie, perhaps), and not making me log in each time. Logging out doesn't seem to actually DO anything... a good, secure router would clear that cookie.
Anyway, I did a before/after check to see if there was a new cookie set after visiting the router page, and there wasn't.
However, if I exit all instances of my browser, then restart the browser, then go to the router page, I'm asked for my password again. Rather curious... I wonder how the router is storing my logged-in state such that I'd see this effect.
I'm probably missing something ridiculously obvious - anyone know why a login session would be tied to a browser instance running, and I'd see no new cookie created by the router admin page?
- Tim