|
|
|
|
|
by codethief
2098 days ago
|
|
I actually think we're completely on the same page. :) > The way you're talking about it, you make it sound like there's an active vulnerability, not just a defense in depth improvement. They're vastly different. Please note that I never termed it a vulnerability (whether active or not). I merely called it a security issue – which it was/is because it gives users a false sense of security. I also made that point very clear in my post on Github. > My previous offer is still on: $500 bucks that you can't exploit this if I link you to a traefik configured in this way you refuse to run it. Being able to recognize and avoid potential security holes and being able to exploit them in practice are two different things. I think I'm fairly good at the former (in the sense that I'm able to avoid the most common pitfalls) but I have only limited experience with the latter. And while I am aware that in-depth hacking expertise would be very valuable even when examining certain security practices (it's definitely on my to-do list), I don't think it is required to point out basic flaws and potential attack vectors. So as much as I appreciate your offer, I don't think me being or not being able to hack your system implies anything with regards to how secure Traefik is. |
|