Douglas Huff [ARCHIVE] on Nostr: 📅 Original date posted:2011-09-15 🗒️ Summary of this message: A discussion ...
📅 Original date posted:2011-09-15
🗒️ Summary of this message: A discussion about a potential mem exhaustion DoS attack in the p2p network code of Bitcoin, with no patch submitted yet.
📝 Original message:On Sep 15, 2011, at 1:17 PM, Gavin Andresen wrote:
>> On Sep 15, 2011 11:20 AM, "Gavin Andresen" <gavinandresen at gmail.com> wrote:
>>> I'm ignoring bandwidth DoS attacks-- we already have the
>>> -maxreceivebuffer option to deal with those.
>>
>> I disagree with this comment. The way this is currently implemented is a mem
>> exhaustion dos in itself waiting to happen and does nothing to prevent
>> network flooding.
>
> Have you submitted a patch to fix it?
No, it requires the entirety of the p2p network code be reworked and large patches aren't accepted.
No reason to take that off list, it's an issue that's been acknowledged on irc numerous times and is in the public channel logs.
--
Douglas Huff
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110915/1aa29047/attachment.sig>;
🗒️ Summary of this message: A discussion about a potential mem exhaustion DoS attack in the p2p network code of Bitcoin, with no patch submitted yet.
📝 Original message:On Sep 15, 2011, at 1:17 PM, Gavin Andresen wrote:
>> On Sep 15, 2011 11:20 AM, "Gavin Andresen" <gavinandresen at gmail.com> wrote:
>>> I'm ignoring bandwidth DoS attacks-- we already have the
>>> -maxreceivebuffer option to deal with those.
>>
>> I disagree with this comment. The way this is currently implemented is a mem
>> exhaustion dos in itself waiting to happen and does nothing to prevent
>> network flooding.
>
> Have you submitted a patch to fix it?
No, it requires the entirety of the p2p network code be reworked and large patches aren't accepted.
No reason to take that off list, it's an issue that's been acknowledged on irc numerous times and is in the public channel logs.
--
Douglas Huff
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110915/1aa29047/attachment.sig>;