You don't want to rely on a specific hasher as your only means of security.  Realistically, it prevents brute forcing but dictionary attacks are still possible (which is where you should really focus on).  bcrypt does make it slow for the normal person to crack but there are still big unknowns in it and the more "secure" scrypt.

bcrypt has two known problems: it's not as slow as originally thought if you threw enough money at it (FPGA, ASIC) and there is a problem with the implementation that gives it something like at least a 4% chance of collisions.  They have not been studied enough, hence it is somewhat like security through obscurity (it took them many years of use before they found out that the standard implementation of bcrypt that just about everyone uses was flawed and would take many more years to completely phase out the bad implementation).

And as was already mentioned, if it's not used with proper safeguards, DoS attacks are possible.

Yup, rackspace.. though my other business has a few servers with them as well (separate account) and those were fine.

There's a DDoS in progress.  The network provider won't allow any new connections to the site but those that use miners that use keep-alive connections are still able to mine until the connection closes.

It was removed and had to be re-implemented.

You should be able to change your passcode now.

That's how DGM works.  Every time a payout is made, you lose some of your score/reward for the next estimated payout.  I'm not sure if there are any sites that show a graph of your historical estimated rewards or update the estimates as frequently as we do (approximately every minute) so you wouldn't notice it at other pools unless you kept track of it manually.

The amount of dropoff depends on the dynamic fee and cross-round leakage.  If you've been using Eclipse, I believe the leakage is 0.99, which will have little dropoff every time you get paid.  The lower the dropoff, the longer it will take to get your rewards to fully mature and you'll need to mine for a longer time period to reach equilibrium.

Meni uses the analogy of a capacitor:

Thanks for signing up   Luck is pretty bad on this round.  We're currently at 5m+ shares and the average should be about 1.5m.

Some tools for managing really ridiculous passwords:
http://xkcd.com/936/
http://keepass.info/
http://www.keepassx.org/

maybe they didn't get your other messages either.

Admin hasn't received any messages.  you can pm me the problem here or post it publicly here or on Ogrr.

this is news to me.  admin's mailbox is empty.  how have you gone about seeking help for your problem, and what is your problem?

It's based on analysis done by others using leaked passwords on social sites.

The common words database used contains:

- Lists of top 20-100 words used in cracked passwords from various sources
- Top common names according to certain sites
- Dictionary words used by password crackers

Common names are on the list because the analysis showed many cracked passwords contained common names.

The list is English-centric so common international words will probably sneak by.

soon!

If you absolutely must have a certain word in the password and it's complaining about it being common, you can increase the length of the password until it gets accepted.  For example, if the password "common123" was rejected, you could try "common12345678" instead.  Also, it's not only common words but common names as well.

$40,000 in store credit for Diablo 2 items at http://lewt.com or $10,000 in Bitcoin as prizes.

https://ogrr.com/viewtopic.php?t=3104

It'll let you know what the problem is.  In your case, the password you chose was considered weak because it contains some words it considers too common.  Passwords must have at least a letter and non-letter (number or special character), can be from 8 to 128 characters, can't contain your username, and must pass the common words check unless it is sufficiently long.

I think it's fixed now.  It was an issue with IE8.

Can you PM me the worker name you're trying to add, browser you're using, and whether javascript is enabled?

What error is it showing when you try to add it?  Have you tried a different worker name?  Perhaps it doesn't like some of the characters in the name.

I think the higher variance lately is a product of the lower hashrate since the big hopper left.  Luck had been just about even until the last block and we've had merged mining going for several weeks now.  Did Mt. Red's bad "luck" begin right when they turned merged mining on?

For anyone that still wants to use this for the 0.6.0 release, I've made some patches with slight modifications to David's code.  It's split up into two parts.  The first part should still be relevant for pool operators (keep-alive connections, hub mode, USR1 signals on block changes).  The second part is mostly obsolete now with merged mining and better pooling software (faster getwork).

You can find the patches at http://pastebin.com/viJV1NLi and http://pastebin.com/UXep0r3c

Some of the updates from 0.4 to 0.6 are non-trivial so this should help.  This particular patch hasn't been tested much but a different one for 0.6.0 rc4 has been running without any problems.

Edit: Oops, the patches were for the current head instead of 0.6.0.
Edit2: Updated the above links for the right patches.

For future reference, these may give you a head start on patching against 0.6.1: http://pastebin.com/XSBqRAaP and http://pastebin.com/5R9N29aA.

whoops.  fixed the link.  just click on statistics > block statistics from the homepage to get there.