4 ms·
One possible reason is for security/abuse? I assume these extensions require communicating with some central server (owned by Microsoft) to exchange informatio
by statictype 6y ago
One possible reason is for security/abuse?
I assume these extensions require communicating with some central server (owned by Microsoft) to exchange information with peers at some point during its use.
Allowing the extension to run in contexts outside of VS Code could be an issue for them?
- hardwaresofton 6y ago> One possible reason is for security/abuse? > I assume these extensions require communicating with some central server (owned by Microsoft) to exchange information with peers at some point during its use. So I'm no WSL expert but why would Windows Subsystem for Linux or SSH need to communicate with some central server? Also unless they're doing some obfuscation, you're going to see those URLs in the binary to start with, no? Or you just... watch where it calls out to? > Allowing the extension to run in contexts outside of VS Code could be an issue for them? How? If it's a warranty issue then they should just issue the right statements in the license and make sure no one is under the impression that there's a warranty attached? I tried to think of some too but security doesn't pass my admittedly simple sniff test.