Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:66875 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 65028 invoked from network); 31 Mar 2013 21:18:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Mar 2013 21:18:42 -0000 Authentication-Results: pb1.pair.com header.from=alex@kazik.de; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=alex@kazik.de; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain kazik.de designates 209.85.220.49 as permitted sender) X-PHP-List-Original-Sender: alex@kazik.de X-Host-Fingerprint: 209.85.220.49 mail-pa0-f49.google.com Received: from [209.85.220.49] ([209.85.220.49:58208] helo=mail-pa0-f49.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 57/86-20307-038A8515 for ; Sun, 31 Mar 2013 16:18:42 -0500 Received: by mail-pa0-f49.google.com with SMTP id kp14so1001343pab.8 for ; Sun, 31 Mar 2013 14:18:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kazik.de; s=google; h=x-received:mime-version:sender:x-originating-ip:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:cc :content-type; bh=A9G52p/O1f52gaKge8FDFXb4/BmzCwytFURc7sgLJC4=; b=cGpWl2Omxg7gLN8Kb1RPaxckRVVtybwoydU2uwOGCXVignLIjuH/Jka/qocLhlEgZR 2Cav0pTaOcv+HJ2WBlMVu5KDF1OBY7Y+uL5ES3MhljDjdT6JyPj9miZr1V7aVmjlGpBH RsXwhPARoQRwydm9DrmyknhUdQX2sf2pvjaFs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:sender:x-originating-ip:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:cc :content-type:x-gm-message-state; bh=A9G52p/O1f52gaKge8FDFXb4/BmzCwytFURc7sgLJC4=; b=X57ZLuyWv1zMVJCrA/15qeNBwXiUXrdt1w0nBph1G+hK3+0xqZhE5uPvXwhoGAwzE+ E5MIZh79Ugg1D81+sabfYG0RQz4kgT4QXRuW25N+H7kCFuUZ4aiL/YmFYZqQDnKka2Rz MHwwfMjFOGH2nQeRCudBsa5jMkDH0fhD10YAFuwaFvc2UD+oHeiUf3DQuneoFH0llxrP 8TpLXaiy68dvXYWwFLZFiUDAZs8UdD6QJisRvS5W7He10UmUBZtKRWtALUsz9rQDcosd CgVrSTRMJfo2o8kTSc7sdSxe+eROuCMHJVpBzw3ZI0yTOHqOxUMqjVNHQqYhXBvbgWMG rUEA== X-Received: by 10.68.211.8 with SMTP id my8mr15055849pbc.7.1364764717353; Sun, 31 Mar 2013 14:18:37 -0700 (PDT) MIME-Version: 1.0 Sender: alex@kazik.de Received: by 10.68.26.135 with HTTP; Sun, 31 Mar 2013 14:18:16 -0700 (PDT) X-Originating-IP: [92.39.17.211] In-Reply-To: <5158847D.4080806@mrclay.org> References: <5157A55A.1070507@sugarcrm.com> <5157AD1D.3020606@sugarcrm.com> <5158847D.4080806@mrclay.org> Date: Sun, 31 Mar 2013 23:18:16 +0200 X-Google-Sender-Auth: FKut0MMZX526i5GqSNcWaDhMhz4 Message-ID: Cc: PHP Internals Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQl4GmB3I33MYQfpjkBsKeBW6szg9/nUslLE99cTim7opVwf8MLfj2yf/fLTPJ0ZlBHgBcIr Subject: Re: [lists.php] Re: [PHP-DEV] [RFC] more secure unserialize() From: lists.php@tx0.eu (ALeX) > JSON and serialize() are (inherently) different serialization formats with different use-cases [...] Yes, and json requires that all strings (including the keys) has to be valid utf-8, and I'm sure that's not always the case (serialize can use binary data in both places).