Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement XML Parsing in Windows EXE Release #566

Open
gtrdlr opened this issue Apr 8, 2022 · 1 comment
Open

Implement XML Parsing in Windows EXE Release #566

gtrdlr opened this issue Apr 8, 2022 · 1 comment
Assignees
Labels

Comments

@gtrdlr
Copy link

gtrdlr commented Apr 8, 2022

OS Used - ALL Information (architecture, linux flavor, etc.)

Windows 10 (EXE)

Pastebin link to error you are encountering

It will auto detect the file you give it with the -f flag as either being a text file with URLs on each new line, nmap xml output, or nessus xml output.
https://github.com/FortyNorthSecurity/EyeWitness/blob/master/README.md

Expected behavior (vs. what you encountered)

The usage of the '-f' flag to parse an NMAP XML

Any additional information

The documentation states that the '-f' flag will parse an NMAP XML file as host input. I know this feature has existed in the Linux version, but doesn't seem to function properly in the Windows version. I presume there are reasons for this but wanted to verify this is a known issue.

@Relkci Relkci added enhancement C# C# Codebase labels Jan 11, 2024
@Relkci
Copy link
Collaborator

Relkci commented Jan 11, 2024

I think you're wanting an enhancement to add XML support on the C# implementation. The -f is intended for line-separated URLS. If implemented, I believe it would be aligned with the -x argument to parse XML for URLS.

@Relkci Relkci changed the title Lack of NMAP XML Parsing in Windows EXE Release Implement XML Parsing in Windows EXE Release Jan 11, 2024
@Relkci Relkci self-assigned this Jan 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants