9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] How do I get a CSR CA's like?
Date: Wed, 27 May 2015 04:24:39 +0200	[thread overview]
Message-ID: <ace7e3e0b8c14c32c271e13da608dfb9@proxima.alt.za> (raw)
In-Reply-To: <CAJH05TC5M2svhWs=4fXiOOkd4JnKmax+oSczsGa4_McLM9pqoA@mail.gmail.com>

> If it's just as simple, this might be the right place/time to use sha256
> for this sort of thing.

Again, I did not look into this in detail, but CSRs I generated
recently with openssl seem to use "SHA1 with RSA encryption" for the
signature:

Certificate Request:
    Data:
        Version: 0 (0x0)
        Subject: C=ZA, L=Kestell, ST=Free State, O=Proxima Research & Development, OU=Public Internet Services, CN=serendipity.proxima.alt.za/emailAddress=admin@proxima.alt.za
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (1024 bit)
                Modulus:
                    xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:
                    xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:
                    xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:
                    xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:
                    xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:
                    xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:
                    xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:
                    xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:
                    xx:xx:xx:xx:xx:xx:xx:xx:xx
                Exponent: 65537 (0x10001)
        Attributes:
            a0:00
    Signature Algorithm: sha1WithRSAEncryption
         xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:
         xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:
         xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:
         xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:
         xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:
         xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:
         xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:
         xx:xx

That was what I thought would take some effort to get right in x509.c

Lucio.




  reply	other threads:[~2015-05-27  2:24 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
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 [this message]
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=ace7e3e0b8c14c32c271e13da608dfb9@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --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).