From: Brantley Coile <bwc@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] certificates and tlssrv
Date: Wed, 31 Mar 2004 08:20:28 -0500 [thread overview]
Message-ID: <83a81270a19a808b4df7202350f77568@borf.com> (raw)
In-Reply-To: <b02895b0ded2d54007e671d5facf65e1@collyer.net>
> I think he wants to have tlssrv present multiple certificates to
> clients, so that they can follow the chain back to the root.
I should know better than to compose a 9fans request at 8pm!
Geoff is correct. I want web browsers not to complain about the
certificate I give them. I have a chain we bought from somewhere.
Under openSSL (don't get me started : ) I put them all into a single
file that was loaded. The readcert(2) seems to stop after reading a
single cert. Should I hack it to catenate them togeter and set the
TLSconn->cert to that whole thing?
Thanks
Brantley
next prev parent reply other threads:[~2004-03-31 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 23:48 Brantley Coile
2004-03-31 1:43 ` David Presotto
2004-03-31 1:47 ` Geoff Collyer
2004-03-31 13:20 ` Brantley Coile [this message]
2004-03-31 20: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=83a81270a19a808b4df7202350f77568@borf.com \
--to=bwc@coraid.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).