Martin 53N 1W wrote:

[...]

See, what confuses me is the claim is the client was leaked. Ok, I
can [...]

Some testers publicised the signup http and Berkeley had a lot of
people signed up in just a few hours. They had relied on 'obscurity'
for their security rather than anything more strict.

Perhaps Berkeley were too soft in not closing the project or killing
the excess accounts. For better, they ran with it and found a few
problems sooner rather than later (:-)).

No, I'm still not buying it. I was a beta tester and right up until Berkeley
decided to release BOINC on the unsuspecting public the beta testers were
attaching to a different project and url:
http://setiboinc.ssl.berkeley.edu/ap/ is the beta url as opposed to
http://setiathome.berkeley.edu for the public project. Berkeley were
actively seeking beta testers to the best of my knowledge and I was still in
fact beta testing when the public version, url and sign-up page was posted
on the SETI site. A completely different sign-up was needed for the public
project, I couldn't sign into it with my beta account key although I could
choose to run them concurrently much as you can with SETI and CPDN with
BOINC.

Something fishy I'm telling ya.
--
~misfit~