Quote from: Wolf0 on December 25, 2016, 09:38:29 AM

Quote from: Claymore on December 25, 2016, 09:10:55 AM

Quote from: Wolf0 on December 25, 2016, 02:36:22 AM

Quote from: nerdralph on December 25, 2016, 01:54:40 AM

Just noticed Claymore has a sense of humor:

Code:

not so easy bro :)

When setting AMD_OCL_BUILD_OPTIONS_APPEND

Setting AMD_OCL_BUILD_OPTIONS gets:

Code:

it fails too ;)

However after a quick hex edit of the amd opencl shared library

Code:

export AMD_OCL_RALPH_OPTIONS_APPEND=-save-temps

Works just great. :-)

Yeah - I've unpacked the real miner binary (zecminer64 is only 66k, this is because it loads Data3.bin, decodes it, and then runs it.)

From there you end up with a binary that looks to have been packed by a modified version of UPX - unpacking what it drops looks like an ELF loaded at 0x80000 - it patches several jumps in it to make it work, because it looks like it expects to be loaded at 0x40000. THAT looks like it drops ld.so and the real miner ELF into memory.

Yo dawg, I herd you like executing, so I put an ELF64 in your ELF64 so you can execute while you execute.

I think now one of my points about Linux release is clear - other devs want to see how my miner works and do reverse engineering as soon as they can. It's much easier to do it in Linux.
My License.txt prohibits such things clearly, so you violate the license.
Remember I violated MIT license in past and was blamed that I steal other's work. Now I see same thing from you. Have fun...

Actually, it would have been easier to reconstruct the actual miner binary on Windows. There's nice tools to do this for the PE32+ (PE 64-bit) format, but jack shit for ELF64.

My owner and I recovered the binary in its original, unpacked form, btw - not much in the way of anti-debugging once you get to there. Some obfuscation, but not much. Checkmate - that was a fun workout; time to figure out something else to do.

Stop worrying about your devfee, it's not about removing it or altering it. It was just fun to do.

Clay you can rest assured that every big(er) cloud hashing company has your miner variations and optimizations already - regardless of ssl, packing, upx, linux etc..