Quote from: steve15 on December 31, 2013, 05:02:00 PM

Quote from: philipma1957 on December 31, 2013, 04:56:54 PM

I did think about it. I found it to be bad timing on your part to announce you did this and that the announcement matches very odd behaviour of our miners. What I would like to know is how many miners other then the two mention have this problem which is why I posted this here. You have admitted you viewed 1100 plus miners. if only the two I mention have this problem after being viewed by you then most likely this has nothing to do with your testing.

Well, just wait until the post goes public then! Hurry up and push KnC to patch up.
Can you imagine the horror once i post the full details?

For your information; the +1100 miners are public available on the net, everybody can scan and see them.
I bruteforced 28 logins, but i never actually logged in. Dont you know your KnC has a log? CHECK YOUR LOG BEFORE THROWING MUD!!!

So you attacked 28 logins of the 1100 plus miners and you were successful with them. your words not mine . you claim to own 2 machines so at best 26 miners are not yours. did you get permission to try them? so I do I know if one or both of the machines I own shares in were not damaged by you?

causing them to lose about .5btc each in hash. look If no one comes to the thread other then me then maybe the 28 machines you hacked were not injured in terms of hash power. but announcing to the world that you hacked /brute forced 28 machines puts you at risk for damages. Any one including me and my 9.5 percent share of 2 Jupiter's (about 100gh) can say your actions caused them harm. Frankly I am posting this here to say that brute forcing some ones password with out permission is not to clever in terms of liability .

Can you prove the 28 machines that were brute forced were not damaged? Can you prove you did not attack the machines I own a piece of? Most people do not realize that for civil damage the proof is not as high as it is for criminal damage. So I am not slinging any mud I am pointing out that you may have set yourself up for problems. you should have asked for 30 knc owners to be testers.

If you had permission to do a brute force attack on the 28 machines you should have told us that right up front.