Hi,
One of the IT futur, is Container (docker like and kubernetes like) and Single
Page Application...
On the other language the tendancy is to simplify the start time and single
start of the application (only one process start the application runc) and
simplify configuration; and simplify log
_
From: Nuno Lopes [mailto:[EMAIL PROTECTED]
... I would love to ear how other VMs handle the
problem, like the JVM, anyone?yes, me too!
_
From: Stanislav Malyshev [mailto:[EMAIL PROTECTED]
I don't think they are "not important", just that they are not important
enough to want them fixed no matter the cost. Running shared hosted
server in a mode that relies on restricted code IMO is wrong anyway, and
for non-shared e
> I don't think you've read the section on prepared statements in the
> PDO documentation, because it does mention it there, although it
> doesn't beat you over the head with the seriousness of the problem.
>
> http://us2.php.net/manual/en/ref.pdo.php#pdo.prepared-statements
Sorry for my buz...
> A quick google search for 'sql injection prepared statements' found
> those 2 statements (1 is a security article) very quickly.
> ...And frankly, its not the manual's job to tell you how to
> write secure code. So, this has to be coming from people.
>
Yes but a php security portal that referen
Mathieu CARBONNEAUX souhaite rappeler le message [EMAIL PROTECTED] Re:
[PHP-DEV] Comments on PHP security».
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
>Limits, table names, and several other query parts are protected by
>MediaWiki's query builder. A complex select query might look like this:
>
>$result = $db->select(
># Tables
>array( 'user', 'revision' ),
># Fields
>array( 'user_name', 'rev_timestamp' ),
># Conditions (WHERE)
_
From: Vlad Bosinceanu [mailto:[EMAIL PROTECTED]
What might help is pushing (via the manual) for the adoption of tools
that prevent common problems, with pdo's prepared statements being one
such tool.ok, documenting is what i say...
but not all use php5 pdo... not all use php5... many
_
From: Brian Moon [mailto:[EMAIL PROTECTED]
We really need to stop spreading this myth that prepared statements are
a security measure. Prepared statements only allow passing of the value
parts of where clauses and a couple of other parts of the query. Limit
values would be the most c
>I'm pretty sure these things are not covering, for example, JNI modules.
>Extensions are basically JNI of PHP.
i'm not very java fan... but i think majority of java application not use any
JNI module... because of this risk and because in majority situation all
necesary can be coded and are c
it's very usefull to have possibility in large php installation (many apache
instance with many differente configuration, in module loaded and
parametter...) to have the possibility to split for each php instance the php
configuration in differente files...
the --with-config-file-scan-dir confi
hi,
i'have made similare patch to make possible to modify the hardcoded by autoconf
configuration of scandir for additional ini by environement variable and/or by
apache directive...
i've used the same solution used with PHPRC env. and PHPINIDir...
i've added PHPRCSCAN_DIR env. and PHPINISCANDir
Hi all,
have two question!
the first is where i can find documentation (other than the php source...!)
about developping new sapi? if exist !?
and for the seconds, have seen in differente sapi source that work like apache
module and php module, with a struct who point to differente handler th
u can have any Web server of your
choice on that machine serving static files, and it can even serve it from
the same application layout structure so that application deployment is not
an issue...
Andi
> -Original Message-
> From: Mathieu CARBONNEAUX [mailto:[EMAIL PROTECTED]
> Sent:
u can have any Web server of your
choice on that machine serving static files, and it can even serve it from
the same application layout structure so that application deployment is not
an issue...
Andi
> -Original Message-
> From: Mathieu CARBONNEAUX [mailto:[EMAIL PROTECTED]
> Sent:
[mailto:[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: internals@lists.php.net
Sent: Sun, 26 Nov 2006 18:30:15 +0100
Subject: [EMAIL PROTECTED] Re: [PHP-DEV] new apache fastcgi implementation and
php fastcgi patch
On Sun, November 26, 2006 4:59 am, Mathieu CARBONNEAUX wrote:
> they only exec
e if it's a good implementation then it might be nice to
contribute it to them.
Andi
> -Original Message-
> From: Mathieu CARBONNEAUX [mailto:[EMAIL PROTECTED]
> Sent: Sunday, November 26, 2006 2:59 AM
> To: internals@lists.php.net
> Subject: [PHP-DEV] new apache fast
hi every body,
i've developped a new implementation of fastcgi module for apache.
i'have used the scheme handler of mod_proxy of apache like new mod_proxy_ajp
in apache 2.2...
the idea is to make possible proxyfy php application behind apache (for
security et and performance...).
to make possib
18 matches
Mail list logo
