You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running latest Mythic with latest Merlin. Unable to build Merlin payload for windows and linux.
I see following error during payload build process:
Sending Build command
there was an error compiling the agent
StdErr:
exit status 1
StdOut:
main.go:34:2: github.com/Ne0nd0g/merlin-agent/[email protected]: replacement directory /opt/merlin-agent does not exist
main.go:35:2: github.com/Ne0nd0g/merlin-agent/[email protected]: replacement directory /opt/merlin-agent does not exist
main.go:36:2: github.com/Ne0nd0g/merlin-agent/[email protected]: replacement directory /opt/merlin-agent does not exist
main.go:37:2: github.com/Ne0nd0g/merlin-agent/[email protected]: replacement directory /opt/merlin-agent does not exist
main.go:38:2: github.com/Ne0nd0g/merlin-agent/[email protected]: replacement directory /opt/merlin-agent does not exist
The text was updated successfully, but these errors were encountered:
@timukas I pulled down and installed Mythic, the http C2 profile, and Merlin from source today. After installing them I was able to create an agent without errors.
The error you provided looks like we've modified the go.mod file to reference files in the container. Likely from our conversation at #17. I removed those directories from the latest commit Ne0nd0g/merlin-docker@6deaf8f because they were not necessary and they bloated the image size. As a temporary workaround, you could add the instructions back to your local copy of the Dockerfile in Payload_Type/merlin/Dockerfile like this:
# Clone Merlin Agent
WORKDIR /opt/
RUN git clone -b v2.4.1 https://github.com/Ne0nd0g/merlin-agent
WORKDIR /opt/merlin-agent
RUN go mod download
Hi,
Running latest Mythic with latest Merlin. Unable to build Merlin payload for windows and linux.
I see following error during payload build process:
The text was updated successfully, but these errors were encountered: