[yoyoma2]

Disclaimer: I'm not a networking person so please ELI5

There is currently a certificate problem as discussed here. As a temporary workaround I added a way for easyddup to use curl with http instead of https and it works.

Question1:
Would it be better to add a workaround using curl with --insecure https ? My limited understanding is that it's insecure because I'm not sure who I'm talking to but still encrypted so a man in the middle couldn't see/modify the contents of the dd-wrt build on the way to me? If the source is already unknown, isn't the man in the middle attack irrelevant?

Question2:
How long until this certificate problem is back to normal? I'm not even clear on the exact problem as easyddup can work on two url's (primary and a fallback) and the certificate on the fallback url works to navigate the builds but the final build download is on the primary url with the bad certificate.

[egc]

Usually the certificate is renewed in 1-3 days.

But now during the holidays it apparently takes longer.

[yoyoma2]

Thanks @egc for question #2. Nobody has an opinion on question #1 whether https with an unverified certificate is better than http? I read this answer before creating this thread but it doesn't really answer the question of which is better. There are degrees of insecurity...

[dale_gribble39]

It wouldn't surprise me if they are waiting for "the rest of the certificates" to expire to do an all-inclusive certificate for the entire domain, i.e. *.dd-wrt.com.

DD-WRT Forum Index -> Broadcom SoC based Hardware -> New Build - 08/21/2023 - r53396

[egc]

[yoyoma2]

Thanks for the replies guys. I'm not complaining about the wait for the valid certificate. Just trying to learn something.