As a dev, if you use a private method, you've just taken ownership of the problem. I suggested to you in our contract not to do it, and that it would likely not be supported, and you did it anyway. Fix your shit, common software or not.
This is what an Apple engineer could write in the electron's github issue if they refused to fix it.
We're not discussing that, but that they have pushed an update without proper testing. You can see from the other comments that breakage is not limited to people using private methods.
Well, mimicking China's GFW is seemingly the objective of some governments. But they are also able to allow some light (text-based) ssh usage and still prevent proxying.
Skilled in not falling for the kind of malware, that Defender is able to catch.
It’s not a very high bar: I have not seen it find anything in a long time, neither on my machines, nor on the ones I inspected after they had been owned.
Accidentally stumbled on this and not sure what problem you're solving: not wanting to type the server name into the `mstsc.exe` window? Not having to re-type credentials across connections?
I have a few servers and workstations I tend to connect to several times a day for work, also occasionally I'll remote back to my home PC when at the office.
These connections belong to different clients and have different gateway or specific settings I like to use. Most of the issues can be resolved by simply having a dedicated folder with the `.rdp` files in them, but some of the servers I connect to have short session timeouts, which make it more difficult than it needs to be to be productive. The app launches Devolutions `mstscex.exe` which provides a 'MouseJiggler' feature which tries to keep the session active. (I've opted to pass args to the binary instead of associating Devolutions `mstscex.exe` with `.rdp` files.)
Self-managing the `.rdp` files could also mean that in the future I could implement encryption of those files to make it safer to carry around on a `USB drive` without fear of loosing it etc.
Apart from that, it's also nice to be able to launch `Meld RDP` and simply press `Ctrl+3` to connect to the 3rd connection for instance. :-)
Short version seems to be that no, your esp32-based devices aren’t remotely exploitable via radio, as some understood the original article to claim. The issue is that there are some undocumented commands that the “host” (code running on the esp chip) can send to the Bluetooth controller.
> If you want to watch a series in multiple arrangements—perhaps to figure out which sequence of episodes makes the most sense—you need a superpermutation. This is a sequence of all possible permutations. Imagine a marathon showing where you watch the first episode, followed by the second, and then watch the second episode, followed by the first (1-2-2-1). To avoid watching the second episode twice in a row, a shorter superpermutation would be 1-2-1; you would only have to watch three episodes to still have every possible order covered.
> Mathematicians have also calculated the shortest superpermutations for a series consisting of n = 4 and n = 5 episodes (33 and 153 episodes, respectively). Beyond that, however, they are in the dark. The shortest superpermutations for n > 5 are not known.
