public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: saksham jain <sakshamjain024@hotmail.com>
To: "overseers@sourceware.org" <overseers@sourceware.org>
Subject: Re: Related to account
Date: Fri, 26 Aug 2022 07:18:26 +0000	[thread overview]
Message-ID: <KL1PR03MB4933111F6F78FB1314805E269B759@KL1PR03MB4933.apcprd03.prod.outlook.com> (raw)
In-Reply-To: <KL1PR03MB49339C9A2E4BE2C6C43923A49B709@KL1PR03MB4933.apcprd03.prod.outlook.com>

Hi team,



I am trying to fix CVE 2021-33574.

I got your solution fix in the bugzilla 27896 – (CVE-2021-33574) mq_notify does not handle separately allocated thread attributes (CVE-2021-33574) (sourceware.org)<https://sourceware.org/bugzilla/show_bug.cgi?id=27896#c1> for glibc 2.28.

One of that solution is below:

https://gitee.com/src-openeuler/glibc/blob/openEuler-20.03-LTS-SP2/backport-CVE-2021-33574-0002-Fix-mq_notify-bug-27896.patch



I want to use the license of the above solution and code. Could you please share the licensee? this is for future reference. Can you please help me to create account, so I can raise 1 request for this information.



Regards,

Saksjain

________________________________
From: saksham jain
Sent: Tuesday, August 23, 2022 4:11 PM
To: overseers@sourceware.org <overseers@sourceware.org>
Subject: Related to account

Hello team,

I want to join as to debug the CVE analysis. Could you please create my account?

Regards,
Saksham Jain

WARNING: multiple messages have this Message-ID
From: saksham jain <sakshamjain024@hotmail.com>
To: "overseers@sourceware.org" <overseers@sourceware.org>
Subject: Re: Related to account
Date: Fri, 26 Aug 2022 07:18:26 +0000	[thread overview]
Message-ID: <KL1PR03MB4933111F6F78FB1314805E269B759@KL1PR03MB4933.apcprd03.prod.outlook.com> (raw)
Message-ID: <20220826071826.Tx6PheW1efDSQpRSZL2-Eajy8CoI96x0U4EFsJhy8es@z> (raw)
In-Reply-To: <KL1PR03MB49339C9A2E4BE2C6C43923A49B709@KL1PR03MB4933.apcprd03.prod.outlook.com>

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

Hi team,



I am trying to fix CVE 2021-33574.

I got your solution fix in the bugzilla 27896 – (CVE-2021-33574) mq_notify does not handle separately allocated thread attributes (CVE-2021-33574) (sourceware.org)<https://sourceware.org/bugzilla/show_bug.cgi?id=27896#c1> for glibc 2.28.

One of that solution is below:

https://gitee.com/src-openeuler/glibc/blob/openEuler-20.03-LTS-SP2/backport-CVE-2021-33574-0002-Fix-mq_notify-bug-27896.patch



I want to use the license of the above solution and code. Could you please share the licensee? this is for future reference. Can you please help me to create account, so I can raise 1 request for this information.



Regards,

Saksjain

________________________________
From: saksham jain
Sent: Tuesday, August 23, 2022 4:11 PM
To: overseers@sourceware.org <overseers@sourceware.org>
Subject: Related to account

Hello team,

I want to join as to debug the CVE analysis. Could you please create my account?

Regards,
Saksham Jain

  parent reply	other threads:[~2022-08-26  7:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23 10:41 saksham jain
2022-08-23 12:54 ` Mark Wielaard
2022-08-26  7:18 ` saksham jain [this message]
2022-08-26  7:18   ` saksham jain
2022-08-26 11:29   ` Frank Ch. Eigler

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=KL1PR03MB4933111F6F78FB1314805E269B759@KL1PR03MB4933.apcprd03.prod.outlook.com \
    --to=sakshamjain024@hotmail.com \
    --cc=overseers@sourceware.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).