Re: 2.4.29 || mod_remoteip w/RemoteIPProxyProtocol

2018-02-27 Thread Marcin Giedz 
or another method is simple copy .c file from 2.5/trunk and compile it with 
2.4.30 using apxs. I did it and it's working fine 

Thx 
Marcin 


Od: "Jacob Perkins"  
Do: "dev"  
Wysłane: wtorek, 27 luty 2018 16:23:07 
Temat: Re: 2.4.29 || mod_remoteip w/RemoteIPProxyProtocol 

Ah right on. Thank you! 

— 
Jacob Perkins 
Product Owner 
cPanel Inc. 

jacob.perk...@cpanel.net 
Office: 713-529-0800 x 4046 
Cell: 713-560-8655 




On Feb 27, 2018, at 8:57 AM, Graham Leggett < minf...@sharp.fm > wrote: 

On 27 Feb 2018, at 4:44 PM, Jacob Perkins < jacob.perk...@cpanel.net > wrote: 


BQ_BEGIN
I have a customer who’s attempting to use RemoteIPProxyProtocol with 
mod_remoteIP. Per 2.4 documentation, this directive should be available ( 
https://httpd.apache.org/docs/2.4/mod/mod_remoteip.html ) 

I built httpd 2.4.29 from sources this morning with APR 1.6.3 and apr-util 
1.6.1, and I’m not seeing this directive as available, and upon putting it into 
the configuration, it can’t find this directive. 




RemoteIPProxyProtocol was backported to v2.4.30, which was not released. You’ll 
find this in v2.4.31 when it is released. v2.4.29 is one version too old, alas. 

Regards, 
Graham 
— 


BQ_END

Re: apr trunk make test results on LFS

2018-02-27 Thread Alain Toussaint 

> If you are doing a 64 bit build, this is likely just a misleading output 
> message. See https://bz.apache.org/bugzilla/show_bug.cgi?id=45615 
> comment 4 and 5.

Indeed, it is a 64bit build. Forgot to add:

gcc 7.3.0 with retpoline, no multilib

binutils 2.30

glibc 2.27

At the moment, it's running under chroot on a debian 9.3 system. Kernel is 
4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u2 (2018-02-21)

Alain

Re: 2.4.29 || mod_remoteip w/RemoteIPProxyProtocol

2018-02-27 Thread Graham Leggett 
On 27 Feb 2018, at 5:00 PM, William A Rowe Jr  wrote:

> They had likely RTFM ... looking at
> https://httpd.apache.org/docs/2.4/mod/mod_remoteip.html#remoteipproxyprotocol
> 
> Compatibility:RemoteIPProxyProtocol is only available in httpd 2.4.28 and 
> newer

Fixed in r1825468.

Regards,
Graham
—



smime.p7s
Description: S/MIME cryptographic signature

Re: apr trunk make test results on LFS

2018-02-27 Thread Rainer Jung 

Am 27.02.2018 um 00:13 schrieb Alain Toussaint:

Hello,

I have a test log of trunk apr build with these configure settings:

./configure --prefix=/usr --disable-static --enable-nonportable-atomics 
--enable-threads --enable-
posix-shm --enable-allocator-uses-mmap --enable-allocator-guard-pages 
--with-gdbm=/usr --with-
openssl=/usr --with-crypto --with-installbuilddir=/usr/share/apr-dev/build 
--with-sqlite3=/usr --
with-libxml2=/usr

of particular note, the errors I'm getting are:

testlfs : |Line 345: Large Files not supported


If you are doing a 64 bit build, this is likely just a misleading output 
message. See https://bz.apache.org/bugzilla/show_bug.cgi?id=45615 
comment 4 and 5.


Regards,

Rainer


I'm compiling in a 16GB (half my ram) tmpfs on mode=0755,uid=0,gid=0 in 
/usr/src:

(lfs chroot) root:/usr/src/apr# df -h
Filesystem  Size  Used Avail Use% Mounted on
/dev/loop0   16G  2.3G   13G  16% /
udev 16G 0   16G   0% /dev
tmpfs16G 0   16G   0% /run
tmpfs16G   22M   16G   1% /usr/src

the tmpfs might not support large file.

testcrypto below:

testcrypto  : |Line 50: Crypto driver 'openssl' DSO could not be opened
|Line 50: Crypto driver 'nss' DSO could not be opened
|Line 50: Crypto driver 'commoncrypto' DSO could not be opened
|Line 50: Crypto driver 'openssl' DSO could not be opened
-Line 50: Crypto driver 'openssl' DSO could not be opened
-Line 50: Crypto driver 'openssl' DSO could not be opened
\Line 50: Crypto driver 'openssl' DSO could not be opened
/Line 50: Crypto driver 'nss' DSO could not be opened
|Line 50: Crypto driver 'nss' DSO could not be opened
|Line 50: Crypto driver 'nss' DSO could not be opened
-Line 50: Crypto driver 'nss' DSO could not be opened
-Line 50: Crypto driver 'commoncrypto' DSO could not be opened
[snip]
SUCCESS

This is on OpenSSL 1.1.0g  2 Nov 2017. Any issues between apr-2 and openssl 
1.1.0g? I look at the
BLFS version 2018-02-26 page 
(http://linuxfromscratch.org/blfs/view/systemd/general/apr-util.html)
of apr-util and we don't need patches for apr-util-1.6.1

These are the only issues that I am having at the moment.

Alain

Re: [VOTE] Release httpd-2.4.30

2018-02-27 Thread Jim Jagielski 
It likely makes sense to CLOSE this vote with the
result that 2.4.30 is not being released...

> On Feb 19, 2018, at 9:54 AM, drugg...@primary.net wrote:
> 
> Hi, all;
>Please find below the proposed release tarball and signatures:
> https://dist.apache.org/repos/dist/dev/httpd/ 
> 
>  
> I would like to call a VOTE over the next few days to release this candidate 
> tarball as 2.4.30:
>  
> [ ] +1: It’s not just good, it’s good enough!
> [ ] +0: Let’s have a talk…
> [ ] -1: There’s trouble in paradise. Here’s what’s wrong.
> -- 
> Daniel Ruggeri

2.4.29 || mod_remoteip w/RemoteIPProxyProtocol

2018-02-27 Thread Jacob Perkins 
Good morning,

I have a customer who’s attempting to use RemoteIPProxyProtocol with 
mod_remoteIP. Per 2.4 documentation, this directive should be available ( 
https://httpd.apache.org/docs/2.4/mod/mod_remoteip.html 
 ) 

I built httpd 2.4.29 from sources this morning with APR 1.6.3 and apr-util 
1.6.1, and I’m not seeing this directive as available, and upon putting it into 
the configuration, it can’t find this directive.

jperkins64 :: /opt/perk # ./bin/apachectl configtest
AH00112: Warning: DocumentRoot [/opt/perk/docs/dummy-host.example.com] does not 
exist
AH00526: Syntax error on line 30 of /opt/perk/conf/extra/httpd-vhosts.conf:
Invalid command 'RemoteIPProxyProtocol', perhaps misspelled or defined by a 
module not included in the server configuration
jperkins64 :: /opt/perk # grep remoteip conf/httpd.conf
LoadModule remoteip_module modules/mod_remoteip.so
jperkins64 :: /opt/perk # grep RemoteIP conf/extra/httpd-vhosts.conf -A2 -B3
ServerAlias www.dummy-host.example.com
ErrorLog "logs/dummy-host.example.com-error_log"
CustomLog "logs/dummy-host.example.com-access_log" common
RemoteIPProxyProtocol On


When I remove that directive from my vhosts.conf, I’m loading the module 
properly (it appears lol):

jperkins64 :: /opt/perk # ./bin/apachectl -M | grep remoteip
AH00112: Warning: DocumentRoot [/opt/perk/docs/dummy-host.example.com] does not 
exist
AH00112: Warning: DocumentRoot [/opt/perk/docs/dummy-host2.example.com] does 
not exist
 remoteip_module (shared)
jperkins64 :: /opt/perk #

Did this directive get pulled out or am I missing something to get this 
enabled? 

—
Jacob Perkins
Product Owner
cPanel Inc.

jacob.perk...@cpanel.net 
Office:  713-529-0800 x 4046
Cell:  713-560-8655

Re: 2.4.29 || mod_remoteip w/RemoteIPProxyProtocol

2018-02-27 Thread Graham Leggett 
On 27 Feb 2018, at 4:44 PM, Jacob Perkins  wrote:

> I have a customer who’s attempting to use RemoteIPProxyProtocol with 
> mod_remoteIP. Per 2.4 documentation, this directive should be available ( 
> https://httpd.apache.org/docs/2.4/mod/mod_remoteip.html 
>  ) 
> 
> I built httpd 2.4.29 from sources this morning with APR 1.6.3 and apr-util 
> 1.6.1, and I’m not seeing this directive as available, and upon putting it 
> into the configuration, it can’t find this directive.

RemoteIPProxyProtocol was backported to v2.4.30, which was not released. You’ll 
find this in v2.4.31 when it is released. v2.4.29 is one version too old, alas.

Regards,
Graham
—



smime.p7s
Description: S/MIME cryptographic signature

Re: 2.4.29 || mod_remoteip w/RemoteIPProxyProtocol

2018-02-27 Thread William A Rowe Jr 
On Tue, Feb 27, 2018 at 8:57 AM, Graham Leggett  wrote:
> On 27 Feb 2018, at 4:44 PM, Jacob Perkins  wrote:
>
> I have a customer who’s attempting to use RemoteIPProxyProtocol with
> mod_remoteIP. Per 2.4 documentation, this directive should be available (
> https://httpd.apache.org/docs/2.4/mod/mod_remoteip.html )
>
> I built httpd 2.4.29 from sources this morning with APR 1.6.3 and apr-util
> 1.6.1, and I’m not seeing this directive as available, and upon putting it
> into the configuration, it can’t find this directive.
>
> RemoteIPProxyProtocol was backported to v2.4.30, which was not released.
> You’ll find this in v2.4.31 when it is released. v2.4.29 is one version too
> old, alas.

They had likely RTFM ... looking at
https://httpd.apache.org/docs/2.4/mod/mod_remoteip.html#remoteipproxyprotocol

Compatibility:RemoteIPProxyProtocol is only available in httpd 2.4.28 and newer

Re: 2.4.29 || mod_remoteip w/RemoteIPProxyProtocol

2018-02-27 Thread Jacob Perkins 
As a note, this does appear to be working on 2.5 / trunk. 

—
Jacob Perkins
Product Owner
cPanel Inc.

jacob.perk...@cpanel.net 
Office:  713-529-0800 x 4046
Cell:  713-560-8655

> On Feb 27, 2018, at 8:44 AM, Jacob Perkins  wrote:
> 
> Good morning,
> 
> I have a customer who’s attempting to use RemoteIPProxyProtocol with 
> mod_remoteIP. Per 2.4 documentation, this directive should be available ( 
> https://httpd.apache.org/docs/2.4/mod/mod_remoteip.html 
>  ) 
> 
> I built httpd 2.4.29 from sources this morning with APR 1.6.3 and apr-util 
> 1.6.1, and I’m not seeing this directive as available, and upon putting it 
> into the configuration, it can’t find this directive.
> 
> jperkins64 :: /opt/perk # ./bin/apachectl configtest
> AH00112: Warning: DocumentRoot [/opt/perk/docs/dummy-host.example.com 
> ] does not exist
> AH00526: Syntax error on line 30 of /opt/perk/conf/extra/httpd-vhosts.conf:
> Invalid command 'RemoteIPProxyProtocol', perhaps misspelled or defined by a 
> module not included in the server configuration
> jperkins64 :: /opt/perk # grep remoteip conf/httpd.conf
> LoadModule remoteip_module modules/mod_remoteip.so
> jperkins64 :: /opt/perk # grep RemoteIP conf/extra/httpd-vhosts.conf -A2 -B3
> ServerAlias www.dummy-host.example.com 
> 
> ErrorLog "logs/dummy-host.example.com 
> -error_log"
> CustomLog "logs/dummy-host.example.com 
> -access_log" common
> RemoteIPProxyProtocol On
> 
> 
> When I remove that directive from my vhosts.conf, I’m loading the module 
> properly (it appears lol):
> 
> jperkins64 :: /opt/perk # ./bin/apachectl -M | grep remoteip
> AH00112: Warning: DocumentRoot [/opt/perk/docs/dummy-host.example.com 
> ] does not exist
> AH00112: Warning: DocumentRoot [/opt/perk/docs/dummy-host2.example.com 
> ] does not exist
>  remoteip_module (shared)
> jperkins64 :: /opt/perk #
> 
> Did this directive get pulled out or am I missing something to get this 
> enabled? 
> 
> —
> Jacob Perkins
> Product Owner
> cPanel Inc.
> 
> jacob.perk...@cpanel.net 
> Office:  713-529-0800 x 4046
> Cell:  713-560-8655
>

Re: 2.4.29 || mod_remoteip w/RemoteIPProxyProtocol

2018-02-27 Thread Jacob Perkins 
Howdy,

I built 2.4.29 and it didn’t have it. I also built 2.5 and it did have it. 

—
Jacob Perkins
Product Owner
cPanel Inc.

jacob.perk...@cpanel.net 
Office:  713-529-0800 x 4046
Cell:  713-560-8655

> On Feb 27, 2018, at 9:00 AM, William A Rowe Jr  wrote:
> 
> On Tue, Feb 27, 2018 at 8:57 AM, Graham Leggett  wrote:
>> On 27 Feb 2018, at 4:44 PM, Jacob Perkins  wrote:
>> 
>> I have a customer who’s attempting to use RemoteIPProxyProtocol with
>> mod_remoteIP. Per 2.4 documentation, this directive should be available (
>> https://httpd.apache.org/docs/2.4/mod/mod_remoteip.html )
>> 
>> I built httpd 2.4.29 from sources this morning with APR 1.6.3 and apr-util
>> 1.6.1, and I’m not seeing this directive as available, and upon putting it
>> into the configuration, it can’t find this directive.
>> 
>> RemoteIPProxyProtocol was backported to v2.4.30, which was not released.
>> You’ll find this in v2.4.31 when it is released. v2.4.29 is one version too
>> old, alas.
> 
> They had likely RTFM ... looking at
> https://httpd.apache.org/docs/2.4/mod/mod_remoteip.html#remoteipproxyprotocol
> 
> Compatibility:RemoteIPProxyProtocol is only available in httpd 2.4.28 and 
> newer

Re: 2.4.29 || mod_remoteip w/RemoteIPProxyProtocol

2018-02-27 Thread Jacob Perkins 
Ah right on. Thank you!

—
Jacob Perkins
Product Owner
cPanel Inc.

jacob.perk...@cpanel.net 
Office:  713-529-0800 x 4046
Cell:  713-560-8655

> On Feb 27, 2018, at 8:57 AM, Graham Leggett  wrote:
> 
> On 27 Feb 2018, at 4:44 PM, Jacob Perkins  > wrote:
> 
>> I have a customer who’s attempting to use RemoteIPProxyProtocol with 
>> mod_remoteIP. Per 2.4 documentation, this directive should be available ( 
>> https://httpd.apache.org/docs/2.4/mod/mod_remoteip.html 
>>  ) 
>> 
>> I built httpd 2.4.29 from sources this morning with APR 1.6.3 and apr-util 
>> 1.6.1, and I’m not seeing this directive as available, and upon putting it 
>> into the configuration, it can’t find this directive.
> 
> RemoteIPProxyProtocol was backported to v2.4.30, which was not released. 
> You’ll find this in v2.4.31 when it is released. v2.4.29 is one version too 
> old, alas.
> 
> Regards,
> Graham
> —
>

Re: One more make pain point

2018-02-27 Thread William A Rowe Jr 
Here is the stderr vpath build result of the current 2.4.x snapshot on
Ubuntu 16.04-LTS, to illustrate my concerns;

mkdir modules
mkdir modules/aaa
mkdir modules/arch
mkdir modules/arch/win32
mkdir modules/cache
mkdir modules/core
mkdir modules/database
mkdir modules/debugging
mkdir modules/echo
mkdir modules/examples
mkdir modules/experimental
mkdir modules/filters
mkdir modules/http
mkdir modules/ldap
mkdir modules/loggers
mkdir modules/lua
configure: WARNING: *** Lua 5.3 5.2 or 5.1 library not found.
configure: WARNING: Lua 5.3 5.2 or 5.1 library is required
mkdir modules/metadata
mkdir modules/proxy
mkdir modules/session
mkdir modules/slotmem
mkdir modules/ssl
mkdir modules/test
mkdir modules/http2
mkdir modules/md
mkdir modules/proxy/balancers
mkdir server
mkdir server/mpm
mkdir server/mpm/event
mkdir server/mpm/prefork
mkdir server/mpm/worker
mkdir modules/arch/unix
mkdir modules/cluster
mkdir modules/dav
mkdir modules/dav/main
mkdir modules/generators
mkdir modules/dav/fs
mkdir modules/dav/lock
mkdir modules/mappers
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see

Re: One more make pain point

2018-02-27 Thread William A Rowe Jr 
No comment?

Note that you won't see these artifacts on a same-tree build, but
will be confronted with a slew of them on any new vpath unix build.

On Mon, Feb 26, 2018 at 2:58 PM, William A Rowe Jr  wrote:
> Any objections to
>
> --- build/mkdir.sh (revision 1825390)
> +++ build/mkdir.sh (working copy)
> @@ -38,7 +38,6 @@
>   continue ;;
>  esac
>  if test ! -d "$pathcomp"; then
> -echo "mkdir $pathcomp" 1>&2
>  mkdir "$pathcomp" || errstatus=$?
>  fi
>  pathcomp="$pathcomp/"
>
> That action does not rise to the alert severity of error output :-/
>
> Or do we want to retain the notice, not redirecting to stderr?