Is it possible to create internally linked MacOS binaries?

[julie-de-ville]

I am trying to create a dylib that can be used with apple's deprecated implementation of reflective loading, and it requires that the binaries be internally linked. Is it possible/feasible to do this with sliver? So far I modified the source code to include -linkmode=internal as a linker flag, but it throws an error because it is trying to enforce externally linked binaries.

[julie-de-ville]

I was able to disable chained fixups by adding linkmode=internal to the ldflags in server/gogo/go.go, I will report back on my progress

[moloch--]

Please do, we've encountered similar problems.

[julie-de-ville]

Thank you. Right now, I am having trouble linking C++ libs, I have tried passing them as linker flags and manually compiling the implants, but no luck so far. This is my first time using go, and I am still learning the C toolchain.

As I understand it, CGO requires a C wrapper to implement C++, so I am going to try doing it that way.

[julie-de-ville]

@moloch-- Specifically what i am trying to do is integrate an implant into this project https://github.com/pwardle/ReflectiveLoader
Do you have any guidance on roughly what it would entail? I think it is within my capabilities, but it is going to take some learning, so I figured I would ask.

Initially, I thought it was just a matter of internally linking the implants to disable unchained fixups, and linking c++ standard libs, because I was getting libc++abi uncaught exception errors when loading, but now I figured out how to link the necessary libs and am still getting uncaught exception.

[moloch--]

Not sure, we were at OBTS when Patrick presented this loader, we played with it a little bit but ran into the same issues you're encountering. We've yet to invest more time into figuring out exactly how to make it work with Golang binaries.