From: Oliver Egginger <bitcoin@olivere•de>
To: Scott Howard <showard314@gmail•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] DOS-Attacks on bitcoin-client?
Date: Sun, 07 Apr 2013 18:35:10 +0200 [thread overview]
Message-ID: <5161A03E.2040802@olivere.de> (raw)
In-Reply-To: <CANg8-dC2FX-9QFE_Bq6djTiEsvvD+0Cc2Vy0Ofzk54DVrdVuxA@mail.gmail.com>
Am 07.04.2013 17:22, schrieb Scott Howard:
> Many new users have started using the reference client which downloads
> the whole blockchain from peers.
Yes I have made a clean start because of the the new database structure.
> There currently isn't a throttling
> mechanism [1] so it's possible to quickly eat up your bandwidth. You
> can try QoS on your router or use the -nolisten command line flag. You
> will still relay transactions, just not serve the whole blockchain.
I see. I successfully have downloaded the Blockchain again. Thus, it
should not occur again now. If it does, I'll be back again. :-)
Thank you for your quick help.
regards
Oliver
next prev parent reply other threads:[~2013-04-07 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 14:43 Oliver Egginger
2013-04-07 15:22 ` Scott Howard
2013-04-07 16:35 ` Oliver Egginger [this message]
2013-04-08 5:42 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5161A03E.2040802@olivere.de \
--to=bitcoin@olivere$(echo .)de \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=showard314@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox