Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[rt.openssl.org #3939] [PATCH] Tests for CVE-2015-1788 #2375

Closed
richsalz opened this issue Feb 2, 2017 · 3 comments
Closed

[rt.openssl.org #3939] [PATCH] Tests for CVE-2015-1788 #2375

richsalz opened this issue Feb 2, 2017 · 3 comments

Comments

@richsalz
Copy link
Contributor

richsalz commented Feb 2, 2017

Migrated from rt.openssl.org#3939 (status was 'new')

Requestors:

Attachments:

From jpixton@gmail.com on 2015-07-12 11:44:44:

Hi Folks,

With the report for CVE-2015-1788 I submitted a patch to improve
testing in this area (including a regression test for the specific
issue).

As far as I can see this hasn't made its way into the repo. So here it
is again to ensure it isn't forgotten.

Cheers,
Joe

From jpixton@gmail.com on 2015-07-12 13:05:23:

Apologies, that patch was HTMLised by github. Attached is the actual patch.

On 12 July 2015 at 12:44, The default queue via RT <rt@openssl.org> wrote:
>
> Greetings,
>
> This message has been automatically generated in response to the
> creation of a trouble ticket regarding:
>         "[PATCH] Tests for CVE-2015-1788",
> a summary of which appears below.
>
> There is no need to reply to this message right now.  Your ticket has been
> assigned an ID of [openssl.org #3939].
>
> Please include the string:
>
>          [openssl.org #3939]
>
> in the subject line of all future correspondence about this issue. To do so,
> you may reply to this message.
>
>                         Thank you,
>                         rt@openssl.org
>
> -------------------------------------------------------------------------
> Hi Folks,
>
> With the report for CVE-2015-1788 I submitted a patch to improve
> testing in this area (including a regression test for the specific
> issue).
>
> As far as I can see this hasn't made its way into the repo. So here it
> is again to ensure it isn't forgotten.
>
> Cheers,
> Joe
>
@richsalz
Copy link
Contributor Author

richsalz commented Feb 2, 2017

this looks good. what do you think @davidben , @levitte @snhenson (look at the second patch :)

@levitte
Copy link
Member

levitte commented Feb 2, 2017

I can certainly make new style test recipe from that.

@mattcaswell
Copy link
Member

This was merged. 6d0b5ee and 691e302

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants