If you look at the status page, you will see there are zero workers connected. It's probably related to the database having been down for a while - the workers haven't been restarted yet.

I'm more surprised by the PRPs from 300 to 800 digits. These seem to have a wide range of forms, but all have a creation date of today.

There are 7 workers connected now and all the PRP's <300 digits are now proven. :)

and here he goes again, this time with 35 digits composite....

[QUOTE=firejuggler;282969]and here he goes again, this time with 35 digits composite....[/QUOTE]
False start. He has settled in at 61 digits now.

It is apparent to any reasonable person that factoring all (say) 41-digit numbers will saturate and shut down the database (or a database of any size). It amounts to a DoS attack and such user should be banned from factorDB for a significant [URL="http://en.wikipedia.org/wiki/Denial-of-service_attack#Legality"]period of time[/URL].

[QUOTE=Batalov;282983]It amounts to a DoS attack ....[/QUOTE]

Hmm, and kar_bon appears to have found some useful documentation.

So much disk space and bandwidth wasted - what a pity.

I tried to stop this several times and blocked quite a lot ip´s, most of them seemed to be proxy or tor exit node ip´s.

I dont know what to do about this at the moment!

[QUOTE=Syd;283041]So much disk space and bandwidth wasted - what a pity.

I tried to stop this several times and blocked quite a lot ip´s, most of them seemed to be proxy or tor exit node ip´s.

I dont know what to do about this at the moment![/QUOTE]Put a Captcha on anything that tries to write to the database?

[QUOTE=Syd;283041]So much disk space and bandwidth wasted - what a pity.

I tried to stop this several times and blocked quite a lot ip´s, most of them seemed to be proxy or tor exit node ip´s.

I dont know what to do about this at the moment![/QUOTE]

Require a login to write to the database? Then bad behavior can be stopped by deleting the user's account.

Re: Xilman
Put the captcha in the user creation process... then at least you only have to do it once and folks with automated (but legitimate) hooks into the database (bchaffin's workers?) won't be affected.

[QUOTE=Syd;283041]I dont know what to do about this at the moment![/QUOTE]

If I may make some suggestions:

- Make each user submit an e-mail address to which a confirmation e-mail is sent. Only once the user confirms the secret (I use a MD5 string of (truly) random data) are they given access. (Warning: this can be used to create annoying e-mails to third parties; limit one sign-up attempt per IP.)

- Use "CAPTCHAs" on both the sign-up page and the confirmation page.

- Establish a "trust" level for each user. Only after a user has proven they are legitimate (by submiting valid and valuable data) are they able to submit large amounts of data.

Unfortunately, this kind of behaviour is common on the "Wild Wobbly Web".... :sad:

force a log-in to write anything in the DB, and put a low limit to how many you can 'write' in the DB, something like 200 id per day.

edit : oh well, i'm late, follow bsquared and chalsall suggestion!