Folding Forum

I know I should have done this when I set them up.. But I am now in the process of adding passkeys to all my clients not just the SMP and about to recommend the same for all my team mates.
Couple of points, I hear that you shouldn't cut and paste them, if this is true that's a pain (I have 20 running).
Changing passkeys on the systray is easy enough via config window, but via consoles is the correct easiest method to shut down client andadd -configonly in target via properties? If you do not use a shortcut is there another method, or should you just create a shortcut first.
Is it really going to be useful to do this with all the uniprocessor clients? I seemed to have missed any rumours/announcements that this client is changing too.

Just want to get this clear in my head before advising others.

Personally, I haven't come across any rumors about cut and paste. I have saved my passkey in a text file and I simply copy and paste the passkey to my uni-processor clients.
I use systray and have no idea about consoles but as far as I know, if you change any settings in F@H, then it is recommended that you restart the client to make sure that all the new settings are applied.
I haven't read any rumors/announcements regarding uni-processor client but I would recommend that you do it as there was a recent case about Team FTL where someone with the same username faced some problems. Here's the link if your intrested (http://foldingforum.org/viewtopic.php?f ... t=Team+FTL)

Hope it helps you.

You do need to shut down the client to reconfigure it with -configonly, and it's fine to paste your passkey into the command line.

What isn't recommended is to open client.cfg manually and paste the passkey into that.

Wrish wrote:You do need to shut down the client to reconfigure it with -configonly, and it's fine to paste your passkey into the command line.

What isn't recommended is to open client.cfg manually and paste the passkey into that.

Ah that's maybe what I was thinking of... the side effect of manually keying in my passkey into 10 clients so far is that I have almost memorized it
Will cut and paste for the other 8 on my #2 system.
Still with this question about whether it is worthwhile for the uniprocessors.. aside from security.

Aside from security; too much free time with nothing better to do or one might be suffering from OCD and wants everything to be perfect

Panther-X wrote:I have saved my passkey in a text file and I simply copy and paste the passkey to my uni-processor clients.

I do the same, and I never had issues ... I just make sure to not copy "exotic" characters (end of line, carriage return, ...).

toTOW wrote:

Panther-X wrote:I have saved my passkey in a text file and I simply copy and paste the passkey to my uni-processor clients.

I do the same, and I never had issues ... I just make sure to not copy "exotic" characters (end of line, carriage return, ...).

The best way that I found is to double click the passkey and it is automatically highlighted so you can copy it easily without worrying about anything.

I made a passkey.txt file inside the fah folder with nothing but that string. So if I ever need to reinstall, or reconfigure, it's and easy cut and paste.

As for passkeys on CPU clients, YES, use them. The security issues should be reason enough. And if they started a Quick Return Bonus for the SMP clients, who's to say a future version of the CPU client with a bonus isn't that far off? Seems to be the trend...

Bonus for the Uni-Processor client would me very welcomed. I do hope that they hae plans to do that in the near future. Until then we can simply suggest this feature to them.

I would have thought that extending this to the remaining 'high performance client' the gpu client would be next, and this would certainly reduce the incidence of cherry-picking or overclocking past stable levels at the very least. But yes it seems to have been a successful strategy.
Anyway conjecture and theory right now..
Passkeys added to all my clients on all systems now, bring it on.

I have seen no official statements about what will happen with respect to passkeys on the GPU or the classic client. The fact that the option is there indicates some kind of grand plan. I've been using them since they were introduced just on general principles.

In addition to the security issue, the personal stats page has been updated so you can search for credits with or without your passkey. I can envision other useful improvements to the stats pages but if any of them actually happen, they're somewhere in the future as part of that grand plan.

Ya, I'm just guessing about CPU clients. Seems like a logical guess... and GPUs would seem to be the next likely target, except that the GPU client developement path is kind of up in the air right now, waiting for OpenCL.

If for nothing else, run the passkey on all supported clients. That way if/when another bonus plan comes along, you have a better chance at having your minimum 10 work units already finished and ready to go.