6.13.x client signiture error with Docking@Home

Message boards : BOINC client : 6.13.x client signiture error with Docking@Home
Message board moderation

To post messages, you must log in.

AuthorMessage
Boyu

Send message
Joined: 28 Oct 11
Posts: 1
United States
Message 41039 - Posted: 7 Nov 2011, 14:31:41 UTC

Hi,

We observed some comparability problem between Docking@Home and the new version of boinc client (6.13.x). But we don't have any error for the version 6.12.x. In Docking@Home server, the boinc API is 5.9.2 version, this project has been running since 2007. Could anyone let me know if this is by designed for the core client 6.13.x or this is a bug for this client version?

Please let me know if I am posting in the wrong place :)

Boyu
ID: 41039 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15480
Netherlands
Message 41041 - Posted: 7 Nov 2011, 14:53:14 UTC - in response to Message 41039.  

As per http://boinc.berkeley.edu/dev/forum_thread.php?id=6917&nowrap=true#40129:

David Anderson wrote:
There are (at least) two issues with 6.13.3:

1) For GPU apps, it passes an additional command-line argument that causes some apps to fail (usually by exiting immediately). This will be fixed in 6.13.4.

2) 6.13.3 handles file upload certificates (a mechanism that prevents DoS attacks on upload servers) differently than previous versions.
This change was necessary to make scheduler requests and replies readable by standard XML parsers. But it means that file uploads will fail to projects that a) use upload certificates, and b) aren't running current server code.

I sent email to boinc_projects describing this change, and recommending that projects disable upload certificates until they're able to upgrade their server code. Not all project admins read boinc_projects, so it may be necessary to contact them via their message boards or email, and I urge Alpha-testers to do so.

-- David


David Anderson, boinc_projects email list wrote:
"Upload certificates" are a mechanism that keeps bad guys from DoS'ing your upload servers (note: such an attack has never happened, as far as I know).

We're changing the format of upload certificates, and we're starting to test a version of the client for which old-format certificates won't work. Volunteers testers won't be able to upload completed jobs, and they may complain to you.

I suggest that all projects disable upload certificates. To do so, add the following to your config.xml file:

<dont_generate_upload_certificates/>
<ignore_upload_certificates/>

To resume using upload certificates, if you wish:

1) upgrade to the current server source code (from trunk)
2) wait for all jobs with old-format certificates to be dispatched
3) re-enable certificates by removing the above lines.

Let me know if any questions.

-- David

ID: 41041 · Report as offensive

Message boards : BOINC client : 6.13.x client signiture error with Docking@Home

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.