Mailing-List: contact lucene-dev-help@jakarta.apache.org; run by ezmlm
Message-ID: <3F734BDF.7080006@lucene.com>
Date: Thu, 25 Sep 2003 13:11:11 -0700
From: Doug Cutting <cutting@lucene.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030701
MIME-Version: 1.0
To: Lucene Developers List <lucene-dev@jakarta.apache.org>
Subject: Re: 1.3 release
References: <486EB0DF-EF0F-11D7-BEE7-000393A564E6@ehatchersolutions.com>
 <3F731234.6000308@lucene.com> <3F732EE6.1070606@earthlink.net>
 <3F733EC6.2040506@lucene.com> <3F734AC8.7040500@earthlink.net>
In-Reply-To: <3F734AC8.7040500@earthlink.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Dmitry Serebrennikov wrote:
> Thanks very much, Doug. I'll give this a shot tonight. This is basically 
> what I tried to do, except that I used rsa key instead of dsa, did not 
> know about having the public key file unreadable to others, placed it
> ~/.ssh/authorized_keys directory (is authorized_keys2 in your example a 
> plain file?), and didn't use :ext: in the -d option to cvs. I guess 
> there's planty here that would have made it not work.:)

authorized_keys2 is for dsa keys, used by the ssh version 2 protocol, 
while authorized_keys is for rsa keys used by ssh versioon 1 protocol. 
I seem to recall that Apache maybe only uses ssh v2, that's why I 
recommended it.  I've generated and installed both sorts of keys, but 
'ssh -v' appears to report that the dsa key is the one actually used.

I'm no expert at this stuff.  I too find it confusing.  But I can get it 
to work.  So please only interpret my instructions as steps in the right 
direction.

Doug