On Aug 23, 2017 13:43, "Thiago Macieira" wrote:
There's also a licensing component here. One cannot distribute GPLv2-only
software linking to OpenSSL 1.1.
Don't buy into the crazy FSF crap. It's bullshit, and it's just a bedtime
story made up by the FSF to try to push
On Sunday, 6 August 2017 00:07:30 PDT Dirk Hohndel wrote:
> While I don't even pretend to be a security expert, this is a topic that I
> have quite some familiarity with. Yes, right now OpenSSL 1.0.2 (latest) is
> still considered "as secure" as 1.1.0 latest. I can understand the Qt team
>
On Sunday, 6 August 2017 18:42:24 PDT Linus Torvalds wrote:
> On Sat, Aug 5, 2017 at 9:16 PM, Thiago Macieira wrote:
> > Patch and diff links in
> > http://code.qt.io/cgit/qt/qtbase.git/commit/?
> > id=cfbe03a6e035ab3cce5f04962cddd06bd414dcea
>
> It doesn't really apply
On Sat, Aug 5, 2017 at 9:16 PM, Thiago Macieira wrote:
>
> Patch and diff links in
> http://code.qt.io/cgit/qt/qtbase.git/commit/?
> id=cfbe03a6e035ab3cce5f04962cddd06bd414dcea
It doesn't really apply cleanly, but it's fixable, so I have 5.9 on F26 working.
Linus
inful.
/D
--
From my phone
Original Message
From: Thiago Macieira <thi...@macieira.org>
Sent: Sun Aug 06 05:26:04 GMT+01:00 2017
To: Linus Torvalds <torva...@linux-foundation.org>
Cc: Subsurface Mailing List <subsurface@subsurface-divelog.org>
Subject: Re: Qt
On Saturday, 5 August 2017 17:07:50 PDT Linus Torvalds wrote:
> You don't use old versions of security software. It's that easy. Not done,
> not acceptable, not a solution.
To be clear: OpenSSL 1.0.2l was released on the very same day as 1.1.0f. Both
branches are currently maintained.
--
On Saturday, 5 August 2017 20:54:59 PDT Linus Torvalds wrote:
> On Aug 5, 2017 20:48, "Thiago Macieira" wrote:
>
> From the Qt Project's point of view, it's a new feature, so it was added to
> the devleopment branch. But it seems the patch is clean enough to be
> backported
On Aug 5, 2017 20:48, "Thiago Macieira" wrote:
>From the Qt Project's point of view, it's a new feature, so it was added to
the devleopment branch. But it seems the patch is clean enough to be
backported if a Linux distribution wants it for its purposes.
Christ, you
On Saturday, 5 August 2017 17:07:50 PDT Linus Torvalds wrote:
> I did see some patches, and another big report that was allegedly closed
> because of those patches, but they don't actually seem to be merged
> although the bug report said they were upstream. I suspect that there is
> some branch
On Saturday, 5 August 2017 15:40:01 PDT Linus Torvalds wrote:
> Ok, I've worked around this by just using my old build, but it means
> that ssl doesn't work, which in turn means that I can't actually do
> the cloud access etc on my F26 desktop.
>
> So I'm tried of my old broken At-5.9 build, and
On Aug 5, 2017 16:44, "Lubomir I. Ivanov" wrote:
this post suggests a solution; use older openssl - e.g. 1.0.2:
Oh, I know about *that* solution, but that's just a bad joke.
You don't use old versions of security software. It's that easy. Not done,
not acceptable, not a
On 6 August 2017 at 01:40, Linus Torvalds wrote:
> Ok, I've worked around this by just using my old build, but it means
> that ssl doesn't work, which in turn means that I can't actually do
> the cloud access etc on my F26 desktop.
>
> So I'm tried of my old broken
Ok, I've worked around this by just using my old build, but it means
that ssl doesn't work, which in turn means that I can't actually do
the cloud access etc on my F26 desktop.
So I'm tried of my old broken At-5.9 build, and would like to know how
to make a proper build against openssl-1.1.0,
13 matches
Mail list logo