Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:119104 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 8062 invoked from network); 9 Dec 2022 16:17:30 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 9 Dec 2022 16:17:30 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 1CE6F180507 for ; Fri, 9 Dec 2022 08:17:27 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-io1-f48.google.com (mail-io1-f48.google.com [209.85.166.48]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Fri, 9 Dec 2022 08:17:26 -0800 (PST) Received: by mail-io1-f48.google.com with SMTP id z144so2280013iof.3 for ; Fri, 09 Dec 2022 08:17:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=basereality-com.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=CpMuFOWT6SsZtujZRIo/OVNQLKgJbWFH9xqM/bBRGUs=; b=D5EOCjynTqqK8fv9enRpYFGCu1tNhnE0qNBtv5c5GefEdc8cNzyodtNqF4W1plxJu7 0t6JOUEJlkmi0CiKIIEGO2gQWZ1fRHxNRGnbyceuOgOHXXp6YNSlGgmTUtJaHsOIlkAj DrmNpjFtEZfw0X/4TYbHlfXhQ/nyMXUAPQ0z/qnpANAVv5WyeP7xvkz8jVQJdCoJFzqa Y1HVkgL//4CkMLHevwRR0jm58XUgoJs2Bn8bP/LQ2DY+voiWKR5Uk7pH8F/7pYedI7mX p0A2LnVDwSXGC+c0fW76J50EjgbiDGS9fvGpAKixBWsPiTvG7IPpngv5lQQ5ubvxhD/9 aCDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=CpMuFOWT6SsZtujZRIo/OVNQLKgJbWFH9xqM/bBRGUs=; b=AHL+ijCT/YuW4hNAWe1E0rn1syvBqJhGcLstsiIm9bKNOXKhfj+Da3ula+GYyxw47X RYmotb4tOrCs6VeiUDCRl+ZrMESTSm49WKKxpfWpnvNEoEJ1GTe+jWzw0nkTPaax3bcg azVV+ZggUOEMkOYYQ4fBpBPU1Vx5Vgkdh37SctqXAdp1VfQqsO+6nqeOJB6O7DLeokNt kVhC0cmNDNonr3B9AOiu6Wfh9ZIrjKL6ynSBVP6HDPwUq/cVsqnbthIu6iLT06Gu8H++ ZHzd8nalgMLkoy22nCFRLgF6fIRVI0E7XZOjaUBgleu4yo/JX15anNMgur+uiKS0yjE4 3uug== X-Gm-Message-State: ANoB5pntd6NU45l4G5o+baPejxrzXRpui2BE2wky7I1xe7Gof11JyzVm 8CkVUfwlaIHgGXu9HnBqbTJK4R14Ir8PUhMZi8r1LUYXHAwyhQ== X-Google-Smtp-Source: AA0mqf4iW9eipbsyrFTtuCZwOnWGjzZwi3VjhmYf47MmWMPG6p2DWJ6A7A4Dh29jAdrSyjTrIp/lVOm3VaIWvzFckqE= X-Received: by 2002:a5d:9911:0:b0:6db:1f90:7e62 with SMTP id x17-20020a5d9911000000b006db1f907e62mr34791682iol.107.1670602645651; Fri, 09 Dec 2022 08:17:25 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Fri, 9 Dec 2022 16:17:14 +0000 Message-ID: To: =?UTF-8?Q?Tim_D=C3=BCsterhus?= Cc: Derick Rethans , PHP Developers Mailing List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] More Appropriate Date/Time Exceptions From: Danack@basereality.com (Dan Ackroyd) On Thu, 8 Dec 2022 at 15:05, Tim D=C3=BCsterhus wrote: > > If your data fails to > unserialize, the only safe option is to throw it away. Even given that, you probably want to investigate how it got corrupted so that you can stop it from happening again. And doing that would rely on being able to see the data that you attempted to unserialize. cheers Dan Ack