Heads up all:
https://bitcointalksearch.org/topic/m.1532516The 64-bit cpuminer 2.2.3 windows binary in the zip file on the OP has been tampered with. Unless you specify the username/password in a specific way, it will ignore your settings and instead use built-in creds.
Cheers.
burside, thank you very much for letting me know. I must have uploaded the wrong binary for the 64-bit Windows version of the miner. That version was compiled for internal use only, and never intended for public distribution. On the up side, that default address would never have worked from the outside of the private network it referred to, and when mining in a pool people notice immediately if shares don't show up in their account, so the only problem this could have caused is that getting the binary to work was trickier because you had to use the
--userpass option instead of
--user and
--pass.
Unfortunately I'm currently away, so I'm unable to recompile the binary, but luckily there's not much difference between 2.2.2 and 2.2.3 apart from the benchmark feature, so for the moment people can just download version 2.2.2, which on Windows should not be any slower.
Miners who are currently using the "wrong" 64-bit 2.2.3 binary with no issues
need not downgrade. There is no risk that your shares go to the wrong server or account, it's just that when you first set the miner up it may be a bit trickier to get your credentials to work, as in that binary not all of the command-line options for setting the credentials work as expected.
