most of them are not repairable. They are manufactured using one-way techniques like fusing plastics vs. screws or clips, or the discrete parts are amalgamated into a single component, or you need special tools (or software) to do anything.
The manufacturers’ service teams want you to think that, but the truth is there will always be aspiring individuals who can figure out the fixes, and through the power of the internet share with the world.
Is an Xbox meant to be fixed? I learned to hot air rework a tiny QFN40 chip and got it working.
I plug a usb-can cable into my vehicle, and unlock all kinds of functionality that was held back (ex. rolling windows down from key fob).
I like to hope that out there are all kinds of engineers making small opportunities for doors to be opened, perhaps for themselves or the collective. So perhaps you too, can contribute with that “secret” menu or properly labeling the PCB pogo pins.
It doesn't. It just foresaw the need to be able to dynamically configure tunnels on first connection and specified all of that. Which seems to me is a lot of what fly io has just mostly reimplemented here.
In any case the point is I would prefer to just have the basic components available and let me piece them together however I want. Mostly to allow using the underlying technology in more contexts that it is currently available in.
Heh, it really sounds like your needs would be better served with IPSec or something. WireGuard was born precisely because they saw that the whole problem making other existing solutions difficult to audit and insecure-in-practice was their thousand ways to configure. So they did the opposite. Low lines of code, few possibilities.
In software you often choose between a small monolith and a big kitchen sink. Once you have 1 more need than the monolith covers, you have to go over to the kitchen sink.
How do you prevent it from entering the food chain again?