3 ms·

Is your theory that "any competent security review" will find every security hole in a product? Because that sure would be great if it were true. Unfortunately

Is your theory that "any competent security review" will find every security hole in a product? Because that sure would be great if it were true. Unfortunately it does not match my experience.

traceroute66 2mo ago
Every security hole ? No, of course not. But things like insecure argument handling are low-hanging fruit for security auditors. Insecure argument handling is not like the more advanced subtle vulnerabilities that we are seeing in some LLM-assisted reports these days. Insecure argument handling is 1990's security. The fundamental problem remains that Tailscale has too many new "features" being added to it the whole time. New features means a whole bunch new code. Which increases bloat and exponentially increases the attack surface. It would be really nice if you could stop shoehorning in every new feature you can think of. Remove some of the existing ones that don't really need to be there. And get your codebase back to a more focused state, get back to your roots as a VPN product. Stop trying to be all things to all men, as the old saying goes.
- TheTaytay 2mo ago
  It appears that you have a major bone to pick with Tailscale and direct replies to your concerns do not seem to matter. They have a good security track record and are extremely widely deployed. I don’t see the evidence for your assertions that it is bloated and insecure.
- raggi 2mo ago
  fwiw, we have been working on increasing modularity options in the client and a substantial volume of features can now be built out of the clients, see https://github.com/tailscale/tailscale/tree/main/feature https://github.com/tailscale/tailscale/tree/main/feature for details. If you are motivated to build a much less featureful client, it is easier now than it has ever been, and this work is ongoing.
inigyou 2mo ago
[flagged]
- john_strinlai 2mo ago
  i think its probably okay to drop it when you are this far deep into a conversation and the affiliation has already been stated multiple times in the existing comment chain.
- tonyneel923 2mo ago
  Try to be civil
ozozozd 2mo ago
That was a subtle strawman. The post you replied you clearly asked why insecure argument handling should be discovered after release. You widened that to mean “every security hole must be discovered prior to release” which made it a much easier argument to attack. The point stands that the insecure argument handling could’ve been discovered by a security audit even when every security hole may not have been found.

Is your theory that "any competent security review" will find every security hole in a product? Because that sure would be great if it were true. Unfortunately it does not match my experience.

traceroute66 2mo ago

Every security hole ? No, of course not. But things like insecure argument handling are low-hanging fruit for security auditors. Insecure argument handling is not like the more advanced subtle vulnerabilities that we are seeing in some LLM-assisted reports these days. Insecure argument handling is 1990's security. The fundamental problem remains that Tailscale has too many new "features" being added to it the whole time. New features means a whole bunch new code. Which increases bloat and exponentially increases the attack surface. It would be really nice if you could stop shoehorning in every new feature you can think of. Remove some of the existing ones that don't really need to be there. And get your codebase back to a more focused state, get back to your roots as a VPN product. Stop trying to be all things to all men, as the old saying goes.

TheTaytay 2mo ago
It appears that you have a major bone to pick with Tailscale and direct replies to your concerns do not seem to matter. They have a good security track record and are extremely widely deployed. I don’t see the evidence for your assertions that it is bloated and insecure.
raggi 2mo ago
fwiw, we have been working on increasing modularity options in the client and a substantial volume of features can now be built out of the clients, see https://github.com/tailscale/tailscale/tree/main/feature https://github.com/tailscale/tailscale/tree/main/feature for details. If you are motivated to build a much less featureful client, it is easier now than it has ever been, and this work is ongoing.

inigyou 2mo ago

[flagged]

john_strinlai 2mo ago
i think its probably okay to drop it when you are this far deep into a conversation and the affiliation has already been stated multiple times in the existing comment chain.
tonyneel923 2mo ago
Try to be civil

ozozozd 2mo ago

That was a subtle strawman. The post you replied you clearly asked why insecure argument handling should be discovered after release. You widened that to mean “every security hole must be discovered prior to release” which made it a much easier argument to attack. The point stands that the insecure argument handling could’ve been discovered by a security audit even when every security hole may not have been found.