Re: mining.BitcoinAffiliatenetwork.com - we're giving away 1 Antminer S3 every day!
Hi,
For all my fellow BAN pool miners that are using Antminer S2s, I thought I'd give you a heads up on a couple of things we were talking about in the IRC chat over this past weekend.
The default firmware file leaves an open security hole for folks to exploit, and hijack your miner to work for them. So far, this has happened to me, with a miner using the name "benutzer" (German for "user"... apropos, right?) at BTC Guild. I don't blame BTC Guild for this one bad apple, but I did try to appeal to them to drop this guy. I don't think I made any progress on that part. I'm sure that they might be good people, with one bad apple.
Well, what I found was a firmware file that was not from Bitmain, but specific for the S2, initramfs.bin.SD-Kano-20140611145346.tar... Avoid it!!! I tried it, and I had 60 million invalid shares in just a moment. What a mess!!!
If your miners are not behind a firewall, for now, all I can advise is that for you to make sure /etc/cgminer.conf.factory has api-allow set as something like this:
"api-allow": "W:127.0.0.1,R:0/0",
It allows you to modify the configurations locally, or via the web interface.
For all my fellow BAN pool miners that are using Antminer S2s, I thought I'd give you a heads up on a couple of things we were talking about in the IRC chat over this past weekend.
The default firmware file leaves an open security hole for folks to exploit, and hijack your miner to work for them. So far, this has happened to me, with a miner using the name "benutzer" (German for "user"... apropos, right?) at BTC Guild. I don't blame BTC Guild for this one bad apple, but I did try to appeal to them to drop this guy. I don't think I made any progress on that part. I'm sure that they might be good people, with one bad apple.
Well, what I found was a firmware file that was not from Bitmain, but specific for the S2, initramfs.bin.SD-Kano-20140611145346.tar... Avoid it!!! I tried it, and I had 60 million invalid shares in just a moment. What a mess!!!
If your miners are not behind a firewall, for now, all I can advise is that for you to make sure /etc/cgminer.conf.factory has api-allow set as something like this:
"api-allow": "W:127.0.0.1,R:0/0",
It allows you to modify the configurations locally, or via the web interface.
This isn't really a BAN issue. The default S1/2 cgminer has this bug. For anyone who buys an Antminer S1-3, I would recommend updating to the most recent firmware from Antminer directly, and then Kano's actual firmware. I've linked them below.
Official Antminer Firmware from Bitmain: https://www.bitmaintech.com/support.htm
S1: https://www.bitmaintech.com/support.htm?pid=00720140411033846942qQqjOD460695
S2: https://www.bitmaintech.com/support.htm?pid=00720140413044945482bs4xshkh072D
S3: https://www.bitmaintech.com/support.htm?pid=007201407180243004432lBQW28O0633
Kano's S1 CGminer: https://github.com/kanoi/cgminer-binaries/tree/master/AntS1
Kano's S2 CGminer: https://github.com/kanoi/cgminer-binaries/tree/master/AntS2
You can search through this forum for postings by Kano himself mentioning his own firmware to verify.
Kano's CGminer actually fixes this bug, but there are some people who have posted fake firmware to scam people out of their mining.
It's only a BAN issue because a bunch of us were talking about it in the BAN IRC channel. It's also a BAN issue, because the current Invalid Shares count includes the 66 million I was writing about. Let's not start trying to tell folks where and when they can write things, and let others decide for themselves what is worthwhile.
The link you've provided is exactly the file that I had used; because it is supposed to fix it. That is why I tried it. That is why I am advising others not to.