[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#751112: marked as done (release-notes: [jessie] Document changes in PHP 5.4->5.5 upgrade)

Your message dated Wed, 14 Jan 2015 19:41:43 +0100
with message-id <54B6B867.8050907@thykier.net>
and subject line Re: Bug#751112: release-notes: [jessie] Document changes in PHP 5.4->5.5 upgrade
has caused the Debian Bug report #751112,
regarding release-notes: [jessie] Document changes in PHP 5.4->5.5 upgrade
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

751112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751112
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release-notes
Severity: normal

Hash: SHA256


this needs to be documented in the release notes:

PHP 5.4->5.5

    - All internal case insensitivity handling for class, function and constant
      names is done according to ASCII rules.  Current locale settings are ignored.
    - self, parent & static keywords now are always case-insensitive (see bug
    - Removed Logo GUIDs: php_logo_guid(), php_egg_logo_guid(),
      php_real_logo_guid() and zend_logo_guid()

PHP 5.5->5.6

    - Core:
      By fixing bug #66015 it is no longer possible to overwrite keys in static scalar
      arrays. Quick example to illustrate:
      class Test {
           const FIRST = 1;
           public $array = array(
               self::FIRST => 'first',
      Test::$array will have as expected three array keys (1, 2, 3) and no longer
      two (0, 1). self::FIRST will no longer overwrite 'third' having key 1 then,
      but will mark the beginning of indexing. 
    - JSON:
      json_decode() no longer accepts non-lowercase variants of lone JSON true,
      false or null values. For example, True or FALSE will now cause json_decode to
      return NULL and set an error value you can fetch with json_last_error().
      This affects JSON texts consisting solely of true, false or null. Text
      containing non-lowercase values inside JSON arrays or objects has never been
    - OpenSSL:
      To prevent man-in-the-middle attacks against encrypted transfers client
      streams now verify peer certificates by default. Previous versions
      required users to manually enable peer verification. As a result of this
      change, existing code using ssl:// or tls:// stream wrappers (e.g.
      file_get_contents(), fsockopen(), stream_socket_client()) may no longer
      connect successfully without manually disabling peer verification via the
      stream context's "verify_peer" setting. Encrypted transfers delegate to
      operating system certificate stores by default if not overridden via the
      new openssl.cafile and openssl.cafile ini directives or via call-time SSL
      context options, so most users should be unaffected by this transparent
      security enhancement. (https://wiki.php.net/rfc/tls-peer-verification)
    - Mcrypt:
      The mcrypt_encrypt(), mcrypt_decrypt() and mcrypt_{MODE}() functions no
      longer accept keys or IVs with incorrect sizes. Furthermore an IV is now
      required if the used block cipher mode requires it.

Especially the OpenSSL change will hit many users.


- -- System Information:
Debian Release: 7.5
  APT prefers stable
  APT policy: (900, 'stable'), (800, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Version: GnuPG v1.4.12 (GNU/Linux)


--- End Message ---
--- Begin Message ---
On 2014-11-26 10:09, Ondřej Surý wrote:
> Hi Niels,
> [...]
> lgtm, but I am ccing the packaging group, maybe William or Lior would
> have some comments.
> Cheers,


Thanks for reviewing it.

I have not heard anything from William or Lior, so I am going ahead and
assuming it is all good. :)  Should you notice anything, please do not
hesitate to reopen the bug (or a file a new one).


--- End Message ---

Reply to: