You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tried the other applicable steps from the Troubleshooting Guide
Completed the Problem Description, Steps to Reproduce and Version sections below
Problem Description
First of all, thanks for including the spyder-terminal in the standalone installers now as well!
However, it seems the underlying server process is not being shut down after Spyder quits. After a few Spyder restarts this leads to multiple python processes listening on different ports at 127.0.0.1 all serving the OS Web Terminal.
This is not only a minor nuisance, but I think can lead to a security incident.
If someone exposes a port(range) to the web while the OS Web Terminal is still running on that port (without any indication, unless you check the ports with lsof), I think someone might expose a terminal to the WWW, which is undesirable.
What steps reproduce the problem?
In a terminal run sudo lsof -i -P | grep LISTEN | grep python to see al listening python processes.
Open Spyder
Run sudo lsof -i -P | grep LISTEN | grep python to see al listening python processes.
Close Spyder
Run sudo lsof -i -P | grep LISTEN | grep python to see al listening python processes.
What is the expected output? What do you see instead?
Expected output
The list of processes retrieved in step 5 should match the list from step 1. I.e. all python processes started by Spyder should be shut down after closing Spyder.
Actual output
A new python process is found in step 5, which was also visible in step 3. If you visit the address that python process listens on (127.0.0.1:<some_port>) you will get the OS Web Terminal, a live terminal into your system.
Issue Report Checklist
conda update spyder
(orpip
, if not using Anaconda)jupyter qtconsole
(if console-related)spyder --reset
Problem Description
First of all, thanks for including the spyder-terminal in the standalone installers now as well!
However, it seems the underlying server process is not being shut down after Spyder quits. After a few Spyder restarts this leads to multiple python processes listening on different ports at
127.0.0.1
all serving the OS Web Terminal.This is not only a minor nuisance, but I think can lead to a security incident.
If someone exposes a port(range) to the web while the OS Web Terminal is still running on that port (without any indication, unless you check the ports with
lsof
), I think someone might expose a terminal to the WWW, which is undesirable.What steps reproduce the problem?
sudo lsof -i -P | grep LISTEN | grep python
to see al listening python processes.sudo lsof -i -P | grep LISTEN | grep python
to see al listening python processes.sudo lsof -i -P | grep LISTEN | grep python
to see al listening python processes.What is the expected output? What do you see instead?
Expected output
The list of processes retrieved in step 5 should match the list from step 1. I.e. all python processes started by Spyder should be shut down after closing Spyder.
Actual output
A new python process is found in step 5, which was also visible in step 3. If you visit the address that python process listens on (
127.0.0.1:<some_port>
) you will get the OS Web Terminal, a live terminal into your system.Paste Traceback/Error Below (if applicable)
Versions
Dependencies
The text was updated successfully, but these errors were encountered: