diff options
| author | Steve Peters <steve@fisharerojo.org> | 2006-07-18 03:10:51 +0000 |
|---|---|---|
| committer | Steve Peters <steve@fisharerojo.org> | 2006-07-18 03:10:51 +0000 |
| commit | 7dda06b0ce85ef7e0a083140f0ca018d4ae2afdc (patch) | |
| tree | 8a61e477150d5a7c2e8f90b0d64bcf0da87f634b /Porting | |
| parent | 9aaf14db0f3c171369e4348eb60c54ad52a14a34 (diff) | |
| download | perl-7dda06b0ce85ef7e0a083140f0ca018d4ae2afdc.tar.gz | |
Additional reason for ssh passphrase failures.
p4raw-id: //depot/perl@28596
Diffstat (limited to 'Porting')
| -rw-r--r-- | Porting/repository.pod | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/Porting/repository.pod b/Porting/repository.pod index 74ac25d116..f51bb19618 100644 --- a/Porting/repository.pod +++ b/Porting/repository.pod @@ -233,7 +233,9 @@ above. If you see a prompt that looks like: Then you either don't have a F<~/.ssh/identity> or F<~/.ssh/id_rsa> file corresponding to your public key, or that file is not readable. -Fix the problem and try again. +Fix the problem and try again. Alternatively, some ssh implementations +will fail to verify your RSA key if the key if readable by others. +Just lower the permissions to make the key readable to yourself. If you only had the public key file for one protocol installed at the server end then make sure your client is using the corresponding |