From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] openssl: update to 1.0.2i (CVE-2016-6304 and more)
Date: Mon, 26 Sep 2016 15:36:52 +0300 [thread overview]
Message-ID: <2d0c4e98-4179-a1e5-9fa4-8b09fab04d92@linux.intel.com> (raw)
In-Reply-To: <86436db9-fb61-2d83-19a3-6396ee8a8de4@gmail.com>
On 09/23/2016 07:25 PM, akuster808 wrote:
> No this demonstrates that folks do want to help out. They to the best
> they can with their abilities and situation. The community has made a
> lot of noise about how important it is to address security issues.
> Except a few of us who do send patches, the community as a whole does
> not stepped up to the table to help out.
>
> Opensource is not an all or nothing proposition. I for one appreciate
> contributions folks make in this area.
If folks want to help out, they'd better spend their time building
automated CI infrastructure that allows us to upgrade openssl to 1.0.2j
in stable releases without the paralyzing fear of breaking things. I
appreciate the intent to help, but I don't see the actual contribution
(of randomly backporting CVEs) as particularly useful in the long run.
Alex
next prev parent reply other threads:[~2016-09-26 12:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 8:38 [PATCH 0/1] openssl: update to 1.0.2i (CVE-2016-6304 and more) Patrick Ohly
2016-09-23 8:39 ` [PATCH 1/1] " Patrick Ohly
2016-09-23 12:01 ` Alexander Kanavin
2016-09-23 16:25 ` akuster808
2016-09-26 12:36 ` Alexander Kanavin [this message]
2016-09-23 10:27 ` [PATCH 0/1] " Patrick Ohly
2016-09-23 12:11 ` Alexander Kanavin
2016-09-23 13:19 ` Patrick Ohly
2016-09-23 14:52 ` Alexander Kanavin
2016-09-23 13:26 ` [PATCHv2] " Patrick Ohly
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=2d0c4e98-4179-a1e5-9fa4-8b09fab04d92@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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