Michael Eder

Results 17 comments of Michael Eder

Sure, here you go. If you need anything else, I'll do my best. [http_post.txt](https://github.com/cobbr/Covenant/files/6313450/http_post.txt) [http_post_response.txt](https://github.com/cobbr/Covenant/files/6313451/http_post_response.txt) [server_headers.txt](https://github.com/cobbr/Covenant/files/6313452/server_headers.txt) [transform.txt](https://github.com/cobbr/Covenant/files/6313453/transform.txt) [urls.txt](https://github.com/cobbr/Covenant/files/6313454/urls.txt) [client_headers.txt](https://github.com/cobbr/Covenant/files/6313455/client_headers.txt) [http_get_response.txt](https://github.com/cobbr/Covenant/files/6313456/http_get_response.txt)

Any chance to get this merged into master? Would love to see this in Covenant in the long run

The scanner was written for scanning larger networks because other tools had too bad performance, but this is a good point. I may add such a thing in the future....

The output is done via Go's native logging framework. It seems that the [logging output is written to stderr by default](https://stackoverflow.com/questions/19965795/go-golang-write-log-to-file/38675513#38675513) - `.\go-tomcat-mgmt-scanner-x64-windows.exe -target 172.28.32.0/24 2> results.txt` therefore did the...

I'd also prefer to run a "benchmark" before merging if @Mr3Jane can provide his test methodology / script as mention in https://github.com/gophish/gophish/issues/2527#issuecomment-1182528213 I briefly looked at the PR and despite...

I did some local tinkering and as it turns out, Gorm went to a new major version 2 (although tagging it as 1.20 - see https://gorm.io/docs/v2_release_note.html). Breaking changes have been...

As I've debuged performance issues in the past, my take for the question why data is always fetched from DB is simplicity. Gophish models are designed with an ORM for...

Thanks @glycerine, I will have a look. Nevertheless, keeping the number of 3rd-parties low is almost always a good idea, so having this integrated into mangos would still be nicer...

did you actually try accessing remote resources with the process you injected the hash into? `whoami` will not show you the impersonated user.

Use your own mailserver