Delivery-date: Wed, 27 Mar 2024 11:26:31 -0700
Sender: bitcoindev@googlegroups.com
Received-SPF: pass (google.com: domain of pete@petertodd.org designates 64.147.123.24 as permitted sender) client-ip=64.147.123.24;
Feedback-ID: i525146e8:Fastmail
Date: Wed, 27 Mar 2024 18:04:46 +0000
From: Peter Todd <pete@petertodd.org>
To: "David A. Harding" <dave@dtrt.org>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] A Free-Relay Attack Exploiting RBF Rule #6
Message-ID: <ZgRfvrYatcpqPNRn@petertodd.org>
References: <f7fbeb4f58904fc5a24b6fc2d829036c@dtrt.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="WIB19lrcLw7AqMfT"
Content-Disposition: inline
In-Reply-To: <f7fbeb4f58904fc5a24b6fc2d829036c@dtrt.org>
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com


--WIB19lrcLw7AqMfT
Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline

On Wed, Mar 27, 2024 at 07:18:08AM -1000, David A. Harding wrote:
> On 2024-03-27 02:10, Peter Todd wrote:
> > On Tue, Mar 26, 2024 at 08:36:45AM -1000, David A. Harding wrote:
> > > Could you tell us more about the disclosure process you followed?
> > 
> > see attached.
> 
> Do I correctly infer from this that you privately reported the attack on
> Thursday around 15:46 UTC, didn't receive any replies in four days
> (including a weekend), and published the attack on Monday at 13:21 UTC?
> 
> That's a very short timeline to use for going public due to not receiving a
> response.  I think it's typical to give triage at least 30 days to respond,
> often while also prompting them additional times for a response if
> necessary.

I'm on the bitcoin-security mailing list. Every single plausible issue that has
been raised in the past few years has gotten a response within two days. A few
days is plenty of time to at least respond with a simple "give us more time" if
needed.

Secondly, I was able to verify independently that the relevant people had seen
the email and weren't planning on replying. Which isn't surprising. It's just
another way to perform an obvious, well known, class of attack.

Anyway, I think the lesson to be learned here is I'd have been better off not
disclosing to bitcoin-security first. You're just harassing me here; I highly
suspect you'd have said nothing at all if I hadn't brought up disclosure.

-- 
https://petertodd.org 'peter'[:-1]@petertodd.org

-- 
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/ZgRfvrYatcpqPNRn%40petertodd.org.

--WIB19lrcLw7AqMfT
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmYEX7wACgkQLly11TVR
LzdUvRAAnEHqY8tv/fTwr1iaFRJ4GsfcHxeY86z5DOxtBcIUnh/21n2fN3wEXMW0
sgMo0Zky2eKfciOukT8Waqiudaijed91KA2fFc3A53Cuhyufkn1HaQHOTpToVGbL
VLWM0CEXltc0mQA1Yzj1BHa6UWJB/EbD4hdRdVcygbcsYgcl9+w22ghIHmtDAoEo
BpO396x0KYnBUDZzozib6v/b+9LcnXnDCf6Pgicj+gIu3ymFT48XPT9d972jG9y2
jb3SXYVVOcSg4AI7Tz1vwN+5wK84assLJFvkrmMqDaP6lHPCiSWquLkNqFrQGZxA
XXgoqCfdJc0pzH7t+QPt10mDXq8b/jZjWDGs7NN3Or4/dAgMb/HswgojGghMKJOF
zUc6YcooB0QynuKmQ9g4BcGySo5flB/nArtoHLZ/Ru/PySO0sns+KTTAtb16N+VD
FKHv7f8QXispApOZ//dG9SoZMQHSfGDjX92I+3EdEvVdD5dt0i2ET/wNohSQHWn9
W7KHa8kAXFibEytsrWOSrwBPBToKFwuQFjbdyFAZPLoZdYVOoQJ3PIXKPiRXWIqr
Wck//SfIAyH6ovyhnbxjqQxGVUlJcSVk5KeRJFvj1Umn45rDmYOgyog8oXWxdc3U
7zZDW7h5PdQb0XUHxRnTYL/eT/Rrr6DqXl+AWZk8eBQqLcKrSx4=
=LTSb
-----END PGP SIGNATURE-----

--WIB19lrcLw7AqMfT--