9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Joe Bowers <joe@mixpanel.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] How do I get a CSR CA's like?
Date: Tue, 26 May 2015 12:44:54 -0700	[thread overview]
Message-ID: <CAJH05TC5M2svhWs=4fXiOOkd4JnKmax+oSczsGa4_McLM9pqoA@mail.gmail.com> (raw)
In-Reply-To: <F49EC73D-1DB4-47F0-97D8-5341E88F0E38@me.com>

[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]

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

On Tue, May 26, 2015 at 12:35 PM, Brantley Coile <brantleycoile@me.com>
wrote:

> I just changed “md5(…)” to “shall(…)” and added an object id to the
> table.  Once I figured out I didn’t have to us RSA to *sign* the CSR, but
> had to have something other than md5, it was easy.
>
> > On May 26, 2015, at 2:00 PM, lucio@proxima.alt.za wrote:
> >
> >> I now have reason to believe that they just removed MD5 from known
> >> signing algorithms, and that a SHA1 will work.  Anyone know anything
> >> about this?
> >
> > There's an exploit for the MD5 version.  It looks pretty serious and
> > deserves to be fixed by disabling the MD5 signing algorithm.
> >
> >       www.phreedom.org/research/rogue-ca/
> >
> > What exactly did you change in /sys/src/libsec/port/x509.c?  I had a
> > quick look this morning, but I didn't have the opportunity to dig deep
> > enough.
> >
> > Lucio.
> >
> >
>
>
>

[-- Attachment #2: Type: text/html, Size: 1610 bytes --]

  reply	other threads:[~2015-05-26 19:44 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 [this message]
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='CAJH05TC5M2svhWs=4fXiOOkd4JnKmax+oSczsGa4_McLM9pqoA@mail.gmail.com' \
    --to=joe@mixpanel.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).