All true, but unrelated.
I just found it curious that HTTPS would help mitigate any of the trouble that routers face from the Internet. I don’t see why that would be the case.
If you actually use the webinterface from the outside of your network then it’s safer to serve it over https. If you don’t, you can firewall off both http and https.
1 Like
Great news! Any specific ETA on that request form?
We’re testing the form this week. That sounds weird, I know, but it asks for things like your registration ID(s), IPs (and, hey, Boulder can’t take CIDR-formats yet!), and registered domains, and we’re not totally confident in the explanations/terminology being understandable, so we’ve got a couple organizations trying it out and providing feedback before publishing it officially.
5 Likes
@jcjones, is there a rough timeline for this form?
@jcjones Any news regarding the form?
No, no news. I’ve been pinging the appropriate parties. I’m afraid I’m not in this particular loop.
2 Likes
At the moment the windows ports don’t support the multiple subdomain option, so we have to get individual certs at the moment, but obviously it’s a struggle when we’re rate limited! Please up the limits.
1 Like
Will there be any criteria for who can use the form? I’m a private user with a lot of subdomains on IIS which isn’t easy to use the multiple subdomain cert method for currently due to the windows clients not supporting this, so I’d really like to use this form
it has been a while, any news about that form?
1 Like
I’m told that setting the rate limits for the initial testers I mentioned above hasn’t been smooth. (I’m out of that direct loop.)
I don’t have an ETA; I just keep pinging on everyone’s behalf. 
1 Like
Hey, thanks for the update 
is there a way to get news about that without nagging you?
i feel bad about that, but on the other hand that’s my only way to get up to date on this topic…
Any news about this form?
What about adding this form to https://letsencrypt.org/upcoming-features/?
Does anybody still believe this is gonna happen?
Still patiently(?) waiting… I registered a domain with the specific purpose of opening it up as a dyndns type service, and I wrote an ACME client designed to be run as a library by network clients and receive free TLS certificates using subdomains of that domain… I’m putting even odds on whether the domain name will expire before it either gets on the Public Suffix List or accepted through this form.
It’s now 5 months. It’s getting a bit silly.
3 Likes
You mean the fact that we are waiting for a feature to overcome beta-only-limits and we are still waiting after beta?
well beta stage is over
for me, hogging the router’s publicly-facing port 80 and 443 on the public IPv4 would definitely be a reason to scrap that router and return it to the store where i bought it, demanding a refund.
using those ports and not being able to forward them to a webserver running on the network behind the router means the router will be seen as defective for some people.