Had been thinking about something similar, but not sure whether it will be useful.
Each sidebar tabsheet has its own unique terminal id, which I use to make sure that the (input and output) data is communicated between each terminal window and the corresponding pseudo terminal process correctly. The server stores the routing information in a map:
Suppose I implemented the following changes:
- add an output to the Terminal-Input node
- include the PID and/or the terminal Id in the output messages
- show the PID and terminalId (both readonly) in the sidebar.
But then you still need to copy/past the PID and/or the terminal Id in your switch node and deploy your flow to filter your own messages:
But then *other users won't see their own messages anymore. Therefore I'm still not convinced that this is very useful in a multi-user environment. But perhaps I'm completely wrong ... And perhaps I could add it for single-user environments? Because most of the users are using it for small systems ...
Ok thanks Nick! Was not sure whether that was enough to secure an endpoint ...
The version on Github now contains this:
RED.httpAdmin.get('/xterm_shell/:terminal_id/:command/:info', RED.auth.needsPermission('xterm.write'), function(req, res) {
And now it still seems to be working on my Raspberry.
Ah ok. That way. Might be indeed handy. Can you post some more details, then I add it afterwards on my readme page. Thanks !!
