This depends on the service itself supporting inheriting sockets for proxies. Is this a common feature? Some services do support listening socket passing which does solve my problem as I can make it listen on a UNIX socket mounted on the host and accessible to the reverse proxy but many of the lower quality services that I want to give this treatment to don't support that either.
If it is a choice between preparing my sd cards with open partitioning tools, or running some non-auditable official tool in binary form, it is an easy choice.
I'll do the former, as I always have.
By the way, a cool quote from the agreement preceding the download page:
>3. RESTRICTIONS: You agree to NOT: (a) disassemble, reverse engineer, decompile, or otherwise attempt to derive any source code for the SDA Software from executable code;
This should be quite alarming. They insist that we format SD cards with their tool, but they don't want us to know what the tool does.
I will not be the one reversing them, but I checked it is possible to download these through tor, and recommend downloading them that way to prevent potential trouble.
> 3. RESTRICTIONS: You agree to NOT: (a) disassemble, reverse engineer, decompile, or otherwise attempt to derive any source code for the SDA Software from executable code;
Depending on where you live, this might have no legal effect. Some jurisdictions allow explicitly for reverse engineering & co. for different purposes (e.g. research, interoperability with other systems, etc.).
Some manufacturers have proprietary undocumented APIs that allow the host to upgrade the firmware in the card, but I’m not sure every maker does, and very sure most wouldn’t bother to update their firmware unless some horrendous issue came up.
It's allowed but people who use Linux want to know about these things ahead of time, as many of us seek to reduce the amount of closed-sourced code running on our systems to give us peace of mind.
Registers aren't free; of course turning on frame pointer elision is going to give you a few extra percentage points of performance. The problem is that it will interfere with your performance team's ability to further profile the program and triage crashes, which is very, very likely going to be worse in the long run than the savings you get from this particular optimization. On register-starved environments like x86 (like the one you linked) it's somewhat forgivable but on any modern platform it's a bad tradeoff 99.9% of the time.
