From: bs <bs@nospam.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] multiple certs
Date: Wed, 31 Mar 2004 21:14:25 -0500 [thread overview]
Message-ID: <406B7B01.7060809@nospam.com> (raw)
In-Reply-To: <61fafe8ab9b86563901218d32ec29c92@borf.com>
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.
next prev parent reply other threads:[~2004-04-01 2:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 22:11 Brantley Coile
2004-04-01 0:51 ` bs
2004-04-01 0:54 ` Brantley Coile
2004-04-01 2:10 ` bs
2004-04-01 2:14 ` bs [this message]
2004-04-01 13:20 ` Russ Cox
2004-04-01 13:38 ` Brantley Coile
2004-04-01 14:28 ` boyd, rounin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=406B7B01.7060809@nospam.com \
--to=bs@nospam.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).