Extending it as a service through ws or default ssh client

[1AbdulkarimMousa]

EDITED:

Sorry if that came across the wrong way! I wasn’t implying anything malicious—just curious about how the project handles networking and system monitoring. I was thinking about potential integrations like Rathole or a reverse WebSocket for multiple TTYs. Appreciate the clarification!

[esin]

What?

This project is not a backdoor and doesn't have any similar features

Why did you decide that?

[1AbdulkarimMousa]

I had to maintain a SaaS solution that provides shell access to client users as a feature, allowing them to manage their deployments. However, their old implementation was unprotected and allowed some user to escape his restricted shell somehow.

To fix this, I wanted to build a more secure and restrictive shell client that works easily over SSH or the web. So, I'm willing to extend intheshell to support this.