From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <f3e0f5ae37b758de7e6a4bd73ecc47d9@9netics.com>
To: 9fans@9fans.net
Date: Sun, 24 May 2015 08:10:32 -0700
From: Skip Tavakkolian <9nut@9netics.com>
In-Reply-To: <5E011ABF-434D-4BE9-9ABA-6A9B8F934038@me.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] How do I get a CSR CA's like?
Topicbox-Message-UUID: 54f71c2e-ead9-11e9-9d60-3106f5b1d025

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=E2=
=80=99t like it. I=E2=80=99ll call them tomorrow.  Thanks for all the hel=
p.
>=20
> bwc
>=20
>> On May 23, 2015, at 1:08 PM, lucio@proxima.alt.za wrote:
>>=20
>>> I then pasted the contents of =E2=80=98csr=E2=80=99 into the page and=
 get =E2=80=9CThis CSR
>>> has an invalid signature!=E2=80=9D
>>=20
>> 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.
>>=20
>> Lucio.
>>=20
>>=20