Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103597
Return-Path: <tessarek@evermeet.cx>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 9459 invoked from network); 12 Dec 2018 19:12:53 -0000
Received: from unknown (HELO atvie01s.evermeet.cx) (77.244.245.66)
  by pb1.pair.com with SMTP; 12 Dec 2018 19:12:53 -0000
Received: from [192.168.178.28] ([194.106.246.136])
	(authenticated bits=0)
	by atvie01s.evermeet.cx (8.15.2/8.15.2) with ESMTPSA id wBCFeGTF014720
	(version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
	Wed, 12 Dec 2018 16:40:16 +0100
DKIM-Filter: OpenDKIM Filter v2.10.3 atvie01s.evermeet.cx wBCFeGTF014720
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evermeet.cx;
	s=default; t=1544629216;
	bh=jWqqZmgm42LN8g0plfGZWBr6IU6JNycPJMki5nNNZn4=;
	h=Subject:To:Cc:References:From:Date:In-Reply-To:From;
	b=e0S1wZeqmci7x5HywXk4HPmAJpOLuUEDWnJk/DdlA76pwVPBHmsiJ6Y5oxvbirtha
	 LFW4FGC2sCgvoMSzsfI5Fag+AvzCO/CgXKyLLn5Me9A/kcfeOxMcTFzovKTLSPCja2
	 1o7e64kiKe9hXEv+SmdbhdJGliBi6H9YrFUHUy/c=
To: Jakub Zelenka <bukka@php.net>
Cc: PHP internals list <internals@lists.php.net>
References: <c092bd28-f212-5ee2-36e7-368724480da3@evermeet.cx>
 <e93bb835-5489-01ef-b29d-189d48276af0@evermeet.cx>
 <CAEKnhAEgC1G-z9LjzdBCEThmEDpw0FU3Y=ErpSoPtkOpHnqg8g@mail.gmail.com>
 <2e358c47-f07d-2bd0-dcbf-8ee1282f1ea1@evermeet.cx>
 <CAEKnhAFN1TNsOSuOVC0gszL=4eBWfePq9XxqJweEwTnchwKOtw@mail.gmail.com>
Openpgp: preference=signencrypt
Message-ID: <4ced5e72-7f71-dac2-cee7-cab5ea0e18be@evermeet.cx>
Date: Wed, 12 Dec 2018 16:40:16 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0)
 Gecko/20100101 Thunderbird/60.3.3
MIME-Version: 1.0
In-Reply-To: <CAEKnhAFN1TNsOSuOVC0gszL=4eBWfePq9XxqJweEwTnchwKOtw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] configure bug with static openssl 1.1.1?
From: tessarek@evermeet.cx ("Helmut K. C. Tessarek")



On 2018-12-12 16:37, Jakub Zelenka wrote:
> On Wed, Dec 12, 2018 at 3:32 PM Helmut K. C. Tessarek
> <tessarek@evermeet.cx <mailto:tessarek@evermeet.cx>> wrote:
> 
>     On 2018-12-12 16:11, Jakub Zelenka wrote:
>     >
>     > You should create a bug report.
>     >
>     > Please note that a static configuration has some issues (e.g.
>     > https://bugs.php.net/bug.php?id=73609 and think there were more issues
>     > maybe). Basically it's not well supported so I would recommend to do a
>     > shared build instead otherwise you are probably on your own unless
>     > someone finds time to look into it.
> 
>     Thanks, Jakub for your reply.
> 
>     Hmm, I checked the link you sent, but this ticket has nothing to do with
>     linking against a static openssl library.
> 
>     This ticket mentions that openssl is not supported as a shared
>     extension. But that is not what I'm doing.
> 
>     I try to link against a static openssl library. But it works when
>     linking against a static openssl 1.0.2 lib.
>     Therefore I highly suspect that there's a problem with configure. But I
>     will open a ticket, and I will also try to link against a dynamic
>     openssl 1.1.1.
> 
>     So linking against a static openssl 1.0.2 works, but against a static
>     openssl 1.1.1 does not work.
> 
>     However, linking against a static openssl library should be supported.
>     Years back people even suggested to always link against a static openssl
>     lib because of security reasons (no hijacking of dynamic libs and
>     whatnot). This might not be relevant anymore, but there's no logical
>     reason why linking against a static openssl 1.1.1 should not work.
> 
> 
> Ah I see! Yeah I think it should work so it might be a bug if it
> doesn't. I would suggest to create a bug report.

Will do.

Thanks,
  K. C.