Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conditional ACME on demand generation #505

Closed
bluecmd opened this issue Jul 10, 2016 · 4 comments
Closed

Conditional ACME on demand generation #505

bluecmd opened this issue Jul 10, 2016 · 4 comments

Comments

@bluecmd
Copy link

bluecmd commented Jul 10, 2016

Hi,

I'm trying to use traefik in a setting where I have a wildcard domain. This is the current behavior:

Client requests https://www.mydomain - www is generated via ACME and www is routed to the correct backend
Client requests https://dummy.mydomain - dummy is generated via ACME and then 404 is sent back as there is no frontend matching this.

What I would like to avoid is that a certificate is generated in step 2. The current behavior makes a DoS attack quite easy as one can just send a handful of Host commands to drain the ACME quota.

I suggest a configuration option that will simply either just close the connection, or maybe present a default certificate in this case.

@emilevauge
Copy link
Member

If you don't have front-end matching, traefik already doesn't generate any certificate.

@bluecmd
Copy link
Author

bluecmd commented Jul 10, 2016

That's not the behavior I was seeing.

What's the connection behavior expected in that case? Connection drop?

@bluecmd
Copy link
Author

bluecmd commented Jul 10, 2016

Another issue I've been thinking about but haven't been able to test yet is when the frontend matches, but the backend doesn't. If you have something like {job}.cloud.mydomain.tld that is using Kubernetes, but there is no {job}. This is actually the problem I'm trying to solve.

I'm not 100% I understand how the traefik learns backends from the various sources, so if it's totally insane let me know.

@emilevauge emilevauge added the bug label Jul 11, 2016
@emilevauge
Copy link
Member

Ouch, due to an update on gorilla/mux gorilla/mux@c329c7d
I will try to find a workaround.

@ldez ldez added the kind/bug/confirmed a confirmed bug (reproducible). label Apr 29, 2017
@ldez ldez added the area/acme label Jun 11, 2017
@traefik traefik locked and limited conversation to collaborators Sep 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants