From: Denys Dmytriyenko <denis@denix.org>
To: Alexandru Vaduva <vaduva.jan.alexandru@gmail.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: openssl: Need PRINC+1 in recipe?
Date: Thu, 10 Apr 2014 17:43:18 -0400 [thread overview]
Message-ID: <20140410214318.GV3370@denix.org> (raw)
In-Reply-To: <CABwVrCq7Z_0NgYv2H7JfW1O+w+Ld5pGy3OsBC6L9wmeOwOKgsg@mail.gmail.com>
On Fri, Apr 11, 2014 at 12:30:31AM +0300, Alexandru Vaduva wrote:
> Sorry to hijack this conversation but I believe in the next version of poky
> the package openssl should be updated and and for the rest of the version a
> patch should be applied to solve the newly appeared exploit.
> More info here:
> http://thehackernews.com/2014/04/heartbleed-openssl-zero-day-bug-leaves.html
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0160
Yes, that's what he was referring to...
> On Thu, Apr 10, 2014 at 11:20 PM, Bryan Evenson <bevenson@melinkcorp.com>wrote:
>
> > All,
> >
> > I was previously on dylan-1.4.1 and today I upgraded to poky/dylan HEAD to
> > take in the openssl security patches. Things are rebuilding, but I noticed
> > that the built package version is openssl-1.0.1e-r15.0, which is the same
> > version currently installed on my system. Shouldn't the PR line change to:
> >
> > PR = "${INC_PR+1}.0"
> >
> > For the packaging systems to take in the update?
Well, I guess people are so used to not caring about tracking PRs anymore,
they forget to bump them when backporting fixes to older branches. Paul?
--
Denys
next prev parent reply other threads:[~2014-04-10 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 20:20 openssl: Need PRINC+1 in recipe? Bryan Evenson
2014-04-10 21:30 ` Alexandru Vaduva
2014-04-10 21:43 ` Denys Dmytriyenko [this message]
2014-04-11 12:46 ` Paul Eggleton
2014-04-11 12:52 ` Paul Eggleton
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=20140410214318.GV3370@denix.org \
--to=denis@denix.org \
--cc=poky@yoctoproject.org \
--cc=vaduva.jan.alexandru@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.