New Posh_v4_x64.dll flagged by AVG whereas v4.1 is not about poshc2

[jmhickman]

If I need to upload a payload somewhere, just let me know.

[riskydissonance]

I'll test it locally anyway but if you can upload the flagged and unflagged DLLs zipped to the issue that'd be super useful, thanks!

[jmhickman]

poshfiles.zip
DLLs, plus the config files (since they're been modified) in case that mattered. No pass on the zip.
The 4.7 payload, iirc (it's been a few days) had to execute to be detected and quarantined. Hopefully it doesn't depend on talking with the server to trigger the detection!

[riskydissonance]

Hi, this should be fixed now on the dev branch as of a5d5e2c, if you're able to confirm that'd be awesome :)

[jmhickman]

Sadface

I pulled down the zip of the dev branch, unpacked, performed Install, had it gen the payloads, and then just moved the payload to the host. Caught it immediately even before running it, unfortunately.

Happily though, once I modified my temp dev server with the values from my customized Config.py and oldurls.txt files( there's some sort of breaking compatibility issue trying to copy the file straight it seems), and regenerated the payloads, the same file sat on disk and was able to be executed and connected without issue.

I chose to report both since I don't know if you are trying to solve the 'default' case or the 'customized' case.

[riskydissonance]

I think we're happy if it works in practice. Thanks :)