From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <406B7B01.7060809@nospam.com>
From: bs <bs@nospam.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
MIME-Version: 1.0
To: 9fans@cse.psu.edu
Subject: Re: [9fans] multiple certs
References: <406B6786.7020904@nospam.com> <61fafe8ab9b86563901218d32ec29c92@borf.com>
In-Reply-To: <61fafe8ab9b86563901218d32ec29c92@borf.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Date: Wed, 31 Mar 2004 21:14:25 -0500
Topicbox-Message-UUID: 4af06084-eacd-11e9-9e20-41e7f4b1d025

Brantley Coile wrote:
>>Brantley Coile wrote:
>>
>>>So, maybe I missed it.  Did anyone have a suggestion
>>>on how to send a certificate chain in tlssrv?
>>>
>>
>>I don't think it can do certs as you see it.
>>
>>What you can do is send the fingerprint of your cert,
>>which it can lookup and authorize.
> 
> 
> I want to do https without having the browser fuss.
> How can figerprints help with that?
> 
If your browser is like Mozilla/Netscape, you can import
the server cert as a .pem file. So, if you know the cert it
presents, you can make the browser aware of it.
Simplest is to issue a self signed cert and import it
in the browser.