Replies: 2 comments 1 reply
-
Thanks for sharing this @hackncode. This is actually a bug that affects all linux installs and not even related to the STS. I'm going to fix this and get it in main this week and create a new release. That should fix your issue but i still might want to give the user a way to supply the paths as arguments to cloudfox, so i might implement that at the same time. Hang tight, and thanks for finding the bug! |
Beta Was this translation helpful? Give feedback.
0 replies
-
@hackncode Can you build from the main branch now and run it again to see if it fixes your issue? |
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.
-
Hi @sethsec-bf
I was using a STS ec2 role with permissions defined for cloudfox to enumerate one of my target cloud accounts. So I don't use any flag for profile while running any tools.
I ran pmapper successfully without any issues.
pmapper graph create
I was able to visualize the graph output.
After this I tried to run all checks and individual checks with cloudfox
When I checked output, I found cloudfox is unable to find the pmapper graph output.
Which I have generated previously.
How do I resolve this ?
Is there a way to manually input this pmapper graph data to cloudfox.
Thanks for the awesome tool 🔥
Beta Was this translation helpful? Give feedback.
All reactions