Yes, I believe the key must be named id_dsa (or id_rsa, depending on what you used to generate it). There is probably a way to change the required name, but the easiest fix is probably to rename it and try again. -Ray
On Wed, Aug 26, 2009 at 12:18 PM, DrewHuddleston <[email protected]>wrote: > > Additionally, does Versions expect the private key to have the name > 'id_dsa'? ...my key does not have that name. > > Take a look at my console error log: > > 26/08/2009 17:00:52 [0x0-0x2d02d].SSHKeychain[308] > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > 26/08/2009 17:00:52 [0x0-0x2d02d].SSHKeychain[308] @ WARNING: > UNPROTECTED PRIVATE KEY FILE! @ > 26/08/2009 17:00:52 [0x0-0x2d02d].SSHKeychain[308] > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > 26/08/2009 17:00:52 [0x0-0x2d02d].SSHKeychain[308] Permissions 0644 > for '/Users/Drew/.ssh/drew_huddleston_200809.ppk' are too open. > 26/08/2009 17:00:52 [0x0-0x2d02d].SSHKeychain[308] It is recommended > that your private key files are NOT accessible by others. > 26/08/2009 17:00:52 [0x0-0x2d02d].SSHKeychain[308] This private key > will be ignored. > 26/08/2009 17:00:52 [0x0-0x24024].com.picodev.Versions[203] > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > 26/08/2009 17:00:52 [0x0-0x24024].com.picodev.Versions[203] @ > WARNING: UNPROTECTED PRIVATE KEY FILE! @ > 26/08/2009 17:00:52 [0x0-0x24024].com.picodev.Versions[203] > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > 26/08/2009 17:00:52 [0x0-0x24024].com.picodev.Versions[203] > Permissions 0644 for '/Users/Drew/.ssh/id_dsa' are too open. > 26/08/2009 17:00:52 [0x0-0x24024].com.picodev.Versions[203] It is > recommended that your private key files are NOT accessible by others. > 26/08/2009 17:00:52 [0x0-0x24024].com.picodev.Versions[203] This > private key will be ignored. > 26/08/2009 17:00:52 [0x0-0x24024].com.picodev.Versions[203] bad > permissions: ignore key: /Users/Drew/.ssh/id_dsa > 26/08/2009 17:00:52 [0x0-0x24024].com.picodev.Versions[203] Permission > denied (publickey,keyboard-interactive). > > > > > > On Aug 26, 4:11 pm, DrewHuddleston <[email protected]> wrote: > > `svn info svn+ssh://usern...@repository_location` resulted in the > > following: > > svn: Syntax error parsing revision 'repository_location' > > > > So I did this instead: > > `svn info svn+ssh://usern...@repository_location@` which resulted in > > the following: > > Permission denied (publickey,keyboard-interactive). > > svn: Connection closed unexpectedly > > > > And of course, I did replace username & repository_location with the > > appropriate info. > > > > Thanks for the help, Ray! > > > > Drew > > > > On Aug 26, 3:28 pm, Ray <[email protected]> wrote: > > > > > > > > > Can you connect to the repository through the Terminal? > > > `svn info svn+ssh://usern...@repository_location` > > > > > -Ray > > > > > On Wed, Aug 26, 2009 at 8:57 AM, DrewHuddleston > > > <[email protected]>wrote: > > > > > > I have followed the instructions provided in Versions help > > > > documentation: > > > > > > [Setting the desired location beginning with svn+ssh:// then] enter > > > > your username in your repository bookmark and leave the password > field > > > > blank. > > > > > > However, when I click the "create" button I receive the following > > > > error: > > > > > > Connection closed unexpectedly > > > > > > I have been researching possible causes and my best guess is Versions > > > > is unable to locate my private key. I have been able to use > > > > Cyberduck's SFTP with this private key and can access the trunk with > > > > the key using a Windows SVN client so I am 90% certain the trouble > > > > rests with Versions. > > > > > > I would love to support this product, but if it does not meet my > needs > > > > I will have to find a different option. > > > > > > Any help? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Versions" 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/versions?hl=en -~----------~----~----~----~------~----~------~--~---
