Re: Mersenne: PrimeNet vulnerable to client misconfiguration?

2001-04-16 Thread Nathan Russell
On Mon, 16 Apr 2001 18:53:33 +0200, Martijn Kruithof wrote: > >Hello, > >if that what you describe is the problem the solution is obvious >If a client checked out an (set of) exponent(s) and has not returned it yet >just re-assign that same (set of) exponent(s). The problem is that the two machi

RE: Mersenne: PrimeNet vulnerable to client misconfiguration?

2001-04-16 Thread Martijn Kruithof
Hello, if that what you describe is the problem the solution is obvious If a client checked out an (set of) exponent(s) and has not returned it yet just re-assign that same (set of) exponent(s). It could also be that some user does this on purpose for instance someone with 5 machines behind a f

RE: Mersenne: PrimeNet vulnerable to client misconfiguration?

2001-04-11 Thread Aaron Blosser
There should, at the least, be some "anti-whammy" protection against the same machine requesting more #'s than it could reasonably handle in a certain time period (2 years is more than generous, I'd think). We've seen this before, have we not? Misconfigured scripts of some sort which keep retrie