vxcontrol/pentagi
1
0
Fork 0
mirror of https://github.com/vxcontrol/pentagi.git synced 2026-07-20 23:57:11 -04:00
Code Issues 45 Packages Projects Releases 9 Wiki Activity

[GH-ISSUE #69] [Enhancement]: Openvas api intergration #37

New Issue
Closed
opened 2026-06-06 22:08:11 -04:00 by yindo · 3 comments
yindo commented 2026-06-06 22:08:11 -04:00
Owner
Copy Link
Copy Source

Originally created by @s-b-repo on GitHub (Oct 25, 2025).
Original GitHub issue: https://github.com/vxcontrol/pentagi/issues/69

Originally assigned to: @asdek on GitHub.

Target Component

Security Tools Integration

Enhancement Description

will help find cves and with pentesting

Technical Details

No response

Designs and Mockups

No response

Alternative Solutions

No response

Verification

  • I have checked that this enhancement hasn't been already proposed
  • This enhancement aligns with PentAGI's goal of autonomous penetration testing
  • I have considered the security implications of this enhancement
  • I have provided clear use cases and benefits
Originally created by @s-b-repo on GitHub (Oct 25, 2025). Original GitHub issue: https://github.com/vxcontrol/pentagi/issues/69 Originally assigned to: @asdek on GitHub. ### Target Component Security Tools Integration ### Enhancement Description will help find cves and with pentesting ### Technical Details _No response_ ### Designs and Mockups _No response_ ### Alternative Solutions _No response_ ### Verification - [ ] I have checked that this enhancement hasn't been already proposed - [ ] This enhancement aligns with PentAGI's goal of autonomous penetration testing - [ ] I have considered the security implications of this enhancement - [ ] I have provided clear use cases and benefits
yindo added the enhancement label 2026-06-06 22:08:11 -04:00
yindo closed this issue 2026-06-06 22:08:11 -04:00
yindo commented 2026-06-06 22:08:12 -04:00
Author
Owner
Copy Link
Copy Source

@asdek commented on GitHub (Oct 25, 2025):

Hello @s-b-repo,

OpenVAS requires systemd to run out of the box. Before implementing this for all users, I'd suggest you experiment to see if this functionality is actually useful for AI agents and whether they can use it correctly.

Setup Instructions:

You can use the base image vxcontrol/kali-linux:systemd and install OpenVAS on top of it.

Option 1 - Package Installation:

FROM vxcontrol/kali-linux:systemd

RUN apt update && apt install openvas gvm -y

# Copy modified entrypoint that starts both systemd and gvm
COPY container-entrypoint.sh /usr/local/bin/container-entrypoint
RUN chmod +x /usr/local/bin/container-entrypoint

Option 2 - Build from Source:
Use the build approach from: https://github.com/greenbone/openvas-scanner/blob/main/.docker/railguards/debian_stable.Dockerfile

Important Notes:

Integration:

  1. Set DOCKER_DEFAULT_IMAGE_FOR_PENTEST=myorg/kali-linux:openvas in your .env file
  2. Restart PentAGI - new pentest tasks will use your custom image
  3. Modify agent system prompts in the web UI or add OpenVAS usage to your custom flow prompts

I'd like to see results from this testing before making changes for all users. Can you share how the agents perform with OpenVAS integration?

<!-- gh-comment-id:3446900723 --> @asdek commented on GitHub (Oct 25, 2025): Hello @s-b-repo, OpenVAS requires systemd to run out of the box. Before implementing this for all users, I'd suggest you experiment to see if this functionality is actually useful for AI agents and whether they can use it correctly. **Setup Instructions:** You can use the base image `vxcontrol/kali-linux:systemd` and install OpenVAS on top of it. **Option 1 - Package Installation:** ```dockerfile FROM vxcontrol/kali-linux:systemd RUN apt update && apt install openvas gvm -y # Copy modified entrypoint that starts both systemd and gvm COPY container-entrypoint.sh /usr/local/bin/container-entrypoint RUN chmod +x /usr/local/bin/container-entrypoint ``` **Option 2 - Build from Source:** Use the build approach from: https://github.com/greenbone/openvas-scanner/blob/main/.docker/railguards/debian_stable.Dockerfile **Important Notes:** - Base image files: https://github.com/vxcontrol/kali-linux-image - The image has a custom entrypoint `/usr/local/bin/container-entrypoint` (see [here](https://github.com/vxcontrol/kali-linux-image/blob/master/container-entrypoint.sh)) - You need to modify this script during your image build to start both systemd and gvm **Integration:** 1. Set `DOCKER_DEFAULT_IMAGE_FOR_PENTEST=myorg/kali-linux:openvas` in your `.env` file 2. Restart PentAGI - new pentest tasks will use your custom image 3. Modify agent system prompts in the web UI or add OpenVAS usage to your custom flow prompts I'd like to see results from this testing before making changes for all users. Can you share how the agents perform with OpenVAS integration?
yindo commented 2026-06-06 22:08:12 -04:00
Author
Owner
Copy Link
Copy Source

@s-b-repo commented on GitHub (Oct 26, 2025):

Hello @s-b-repo,

OpenVAS requires systemd to run out of the box. Before implementing this for all users, I'd suggest you experiment to see if this functionality is actually useful for AI agents and whether they can use it correctly.

Setup Instructions:

You can use the base image vxcontrol/kali-linux:systemd and install OpenVAS on top of it.

Option 1 - Package Installation:

FROM vxcontrol/kali-linux:systemd

RUN apt update && apt install openvas gvm -y

Copy modified entrypoint that starts both systemd and gvm

COPY container-entrypoint.sh /usr/local/bin/container-entrypoint
RUN chmod +x /usr/local/bin/container-entrypoint

Option 2 - Build from Source: Use the build approach from: https://github.com/greenbone/openvas-scanner/blob/main/.docker/railguards/debian_stable.Dockerfile

Important Notes:

* Base image files: https://github.com/vxcontrol/kali-linux-image

* The image has a custom entrypoint `/usr/local/bin/container-entrypoint` (see [here](https://github.com/vxcontrol/kali-linux-image/blob/master/container-entrypoint.sh))

* You need to modify this script during your image build to start both systemd and gvm

Integration:

1. Set `DOCKER_DEFAULT_IMAGE_FOR_PENTEST=myorg/kali-linux:openvas` in your `.env` file

2. Restart PentAGI - new pentest tasks will use your custom image

3. Modify agent system prompts in the web UI or add OpenVAS usage to your custom flow prompts

I'd like to see results from this testing before making changes for all users. Can you share how the agents perform with OpenVAS integration?

if we train them its possible how it works and just make a api for openvas comptiablity to relay command based on what the ai want to do

<!-- gh-comment-id:3448922669 --> @s-b-repo commented on GitHub (Oct 26, 2025): > Hello [@s-b-repo](https://github.com/s-b-repo), > > OpenVAS requires systemd to run out of the box. Before implementing this for all users, I'd suggest you experiment to see if this functionality is actually useful for AI agents and whether they can use it correctly. > > **Setup Instructions:** > > You can use the base image `vxcontrol/kali-linux:systemd` and install OpenVAS on top of it. > > **Option 1 - Package Installation:** > > FROM vxcontrol/kali-linux:systemd > > RUN apt update && apt install openvas gvm -y > > # Copy modified entrypoint that starts both systemd and gvm > COPY container-entrypoint.sh /usr/local/bin/container-entrypoint > RUN chmod +x /usr/local/bin/container-entrypoint > > **Option 2 - Build from Source:** Use the build approach from: https://github.com/greenbone/openvas-scanner/blob/main/.docker/railguards/debian_stable.Dockerfile > > **Important Notes:** > > * Base image files: https://github.com/vxcontrol/kali-linux-image > > * The image has a custom entrypoint `/usr/local/bin/container-entrypoint` (see [here](https://github.com/vxcontrol/kali-linux-image/blob/master/container-entrypoint.sh)) > > * You need to modify this script during your image build to start both systemd and gvm > > > **Integration:** > > 1. Set `DOCKER_DEFAULT_IMAGE_FOR_PENTEST=myorg/kali-linux:openvas` in your `.env` file > > 2. Restart PentAGI - new pentest tasks will use your custom image > > 3. Modify agent system prompts in the web UI or add OpenVAS usage to your custom flow prompts > > > I'd like to see results from this testing before making changes for all users. Can you share how the agents perform with OpenVAS integration? if we train them its possible how it works and just make a api for openvas comptiablity to relay command based on what the ai want to do
yindo commented 2026-06-06 22:08:12 -04:00
Author
Owner
Copy Link
Copy Source

@fartwhif commented on GitHub (Mar 21, 2026):

idk if this is relevant or helps but i caught mine doing this , so it fails due to disabled or missing package repo maybe


/work $ apt-get update && apt-get install -y openvas

Hit:1 http://deb.debian.org/debian trixie InRelease
Hit:2 http://deb.debian.org/debian trixie-updates InRelease
Hit:3 http://deb.debian.org/debian-security trixie-security InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package openvas


/work $ openvas-setup --non-interactive

sh: 1: openvas-setup: not found


/work $
<!-- gh-comment-id:4103088361 --> @fartwhif commented on GitHub (Mar 21, 2026): idk if this is relevant or helps but i caught mine doing this , so it fails due to disabled or missing package repo maybe ``` /work $ apt-get update && apt-get install -y openvas Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian trixie-updates InRelease Hit:3 http://deb.debian.org/debian-security trixie-security InRelease Reading package lists... Done Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package openvas /work $ openvas-setup --non-interactive sh: 1: openvas-setup: not found /work $ ```
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: vxcontrol/pentagi#37
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?