Permalink
Switch branches/tags
Commits on Jul 4, 2012
  1. PHP 5.3.15RC1

    johannes committed Jul 4, 2012
  2. Revert change 3f3ad30: There shouldn't be new features in 5.3, especi…

    johannes committed Jul 4, 2012
    …ally
    
    not if they aren't in 5.4, too.
Commits on Jul 2, 2012
Commits on Jul 1, 2012
  1. Revert JSON changes to PHP 5.3

    nikic committed Jul 1, 2012
    This reverts the following commits:
    
    9743246
    4662151
    84fe2cc
    
    This does not revert the JSON changes released in PHP 5.3.14.
  2. remove duplicates, fix order

    smalyshev committed Jul 1, 2012
Commits on Jun 30, 2012
  1. - Fixed bug #62415 (Undefined variable: diff in run-tests.php on line…

    felipensp committed Jun 30, 2012
    … 2093 for successful XFAIL)
Commits on Jun 29, 2012
  1. Fix some lengths in crypt()

    nikic committed Jun 29, 2012
    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 committed Jun 29, 2012
  3. Fixed bug #62443 (Crypt SHA256/512 Segfaults With Malformed Salt)

    Anthony Ferrara committed Jun 29, 2012
    Fixed a memory allocation bug in crypt() SHA256/512 that can
    cause segmentation faults when passed in salts with a null byte
    early.
Commits on Jun 28, 2012
  1. Add json_last_error_msg() function

    nikic committed Jun 28, 2012
    This replaces json_last_error(true) and is consistent with other custom
    error handling functions.
Commits on Jun 27, 2012
  1. Fix #62432 ReflectionMethod random corrupt memory on high concurrent

    johannes committed Jun 27, 2012
    This fixes the same issue in multiple extensions. This isn't needed
    in later branches as 5.4 introduced object_properties_init()
  2. Improve JSON error handling

    nikic committed Jun 27, 2012
    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. Fix memleak in CLI

    johannes committed Jun 27, 2012
Commits on Jun 26, 2012
  1. ws fix

    smalyshev committed Jun 26, 2012
Commits on Jun 25, 2012
  1. BFN

    moriyoshi committed Jun 25, 2012
Commits on Jun 24, 2012
  1. Fix memory allocation checks for base64 encode

    nikic committed Jun 24, 2012
    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
    memory.)
    
    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. Improve json_encode error handling

    nikic committed Jun 23, 2012
    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:
    
      * JSON_ERROR_RECURSION
      * JSON_ERROR_INF_OR_NAN
      * JSON_ERROR_UNSUPPORTED_TYPE
    
    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
    later.
  2. - BFN

    felipensp committed Jun 23, 2012
  3. - Improved fix for #62384

    felipensp committed Jun 23, 2012
Commits on Jun 22, 2012
  1. Remove extra ;

    johannes committed Jun 22, 2012
Commits on Jun 20, 2012
Commits on Jun 19, 2012
  1. Add NEWS for bug #62262

    nikic committed Jun 19, 2012
  2. Fixed bug RecursiveArrayIterator does not implement Countable

    nikic committed Jun 19, 2012
    ArrayIterator implemented Countable only after it was already inherited by
    RecursiveArrayIterator. Thus the interface was missing in RAI.
  3. sync zip ext version with pecl

    weltling committed Jun 19, 2012
Commits on Jun 18, 2012
  1. com ext upgrading correction

    weltling committed Jun 18, 2012
  2. com ext upgrading info

    weltling committed Jun 18, 2012
Commits on Jun 17, 2012
  1. Reverted the BC fix regarding to #57905, test adopted

    weltling committed Jun 17, 2012
    New 0.10.1 has a stronger archive integrity check. Restoring
    the old behaviour of libzip < 0.10.1 makes no sense at this
    place.