Page 1 of 1

Getting Hacking Attempt Message

PostPosted: Fri Feb 16, 2007 3:16 pm
Author: .QUACK.Major.Pain
Your phpBB Version: 2.0.
phpBB Type: Integramod 141
MODs: No
Your knowledge: Beginner
Board URL: http://aaquacks.com/forum

PHP Version:
MySQL Version:


What was done before the problem appeared?
define('CT_SECLEVEL', 'MEDIUM');
$ct_ignorepvar = array('send');

in admin/admin_email_users.php



What was done to try to solve the problem?
none



De.scription and Message

I went into General Admin/Mass Email & PM section, click on a box next to a name and then clciked on Send A Email Or PM at the top of the page. I then got the cracker tracker error. I did the suggested debug listed above. Then I tried to do same sequence again, and now I don't get the cracker tracker error, I get a little message in top left of the screen stating 'Hacking Attempt'.

What's the fix now?

Re: Getting Hacking Attempt Message

PostPosted: Fri Feb 16, 2007 7:46 pm
Author: Helter
try changing
define('CT_SECLEVEL', 'MEDIUM');
to
define('CT_SECLEVEL', 'LOW');

Re: Getting Hacking Attempt Message

PostPosted: Fri Feb 16, 2007 11:03 pm
Author: .QUACK.Major.Pain
already tried that and still get same message

Re: Getting Hacking Attempt Message

PostPosted: Sat Feb 17, 2007 9:35 pm
Author: Teelk
Try moving...
Code: Select all
define('IN_PHPBB', true);
... above this code...
Code: Select all
if( !empty($setmodules) ){     $file = basename(__FILE__);     $module['General']['Mass_Email_Users'] = $file;     return;}  

Re: Getting Hacking Attempt Message

PostPosted: Sat Feb 17, 2007 10:05 pm
Author: .QUACK.Major.Pain
Did that change and still get: 'Hacking attempt!' message

Re: Getting Hacking Attempt Message

PostPosted: Sun Feb 18, 2007 1:05 pm
Author: Teelk
Wow, this is the second post today that I've found that I gave a really bad answer to. I was so tired yesterday lol.

Ok, the admin/ folder files aren't used to generate the modules anymore, the admin/modules folder is. You're getting a hacking attempt because the file admin/modules/admin_email_users.php isn't defined as a viewable file.

So, open admin/modules/admin_email_users.php

FIND
Code: Select all
if( !empty($setmodules) ){     $file = basename(__FILE__);     $module['General']['Mass_Email_Users'] = $file;     return;}

BEFORE ADD
Code: Select all
define('IN_PHPBB', true);


Congrats, you found an actual bug. <img>

Re: Getting Hacking Attempt Message

PostPosted: Sun Feb 18, 2007 2:04 pm
Author: .QUACK.Major.Pain
OK tried that too - same result - same message

I tried clicking box next to name and then clicking Send An Email Or A PM = hacking attempt!

I tried clicking box next to name and then clicking Add The Selected Users = hacking attempt!

Am I doing it right?

Must be having fun sorting out all the bugs. Guess ya take em 1 at a time. LOL

Re: Getting Hacking Attempt Message

PostPosted: Fri Mar 30, 2007 1:30 pm
Author: Omni-Lee
Has a fix been found for this? The ones supplied within this thread do correct the Hacking Attempt! error.

Re: Getting Hacking Attempt Message

PostPosted: Fri Mar 30, 2007 4:36 pm
Author: .QUACK.Major.Pain
define('IN_PHPBB', 1); define('IN_PHPBB', true);

Are the above 2 the same? The left is used in debug, the right is in the actual file.

The above fix doesn't work. I still get the "Hacking Attempt!!!" message.

The original files trigger CT error.
When you do the debug that is suggestted, that's when you get the hacking attempt error.

Re: Getting Hacking Attempt Message

PostPosted: Fri Mar 30, 2007 10:04 pm
Author: Frost
I tried doing the suggestions mentioned above and like them found it doesn't work.

So here's what I've seen if it helps.

When using debug mode, the ctracker warning is not logged as a debug, but as a "Worm & Exploit Protection"

Inside the logs it reads...

Appeal - /forum/admin/admin_email_users.php?

Referer - http://www.black-fusion.com/forum/admin ... 6798fba1d2

I tried...

Editing both admin_email_users.php in admin/ and admin/modules/
Changing around.. etc

Re: Getting Hacking Attempt Message

PostPosted: Thu May 10, 2007 5:40 pm
Author: .QUACK.Major.Pain
Bump - Is anyone still looking at this??? <img>

Re: Getting Hacking Attempt Message

PostPosted: Sat Jun 16, 2007 2:43 am
Author: Ezra
I wanted to give this topic a bump, because this problem isn't solved yet. I also tried the options given, but with no result.

Does anyone have any idea how to fix this error? Thanks.

Greetings,
Ezra

Re: Getting Hacking Attempt Message

PostPosted: Mon Jun 18, 2007 10:32 am
Author: Ezra
I hope I don't sound impatient. But, I was really hoping that you guys can look into this. Unfortunately I can't do it myself, so I need your help on this.

I have to send a large group of users an email, so I would really like this function to work. I'm a n00b on programming, so I don't know if I aks a simple or difficult question.

Maybe you can at least let me know if you're working on it or not, if not, I have to find another easy way to email a selection of my users.

Thanks!
Ezra

Re: Getting Hacking Attempt Message

PostPosted: Mon Jun 18, 2007 7:17 pm
Author: Helter
I cannot reproduce the problem. On this site, I opened

/forum/admin/admin_email_users.php

found

define('IN_PHPBB', true);

after that, I added

define('CT_SECLEVEL', 'LOW');
$ct_ignorepvar = array('send');


problem solved.

here is the begining of the file



Code: Select all
 <?php/***************************************************************************  *                                      admin_email_users.php  *                                   ------------------  *  *   begin                             ]['Mass_Email_Users'] = $file;     return;}  define('IN_PHPBB', true);  define('CT_SECLEVEL', 'LOW');$ct_ignorepvar = array('send');  $phpbb_root_path = '../';require($phpbb_root_path . 'extension.inc');require("pagestart.$phpEx");include($phpbb_root_path.'language/lang_' . $board_config['default_lang'] . '/lang_admin_mail_users.'.$phpEx);include($phpbb_root_path . 'includes/functions_post.'.$phpEx);include($phpbb_root_path . 'includes/bbcode.'.$phpEx);  

Re: Getting Hacking Attempt Message

PostPosted: Mon Jun 18, 2007 7:49 pm
Author: .QUACK.Major.Pain
Had that change but set to medium - I changed it to low and tried.
Still same result - I select a box and then click on Send email or PM

Result: Hacking attempt!

Gotta be something wrong with the coding.

Have to find the file that puts up the message "hacking attempt'

Re: Getting Hacking Attempt Message

PostPosted: Mon Jun 18, 2007 8:41 pm
Author: Helter
if it is something wrong with the coding, it eludes me. Ive added the fix to all 3 of my active sites and all work fine. I just succesfully sent a mass email to many of the staff here. Have you added the update?
http://www.integramod.com/forum/viewtop ... t=ctracker

Re: Getting Hacking Attempt Message

PostPosted: Mon Jun 18, 2007 8:46 pm
Author: .QUACK.Major.Pain
I noticed a problem.
If you select no boxes and click on Send a Pm or Email, it goes to the next page.
If you select a box, you get the Hacking Attempt! message.

The Hacking Attempt message comes from ctracker/engines/ct_security.php

<?php
/**
* <b>CrackerTracker File: ct_security.php</b><br><br>
*
* This file is responsible for the worm protection Unit of the CrackerTracker
* Security System. The File includes a definition Array wich is used to
* heuristically scan URL requests for attacks.
*
* We included some virtual Troopers for you. <img>
*
*
* @author Christian Knerr (cback) and Tekin BirdÃÂ ¼zen (cYbercOsmOnauT)
* @package ctracker
* @version 5.0.3
* @since 15.07.2006 - 21:36:24
* @copyright (c) 2006 http://www.cback.de
*
* @license http://opensource.org/licenses/gpl-license.php GNU Public License
*/

if( !defined('IN_PHPBB') )
{
die("Hacking attempt!");
}


/*
* Change the following to define('CT_DEBUG_MODE', true);
* if you want to activate the debug mode of CrackerTracker
* but don't forget to deactivate it again as soon as possible
*/
define('CT_DEBUG_MODE', false);

/*
* DO NOT CHANGE ANYTHING BELOW!
* CHANGING STUFF BELOW CAN DRAMATICALLY DECREASE
* THE SECURITY OF YOUR BOARD SO PLEASE
* DO NOT CHANGE ANYTHING BELOW THIS LINE!
*/

Re: Getting Hacking Attempt Message

PostPosted: Mon Jun 18, 2007 8:49 pm
Author: .QUACK.Major.Pain
Are you using Mass Email and PM or just Mass Email?

The mass email works fine.
It's the Mass Email ans PM page that gives this error.

Both my sites give the hacking error and I've set to low on both.

At first I got the CT error - then did fix - then the hacking attempt error started

Re: Getting Hacking Attempt Message

PostPosted: Mon Jun 18, 2007 10:09 pm
Author: Helter
I did exactly the steps from the first post. Ive also done many alternate steps. There is no coding error. Other than phpbb updates, this file dates back past ver132
the only diference is that CT intercepts the call to the db and blocks it. The fix I posted stops CT from interfering. Im assuming the phpbb "hacking attempt" message, is the result of whatever you did to try to stop the CT message. I remember you posting in another thread about a php function being disabled on your server. Open your php.ini and do a search for that function. Youll probably find it in a list of disabled functions. It might be helpful to know what other functions have been disabled

Re: Getting Hacking Attempt Message

PostPosted: Tue Jun 19, 2007 4:26 am
Author: .QUACK.Major.Pain
I can't see it being something I did if others get the same error.
Frost and 2-3 others have same message. So obviously you have a different setting or something changed in your file that we don't have.

Can you put your file in post here and I'll upload it to mine and test it. At least I can eliminate if it's the file or another issue.

Re: Getting Hacking Attempt Message

PostPosted: Tue Jun 19, 2007 8:24 am
Author: Helter
here it is.

Re: Getting Hacking Attempt Message

PostPosted: Tue Jun 19, 2007 12:05 pm
Author: Ezra
"HelterSkelter";p="26697" wrote:here it is.


I just uploaded that file, but still get the same error. By the way, the error comes when I use "Mass Email and PM", not the "Mass Email".

Thanks for looking into this, I hope someone can find the solution to this.

Re: Getting Hacking Attempt Message

PostPosted: Tue Jun 19, 2007 1:18 pm
Author: .QUACK.Major.Pain
Well your file was slightly smaller than mine but even with the change, it still gives me the error too.

Next step?

Not sure what to look for in php.ini, but here it is - maybe you can see something

[PHP]

;;;;;;;;;;;;;;;;;;;
; About this file ;
;;;;;;;;;;;;;;;;;;;
; This file controls many aspects of PHP's behavior. In order for PHP to
; read it, it must be named 'php.ini'. PHP looks for it in the current
; working directory, in the path designated by the environment variable
; PHPRC, and in the path that was defined in compile time (in that order).
; Under Windows, the compile-time path is the Windows directory. The
; path in which the php.ini file is looked for can be overriden using
; the -c argument in command line mode.
;
; The syntax of the file is extremely simple. Whitespace and Lines
; beginning with a semicolon are silently ignored (as you probably guessed).
; Section headers (e.g. [Foo]) are also silently ignored, even though
; they might mean something in the future.
;
; Directives are specified using the following syntax:
; directive = value
; Directive names are *case sensitive* - foo=bar is different from FOO=bar.
;
; The value can be a string, a number, a PHP constant (e.g. E_ALL or M_PI), one
; of the INI constants (On, Off, True, False, Yes, No and None) or an expression
; (e.g. E_ALL & ~E_NOTICE), or a quoted string ("foo").
;
; Expressions in the INI file are limited to bitwise operators and parentheses:
; | bitwise OR
; & bitwise AND
; ~ bitwise NOT
; ! boolean NOT
;
; Boolean flags can be turned on using the values 1, On, True or Yes.
; They can be turned off using the values 0, Off, False or No.
;
; An empty string can be denoted by simply not writing anything after the equal
; sign, or by using the None keyword:
;
; foo = ; sets foo to an empty string
; foo = none ; sets foo to an empty string
; foo = "none" ; sets foo to the string 'none'
;
; If you use constants in your value, and these constants belong to a dynamically
; loaded extension (either a PHP extension or a Zend extension), you may only
; use these constants *after* the line that loads the extension.
;
; All the values in the php.ini-dist file correspond to the builtin
; defaults (that is, if no php.ini is used, or if you delete these lines,
; the builtin defaults will be identical).


;;;;;;;;;;;;;;;;;;;;
; Language Options ;
;;;;;;;;;;;;;;;;;;;;

engine = On ; Enable the PHP .scripting language engine under Apache
short_open_tag = On ; allow the <? tag. otherwise, only <?php and <script> tags are recognized.
asp_tags = Off ; allow ASP-style <% %> tags
precision = 14 ; number of significant digits displayed in floating point numbers
y2k_compliance = Off ; whether to be year 2000 compliant (will cause problems with non y2k compliant browsers)
output_buffering = Off ; Output buffering allows you to send header lines (including cookies)
; even after you send body content, in the price of slowing PHP's
; output layer a bit.
; You can enable output buffering by in runtime by calling the output
; buffering functions, or enable output buffering for all files
; by setting this directive to On.
implicit_flush = Off ; Implicit flush tells PHP to tell the output layer to flush itself
; automatically after every output block. This is equivalent to
; calling the PHP function flush() after each and every call to print()
; or echo() and each and every HTML block.
; Turning this option on has serious performance implications, and
; is generally recommended for debugging purposes only.
allow_call_time_pass_reference = On ; whether to enable the ability to force arguments to be
; passed by reference at function-call time. This method
; is deprecated, and is likely to be unsupported in future
; versions of PHP/Zend. The encouraged method of specifying
; which arguments should be passed by reference is in the
; function declaration. You're encouraged to try and
; turn this option Off, and make sure your .scripts work
; properly with it, to ensure they will work with future
; versions of the language (you will receive a warning
; each time you use this feature, and the argument will
; be passed by value instead of by reference).

; Safe Mode
safe_mode = On
safe_mode_exec_dir =
safe_mode_allowed_env_vars = PHP_ ; Setting certain environment variables
; may be a potential security breach.
; This directive contains a comma-delimited
; list of prefixes. In Safe Mode, the
; user may only alter environment
; variables whose names begin with the
; prefixes supplied here.
; By default, users will only be able
; to set environment variables that begin
; with PHP_ (e.g. PHP_FOO=BAR).
; Note: If this directive is empty, PHP
; will let the user modify ANY environment
; variable!
safe_mode_protected_env_vars = LD_LIBRARY_PATH ; This directive contains a comma-
; delimited list of environment variables,
; that the end user won't be able to
; change using putenv().
; These variables will be protected
; even if safe_mode_allowed_env_vars is
; set to allow to change them.


disable_functions = ; This directive allows you to disable certain
; functions for security reasons. It receives
; a comma separated list of function names.
; This directive is *NOT* affected by whether
; Safe Mode is turned on or off.


; Colors for Syntax Highlighting mode. Anything that's acceptable in <font> would work.
highlight.string = #DD0000
highlight.comment = #FF8000
highlight.keyword = #007700
highlight.bg = #FFFFFF
highlight.default = #0000BB
highlight.html = #000000

; Misc
expose_php = On ; Decides whether PHP may expose the fact that it is installed on the
; server (e.g., by adding its signature to the Web server header).
; It is no security threat in any way, but it makes it possible
; to determine whether you use PHP on your server or not.



;;;;;;;;;;;;;;;;;;;
; Resource Limits ;
;;;;;;;;;;;;;;;;;;;

max_execution_time = 30 ; Maximum execution time of each .script, in seconds
memory_limit = 8M ; Maximum amount of memory a .script may consume (8MB)


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Error handling and logging ;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; error_reporting is a bit-field. Or each number up to get desired error reporting level
; E_ALL - All errors and warnings
; E_ERROR - fatal run-time errors
; E_WARNING - run-time warnings (non fatal errors)
; E_PARSE - compile-time parse errors
; E_NOTICE - run-time notices (these are warnings which often result from a bug in
; your code, but it's possible that it was intentional (e.g., using an
; uninitialized variable and relying on the fact it's automatically
; initialized to an empty string)
; E_CORE_ERROR - fatal errors that occur during PHP's initial startup
; E_CORE_WARNING - warnings (non fatal errors) that occur during PHP's initial startup
; E_COMPILE_ERROR - fatal compile-time errors
; E_COMPILE_WARNING - compile-time warnings (non fatal errors)
; E_USER_ERROR - user-generated error message
; E_USER_WARNING - user-generated warning message
; E_USER_NOTICE - user-generated notice message
; Examples:
; error_reporting = E_ALL & ~E_NOTICE ; show all errors, except for notices
; error_reporting = E_COMPILE_ERROR|E_ERROR|E_CORE_ERROR ; show only errors
error_reporting = E_ALL & ~E_NOTICE ; Show all errors except for notices
display_errors = On ; Print out errors (as a part of the output)
; For production web sites, you're strongly encouraged
; to turn this feature off, and use error logging instead (see below).
; Keeping display_errors enabled on a production web site may reveal
; security information to end users, such as file paths on your Web server,
; your database schema or other information.
display_startup_errors = Off ; Even when display_errors is on, errors that occur during
; PHP's startup sequence are not displayed. It's strongly
; recommended to keep display_startup_errors off, except for
; when debugging.
log_errors = On ;
; As stated above, you're strongly advised to use error logging in place of
; error displaying on production web sites.
track_errors = Off ; Store the last error/warning message in $php_errormsg (boolean)
;error_prepend_string = "<font>" ; string to output before an error message
;error_append_string = "</font>" ; string to output after an error message
error_log = error_log ;
error_log = error_log ;
warn_plus_overloading = Off ; warn if the + operator is used with strings


;;;;;;;;;;;;;;;;;
; Data Handling ;
;;;;;;;;;;;;;;;;;
; Note - track_vars is ALWAYS enabled as of PHP 4.0.3
variables_order = "EGPCS" ; This directive describes the order in which PHP registers
; GET, POST, Cookie, Environment and Built-in variables (G, P,
; C, E & S respectively, often referred to as EGPCS or GPC).
; Registration is done from left to right, newer values override
; older values.
register_globals = Off ; Whether or not to register the EGPCS variables as global
; variables. You may want to turn this off if you don't want
; to clutter your .scripts' global scope with user data. This makes
; most sense when coupled with track_vars - in which case you can
; access all of the GPC variables through the $HTTP_*_VARS[],
; variables.
; You should do your best to write your .scripts so that they do
; not require register_globals to be on; Using form variables
; as globals can easily lead to possible security problems, if
; the code is not very well thought of.
register_argc_argv = On ; This directive tells PHP whether to declare the argv&argc
; variables (that would contain the GET information). If you
; don't use these variables, you should turn it off for
; increased performance
post_max_size = 55M ; Maximum size of POST data that PHP will accept.
gpc_order = "GPC" ; This directive is deprecated. Use variables_order instead.

; Magic quotes
magic_quotes_gpc = On ; magic quotes for incoming GET/POST/Cookie data
magic_quotes_runtime= Off ; magic quotes for runtime-generated data, e.g. data from SQL, from exec(), etc.
magic_quotes_sybase = Off ; Use Sybase-style magic quotes (escape ' with '' instead of ')

; automatically add files before or after any PHP document
auto_prepend_file =
auto_append_file =

; As of 4.0b4, PHP always outputs a character encoding by default in
; the Content-type: header. To disable sending of the charset, simply
; set it to be empty.
; PHP's built-in default is text/html
default_mimetype = "text/html"
;default_charset = "iso-8859-1"

;;;;;;;;;;;;;;;;;;;;;;;;;
; Paths and Directories ;
;;;;;;;;;;;;;;;;;;;;;;;;;
include_path = ".:/usr/lib/php:/usr/local/lib/php" ;
doc_root = ; the root of the php pages, used only if nonempty
user_dir = ; the directory under which php opens the .script using /~username, used only if nonempty
extension_dir = ./ ; directory in which the loadable extensions (modules) reside
enable_dl = On ; Whether or not to enable the dl() function.
; The dl() function does NOT properly work in multithreaded
; servers, such as IIS or Zeus, and is automatically disabled
; on them.


;;;;;;;;;;;;;;;;
; File Uploads ;
;;;;;;;;;;;;;;;;
file_uploads = On ; Whether to allow HTTP file uploads
;upload_tmp_dir = ; temporary directory for HTTP uploaded files (will use system default if not specified)
upload_max_filesize = 6M ; Maximum allowed size for uploaded files


;;;;;;;;;;;;;;;;;;;;;;
; Dynamic Extensions ;
;;;;;;;;;;;;;;;;;;;;;;
; if you wish to have an extension loaded automaticly, use the
; following syntax: extension=modulename.extension
; for example, on windows,
; extension=msql.dll
; or under UNIX,
; extension=msql.so
; Note that it should be the name of the module only, no directory information
; needs to go here. Specify the location of the extension with the extension_dir directive above.

;zend_optimizer.optimization_level=15
;zend_extension="/usr/local/Zend/lib/ZendOptimizer.so"

;Windows Extensions
;Note that MySQL and ODBC support is now built in, so no dll is needed for it.
;
;extension=php_cpdf.dll
;extension=php_cybercash.dll
;extension=php_db.dll
;extension=php_dbase.dll
;extension=php_domxml.dll
;extension=php_dotnet.dll
;extension=php_exif.dll
;extension=php_fdf.dll
;extension=php_gd.dll
;extension=php_gettext.dll
;extension=php_ifx.dll
;extension=php_imap.dll
;extension=php_interbase.dll
;extension=php_java.dll
;extension=php_ldap.dll
;extension=php_mhash.dll
;extension=php_mssql65.dll
;extension=php_mssql70.dll
;extension=php_oci8.dll
;extension=php_oracle.dll
;extension=php_pdf.dll
;extension=php_pgsql.dll
;extension=php_sablot.dll
;extension=php_swf.dll
;extension=php_sybase_ct.dll
;extension=php_zlib.dll


;;;;;;;;;;;;;;;;;;;
; Module Settings ;
;;;;;;;;;;;;;;;;;;;

[Syslog]
define_syslog_variables = Off ; Whether or not to define the various syslog variables,
; e.g. $LOG_PID, $LOG_CRON, etc. Turning it off is a
; good idea performance-wise. In runtime, you can define
; these variables by calling define_syslog_variables()


[mail function]
;SMTP = localhost ;
;sendmail_from = <a>me@localhost.com</a> ;
sendmail_path = /usr/sbin/sendmail -t -i ;

[Debugger]
debugger.host = localhost
debugger.port = 7869
debugger.enabled = False

[Logging]
; These configuration directives are used by the example logging mechanism.
; See examples/README.logging for more explanation.
;logging.method = db
;logging.directory = /path/to/log/directory

[Java]
;java.class.path = .php_java.jar
;java.home = c:jdk
;java.library = c:jdkjrebinhotspotjvm.dll
;java.library.path = .


[SQL]
sql.safe_mode = Off

[ODBC]
;uodbc.default_db = Not yet implemented
;uodbc.default_user = Not yet implemented
;uodbc.default_pw = Not yet implemented
uodbc.allow_persistent = On ; allow or prevent persistent links
uodbc.check_persistent = On ; check that a connection is still validbefore reuse
uodbc.max_persistent = -1 ; maximum number of persistent links. -1 means no limit
uodbc.max_links = -1 ; maximum number of links (persistent+non persistent). -1 means no limit
uodbc.defaultlrl = 4096 ; Handling of LONG fields. Returns number of bytes to variables, 0 means passthru
uodbc.defaultbinmode = 1 ; Handling of binary data. 0 means passthru, 1 return as is, 2 convert to char
; See the documentation on odbc_binmode and odbc_longreadlen for an explanation of uodbc.defaultlrl
; and uodbc.defaultbinmode

[MySQL]
mysql.allow_persistent = On ; allow or prevent persistent link
mysql.max_persistent = -1 ; maximum number of persistent links. -1 means no limit
mysql.max_links = -1 ; maximum number of links (persistent+non persistent). -1 means no limit
mysql.default_port = ; default port number for mysql_connect(). If unset,
; mysql_connect() will use the $MYSQL_TCP_PORT, or the mysql-tcp
; entry in /etc/services, or the compile-time defined MYSQL_PORT
; (in that order). Win32 will only look at MYSQL_PORT.
mysql.default_socket = ; default socket name for local MySQL connects. If empty, uses the built-in
; MySQL defaults
mysql.default_host = ; default host for mysql_connect() (doesn't apply in safe mode)
mysql.default_user = ; default user for mysql_connect() (doesn't apply in safe mode)
mysql.default_password = ; default password for mysql_connect() (doesn't apply in safe mode)
; Note that this is generally a *bad* idea to store passwords
; in this file. *Any* user with PHP access can run
; 'echo cfg_get_var("mysql.default_password")' and reveal that
; password! And of course, any users with read access to this
; file will be able to reveal the password as well.

[mSQL]
msql.allow_persistent = On ; allow or prevent persistent link
msql.max_persistent = -1 ; maximum number of persistent links. -1 means no limit
msql.max_links = -1 ; maximum number of links (persistent+non persistent). -1 means no limit

[PostgresSQL]
pgsql.allow_persistent = On ; allow or prevent persistent link
pgsql.max_persistent = -1 ; maximum number of persistent links. -1 means no limit
pgsql.max_links = -1 ; maximum number of links (persistent+non persistent). -1 means no limit

[Sybase]
sybase.allow_persistent = On ; allow or prevent persistent link
sybase.max_persistent = -1 ; maximum number of persistent links. -1 means no limit
sybase.max_links = -1 ; maximum number of links (persistent+non persistent). -1 means no limit
;sybase.interface_file = "/usr/sybase/interfaces"
sybase.min_error_severity = 10 ; minimum error severity to display
sybase.min_message_severity = 10 ; minimum message severity to display
sybase.compatability_mode = Off ; compatability mode with old versions of PHP 3.0.
; If on, this will cause PHP to automatically assign types to results
; according to their Sybase type, instead of treating them all as
; strings. This compatability mode will probably not stay around
; forever, so try applying whatever necessary changes to your code,
; and turn it off.

[Sybase-CT]
sybct.allow_persistent = On ; allow or prevent persistent link
sybct.max_persistent = -1 ; maximum number of persistent links. -1 means no limit
sybct.max_links = -1 ; maximum number of links (persistent+non persistent). -1 means no limit
sybct.min_server_severity = 10 ; minimum server message severity to display
sybct.min_client_severity = 10 ; minimum client message severity to display

[bcmath]
bcmath.scale = 0 ; number of decimal digits for all bcmath functions

[browscap]
;browscap = extra/browscap.ini

[Informix]
ifx.default_host = ; default host for ifx_connect() (doesn't apply in safe mode)
ifx.default_user = ; default user for ifx_connect() (doesn't apply in safe mode)
ifx.default_password = ; default password for ifx_connect() (doesn't apply in safe mode)
ifx.allow_persistent = On ; allow or prevent persistent link
ifx.max_persistent = -1 ; maximum number of persistent links. -1 means no limit
ifx.max_links = -1 ; maximum number of links (persistent+non persistent). -1 means no limit
ifx.textasvarchar = 0 ; if set on, select statements return the contents of a text blob instead of it's id
ifx.byteasvarchar = 0 ; if set on, select statements return the contents of a byte blob instead of it's id
ifx.charasvarchar = 0 ; trailing blanks are stripped from fixed-length char columns. May help the life
; of Informix SE users.
ifx.blobinfile = 0 ; if set on, the contents of text&byte blobs are dumped to a file instead of
; keeping them in memory
ifx.nullformat = 0 ; NULL's are returned as empty strings, unless this is set to 1. In that case,
; NULL's are returned as string 'NULL'.

[Session]
session.save_handler = files ; handler used to store/retrieve data
session.save_path = /tmp ; argument passed to save_handler
; in the case of files, this is the
; path where data files are stored
session.use_cookies = 1 ; whether to use cookies
session.name = PHPSESSID
; name of the session
; is used as cookie name
session.auto_start = 0 ; initialize session on request startup
session.cookie_lifetime = 0 ; lifetime in seconds of cookie
; or if 0, until browser is restarted
session.cookie_path = / ; the path the cookie is valid for
session.cookie_domain = ; the domain the cookie is valid for
session.serialize_handler = php ; handler used to serialize data
; php is the standard serializer of PHP
session.gc_probability = 1 ; percentual probability that the
; 'garbage collection' process is started
; on every session initialization
session.gc_maxlifetime = 1440 ; after this number of seconds, stored
; data will be seen as 'garbage' and
; cleaned up by the gc process
session.referer_check = ; check HTTP Referer to invalidate
; externally stored URLs containing ids
session.entropy_length = 0 ; how many bytes to read from the file
session.entropy_file = ; specified here to create the session id
; session.entropy_length = 16
; session.entropy_file = /dev/urandom
session.cache_limiter = nocache ; set to {nocache,private,public} to
; determine HTTP caching aspects
session.cache_expire = 180 ; document expires after n minutes
session.use_trans_sid = 1 ; use transient sid support if enabled
; by compiling with --enable-trans-sid

[MSSQL]
;extension=php_mssql.dll
mssql.allow_persistent = On ; allow or prevent persistent link
mssql.max_persistent = -1 ; maximum number of persistent links. -1 means no limit
mssql.max_links = -1 ; maximum number of links (persistent+non persistent). -1 means no limit
mssql.min_error_severity = 10 ; minimum error severity to display
mssql.min_message_severity = 10 ; minimum message severity to display
mssql.compatability_mode = Off ; compatability mode with old versions of PHP 3.0.

[Assertion]
;assert.active = On ; assert(expr); active by default
;assert.warning = On ; issue a PHP warning for each failed assertion.
;assert.bail = Off ; don't bail out by default.
;assert.callback = 0 ; user-function to be called if an assertion fails.
;assert.quiet_eval = 0 ; eval the expression with current error_reporting(). set to true if you want error_reporting(0) around the eval().

[Ingres II]
ingres.allow_persistent = On ; allow or prevent persistent link
ingres.max_persistent = -1 ; maximum number of persistent links. (-1 means no limit)
ingres.max_links = -1 ; maximum number of links, including persistents (-1 means no limit)
ingres.default_database = ; default database (format : [node_id::]dbname[/srv_class]
ingres.default_user = ; default user
ingres.default_password = ; default password

[Verisign Payflow Pro]
pfpro.defaulthost = "test.signio.com" ; default Signio server
pfpro.defaultport = 443 ; default port to connect to
pfpro.defaulttimeout = 30 ; default timeout in seconds

; pfpro.proxyaddress = ; default proxy IP address (if required)
; pfpro.proxyport = ; default proxy port
; pfpro.proxylogon = ; default proxy logon
; pfpro.proxypassword = ; default proxy password

; Local Variables:
; tab-width: 4
; End:



;[Zend]
;zend_optimizer.optimization_level=15
;zend_extension_manager.optimizer=/usr/local/Zend/lib/Optimizer-2.5.10
;zend_extension_manager.optimizer_ts=/usr/local/Zend/lib/Optimizer_TS-2.5.10

;zend_optimizer.version=2.5.10


[Zend]
zend_optimizer.optimization_level=15
zend_extension_manager.optimizer=/usr/local/Zend/lib/Optimizer-2_6_2
zend_extension_manager.optimizer_ts=/usr/local/Zend/lib/Optimizer_TS-2_6_2
zend_optimizer.version=2.6.2



;cgi.fix_pathinfo = 1 ;needed for CGI/FastCGI mode


zend_extension=/usr/local/Zend/lib/ZendExtensionManager.so
zend_extension_ts=/usr/local/Zend/lib/ZendExtensionManager_TS.so