Quote from: kade123 on March 01, 2018, 09:23:00 AM

Quote from: melpheos on March 01, 2018, 08:13:32 AM

Quote from: kade123 on March 01, 2018, 04:28:25 AM

Quote from: quick_dry on February 28, 2018, 06:25:11 PM

Quote from: kade123 on February 27, 2018, 06:23:45 PM

Quote from: melpheos on February 27, 2018, 04:21:14 PM

Quote from: kade123 on February 26, 2018, 08:46:23 PM

@realbminer not saying this miner is a Trojan horse, but it was working ok for many hours then in the night suddenly it started using all my hash for miners using it "Bminer 5.4" to mine somewhere else with IP address amazon compute(i.e. hosted by amazon) and some other places there was no change on the console nor was there a disconnect from the miner just that all shares found where going else where and my pool address share rate went to zero for about 30-60 minutes though miners where mining for all systems using the miner.

That is miner was mining for someone else for 30-60 minutes(not fee mining), this could have been triggered remotely by you as the miner appears shady, you need to explain, also there maybe a back door author uses to access mining machines using windows RDP (I had to disable this as passwords no longer accepted on some systems for RDP sessions)

@realbminer needs to adress this question but you also need to show the logs showing this. This is your first post so as you can imagine one can question it as well

The miner appears to have a backdoor or some sort of remote control where author "@realbminer" can selectively control clients that use his miner "bminer" where to direct hash from 0 to 100 % as he sees fit; you are not going to see it in logs, only external tools that monitor the process remote connections it initiates will detect this, the console is to only fool you. I will try and capture a picture when it makes a connection, he appears to trigger it when he thinks no one is watch i.e. miner as been mining for a long time no starts or stops, he then directs what ever percentage to an amazon compute host while completely ignoring your pool and switches back as he sees fit, I think for a 1080 Ti the miner may hash around 780-800+ and he only gives you about 750 and controls a lot of things, he knows this is true that is why pros are not using his miner, he is a devious criminal.

I haven't monitored the network connection, but I've seen the pattern you describe. Does it match my post a page or two earlier?

It mines for maybe 8 or 10 hours, and then all of a sudden it stops mining to your pool - but is clearly still doing something, as the power usage does not change at all. Then, if you activate the window and press a key, it does a restart and goes back to mining to your pool. It could be something nefarious, but it could be some bug in the code gets it stuck in a loop churning away burning power but accomplishing nothing.

Sending a keypress to the window every half an hour or so _seems_ to stop it doing this.

Find below suspicious activity of Bminer mining to amazon URL, this is not possible unless remote information is passed by developer to miner dynamically as IP and instance names are generated dynamically by amazon and I doubt he created a persistent instance that has been going for months

@realbminer there are laws against Trojans and you could be investigated and prosecuted (https://www.computerhope.com/issues/ch001196.htm)

Erm have you check what this IP is ?
It's one of the zcash flypool URL and the port it's their standard stratum port !
This is the dev fee !

Look the issue here is the miner stops mining to the pool you set for it to mine and mines for developer for over an hour using all your hash this is not how developer fee is collected normally and it seems to be a way to get extra developer fees separate from normal fees, don't know the trigger for this could be remotely, normally that particular IP is not used and only seems to be used when this behavior is detected as now confined by at least two users.

I suspect more a bug.
For instance maybe when your main pool is down, it will not properly check the main pool again but will switch to dev and stays there...
Personaly i never encountered this issue on 4 rigs.
This particular IP is a flypool ip. Dev cannot use it to do anything remotely (except if dev is working for flypool which i doubt)