9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: bs <bs@nospam.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] multiple certs
Date: Wed, 31 Mar 2004 19:51:18 -0500	[thread overview]
Message-ID: <406B6786.7020904@nospam.com> (raw)
In-Reply-To: <236644674bedacddc3c60778cf9d5a99@borf.com>

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.

This is similar to what some telnet clients do:
(a) someone must have had the authorization to the
     fp on the server
(b) you are presenting me with that, so, you are OK

http://www.vandyke.com/products/securecrt/public_key.html




  reply	other threads:[~2004-04-01  0:51 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 [this message]
2004-04-01  0:54   ` Brantley Coile
2004-04-01  2:10     ` bs
2004-04-01  2:14     ` bs
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=406B6786.7020904@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).