Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
tag: php-5.3.15RC1
Commits on Jul 4, 2012
  1. @johannes

    PHP 5.3.15RC1

    johannes authored
  2. @johannes

    Revert change 3f3ad30: There shouldn't be new features in 5.3, especi…

    johannes authored
    not if they aren't in 5.4, too.
Commits on Jul 2, 2012
  1. fix (signed) integer overflow (part of bug #52550

    Nuno Lopes authored
Commits on Jul 1, 2012
  1. @nikic

    Revert JSON changes to PHP 5.3

    nikic authored
    This reverts the following commits:
    This does not revert the JSON changes released in PHP 5.3.14.
  2. @smalyshev

    remove duplicates, fix order

    smalyshev authored
Commits on Jun 30, 2012
  1. @felipensp

    - Fixed bug #62415 (Undefined variable: diff in run-tests.php on line…

    felipensp authored
    … 2093 for successful XFAIL)
Commits on Jun 29, 2012
  1. @nikic

    Fix some lengths in crypt()

    nikic authored
    Use salt_len_in instead of strlen(salt) or PHP_MAX_SALT_LEN, otherwise too
    much memory will be allocated.
    sha512 has a 86 character checksum, not 43. That probably was a copy&paste
    from the sha256 code which indeed has 43.
    The allocation also was using sizeof(char *), thus allocating 4 or 8 times
    as much memory as necessary. The sizeof(char *) was removed in the 5.4
    branch in b7a92c9 but forgotten on 5.3.
    The memset 0 call was using PHP_MAX_SALT_LEN which can be smaller than the
    output buffer and thus not zeroing out everything. Use the size of the
    output buffer (needed) instead.
  2. new charsets

    andrey authored
  3. Fixed bug #62443 (Crypt SHA256/512 Segfaults With Malformed Salt)

    Anthony Ferrara authored
    Fixed a memory allocation bug in crypt() SHA256/512 that can
    cause segmentation faults when passed in salts with a null byte
Commits on Jun 28, 2012
  1. @nikic

    Add json_last_error_msg() function

    nikic authored
    This replaces json_last_error(true) and is consistent with other custom
    error handling functions.
Commits on Jun 27, 2012
  1. @johannes

    Fix #62432 ReflectionMethod random corrupt memory on high concurrent

    johannes authored
    This fixes the same issue in multiple extensions. This isn't needed
    in later branches as 5.4 introduced object_properties_init()
  2. @nikic

    Improve JSON error handling

    nikic authored
    json_encode() no longer throws warnings. Instead only the error code for
    json_last_error() is set.
    As it is hard to debug the error from just an error code an optional
    $as_string parameter was added to json_last_error(), which returns an
    error message instead of an error code.
  3. @johannes

    Fix memleak in CLI

    johannes authored
Commits on Jun 26, 2012
  1. @smalyshev

    ws fix

    smalyshev authored
Commits on Jun 25, 2012
  1. @moriyoshi


    moriyoshi authored
  2. @moriyoshi
Commits on Jun 24, 2012
  1. @nikic

    Fix memory allocation checks for base64 encode

    nikic authored
    base64_encode used safe_emalloc, but one of the arguments was derived from a
    multiplication, thus making the allocation unsafe again.
    There was a size check in place, but it was off by a factor of two as it
    didn't account for the signedness of the integer type.
    The unsafe allocation is not exploitable, but still causes funny behavior
    when the sized overflows into a negative number.
    To fix the issue the *4 factor is moved into the size argument (where it is
    known to be safe), so safe_emalloc can carry out the multiplication.
    The size check is removed as it doesn't really make sense once safe_emalloc
    works correctly. (Would only cause base64_encode to silently return false
    instead of throwing an error. Also could cause problems with other uses of
    the base64 encoding API, which all don't check for a NULL return value.)
    Furthermore the (length + 2) < 0 check is replaced with just length < 0.
    Allowing lengths -2 and -1 doesn't make sense semantically and also is not
    honored in the following code (negative length would access unallocated
    Actually the length < 0 check doesn't make sense altogether, but I left it
    there just to be safe.
Commits on Jun 23, 2012
  1. @nikic

    Improve json_encode error handling

    nikic authored
    json_encode() now returns bool(false) for all possible errors, throws the
    respective warning and also sets the respective json_last_error() error
    code. Three new error codes have been added:
    To get a partial JSON output instead of bool(false) the option
    JSON_PARTIAL_OUTPUT_ON_ERROR can be specified. In this case the invalid
    segments will be replaced either by null (for recursion, unsupported type
    and invalid JSON) or 0 (for Inf and NaN).
    The warning for invalid UTF-8 stays intact and is thrown also with
    display_errors = On. If this behavior is undesired this can be remedied
  2. @felipensp

    - BFN

    felipensp authored
  3. @felipensp

    - Improved fix for #62384

    felipensp authored
Commits on Jun 22, 2012
  1. @johannes
  2. @johannes

    Remove extra ;

    johannes authored
  3. @felipensp
  4. @johannes
Commits on Jun 20, 2012
  1. @johannes
Commits on Jun 19, 2012
  1. @nikic

    Add NEWS for bug #62262

    nikic authored
  2. @nikic

    Fixed bug RecursiveArrayIterator does not implement Countable

    nikic authored
    ArrayIterator implemented Countable only after it was already inherited by
    RecursiveArrayIterator. Thus the interface was missing in RAI.
  3. @weltling
  4. @weltling
  5. @weltling
Commits on Jun 18, 2012
  1. @weltling

    com ext upgrading correction

    weltling authored
  2. @weltling

    com ext upgrading info

    weltling authored
Commits on Jun 17, 2012
  1. @weltling

    Reverted the BC fix regarding to #57905, test adopted

    weltling authored
    New 0.10.1 has a stronger archive integrity check. Restoring
    the old behaviour of libzip < 0.10.1 makes no sense at this
Something went wrong with that request. Please try again.