From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Fri, 28 Jun 2024 18:33:44 -0700 Received: from mail-yw1-f184.google.com ([209.85.128.184]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sNMyG-00042N-0V for bitcoindev@gnusha.org; Fri, 28 Jun 2024 18:33:44 -0700 Received: by mail-yw1-f184.google.com with SMTP id 00721157ae682-64b9800b377sf9041087b3.0 for ; Fri, 28 Jun 2024 18:33:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1719624818; x=1720229618; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:sender:from :to:cc:subject:date:message-id:reply-to; bh=krD6xbHBQgJtKEbHImowvgUGrHZ8o4+xD9znhhuWeEs=; b=JJFcvQlG9EJNWqTh9ldzcM2Ty3IFLbBsOdahLNwHfnWbg8yBrdjAYZCser0leRowDu kWTRZsu05k5TLZ6ZR29ftdHGokSL0KbgTGf3FJodlA/VLNNZBqVvLs2HAtfY9z4RFn80 r7UzLJGABu5wzdYY3GRj15hnFbPbQnoZclCPu4I8Jeyd67RZyd/tuQEuNKei4IMe+M+X HdHvpYSdni7pP4M71E+yQ8np+LZLr5S0m99i5DOgNL3GL8APCojXqoEvBIt/0wIvluN1 LwbVosTX5y4jy6bnUHOu9aOkylqmPAG/t7Fm2ar8EwELa6YWfRiY7+NADsO5u6xU3LAA 3lUw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups-com.20230601.gappssmtp.com; s=20230601; t=1719624818; x=1720229618; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:from:to:cc :subject:date:message-id:reply-to; bh=krD6xbHBQgJtKEbHImowvgUGrHZ8o4+xD9znhhuWeEs=; b=AOygmLZdV/WcElapaCFz3pw//8Fch624XHW5hx9/1K+sHhFs+V7+Mm9qhDxYlUqyBh DMENaFbjSr3St2ew6xz0X1m6VH+E8juzZ001Ev5Jo3r/l3ftUKaMfAaHP5eU3V05RehQ kNH8TS6Ta1mBQMUqO/DrqVqaQ2UDf182g7CiOyJq4w8DJwG77A0HsfOILVUfxyeJTLXf yfmfPnRDvZnXqmqwioIN7WjOwrkkhUsEGlqmgXLDlIueuJs1XCYzTbxeoZI+MkXm2Kon 8m0KVMmDajIo1spPDM1dQ+YRHXPPIkzXut/iUEJS5656XGf1qiztN1FSCQWiXactrthU hvXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719624818; x=1720229618; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:x-beenthere :x-gm-message-state:sender:from:to:cc:subject:date:message-id :reply-to; bh=krD6xbHBQgJtKEbHImowvgUGrHZ8o4+xD9znhhuWeEs=; b=cD0bfBANqSo2oMBCwIb9ISbB2r+OG2MPodaXOM3Ekr/VLU9GFv3TgAcIjvsPbFDJ/D RoRGHwdzs/rSv7T/MFpkk8/Gat7yLeVaIuCpb1gIPUIvfcNIx6DYFzbo+6TkHxltMN8l h+KzQDuWJoynYbRQs4o3t41TBe7CXX5c96Y1KkkysDbyx6+ri/zzyJlgAkJx97BaXWcG QoStCEXZApz0T9JIOPT3srR6ObvkoiO0rmeZf0E0jdoCeIHtYeBHyAJEzV47kUvQepCs hh6UYgO84R0/iwdI8KxMXgMi5qsXhbC78yTxxcvPXFI5P5DSG3QDAXTxLEIfnDimmqDn l90A== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AJvYcCUBtNdp4wnB1CVDpAwD8Kz+MbBFZ9+LWFP+8Kp6gwUXEGzh7RPQlx2He0uZWqphE9jgGUsW58qxbTpcgrOh4N4MiI+oYJA= X-Gm-Message-State: AOJu0YxsN9wAb5c+zc2TCshhhMK9LZEffXWKjRBgyV9miwjRmCCdr5Fo teHx3ErwtycjKplkwHQssEqc9GufJ4qN7gH5FXmsadzbP7SCISyU X-Google-Smtp-Source: AGHT+IFKJEax3Xbv/vxx6VstIKwBGAzmIU/8UAwPqbCp5jrBF/BjC0ZapnCuqcCJuJKMXA23DW9Iyw== X-Received: by 2002:a5b:c03:0:b0:e03:2333:a6f0 with SMTP id 3f1490d57ef6-e035bf4f044mr2349975276.10.1719624817778; Fri, 28 Jun 2024 18:33:37 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com Received: by 2002:a05:6902:722:b0:dfa:77ba:dc1f with SMTP id 3f1490d57ef6-e0356274b10ls1984188276.2.-pod-prod-06-us; Fri, 28 Jun 2024 18:33:36 -0700 (PDT) X-Received: by 2002:a05:6902:2b8d:b0:e02:c619:73d with SMTP id 3f1490d57ef6-e030403de41mr977500276.5.1719624816213; Fri, 28 Jun 2024 18:33:36 -0700 (PDT) Received: by 2002:a0d:e6cd:0:b0:64a:6fb4:b878 with SMTP id 00721157ae682-64a84019cd1ms7b3; Fri, 28 Jun 2024 18:31:08 -0700 (PDT) X-Received: by 2002:a05:6902:2b8c:b0:e03:5220:a9df with SMTP id 3f1490d57ef6-e035220ac95mr360694276.0.1719624667849; Fri, 28 Jun 2024 18:31:07 -0700 (PDT) Date: Fri, 28 Jun 2024 18:31:07 -0700 (PDT) From: Eric Voskuil To: Bitcoin Development Mailing List Message-Id: <26b7321b-cc64-44b9-bc95-a4d8feb701e5n@googlegroups.com> In-Reply-To: <3f0064f9-54bd-46a7-9d9a-c54b99aca7b2n@googlegroups.com> References: <72e83c31-408f-4c13-bff5-bf0789302e23n@googlegroups.com> <5b0331a5-4e94-465d-a51d-02166e2c1937n@googlegroups.com> <9a4c4151-36ed-425a-a535-aa2837919a04n@googlegroups.com> <3f0064f9-54bd-46a7-9d9a-c54b99aca7b2n@googlegroups.com> Subject: Re: [bitcoindev] Re: Great Consensus Cleanup Revival MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_470777_500630627.1719624667635" X-Original-Sender: eric@voskuil.org Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -0.7 (/) ------=_Part_470777_500630627.1719624667635 Content-Type: multipart/alternative; boundary="----=_Part_470778_504734575.1719624667635" ------=_Part_470778_504734575.1719624667635 Content-Type: text/plain; charset="UTF-8" Hello Antoine (other), > If you have code in pure C with variables on the stack no malloc, doing a check of the coinbase size after the socket read can be certainly more robust than checking a non-null pointer. Can you please clarify this for me? When you say "non-null pointer" do you mean C pointer or transaction input "null point" (sequence of 32 repeating 0x00 bytes and 4 0xff)? What do you mean by "more robust"? Thanks, Eric -- You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/26b7321b-cc64-44b9-bc95-a4d8feb701e5n%40googlegroups.com. ------=_Part_470778_504734575.1719624667635 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello Antoine (other),

>=C2=A0 If you have code in pure C with variables on the stack no malloc, doing a c= heck of the coinbase size after the socket read can be certainly more robus= t than checking a non-null pointer.=C2=A0

Can you please clarify= this for me? When you say "non-null pointer" do you mean C pointer or tran= saction input "null point" (sequence of 32 repeating 0x00 bytes and 4 0xff)= ? What do you mean by "more robust"?

Thanks,
Eric

--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg= id/bitcoindev/26b7321b-cc64-44b9-bc95-a4d8feb701e5n%40googlegroups.com.=
------=_Part_470778_504734575.1719624667635-- ------=_Part_470777_500630627.1719624667635--