There is NO Wildcard SSL Certificate for your DDNS Service (*.tplinkdns.com)
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.There is NO Wildcard SSL Certificate for your DDNS Service (*.tplinkdns.com)
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
They are free these days from Let's Encrypt so there is almost no reason not to. ESPECIALLY because all (I believe?) customers see this when they go to a DDNS link they bind, like examplecustomer.tplinkdns.com
https://cloudup.com/cEznrJKPc3b
This happens in EVERY browser, and with Safari it has to be done EVERY TIME (there is no whitelisting) you login to your router remotely. Obviously, local everything is fine, but you should have a real signed WILDCARD certificate to make extra certain of people's trust in TPLink and their commitment to security (SSL playing a big role in that, and browser warnings scare people away pretty fast).
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thank you very much for your feedback.
We went ahead and forwarded your concern and suggestion to our developers.
- Copy Link
- Report Inappropriate Content
@JoelS Was this ever resolved or should I just throw away my router?
- Copy Link
- Report Inappropriate Content
@blackadam Throw it out! Without this minor polish of an otherwise perfect device, it makes it a worthless router.
That, by extension, means they did not fix this peculiarity. You can use other DDNSes, but I find it surprising that *.tplinkdns.com doesn't exist in the router itself. Just a self signed cert which is impossible to whitelist because it changes all the time.
- Copy Link
- Report Inappropriate Content
@Tony Did you ever hear back about this?
- Copy Link
- Report Inappropriate Content
Bump
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@JoelS This likewise happens to me and I have to enter my password every time I get the notice that my router is "insecure" when a *.tplinkdns.com wildcard cert (which is free from Let's Encrypt) would solve this problem completely. This should be discussed by the staff at the very least. It's a very scary message that most people will misunderstand.
- Copy Link
- Report Inappropriate Content
Still waiting to hear back from @Tony on this one.
- Copy Link
- Report Inappropriate Content
Currently, there have not been any talks of that being available. One of our engineers did mention talking to our R&D and Product teams of various ideas, etc.
Feedback regarding security can be submitted here: https://www.tp-link.com/us/press/security-advisory/
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 7821
Replies: 11
Voters 0
No one has voted for it yet.