Posts by GHz

1) Message boards : BOINC client : Duplicate host after backup restore: why? (Message 9334)
Posted 3 Apr 2007 by Profile GHz
Post:
Thanks very much to MikeMarsUK and Metod, S56RKO for the information about this case :)

Bye
2) Message boards : BOINC client : Duplicate host after backup restore: why? (Message 9162)
Posted 28 Mar 2007 by Profile GHz
Post:
Hi, i have a question about a problem of duplicate host.
One user report me this problem. He was attached only to seti@home, and before change the client (from cruncher to KWNS), he make a backup of the boinc folder. The update of the client failed (all wu in error because the app_info was not ok and boinc was unable to find the client). This is a screen of the error: http://img81.imageshack.us/img81/1217/errorib0.png
After this, he close BOINC and restore the backup. It works ok like before, but the scheduler generate a new host CPID :| and a new host in the account! Why this?? This is the log after restore of the backup:
27/03/2007 23.01.08||Starting BOINC client version 5.4.9 for windows_intelx86
27/03/2007 23.01.08||libcurl/7.15.3 OpenSSL/0.9.8a zlib/1.2.3
27/03/2007 23.01.08||Data directory: C:\BOINC
27/03/2007 23.01.08|SETI@home|Found app_info.xml; using anonymous platform
27/03/2007 23.01.08||Processor: 1 AuthenticAMD AMD Athlon(TM) XP 2000+
27/03/2007 23.01.08||Memory: 767.47 MB physical, 2.21 GB virtual
27/03/2007 23.01.08||Disk: 76.32 GB total, 51.14 GB free
27/03/2007 23.01.08|SETI@home|URL: http://setiathome.berkeley.edu/; Computer ID: 774216; location: home; project prefs: default
27/03/2007 23.01.08||General prefs: from SETI@home (last modified 2006-07-31 23:47:11)
27/03/2007 23.01.08||General prefs: no separate prefs for home; using your defaults
27/03/2007 23.01.08||Remote control allowed
27/03/2007 23.01.08||Listening on port 31416
27/03/2007 23.01.08|SETI@home|Resuming task 03no03aa.12667.9393.254826.3.8_2 using setiathome_enhanced version 519
27/03/2007 23.01.08|SETI@home|Started upload of file 27se04ab.11205.19489.248590.3.33_3_0
27/03/2007 23.01.08|SETI@home|Fetching scheduler list
27/03/2007 23.01.13|SETI@home|Scheduler list download succeeded
27/03/2007 23.01.18|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
27/03/2007 23.01.18|SETI@home|Reason: Requested by user
27/03/2007 23.01.18|SETI@home|(not requesting new work or reporting completed tasks)
27/03/2007 23.01.23|SETI@home|Scheduler request succeeded
27/03/2007 23.01.23|SETI@home|Generated new host CPID: 0e75ed54f7c7d5eb4db7b45e19c0946a
27/03/2007 23.01.29||Project communication failed: attempting access to reference site
27/03/2007 23.01.30|SETI@home|Temporarily failed upload of 27se04ab.11205.19489.248590.3.33_3_0: http error
27/03/2007 23.01.30|SETI@home|Backing off 1 minutes and 23 seconds on upload of file 27se04ab.11205.19489.248590.3.33_3_0
27/03/2007 23.01.32||Access to reference site succeeded - project servers may be temporarily down.
27/03/2007 23.01.48|SETI@home|Started upload of file 27se04ab.11205.19489.248590.3.33_3_0
27/03/2007 23.02.09||Project communication failed: attempting access to reference site
27/03/2007 23.02.10|SETI@home|Temporarily failed upload of 27se04ab.11205.19489.248590.3.33_3_0: http error
27/03/2007 23.02.10|SETI@home|Backing off 3 minutes and 26 seconds on upload of file 27se04ab.11205.19489.248590.3.33_3_0
27/03/2007 23.02.11||Access to reference site succeeded - project servers may be temporarily down.
27/03/2007 23.02.58|SETI@home|Started upload of file 27se04ab.11205.19489.248590.3.33_3_0
27/03/2007 23.03.20||Project communication failed: attempting access to reference site
27/03/2007 23.03.20|SETI@home|Temporarily failed upload of 27se04ab.11205.19489.248590.3.33_3_0: http error
27/03/2007 23.03.20|SETI@home|Backing off 18 minutes and 3 seconds on upload of file 27se04ab.11205.19489.248590.3.33_3_0
27/03/2007 23.03.21||Access to reference site succeeded - project servers may be temporarily down.
27/03/2007 23.03.28|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
27/03/2007 23.03.28|SETI@home|Reason: Requested by user
27/03/2007 23.03.28|SETI@home|(not requesting new work or reporting completed tasks)
27/03/2007 23.03.33|SETI@home|Scheduler request succeeded
27/03/2007 23.04.11|SETI@home|Started upload of file 27se04ab.11205.19489.248590.3.33_3_0
27/03/2007 23.04.33||Project communication failed: attempting access to reference site
27/03/2007 23.04.33|SETI@home|Temporarily failed upload of 27se04ab.11205.19489.248590.3.33_3_0: http error
27/03/2007 23.04.33|SETI@home|Backing off 5 minutes and 7 seconds on upload of file 27se04ab.11205.19489.248590.3.33_3_0
27/03/2007 23.04.34||Access to reference site succeeded - project servers may be temporarily down.
27/03/2007 23.04.52|SETI@home|Started upload of file 27se04ab.11205.19489.248590.3.33_3_0
27/03/2007 23.05.14||Project communication failed: attempting access to reference site
27/03/2007 23.05.14|SETI@home|Temporarily failed upload of 27se04ab.11205.19489.248590.3.33_3_0: http error
27/03/2007 23.05.14|SETI@home|Backing off 49 minutes and 28 seconds on upload of file 27se04ab.11205.19489.248590.3.33_3_0
27/03/2007 23.05.15||Access to reference site succeeded - project servers may be temporarily down.
27/03/2007 23.06.27|SETI@home|Started upload of file 27se04ab.11205.19489.248590.3.33_3_0
27/03/2007 23.06.48||Project communication failed: attempting access to reference site
27/03/2007 23.06.48|SETI@home|Temporarily failed upload of 27se04ab.11205.19489.248590.3.33_3_0: http error
27/03/2007 23.06.48|SETI@home|Backing off 2 hours, 25 minutes and 29 seconds on upload of file 27se04ab.11205.19489.248590.3.33_3_0
27/03/2007 23.06.50||Access to reference site succeeded - project servers may be temporarily down.
28/03/2007 0.28.58|SETI@home|Started upload of file 27se04ab.11205.19489.248590.3.33_3_0
28/03/2007 0.29.55|SETI@home|Finished upload of file 27se04ab.11205.19489.248590.3.33_3_0
28/03/2007 0.29.55|SETI@home|Throughput 2895 bytes/sec
28/03/2007 1.10.54|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
28/03/2007 1.10.54|SETI@home|Reason: Requested by user
28/03/2007 1.10.54|SETI@home|Reporting 1 tasks
28/03/2007 1.10.59|SETI@home|Scheduler request succeeded
28/03/2007 1.10.59|SETI@home|Message from server: Can't find host record
28/03/2007 1.10.59|SETI@home|Generated new host CPID: bc07657a8b3d56cab08100c48b4b0f94


The original host (774216) exist in the account page and seems to be ok. Why boinc generate other host and CPID? I want to understand....:P
3) Message boards : BOINC Manager : Trojan boinc installation by rogue member (Message 8362)
Posted 22 Feb 2007 by Profile GHz
Post:
Thanks to all involved in the removement of this ***** (insert your smear word of choice).

Thanks GHz for his efforts.

Thanks the unknown (and unvoluntary) cruncher for his/her cooperation.

Thanks to the guys'n'galy at the projects to deal with this ***** quite fast (the remaining ones will follow soon I hope).





Thank you to the members of Boinc Italy for all the information. If you have some way of contacting your anonymous informant (private message or email?), would you please say thank you to him from us all.


Of course, I've sent him a message about with a link to this thread too ;)

Bye,
Paolo - GHz
4) Message boards : BOINC Manager : Trojan boinc installation by rogue member (Message 8332)
Posted 21 Feb 2007 by Profile GHz
Post:
Hi mo.v,
thanks to inform all the BOINC comunity about the "Wate" problem.

We are happy for having contributed to discover and to stop it.

I've first contacted Dr.David to explain him the problem, and the day after we contacted all the interested project (thanks to LucaB for his effort in this phase too!). The first project that blocked Wate account was Rosetta, and after CPDN where the account was totaly deleted (that is the best thing we hoped for that bad user!). After all other projects blocked his account (the last was BURP, yesterday where Wate is ranked #1!). I can't verify it on Predictor and SIMAP because I don't have his account key of that projects. When the infected user send me the BOINC folder for the analysis, I've checked some of wate accounts, and the thing that impressed me so much, was the very high number of infected hosts listed!

When we tried to investigate about the cause of the infection, the infected user said that he downloaded a suspected file from P2P that can be the cause of the problems. I've tired to download the same file, and I discover that it was a trojan/backdoor, and I think that is the method used by Wate (I've not executed it to test :P). So I recommend to use a good antivirus program and always pay attention on what we download from unknown sources.

We are happy that now the Wate game is over. Thanks to the infected user for his collaboration to resolve the mystery, and thanks to all other BOINC.Italy members that have helped and contributet in some way, first of all LucaB. Thanks also to Dr.David and to all the project's admins.

Bye,
Paolo (GHz)
BOINC.Italy team



Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.