From: "Felipe Bichued" <bichued@gmail.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cert signing request
Date: Tue, 9 Jan 2007 08:59:04 -0200 [thread overview]
Message-ID: <d553b5590701090259s5fb168d3t5a64e1bae5e1e864@mail.gmail.com> (raw)
In-Reply-To: <82c890d00701090056g34428d74pf550de61680e043d@mail.gmail.com>
I saw that but totally forgot to check if auth tools made any use of it.
Seems like what Skip wants is auth/rsa2csr.
Sorry for the earlier noise.
On 1/9/07, Gabriel Diaz <gabidiaz@gmail.com> wrote:
> hello
>
> a quick look in /sys/src/libsec/port/x509.c shows
>
> uchar*
> X509req(RSApriv *priv, char *subj, int *certlen)
> {
> /* RFC 2314, PKCS #10 Certification Request Syntax */
>
> so it is done already, at least using the RSA lab way :)
> (the rfc2511 seems to be the Entrust/Verisign way of doing the same :-? )
>
> slds.
>
> gabi
>
>
>
>
> On 1/9/07, Gabriel Diaz <gabidiaz@gmail.com> wrote:
> >
> > hello
> >
> > i think this doesn't work if you want to ask Verisign to sign your
> request, isn't it?, but i think libsec has almost all the code to build a
> request as in rfc2511 :-? am i wrong?
> >
> > slds.
> >
> > gabi
> >
> >
> >
> >
> > On 1/9/07, Charles Forsyth <forsyth@terzarima.net > wrote:
> > > > As far as I know libsec still doesn't know how to write x509.
> > >
> > > rsa(8) has rsa2x509 and an example
> > > Generate a fresh key and use it to start a TLS-enabled web
> > > server:
> > >
> > > auth/rsagen -t 'service=tls owner=*' >key
> > > auth/rsa2x509 'C=US CN=*.cs.bell- labs.com' key |
> > > auth/pemencode CERTIFICATE >cert
> > > cat key >/mnt/factotum/ctl
> > > ip/httpd/httpd -c cert
> > >
> >
> >
>
>
--
Felipe
next prev parent reply other threads:[~2007-01-09 10:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 0:26 Skip Tavakkolian
2007-01-09 1:03 ` Felipe Bichued
2007-01-09 3:13 ` Benn Newman
2007-01-09 4:10 ` Skip Tavakkolian
2007-01-09 8:32 ` Charles Forsyth
2007-01-09 8:44 ` Gabriel Diaz
2007-01-09 8:56 ` Gabriel Diaz
2007-01-09 10:59 ` Felipe Bichued [this message]
2007-01-09 16:17 ` Skip Tavakkolian
2007-01-09 9:35 ` Charles Forsyth
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=d553b5590701090259s5fb168d3t5a64e1bae5e1e864@mail.gmail.com \
--to=bichued@gmail.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).