Closed ghost closed 2 years ago
This is a lot of useful information. Thank you for reporting this behavior.
You could build using the cloud builder service. Bring up Xena-Service-Pyramid API as a Docker container and a Postgres database for it. Then from the UI you can build Apep using the /build page, which you can navigate to using the menu on the right side of the screen.
If building Apep bot manually then you need to format the public key with the new lines in the string. \n <---- Also try building on a Linux machine (WSL that you mentioned) by executing build.sh script. Since it is recommended to apply binary obfuscation during the compile time. If that's not done, then the sample will be easier to discover by humans and anti-virus solutions. And much easier to debug thus reverse engineer.
If I understood you correctly those are the issues. Inform me if something else does not perform as expected.
I have run into the same error on these platforms:
I have gotten everything set up via the script
setup_linux_64bit
and also by manually activating each service via npm commands. As well as docker manually creating each service and postgres container.After the services are set up, and even just from getting atila, my key pair, the face and the tokens set up I change env to env.go and add my information and when I try to run the Apep bot each time i get this error:
I have manually done
go get ...
for each module that needs to be added. and running go build will build the executable "xena" in the folder. But running that produces the same error.I have also tried running the main_win_32 & main_linux_64 executables that are generated after running
go build
andsh build.sh
and it yeilds the same error. In and out of WSL2 and both the linux distrobutions.my env.go
I have added the public key both as is, with the line breaks (\n) after each block at each character as it was displayed when it wwas generated and have gone back and formatted it as one continuous string.
main.go