it can be customized with some limitations
I think using a name other than 'crypt' would be advisable - maybe
php_crypt or something. Otherwise you have a namespace clash with the
usual crypt, which may cause all sorts of grief.
--
Jim Segrave [EMAIL PROTECTED]
--
PHP Development
is prefixed with -- */
+*(loc-3)=='\n') /* ensure beginning
+of line */
#endif
) {
break;
--
Jim Segrave [EMAIL PROTECTED]
--
PHP Development
On Fri 01 Mar 2002 (11:00 -0800), Rasmus Lerdorf wrote:
On Fri, 1 Mar 2002, Jim Segrave wrote:
Guys, I fixed this memchr()+1 issue a couple of days ago. See
http://cvs.php.net/diff.php/php4/main/rfc1867.c?r1=1.71.2.2r2=1.71.2.3ty=u
It's a crash-bug, not an exploitable buffer
, that is :) will have a patch shortly. Additionally,
an upcoming release of MySQL will feature an additional permission to
control this case.
And this is a much better solution - we'll look forward to that.
--
Jim Segrave [EMAIL PROTECTED]
--
PHP Development Mailing List http
)
{
--
Jim Segrave [EMAIL PROTECTED]
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, visit: http://www.php.net/unsub.php
