Quote from: cvax on March 24, 2014, 01:51:40 AM

Quote from: tachyon_john on March 24, 2014, 12:13:59 AM

Quote from: tachyon_john on March 24, 2014, 12:10:36 AM

Quote from: tachyon_john on March 24, 2014, 12:08:11 AM

Quote from: cbuchner1 on March 23, 2014, 10:02:34 PM

Quote from: tachyon_john on March 23, 2014, 09:48:06 PM

I assume cudaminer honors reconnect requests because a quick 'grep shows that it has logging code for a reconnect message. Given the man-in-the-middle/spoofing attacks going on with several of the pools, there should probably be a way to tell cudaminer not to accept reconnect requests when started with a particular command line flag, and optionally to log the reconnect data or report it in some way.

is there a thread where I can read more about man in the middle attacks with pool mining?

It's happening on a bunch of pools. So far I've heard: cleverminer, wafflepool, multipool.us, and others that I'm forgetting just now. The wafflepool thread has some extensive discussion about it, protocol captures, etc.

I see people are now working on patches for other miners (just got back from dinner so I'm catching up):
https://bitcointalk.org/index.php?topic=433634.3200

Kalroth just posted patch for his miner:
https://bitcointalk.org/index.php?topic=433634.3220
https://github.com/Kalroth/cgminer-3.7.2-kalroth/commit/d78f8c896010049a06275db13a2816c0e201e41e

Skimmed through it. It isn't clear to me is cudaminer even actually impacted?

All miners that respond to "reconnect" messages sent by the pool are impacted, which is most of them....