Comment 1 for bug 1559455

I just realized that command line apps can be treated the same as any other app. All that's required is the usual network accesss enable/disable switch in the corner of the terminal window. Any commands or other apps launched in that terminal inherit that network access status, just like a thread launched or forked from a windowed app. If several concurrent threads are launched from that terminal, then they are all simultaneously affected by the switch, even if its state is altered after the threads have launched.

There is also the question of how to select the default state of the switch. Initially, it should always be off. Then if it's enabled for app ABC, then all future instances of app ABC, even after the next reboot, should have it enabled. Similarly if it is disabled once again. This implies a simple setting in a registry somewhere which contains network switch defaults for each app.