Thank you for bringing it to our attention that it was not well documented. I have update our FAQ with this answer as well.
http://code.google.com/p/support/wiki/FAQ#Where_do_I_get_a_password_for_committing_to_Subversion? Nathan On Tue, Mar 31, 2009 at 11:55 AM, IsmAvatar <[email protected]> wrote: > > Thank you very much for your answer, Nathan. This explains it very > well for me. > -IsmAvatar > > On Mar 31, 12:46 pm, Nathan Ingersoll <[email protected]> wrote: >> Hi IsmAvatar, >> >> You have basically answered your own question. :-) >> >> The default for many svn clients in the wild is to automatically cache >> the password on your local disk. Your Google Account password is much >> too valuable to expose in this manner. So while there is an >> inconvenience for users with clients that do not automatically cache >> the password, the risk it avoids in the other clients is worth it. >> >> As for why you cannot set it, for the reasons mentioned above, we >> would prefer this password to be thought of in the same way as a >> temporary password sent via email. It has a similar level of security >> in that it is potentially accessible by third-parties as plain text. >> Allowing users to set their own password is likely to encourage them >> to divulge their Google Account or other high risk passwords. >> >> I hope that answers your questions. >> Nathan >> >> On Tue, Mar 31, 2009 at 11:11 AM, IsmAvatar <[email protected]> wrote: >> >> > I've searched all over the place but could not find any explanation as >> > to why Google Code requires you to use their generated password >> > instead of your gmail password or any other user-defined password. I >> > did find one post to this group earlier that asked if they could set >> > their own password, and they received the reply: "No", which tells me >> > nothing. He also stated "it's hard to remember the password" to which >> > he received the reply "Then use svn's built in password caching" (and >> > all I could think is "because that's totally secure</sarcasm>") Many >> > other SVN repository hosting solutions allow you to set your own >> > password. In fact, as far as I'm aware, it seems the global norm that >> > password randomization is only for if you wish to lose your account >> > without deleting in or having it compromised... >> >> > So all I ask is: Why? Why does our code password have to be generated? >> > Why can't we just set it? >> >> > -IsmAvatar > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hosting at Google Code" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en -~----------~----~----~----~------~----~------~--~---
