Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 2
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 559 times and has 1 reply Next Thread
gharbeia
Cruncher
Joined: May 20, 2009
Post Count: 1
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
confused restricted password incompatability

Greetings,

The accounts' password policy prevents the use of "special characters", quoted to be "!@#$%^&*_+=:;, etc...", while most websites allow these characters in passwords, and in fact encourage their use because of the added security.

The problem, however, is that in order to attach to WCG using a project manager like BAM, I have to not only change (downgrade) my password in BAM to something compatible with what WCG accepts, but also in every other project that I subscribe to, in order to allow BAM to use my password known to it to de/attach to these projects.

I find this unreasonable, no?

Of course having a centralised manager which depends on a unified password, instead of a public key of some kind, is short-sight.

Regards,
[Nov 15, 2010 12:51:19 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: restricted password incompatability

Greetings too,

Agreed and not agreed, previous discussions having gone before on this through these forums. Current password level and minimum length is good enough for a couple of large corporations that donate 10's of thousands of devices' idle cycle time to WCG a fully run project by IBM staff, inside their global network, so you can imagine that the state of security is taken serious, and at that WCG being the only one that actually requires https connection. Do any other BOINC projects require that?

For now, you cannot effectuate an WCG client attach via BAM to a new client... you've got to do the BAM attach anyhow FAIK. It has to be first time done manually at the client, after which you can attach and detach as often as you like via BAM. Works for me.

On the quoted line below, presume you're talking about BAM. For that you've got to get in touch with Willy. In addition, thought that through that manager you could change email and password for all project accounts in 1 go. Certainly you've shared your passwords with BAM.

Of course having a centralised manager which depends on a unified password, instead of a public key of some kind, is short-sight.

----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Nov 15, 2010 1:13:33 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread