From: Eric Grosse <ehg@lucent.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] x509(8)
Date: Sat, 25 Oct 2003 09:21:09 -0400 [thread overview]
Message-ID: <a6582b842e58e8aa67fc665b6d0162e7@plan9.bell-labs.com> (raw)
In-Reply-To: <E1ADDxi-000F7w-03@t40.swtch.com>
> x509(8) is dead. The man page index is out-of-date.
> See rsa(8) and pem(8).
See also rsa(2) and /sys/src/libsec/port/x509.c. We use X.509
certificates because the rest of the world does, and so this is
a feasible way to ship public keys around, whether or not you
buy into the whole PKI hierarchy.
prev parent reply other threads:[~2003-10-25 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-25 2:03 mirtchov
2003-10-25 2:15 ` Russ Cox
2003-10-25 13:21 ` Eric Grosse [this message]
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=a6582b842e58e8aa67fc665b6d0162e7@plan9.bell-labs.com \
--to=ehg@lucent.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).