[GH-ISSUE #42] ARM: Kali Archive Keyring #21

New Issue

2026-06-06T22:08:02-04:00

yindo commented

2026-06-06 22:08:02 -04:00

Originally created by @edge5phil on GitHub (May 28, 2025).
Original GitHub issue: https://github.com/vxcontrol/pentagi/issues/42

Originally assigned to: @asdek on GitHub.

Affected Component

Security Tools Integration

Describe the bug

Tools can't be installed

Steps to Reproduce

Kali via Parallels on M2 Mac

System Configuration

MacOS -> Parallels

Logs and Artifacts

Hello
Maybe someone has hint for me what I'm doing wrong?
Bests
P.

Screenshots or Recordings

No response

Verification

I have checked that this issue hasn't been already reported
I have provided all relevant configuration files (with sensitive data removed)
I have included relevant logs and error messages
I am running the latest version of PentAGI

Originally created by @edge5phil on GitHub (May 28, 2025). Original GitHub issue: https://github.com/vxcontrol/pentagi/issues/42 Originally assigned to: @asdek on GitHub. ### Affected Component Security Tools Integration ### Describe the bug Tools can't be installed ### Steps to Reproduce Kali via Parallels on M2 Mac ### System Configuration MacOS -> Parallels ### Logs and Artifacts ![Image](https://github.com/user-attachments/assets/9a528516-eab9-470d-b123-eab9e8a06a77) Hello Maybe someone has hint for me what I'm doing wrong? Bests P. ### Screenshots or Recordings _No response_ ### Verification - [x] I have checked that this issue hasn't been already reported - [x] I have provided all relevant configuration files (with sensitive data removed) - [x] I have included relevant logs and error messages - [x] I am running the latest version of PentAGI

yindo added the bug label 2026-06-06 22:08:02 -04:00

yindo closed this issue

2026-06-06 22:08:02 -04:00

yindo commented

2026-06-06 22:08:02 -04:00

@asdek commented on GitHub (May 28, 2025):

Hello @edge5phil

The issue you're facing is in the booyaabes/kali-linux-full:latest Docker image referenced here

As a workaround, ask PentAGI to use a different image, such as the official Kali Linux full image, when you start your initial request. I'll replace this problematic image in the next update.

This appears related to the issue described here: https://www.kali.org/blog/new-kali-archive-signing-key/ - the Docker image hasn't been updated in a while and contains outdated signing keys.

You can also manually fix this by following the steps in the article above, then using docker commit to replace the booyaabes/kali-linux-full:latest image locally. The next attack simulation will use your fixed image from your local Docker registry.

@asdek commented on GitHub (May 28, 2025): Hello @edge5phil The issue you're facing is in the `booyaabes/kali-linux-full:latest` Docker image [referenced here](https://github.com/vxcontrol/pentagi/blob/master/backend/pkg/templates/prompts/image_chooser.tmpl#L6C80-L6C114) As a workaround, ask PentAGI to use a different image, such as the official Kali Linux full image, when you start your initial request. I'll replace this problematic image in the next update. This appears related to the issue described here: https://www.kali.org/blog/new-kali-archive-signing-key/ - the Docker image hasn't been updated in a while and contains outdated signing keys. You can also manually fix this by following the steps in the article above, then using `docker commit` to replace the `booyaabes/kali-linux-full:latest` image locally. The next attack simulation will use your fixed image from your local Docker registry.

yindo commented

2026-06-06 22:08:03 -04:00

@edge5phil commented on GitHub (Jun 2, 2025):

Thank you very much @asdek

I did run

prepare kali image kalilinux/kali-rolling

to enum target 192.168.1.1

Everything works now very well :-)

@edge5phil commented on GitHub (Jun 2, 2025): Thank you very much @asdek I did run ``` prepare kali image kalilinux/kali-rolling to enum target 192.168.1.1 ``` Everything works now very well :-)

yindo commented

2026-06-06 22:08:03 -04:00

@asdek commented on GitHub (Jun 2, 2025):

Hello @edge5phil

Sounds good! I'm glad that approach worked for you.

I wanted to let you know that I've just released a new update that brings assistant functionality and improves overall system stability. These changes should make your pentesting experience even better.

You can check out the details here: https://github.com/vxcontrol/pentagi/pull/44

To get the latest version, simply run:

docker compose pull && docker compose up -d

Let me know if you have any questions about the new features!

@asdek commented on GitHub (Jun 2, 2025): Hello @edge5phil Sounds good! I'm glad that approach worked for you. I wanted to let you know that I've just released a new update that brings assistant functionality and improves overall system stability. These changes should make your pentesting experience even better. You can check out the details here: https://github.com/vxcontrol/pentagi/pull/44 To get the latest version, simply run: ``` docker compose pull && docker compose up -d ``` Let me know if you have any questions about the new features!

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: vxcontrol/pentagi#21