delajed
join:2008-06-02
Etobicoke, ON | Web Admin access - HTTPS; what about SSL? I've enabled both web access and https on the admin settings. However when trying to access the router I'm being told that the certificate is invalid?
I'm just concerned what the best route I can take to ensure the security of my network. | |
|
 public
join:2002-01-19
Santa Clara, CA
 ·DSL EXTREME
| Re: Web Admin access - HTTPS; what about SSL? said by delajed  :I've enabled both web access and https on the admin settings. However when trying to access the router I'm being told that the certificate is invalid? Because it was issued to the vendor and not to your specific advice. Just add an exception for the ip of your router. | |
|
upb
Premium
join:2004-03-15
Carriere, MS
·AT&T Southeast
| It's a self-signed certificate, meaning that you'll have to tell your browser to accept it, either temporarily or permanently. In either case, the encryption still works, and that's the main point of making an https (TLS/SSL) connection to the router. Since the router's userid and password are supplied over an encrypted connection, it makes you much more secure against eavesdroppers. I also change my web server to use a non-standard tcp port, so that the people / worms which are always checking out ports 80 and 443 will be left in the dark. | |
|
Bill_MI
Bill In Michigan
Premium,MVM
join:2001-01-03
Royal Oak, MI
 ·Comcast
| Good info already - communication is still secure. A little about such a "self-signed" certificate...
What's lacking is a 3rd reputable party saying: "Yep, this is your router you're talking to". With banking sites being imitated this is a critical "authentication" portion. How important is it for your router? Are you worried about an impostor that looks like your router stealing your password? THAT is the exact risk. | |
|
delajed
join:2008-06-02
Etobicoke, ON
| Agreed. Thanks for all the information. What I was worried about was giving away access (login/password) to my router, whenever I accessed it remotely. I know that using HTTPS encrypts those fields, but was just concerned when I was prompted with an "invalid certificate" popup. | |
|
|
|
|
