From: Yitzchak Scott-Thoennes Date: Fri, 3 Aug 2007 11:47:22 +0000 (-0700) Subject: ssh-keygen usage in repository.pod out of date X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=0fac28e65c3df7a4905870251fba61bf435df523;p=p5sagit%2Fp5-mst-13.2.git ssh-keygen usage in repository.pod out of date Message-Id: <37856.64.81.167.122.1186166842.squirrel@webmail.efn.org> p4raw-id: //depot/perl@31681 --- diff --git a/Porting/repository.pod b/Porting/repository.pod index f51bb19..637cf2f 100644 --- a/Porting/repository.pod +++ b/Porting/repository.pod @@ -70,7 +70,10 @@ will be the file F<~/.ssh/identity> which is suitable unless you particularly want to keep separate ssh identities for some reason. If so, you could save the perl repository private key in the file F<~/.ssh/perl>, for example, but I will use the standard filename -in the remainder of the examples of this document. +in the remainder of the examples of this document. (Some ssh +implementations will default to creating a F<~/.ssh/id_rsa*> +ssh prototcol 2 RSA key pair instead - see below. Use the -t rsa1 +option if you really want a protocol 1 key pair.) After typing in the filename, it will prompt you to type in a passphrase. The private key will itself be encrypted so that it is