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

Problem processing campaign ID - Errorno 22 #30

Open
Pintag opened this issue May 10, 2022 · 2 comments
Open

Problem processing campaign ID - Errorno 22 #30

Pintag opened this issue May 10, 2022 · 2 comments

Comments

@Pintag
Copy link

Pintag commented May 10, 2022

[+] Processed detailed analysis for 198 of 201.
[+] Processed detailed analysis for 199 of 201.
[+] Processed detailed analysis for 200 of 201.
[+] Processed detailed analysis for 201 of 201.
[+] Finished writing detailed analysis...
[!] There was a problem processing campaign ID 689!
L.. Details: [Errno 22] Invalid argument: 'Gophish Results for Login\t.xlsx'

If I run the report in Word, the same result.
Any suggestions on how to fix this?

@chrismaddalena
Copy link
Owner

Hey @Pintag! I think I see the problem. It seems very likely the \ in your campaign name is causing "Gophish Results for" to be read as a directory, so the script is trying to create t.xlsx inside ./Gophish Results for/.

I'll take a look at fixing this. In the meantime, I expect changing the campaign's name to remove the \ will let you produce your report. Let me know if that doesn't work.

@chrismaddalena
Copy link
Owner

I've spent some time refactoring the code to address other issues and requests and could not reproduce any issues with a campaign name with a slash. It could be something specific to the OS.

[Errno 22] Invalid argument is raised when the named file cannot be accessed. I don't encounter any issues on macOS or Linux with campaign names and special characters, but it's still good to sanitize the campaign name.

In this latest commit, the campaign names will be stripped of any non-alphanumeric characters before being used for the filename. I expect that will resolve the issue. Let me know if you have trouble :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants