Crowdsourcing Bruteforcing: Help me win the EngineYard challenge • Hacker News Board

Re: Crowdsourcing Bruteforcing: Help me win the EngineYard challenge

#31

Post by barredo » Mon, Jul 20, 2009, 9:01 PM UTC

sil3ntmac wrote: post #30

judofyr wrote: post #26

Did you just get a hamming distance of 0, or is something broken?

Nah, some script kiddie messin with me. Fixed and patching the hole now...

Well, 43 isn't that bad :-)

Re: Crowdsourcing Bruteforcing: Help me win the EngineYard challenge

#32

Post by simonista » Mon, Jul 20, 2009, 9:05 PM UTC

I'd be curious to hear how many people/cycles you get to help with this.

Re: Crowdsourcing Bruteforcing: Help me win the EngineYard challenge

#33

Post by sil3ntmac » Mon, Jul 20, 2009, 9:06 PM UTC

barredo wrote: post #31

sil3ntmac wrote: post #30

Earlier quoted context omitted.

Nah, some script kiddie messin with me. Fixed and patching the hole now...

Well, 43 isn't that bad :-)

Haha, he left a message in my database.

"Oh but for your trouble I generated a few hundred thousand hashes for you. --Phil Freo"

Thanks Phil :-) Your message's hash had a hamming distance of 73

Re: Crowdsourcing Bruteforcing: Help me win the EngineYard challenge

#34

Post by ErrantX » Mon, Jul 20, 2009, 9:11 PM UTC

mbrubeck wrote: post #14

Periodic wrote: post #9

Earlier quoted context omitted.

It's going to be a lot slower, particularly with the goal of not slowing down a person's browser. By default, at least for me, their page is doing 1 hash per 200ms, or 5/second. On the other hand, a quick Haskell implementation using Data.Digest.Pure.SHA is doing about 6,000 hashes per second (might have been 8000, I forget now) per core on an Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz So you're looking at 1000 peopl…

This JavaScript version: http://news.ycombinator.com/item?id=715014 (which doesn't do any throttling) is doing ~1500 hashes per second in one Chrome tab on my fairly old (2.8 GHz Pentium D) desktop. I'm curious how fast it would be on your Core 2 Duo in two Chrome tabs.

Mine peaked at 3,450 or so on a Core2 Quad @ 3.2Ghz

Re: Crowdsourcing Bruteforcing: Help me win the EngineYard challenge

#35

Post by rarestblog » Mon, Jul 20, 2009, 9:13 PM UTC

mbrubeck wrote: post #11

fsniper wrote: post #10

Earlier quoted context omitted.

Well on my dual core, opening a new tab could not fire up the other core. Opening opera side by the firefox did the trick.

I've got two tabs in Chrome using two CPU cores.

I've got 6 tabs on Core2Duo in Chrome, barely uses 25% CPU total.

Re: Crowdsourcing Bruteforcing: Help me win the EngineYard challenge

#36

Post by infinity » Mon, Jul 20, 2009, 9:14 PM UTC

infinity wrote: post #21

Very cool idea, I wish you good luck!

I have just opened another 6 tabs on a different Duo Core machine, all sliders set to max. I will tell some more people ...

Re: Crowdsourcing Bruteforcing: Help me win the EngineYard challenge

#37

Post by sil3ntmac » Mon, Jul 20, 2009, 9:15 PM UTC

philfreo wrote: post #23

I hope you aren't disappointed when you a see a new update on your AJAX postback page that looks like a new winning string, when you see it is simply a note from me. :) (I also generated a few hundred thousand hashes for you)

Thanks Phil :)

I added a word checker, so no more of this tomfoolery!

Re: Crowdsourcing Bruteforcing: Help me win the EngineYard challenge

#38

Post by rarestblog » Mon, Jul 20, 2009, 9:15 PM UTC

Please increase delta range down to 1ms, Chrome barely uses CPU power at 10ms. 6 tabs @10ms uses 25% of Core2Duo.

Re: Crowdsourcing Bruteforcing: Help me win the EngineYard challenge

#39

Post by rarestblog » Mon, Jul 20, 2009, 9:17 PM UTC

rarestblog wrote: post #38

Please increase delta range down to 1ms, Chrome barely uses CPU power at 10ms. 6 tabs @10ms uses 25% of Core2Duo.

Also decrease rate at which HTML stats are updated - DOM update slows stuff down, it should update stats only once a second or so.

Re: Crowdsourcing Bruteforcing: Help me win the EngineYard challenge

#40

Post by sil3ntmac » Mon, Jul 20, 2009, 9:21 PM UTC

rarestblog wrote: post #39

rarestblog wrote: post #38

Please increase delta range down to 1ms, Chrome barely uses CPU power at 10ms. 6 tabs @10ms uses 25% of Core2Duo.

Also decrease rate at which HTML stats are updated - DOM update slows stuff down, it should update stats only once a second or so.

Updated to 1ms! I'll work on the HTML stat updates

Edit: fixed and fixed