Replies: 1 comment 1 reply
-
|
The project seems to be sticking to default Python libraries (os, aiofiles, asyncio, etc.) and using the python:3.12 docker image which is Debian-based. Kali is also based on Debian, so as long as Python 3.12 is installed on the Kali image you use I can't foresee any issues. I guess the only way to figure it out is by trying it, by tinkering with the Dockerfile. BTW this would be a nice feature for the future Terminals orchestrator (being able to select the distro) |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I'm looking at creating a customized version of open-terminal that is based on the official kali linux image - https://hub.docker.com/r/kalilinux/kali-rolling for integrating pentesting capabilities into open-webui.
I suppose it might be tenable to either fork this project and modify the Dockerfile OR maybe I could produce a new multi-build Dockerfile that uses the kali base image and the open-terminal entrypoint to support the config files, and integration with open-webui.
Just looking to see what others might think the best route is. I've built my own similar setup for a custom agent tool I developed, but I would rather spend my dev cycles leveraging the open-webui ecosystem instead.
Beta Was this translation helpful? Give feedback.
All reactions