Quote from: Veldy on June 04, 2011, 03:36:55 PM

Quote from: mother_of_another on June 04, 2011, 01:31:06 AM

Quote from: aBitcoiner on June 04, 2011, 01:21:22 AM

Quote from: mother_of_another on June 04, 2011, 12:54:07 AM

Edit: better still how about tunnelling the workers in and shutting EVERYTHING else out?

Then people would have to foward ports and use a special client.

Why special client? Are there problems with RPC across TCP/SSH?

And how much more work is it than stopping miners etc all the time? We need to secure these pools, it is as obvious as the nose on your face. I think creighto says the enemy of the good is the perfect. Anything better than nothing.

The SSH CPU overhead of thousands of miners connected at once may be a lot. Ready to donate more?

BTW, SSH attempts can still be started and left to time out without sign-on. So, essentially the same attack vector [unintentional or intentional] still exists.

Yeah had thought that might be the case but was hoping not ... so what to do? Register IP's with pool, can't imagine that would be popular or that simple either.

My hunch is they DDOS in the hope of colliding with enough work packets that eventually they'll start hitting golden tickets .... if the pool and miners were connected across Tor they wouldn't even know which packets to aim at ... but back to the other overheads there like ssh. Tough one.