Any news on this?

Ta 

I received an answer to a PM I sent to Bitmain/BitmainWarranty:


The usual lies. My reply (some details retracted):

Bitmain & BitmainWarranty,

For the last TWO months you have been saying the same thing - we are now at the stage where your users are becoming increasingly suspicious as to why you are delaying the firmware update. It simply does not take two months to compile & test a firmware image, especially when the only change is an updated cgminer. The cgminer devs are able to compile updates to cgminer within a few hours, so why is it taking you months?

The security vulnerability that enables the stratum redirect attack (some victims of this attack have posted details on this forum) was fixed in cgminer on May 2nd 2014 - over 5 months ago - yet Bitmain have continued to use the vulnerable version in all their miners since then, even the S3's and original S4's came with the older cgminers installed.....why? What possible reason would a mining manufacturer insist on using a particular version of cgminer knowing that they are vulnerable to having their work redirected to a different pool without the users knowledge? There can be only one possible answer - and that is that you, Bitmain, and others want to keep this vulnerability for your own nefarious purposes, and have been deliberately delaying the release of the fixed version so as to enable you to continue to redirect users hashes to your own particular pool accounts for personal gain at your users expense.

Bitmain are now paying someone to repeat your excuses & post inaccurate answers on your threads, the fact that this same person also writes manufacturers trustworthiness guides on bitcointalk is not only very concerning, but also a blatant attempt to deter him from giving an accurate account of your failings. Basically - you're paying him off. Maybe if you had employed the cgminer developers instead, you would have been able to fix your firmware issues many months ago - but then you wouldn't have had your little "back door" into thousands of miners would you?

Once again I will remind you of the promise you made to the community & your thousands of users 2 months ago:


BITMAIN - DO AS YOU PROMISED 7 WEEKS AGO & GET THIS S2 FIRMWARE OUT - NO MORE DELAYS, LIES, HOLIDAY EXCUSES OR BROKEN PROMISES- GET IT DONE!!!!

Who the freak is flooding p2pool with 50% DOA's?!!



Sort it out.......

Right, the one that doesn't fix anything then. Still, at least it's possible to flash this time, that's an improvement......

I don't know what's worse, uploading firmware that doesn't fix any issues - or being promised firmware to fix issues & not bothering to upload it, as is the S2 situation.

What an abortion.

That's not Bitmain. BitmainWarranty? 14 posts? How can someone who apparently works for Bitmain not be able to upload it to his own website? And it still don't work? Still like to see the email too, sounds dodgy as fook to me.......

Anyone can generate an MD5 too......I can't find anything from Bitmain saying they have verified this as genuine.......maybe you can post the complete email?

Since when did it need an "engineer" to upload a file to a website?  Anyone can do that, it's not hard at all.....

I would be very wary of using an image someone got in an email claiming to be from Bitmain, if they can email it to someone - they can also upload it to their site.

Where in Italy?

-1

And I'll keep posting until they do it, as they promised, over 7 weeks ago. There are S2 users who are having their hash rate stolen because of this, maybe if it was happening to you as well you'd understand......


If you consider complaining about broken promises, lies & lack of support "childish", there's something wrong with your moral compass.

Forget about Bitmain helping you out with this - they won't. I've uploaded my S2 image file for you here:

https://www.dropbox.com/s/py9jus9mk3tk21e/bitmain.img.zip?dl=0

Use win32diskimager to format your SD card & burn the image.

Realize that doing this will still leave you open to the "stratum redirect attack" you have been experiencing, but it won't do you any harm to try. The image is the exact same one as I am currently using in my S2's - so it's clean & working 100%. I suggest you hound Bitmain constantly until they do as they promised & release an updated S2 image file with the latest cgminer in it that will fix the security issue.

Good luck 

This is becoming a bad joke. I think the only option now is to start flooding them with PM's & emails, as they obviously don't give a shit. There are customers out there who are having their hash rate stolen as a direct result of Bitmains incompetence, broken promises and lies.....

BITMAIN - DO AS YOU PROMISED 7 WEEKS AGO & GET THIS S2 FIRMWARE OUT - NO MORE DELAYS, LIES, HOLIDAY EXCUSES OR BROKEN PROMISES- GET IT DONE!!!!

Same here. Even though UPS are slightly cheaper, their charges & import duties are higher than DHL, so it sort of evens it all out. Still WAY too expensive though 

So, confirmation that it is not a firmware issue, but a hardware issue - and that the upcoming firmware release, if/when it arrives, is only a workaround:


Many thanks to ckolivas once again for all his efforts! 

Ah, that explains it - thanks ck. Did dogiemain bitmain say if they would replace the controller in the next batch - or will they just keep using the workaround (i.e. hack)?

I get the feeling bitmain are paying the wrong person......

Now more expensive & without free shipping.......

Uno hash power......going UP! 

iyftech.zapto.org:9655

It will find your node automatically - might take a few days to propagate 

Using SSD's won't help I'm afraid, the Neptunes are known not to be p2pool compatible. There is a shortage of hardware that works efficiently with p2pool atm. Currently, the only miners of any size that are p2pool friendly are all Spondoolies units & the Bitmain S1's & S3's. I have had Bitmain testing the S4 on my p2pool node - it's an abomination, like the S2 was, but worse  . Technobit have told me that they are working on a firmware fix for p2pool, but I'm not holding my breath....

If you tell me what the standard cgminer settings are in the S4, particularly the "queue" parameter,  - I will be able to suggest what needs changing in an effort to decrease the DOA/Reject rate & achieve the full 2Th/s. It is obvious from the many posts here that the hashrate on the webUI can be completely different from the poolside hashrate, so can't be trusted. Also, as my graph of your S4 on p2pool clearly shows, over 30% of the work done by the S4 on p2pool is being wasted - so until this is fixed, I strongly suggest that you remove your claim that the S4 is compatible with p2pool as not only is this not true, but it's also false advertising & will save you many complaints from users who purchase the S4 to use with p2pool.