From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@9fans.net
Subject: Re: [9fans] How do I get a CSR CA's like?
Date: Sun, 24 May 2015 08:10:32 -0700 [thread overview]
Message-ID: <f3e0f5ae37b758de7e6a4bd73ecc47d9@9netics.com> (raw)
In-Reply-To: <5E011ABF-434D-4BE9-9ABA-6A9B8F934038@me.com>
going by my notes from the last time i used plan9 tools to generate a
CSR, the only differences i see are quoting the O attribute to handle
spaces in organization name and dropping the word "SIGNING" from
PEM header/footer.
> Thanks all. It goes through sslshopper fine, but the CA still doesn’t like it. I’ll call them tomorrow. Thanks for all the help.
>
> bwc
>
>> On May 23, 2015, at 1:08 PM, lucio@proxima.alt.za wrote:
>>
>>> I then pasted the contents of ‘csr’ into the page and get “This CSR
>>> has an invalid signature!”
>>
>> It's worth playing with openssl to check the output from auth/rsa2csr.
>> The diagnostics are bound to be a bit less vague. Trying your
>> instructions, the PEM encoded csr includes the seemingly unwanted word
>> "SIGNING" in the headers. When I remove it (and a space) openssl req
>> reports a valid certificate request.
>>
>> Lucio.
>>
>>
next prev parent reply other threads:[~2015-05-24 15:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-23 15:31 Brantley Coile
2015-05-23 16:40 ` David du Colombier
2015-05-23 17:08 ` lucio
2015-05-24 12:10 ` Brantley Coile
2015-05-24 13:07 ` lucio
2015-05-24 15:10 ` Skip Tavakkolian [this message]
2015-05-25 19:06 ` Brantley Coile
2015-05-26 13:27 ` Brantley Coile
2015-05-26 14:44 ` Brantley Coile
2015-05-26 14:46 ` Brantley Coile
2015-05-26 18:00 ` lucio
2015-05-26 19:35 ` Brantley Coile
2015-05-26 19:44 ` Joe Bowers
2015-05-27 2:24 ` lucio
2015-05-27 16:41 ` cinap_lenrek
2015-05-27 17:57 ` cinap_lenrek
2015-05-23 17:43 ` balaji
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=f3e0f5ae37b758de7e6a4bd73ecc47d9@9netics.com \
--to=9nut@9netics.com \
--cc=9fans@9fans.net \
/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).