WriteAccessHintAndTips

WriteAccessHintAndTips

Some things to beware of in the key deposit/writable-checkout process (DoingWritableCheckouts).

• Cut-and-paste of your keys can introduce spurious spaces and newlines - make sure you preserve the exact structure when depositing.
• As of this writing (Feb, 2002), most ssh clients/servers that i've used have an obscure, bogus behavior when it comes to using ssh v1 keys in the presence of v2 keys. If you have both an identity file and an id_rsa or id_dsa file (or both), by default, attempts to ssh will try only the id_rsa or id_dsa files (or both), but not fallback to the identity file.

  The workaround is either to use the v2 keys, or else include the line:

        protocol 1,2
  

  in your ~/.ssh/config file, to make it try the v1 key first. (You can qualify the scope of that directive to cvs.zope.org by preceding that line with a Host cvs.zope.org line.)

• Before doing a checkout, first try to ssh to cvs.zope.org - you should not be able to log in, but you should be able to successfully authenticate and then get an environment-variable dump, followed by some CVS complaints. (That's because your key entry was qualified with something that restricts your access to CVS only.) You should be challenged for your passphrase, not a password.

  If you are challenged for a password, something's amiss.

  First, if your origin account has a different name than the cvs account, you need to qualify your ssh (and the checkout lines you'll use) to specify the remote account name, eg:

  ssh cvs.zope.org -l soandso

  and:

  cvs -d :ext:soandso@cvs.zope.org:/cvs-repository co Zope

  If that doesn't help, try using the ssh -v option to get some indication about where the login is failing, and contact mailto:[email protected] for assistance.