Re: 1.6.0 release candidates

[Steffen <in...@apachelounge.com>]

Now also build with Openssl 1.1.0e.

Running now on Apachelounge.


Build with:
-----------
httpd 2.4.26-dev
nghttp2 1.21.1
apr 1.6.1-dev  with IPv6 enabled
apr-util 1.6.1-dev  with Crypto OpenSSL enabled
apr-iconv 1.2.1
openssl 1.1.0e
zlib 1.2.11
pcre 8.40 with JIT, SUPPORT_UTF8 and REBUILD_CHARTABLES enabled
httpd.exe with OPENSSL_Applink and SupportedOS Manifest
libxml2 2.9.4
lua 5.2.4
expat 2.2.0



On Tuesday 18/04/2017 at 13:37, Steffen  wrote:
>
> Build Win32 with current httpd-2.4.26-dev, used not nick's files but 
> exported today 1.6.1-dev
>
> Used the IDE build (.dsw and dsp).
>
> Building fine.
>
> New warnings:
>
>
> locks\win32\proc_mutex.c(170): warning C4244: 'initializing': 
> conversion from 'apr_interval_time_t' to 'DWORD', possible loss of 
> data
>    thread_cond.c
> locks\win32\thread_cond.c(125): warning C4244: 'initializing': 
> conversion from 'apr_interval_time_t' to 'DWORD', possible loss of 
> data
>    thread_mutex.c
> locks\win32\thread_mutex.c(121): warning C4244: 'initializing': 
> conversion from 'apr_interval_time_t' to 'DWORD', possible loss of 
> data
>
>
> On Tuesday 18/04/2017 at 13:15, Rainer Jung  wrote:
>>
>> Am 18.04.2017 um 12:09 schrieb Nick Kew:
>>>
>>>
>>> On Mon, 2017-04-17 at 17:06 +0100, Nick Kew wrote:
>>>>
>>>>
>>>>                And I need to do some more digging
>>>> around that bogus PGP key!
>>>
>>> OK, this follows a subject that's been raised @apache before:
>>> https://mail-search.apache.org/members/private-arch/members/201606.mbox/%3C1464999260.7490.275.camel@mimir.webthing.com%3E
>>> following which apache's own pages were fixed to stop using
>>> 32-bit key IDs.
>>>
>>> Underlying story is at https://evil32.com/ .  I think I shall also
>>> blog this story and add my own thoughts.
>>
>> Thank a bunch. So I had imported the wrong key resp. the right and the 
>>  wrong key by only using the short form of the fingerprint.
>>
>> It turns out, that for my keys also invalid clones with the same short 
>>  fingerprint exist :(
>>
>> I will be more careful in the future, using the full fingerprint.
>>
>> Thanks again!
>>
>> Rainer
>
>
>