Dependencies error

[amirhr098]

Because you didn't use virtual environment for using and installing the libraries, the versions of the libraries and their installation has bugs. Such as the errors I've written bellow. Please update your code for installing the code into a venv.

Error:
ModuleNotFoundError: No module named 'urllib3.contrib.appengine'

This environment is externally managed
╰─> To install Python packages system-wide, try ...

[kavehs87]

i did a docker compose support fork. please accept the pull request. thank you for your great idea. nice one.

[Saeid008]

Hello @ItzGlace

Thanks for the project — it’s a very useful idea 👍
I noticed that the bot does not seem to enforce a whitelist of allowed Telegram chat IDs. Currently, security relies mainly on keeping the bot token secret. If the bot username is discovered or the token is leaked, any user could potentially interact with the bot and trigger SSH actions, which is risky for a server-level tool.
I strongly recommend:
*Adding an enforced ALLOWED_CHAT_IDS whitelist
*Ignoring all messages from unauthorized chat IDs
*Optionally refusing to start if no whitelist is configured

This would significantly improve security and make the bot safer for real-world use.

Thanks for considering this!

[ItzGlace]

Because you didn't use virtual environment for using and installing the libraries, the versions of the libraries and their installation has bugs. Such as the errors I've written bellow. Please update your code for installing the code into a venv.

Error:
ModuleNotFoundError: No module named 'urllib3.contrib.appengine'

This environment is externally managed
╰─> To install Python packages system-wide, try ...

This problem will get fixed in the next update , you may run the code directly and install paramiko + python telegram bot lib to fix this issue
For now im focusing on ftp/sftp support for the bot with whitelisting id features

[ItzGlace]

Hello @ItzGlace

Thanks for the project — it’s a very useful idea 👍
I noticed that the bot does not seem to enforce a whitelist of allowed Telegram chat IDs. Currently, security relies mainly on keeping the bot token secret. If the bot username is discovered or the token is leaked, any user could potentially interact with the bot and trigger SSH actions, which is risky for a server-level tool.
I strongly recommend:
*Adding an enforced ALLOWED_CHAT_IDS whitelist
*Ignoring all messages from unauthorized chat IDs
*Optionally refusing to start if no whitelist is configured

This would significantly improve security and make the bot safer for real-world use.

Thanks for considering this!

This bot is like a bridge to access ssh over telegram so when other users donr have the pass od your ssh server they wouldnt be able to access it, formaly for this problem i used multiple factors like "no-log-policy" or "no-db-usage" to presist each users privacy and ensure the security of the server

So in the end this bot is only a bridge and just allows users to access they're ssh server over telegram not just the server that this python client runs on
It acts like a client for the users tk access any server ssh they want over telegram

I also added some rules for the paramiko interaction with the user's server like limiting any ssh connection that is not command based(socks over ssh, injections, ...)

I look forward to add cloudflare warp to protect the bot's ip , allow ftp access over telegram and even make two versions (public and private usage with id whitelist)

Thanks for the feedback on this tool I always appreciate suggestions for making this project something better and more useful