On Wed, Nov 23, 2016 at 11:59:16AM +0400, Stepan Golosunov wrote:
> 22.11.2016 в 22:57:30 +0200 Adrian Bunk написал:
> > 23:14 < bunk> Q_: If you come up with a better patch than mine in #844018,
> > please post to that bug. I know that my patch is not pretty,
> > but
> >
22.11.2016 в 22:57:30 +0200 Adrian Bunk написал:
> 23:14 < bunk> Q_: If you come up with a better patch than mine in #844018,
> please post to that bug. I know that my patch is not pretty,
> but
> I did not find any better short-term solution.
Search for
20.11.2016 в 22:35:26 +0100 Jan Niehusmann написал:
> On Mon, Nov 21, 2016 at 01:03:19AM +0400, Stepan Golosunov wrote:
> > So far I do not know why using libssl1.1 together with a
> > libssl1.0.2-using Qt wouldn't work.
>
> Well I don't know enough about the dynamic linker and about the
On Mon, Nov 21, 2016 at 01:03:19AM +0400, Stepan Golosunov wrote:
> So far I do not know why using libssl1.1 together with a
> libssl1.0.2-using Qt wouldn't work.
Well I don't know enough about the dynamic linker and about the internals
of openssl to know if (indirectly) linking to both libraries
20.11.2016 в 21:29:35 +0100 Jan Niehusmann написал:
> On Mon, Nov 21, 2016 at 12:02:45AM +0400, Stepan Golosunov wrote:
> > It would be a grave bug in such application if it does not have a
> > working version, yes. Whether or not it would be a serious bug in
> > lubcurl3 depends on how many and
On Mon, Nov 21, 2016 at 12:02:45AM +0400, Stepan Golosunov wrote:
> It would be a grave bug in such application if it does not have a
> working version, yes. Whether or not it would be a serious bug in
> lubcurl3 depends on how many and how important such applications are.
> (And how difficult
20.11.2016 в 20:01:25 +0100 Jan Niehusmann написал:
> On Sun, Nov 20, 2016 at 07:40:22PM +0400, Stepan Golosunov wrote:
> > If SONAME change is needed it is needed when linking libcurl with
> > libssl1.0.2 too. (But when linking libcurl with libssl1.0.2 more
> > applications are affected due to
20.11.2016 в 23:38:48 +0400 Stepan Golosunov написал:
> 20.11.2016 в 20:01:25 +0100 Jan Niehusmann написал:
> > Still, for 1.1 the SONAME change is definitely necessary.
>
> Breaks: against applications using CURLOPT_SSL_CTX_FUNCTION and
> compiled with OpenSSL 1.0 will probably suffice in that
20.11.2016 в 20:48:44 +0100 Jan Niehusmann написал:
> On Sun, Nov 20, 2016 at 11:38:49PM +0400, Stepan Golosunov wrote:
> > > Still, for 1.1 the SONAME change is definitely necessary.
> >
> > Breaks: against applications using CURLOPT_SSL_CTX_FUNCTION and
> > compiled with OpenSSL 1.0 will
On Sun, Nov 20, 2016 at 11:38:49PM +0400, Stepan Golosunov wrote:
> > Still, for 1.1 the SONAME change is definitely necessary.
>
> Breaks: against applications using CURLOPT_SSL_CTX_FUNCTION and
> compiled with OpenSSL 1.0 will probably suffice in that case.
Wouldn't this still be a serious bug
On Sun, Nov 20, 2016 at 07:40:22PM +0400, Stepan Golosunov wrote:
> If SONAME change is needed it is needed when linking libcurl with
> libssl1.0.2 too. (But when linking libcurl with libssl1.0.2 more
> applications are affected due to the need of explicit initialization.)
Upstream documentation
11.11.2016 в 21:30:07 +0100 Jan Niehusmann написал:
> the curl ABI contains structs inherited from OpenSSL, e.g. in calls
> like:
>
> curl_easy_setopt(easy, CURLOPT_SSL_CTX_FUNCTION, _cb);
>
> Here, sslCtxFunction_cb is a function which takes an SSL_CTX * as a
> parameter.
>
> (This is from
Control: tags -1 patch
On Fri, Nov 11, 2016 at 09:30:07PM +0100, Jan Niehusmann wrote:
> Package: libcurl3
> Version: 7.51.0-1
> Severity: serious
> Justification: Policy 8.1
>
> Dear Maintainer,
>
> the curl ABI contains structs inherited from OpenSSL, e.g. in calls
> like:
>
>
Package: libcurl3
Version: 7.51.0-1
Severity: serious
Justification: Policy 8.1
Dear Maintainer,
the curl ABI contains structs inherited from OpenSSL, e.g. in calls
like:
curl_easy_setopt(easy, CURLOPT_SSL_CTX_FUNCTION, _cb);
Here, sslCtxFunction_cb is a function which takes an SSL_CTX * as a
14 matches
Mail list logo
