hi,
i found this also. I'm running gentoo witha recent kernel, but the php was compiled without the 'hash' keyword.
I've rebuilt ('emerged ") and plan to try shortly (haven't had time yet).
fwiw, my current use flags are as follows if any gentoo-folks know if gentoo needs any other use flags turned on to run elgg, please weigh in.
thanks:
reference: current use flags
[ebuild R ] dev-lang/php-5.2.10 USE="apache2 berkdb bzip2 cgi cli crypt gd gdbm hash iconv imap ipv6 ldap mysql ncurses nls pcre readline reflection session simplexml spell spl ssl truetype unicode xml zlib -adabas -bcmath -birdstep -calendar -cdb -cjk -concurrentmodphp -ctype -curl -curlwrappers -db2 -dbase -dbmaker -debug -discard-path -doc -empress -empress-bcs -esoob -exif -fastbuild -fdftk -filter -firebird -flatfile -force-cgi-redirect -frontbase -ftp -gd-external -gmp -inifile -interbase -iodbc (-java-external) -json -kerberos -kolab -ldap-sasl -libedit -mcve -mhash -msql -mssql -mysqli -oci8 -oci8-instant-client -odbc -pcntl -pdo -pic -posix -postgres -qdbm -recode -sapdb -sharedext -sharedmem -snmp -soap -sockets -solid -sqlite -suhosin -sybase -sybase-ct -sysvipc -threads -tidy -tokenizer -wddx -xmlreader -xmlrpc -xmlwriter -xpm -xsl -yaz -zip" 0 kB
SOLVED
a follow-up: rebuilding (emerging) php with the 'hash' option (use flag) solved the problem
Thanks for the help.
suggestion:
@Billmil -- Elgg in non-debug mode should definitely not have display errors on by default. It is a standard security practice in web applications to disable specific error reporting on live servers. However, in debug mode, error reporting should be enabled. The same applies to hiding it in a div. The reasoning behind this is that you don't want a misconfigured application announcing publicly what's happening on your server.
hi,
i found this also. I'm running gentoo witha recent kernel, but the php was compiled without the 'hash' keyword.
I've rebuilt ('emerged ") and plan to try shortly (haven't had time yet).
fwiw, my current use flags are as follows if any gentoo-folks know if gentoo needs any other use flags turned on to run elgg, please weigh in.
thanks:
reference: current use flags
[ebuild R ] dev-lang/php-5.2.10 USE="apache2 berkdb bzip2 cgi cli crypt gd gdbm hash iconv imap ipv6 ldap mysql ncurses nls pcre readline reflection session simplexml spell spl ssl truetype unicode xml zlib -adabas -bcmath -birdstep -calendar -cdb -cjk -concurrentmodphp -ctype -curl -curlwrappers -db2 -dbase -dbmaker -debug -discard-path -doc -empress -empress-bcs -esoob -exif -fastbuild -fdftk -filter -firebird -flatfile -force-cgi-redirect -frontbase -ftp -gd-external -gmp -inifile -interbase -iodbc (-java-external) -json -kerberos -kolab -ldap-sasl -libedit -mcve -mhash -msql -mssql -mysqli -oci8 -oci8-instant-client -odbc -pcntl -pdo -pic -posix -postgres -qdbm -recode -sapdb -sharedext -sharedmem -snmp -soap -sockets -solid -sqlite -suhosin -sybase -sybase-ct -sysvipc -threads -tidy -tokenizer -wddx -xmlreader -xmlrpc -xmlwriter -xpm -xsl -yaz -zip" 0 kB
SOLVED
a follow-up: rebuilding (emerging) php with the 'hash' option (use flag) solved the problem
Thanks for the help.
suggestion:
@Billmil -- Elgg in non-debug mode should definitely not have display errors on by default. It is a standard security practice in web applications to disable specific error reporting on live servers. However, in debug mode, error reporting should be enabled. The same applies to hiding it in a div. The reasoning behind this is that you don't want a misconfigured application announcing publicly what's happening on your server.
hi,
i found this also. I'm running gentoo witha recent kernel, but the php was compiled without the 'hash' keyword.
I've rebuilt ('emerged ") and plan to try shortly (haven't had time yet).
fwiw, my current use flags are as follows if any gentoo-folks know if gentoo needs any other use flags turned on to run elgg, please weigh in.
thanks:
reference: current use flags
[ebuild R ] dev-lang/php-5.2.10 USE="apache2 berkdb bzip2 cgi cli crypt gd gdbm hash iconv imap ipv6 ldap mysql ncurses nls pcre readline reflection session simplexml spell spl ssl truetype unicode xml zlib -adabas -bcmath -birdstep -calendar -cdb -cjk -concurrentmodphp -ctype -curl -curlwrappers -db2 -dbase -dbmaker -debug -discard-path -doc -empress -empress-bcs -esoob -exif -fastbuild -fdftk -filter -firebird -flatfile -force-cgi-redirect -frontbase -ftp -gd-external -gmp -inifile -interbase -iodbc (-java-external) -json -kerberos -kolab -ldap-sasl -libedit -mcve -mhash -msql -mssql -mysqli -oci8 -oci8-instant-client -odbc -pcntl -pdo -pic -posix -postgres -qdbm -recode -sapdb -sharedext -sharedmem -snmp -soap -sockets -solid -sqlite -suhosin -sybase -sybase-ct -sysvipc -threads -tidy -tokenizer -wddx -xmlreader -xmlrpc -xmlwriter -xpm -xsl -yaz -zip" 0 kB
SOLVED
a follow-up: rebuilding (emerging) php with the 'hash' option (use flag) solved the problem
Thanks for the help.
suggestion:
@Billmil -- Elgg in non-debug mode should definitely not have display errors on by default. It is a standard security practice in web applications to disable specific error reporting on live servers. However, in debug mode, error reporting should be enabled. The same applies to hiding it in a div. The reasoning behind this is that you don't want a misconfigured application announcing publicly what's happening on your server.
hi,
i found this also. I'm running gentoo witha recent kernel, but the php was compiled without the 'hash' keyword.
I've rebuilt ('emerged ") and plan to try shortly (haven't had time yet).
fwiw, my current use flags are as follows if any gentoo-folks know if gentoo needs any other use flags turned on to run elgg, please weigh in.
thanks:
reference: current use flags
[ebuild R ] dev-lang/php-5.2.10 USE="apache2 berkdb bzip2 cgi cli crypt gd gdbm hash iconv imap ipv6 ldap mysql ncurses nls pcre readline reflection session simplexml spell spl ssl truetype unicode xml zlib -adabas -bcmath -birdstep -calendar -cdb -cjk -concurrentmodphp -ctype -curl -curlwrappers -db2 -dbase -dbmaker -debug -discard-path -doc -empress -empress-bcs -esoob -exif -fastbuild -fdftk -filter -firebird -flatfile -force-cgi-redirect -frontbase -ftp -gd-external -gmp -inifile -interbase -iodbc (-java-external) -json -kerberos -kolab -ldap-sasl -libedit -mcve -mhash -msql -mssql -mysqli -oci8 -oci8-instant-client -odbc -pcntl -pdo -pic -posix -postgres -qdbm -recode -sapdb -sharedext -sharedmem -snmp -soap -sockets -solid -sqlite -suhosin -sybase -sybase-ct -sysvipc -threads -tidy -tokenizer -wddx -xmlreader -xmlrpc -xmlwriter -xpm -xsl -yaz -zip" 0 kB
SOLVED
a follow-up: rebuilding (emerging) php with the 'hash' option (use flag) solved the problem
Thanks for the help.
suggestion:
@Billmil -- Elgg in non-debug mode should definitely not have display errors on by default. It is a standard security practice in web applications to disable specific error reporting on live servers. However, in debug mode, error reporting should be enabled. The same applies to hiding it in a div. The reasoning behind this is that you don't want a misconfigured application announcing publicly what's happening on your server.
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by Raül Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.