On 02/14/2018 07:58 AM, Richard Purdie wrote:
> On Tue, 2018-02-13 at 08:27 -0800, akuster808 wrote:
>> On 02/12/2018 01:08 PM, robert_jos...@selinc.com wrote:
>>> I'm working with the pyro release, and noticed that it's still
>>> using
>>> openssl 1.0.2k. The latest version in the 1.0.2 series
On Tue, 2018-02-13 at 08:27 -0800, akuster808 wrote:
>
> On 02/12/2018 01:08 PM, robert_jos...@selinc.com wrote:
> >
> > I'm working with the pyro release, and noticed that it's still
> > using
> > openssl 1.0.2k. The latest version in the 1.0.2 series is 1.0.2n,
> > which is
> > already availa
akuster808 wrote on 02/13/2018 08:27:52 AM:
> On 02/12/2018 01:08 PM, robert_jos...@selinc.com wrote:
> > I'm working with the pyro release, and noticed that it's still using
> > openssl 1.0.2k. The latest version in the 1.0.2 series is 1.0.2n,
which is
> > already available on master. Is there
On 02/12/2018 01:08 PM, robert_jos...@selinc.com wrote:
> I'm working with the pyro release, and noticed that it's still using
> openssl 1.0.2k. The latest version in the 1.0.2 series is 1.0.2n, which is
> already available on master. Is there a reason that the newer version
> hasn't made it b
On 02/12/2018 11:08 PM, robert_jos...@selinc.com wrote:
I'm working with the pyro release, and noticed that it's still using
openssl 1.0.2k. The latest version in the 1.0.2 series is 1.0.2n, which is
already available on master. Is there a reason that the newer version
hasn't made it back to pyro
I'm working with the pyro release, and noticed that it's still using
openssl 1.0.2k. The latest version in the 1.0.2 series is 1.0.2n, which is
already available on master. Is there a reason that the newer version
hasn't made it back to pyro (or rocko, which is on 1.0.2m)? I know new
package ve
