| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 46
|
|
| Author |
|
|
twilyth
Master Cruncher US Joined: Mar 30, 2007 Post Count: 2130 Status: Offline Project Badges:
|
Something just occurred to me. How exactly does WCG think they're going to be able to confirm team changes? Even if you monitor an acct for email changes, the fact of the matter is that if a person's WCG acct wasn't adequately secured, the same probably goes for their email.
----------------------------------------They really need to get the word out to ALL WCG members post haste before many more accounts and possibly their email addresses have been compromised. You need to get ahead of attacks like this, not just react to them. ![]() ![]() |
||
|
|
branjo
Master Cruncher Slovakia Joined: Jun 29, 2012 Post Count: 1892 Status: Offline Project Badges:
|
Thanks jhindo for info and for the link
---------------------------------------- Cheers ![]() ![]() Crunching@Home since January 13 2000. Shrubbing@Home since January 5 2006 ![]() |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I believe I found our hacker.
One nice thing about ripple is that it has a public ledger. Our hacker has a ripple public address of: r44Z941P6eJxudgXU6Mf5Fz9q9cjZ9pVRR I found this address by looking at the computing for good stats of: 99hawk Argfan Barnsley_Tatts All of them had their XRP sent to the same address, the one referenced above. It might be possible to contact a gateway to determine the identity of this individual. I estimate 5 accounts remain hacked, based on the ripple addresses recent activity. |
||
|
|
twilyth
Master Cruncher US Joined: Mar 30, 2007 Post Count: 2130 Status: Offline Project Badges:
|
Lydian: Nice work. Thanks for putting in the effort. Hopefully the RL staff can look more into this with this lead. Cheers!!!
----------------------------------------![]() ![]() ![]() |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Securing the website by using some form of lockout after 2 or 3 failed attempts would not be a solution. Boinc clients use the same password to connect so all someone would have to do is bypass the website by writing a script that runs a dictionary attack against the Boinc servers by pretending to be a boinc client trying to connect. Then once a valid password is found a single, valid, logon to the website could be made. The logon process to all areas needs hardening.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Documentation suggests this route gets closed after 10 failed attempts followed by blacklisting and a mail to the administrator.
|
||
|
|
|