Quote from: JayDDee on July 16, 2021, 03:35:23 PM

Quote from: shadowofthedamn on July 15, 2021, 07:38:33 PM

claymore more epochs is maintained as a mod and is as good. see its link:
https://bitcointalk.org/index.php?topic=5305046.0

More Epochs Mod is not Claymore Miner, it's a binary hack of Claymore Miner. No one will issue a certificate
for a product created by hacking.

First of all, MoreEpochs Mod is not a "hack". Claymore miner stopped working at epoch 384 at the end of december 2020. MoreEpochs mod gave that legendary miner second life, and many people are happy to continue to use it.

Second, Claymore miner's .exe file was never signed. How come respected developer didn't sign his product? I make life easy for you and answer - because Claymore didn't want to reveal himself and you have to give out all of your personal info to get personal certificate.

Third, when Claymore released first version of his miner with strap driver, driver was signed with test certificate and required Windows test signing mode to work. Later Claymore signed the driver, but not with his personal certificate (which he never had) as some people thinks, but instead with certificate that was freely available on the internet. You can check it, if you have original Claymore miner archive, install strap driver with command
"ethdcrminer64.exe -driver install" and go check c:\windows\system32\drivers\cmdrv64.sys, right click, properties, digital signature.
You will see that it is signed with "HT Srl", which is obviously not personal certificate, with expired root certificate.

Original strap driver doesn't work on AMD drivers 20.5.1+, and after I've completed unique and very hard task of updating that strap driver, so it can support AMD drivers 20.5.1+, I have to resign it. I've resigned it with same free available certificate that Claymore was using. You can check it by installing MoreEpochs mod 2.5 and then install updated strap driver with "ethdcrminer64.exe -driver install" and go check c:\windows\system32\drivers\cmdrv64.sys to see that it's signed with same "HT Srl" cert.

With update KB5004237 MS removed many expired certificates, and of course the one that Claymore and I was using to sign strap driver. So right now there is only one way to continue to use signed strap driver - remove update KB5004237 and disable automatic updates. Also I can resign driver with test cert (as Claymore did in first version of strap driver) and it will require Windows test signing mode to work.