unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Dirkjan Bussink <dbussink@github.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: John Crepezzi <seejohnrun@github.com>,
	Kevin Sawicki <kevinsawicki@github.com>,
	unicorn-public@yhbt.net
Subject: Re: Potential Unicorn vulnerability
Date: Fri, 19 Mar 2021 14:55:20 +0100	[thread overview]
Message-ID: <4A8AD1DE-1600-4115-87B4-6FFFD3B62C67@github.com> (raw)
In-Reply-To: <20210317084707.GA27536@dcvr>

Hi Eric.

> On 17 Mar 2021, at 09:47, Eric Wong <normalperson@yhbt.net> wrote:
> 
> Sure, I don't see why not.  Though (as you might've figured) I'm
> not a fan of marketing or putting a positive spin on things at all.
> I can't dictate what others say, but I'm learning to get worse at
> marketing over time :>

FYI, we posted the results of our investigation at
https://github.blog/2021-03-18-how-we-found-and-fixed-a-rare-race-condition-in-our-session-handling/.

We tried to stay factual there but I can’t judge of course how
anyone reads it.

Cheers,

Dirkjan


      reply	other threads:[~2021-03-19 13:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <F6712BF3-A4DD-41EE-8252-B9799B35E618@github.com>
     [not found] ` <20210311030250.GA1266@dcvr>
     [not found]   ` <7F6FD017-7802-4871-88A3-1E03D26D967C@github.com>
2021-03-12  9:41     ` Potential Unicorn vulnerability Eric Wong
2021-03-12 11:14       ` Dirkjan Bussink
2021-03-12 12:00         ` Eric Wong
2021-03-12 12:24           ` Dirkjan Bussink
2021-03-13  2:26             ` Eric Wong
2021-03-13  2:31               ` [PATCH] http_request: drop unnecessary #clear call Eric Wong
2021-03-16 10:15               ` Potential Unicorn vulnerability Dirkjan Bussink
2021-03-16 10:31                 ` Eric Wong
2021-03-17  8:03                   ` Dirkjan Bussink
2021-03-17  8:47                     ` Eric Wong
2021-03-19 13:55                       ` Dirkjan Bussink [this message]

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

  List information: https://yhbt.net/unicorn/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A8AD1DE-1600-4115-87B4-6FFFD3B62C67@github.com \
    --to=dbussink@github.com \
    --cc=kevinsawicki@github.com \
    --cc=normalperson@yhbt.net \
    --cc=seejohnrun@github.com \
    --cc=unicorn-public@yhbt.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.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/unicorn.git/

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 read-only IMAP folder(s) and NNTP newsgroup(s).