public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Oliver Egginger <bitcoin@olivere.de>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] DOS-Attacks on bitcoin-client?
Date: Sun, 07 Apr 2013 16:43:30 +0200	[thread overview]
Message-ID: <51618612.9010603@olivere.de> (raw)

Hello,

I'm using your bitcoin-qt client (version 0.8.1). Normally everything is 
working pretty fine, but sometimes it seems that other nodes produce an 
enormous amount of traffic. I have not had the time to investigate 
thoroughly yet. I only have briefly viewed with tshark.

So far I have just restarted the client in the hope that it no longer 
connects with the 'evil' node. This usually works quite well.

Is anything about DOS-Attacks known to you?

regards
Oliver



             reply	other threads:[~2013-04-07 15:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-07 14:43 Oliver Egginger [this message]
2013-04-07 15:22 ` [Bitcoin-development] DOS-Attacks on bitcoin-client? Scott Howard
2013-04-07 16:35   ` Oliver Egginger
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=51618612.9010603@olivere.de \
    --to=bitcoin@olivere.de \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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