From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Rb671-0001co-KZ for bitcoin-development@lists.sourceforge.net; Thu, 15 Dec 2011 07:52:19 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.53 as permitted sender) client-ip=74.125.82.53; envelope-from=timon.elviejo@gmail.com; helo=mail-ww0-f53.google.com; Received: from mail-ww0-f53.google.com ([74.125.82.53]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1Rb670-0001EB-LT for bitcoin-development@lists.sourceforge.net; Thu, 15 Dec 2011 07:52:19 +0000 Received: by wgbds1 with SMTP id ds1so3117717wgb.10 for ; Wed, 14 Dec 2011 23:52:12 -0800 (PST) MIME-Version: 1.0 Received: by 10.227.197.70 with SMTP id ej6mr1277647wbb.13.1323935532607; Wed, 14 Dec 2011 23:52:12 -0800 (PST) Received: by 10.223.81.79 with HTTP; Wed, 14 Dec 2011 23:52:12 -0800 (PST) In-Reply-To: <4EE9A5A9.3000904@parhelic.com> References: <1323929094.37881.YahooMailClassic@web120902.mail.ne1.yahoo.com> <4EE9A5A9.3000904@parhelic.com> Date: Thu, 15 Dec 2011 08:52:12 +0100 Message-ID: From: =?ISO-8859-1?Q?Jorge_Tim=F3n?= Cc: bitcoin-development@lists.sourceforge.net Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (timon.elviejo[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.2 MISSING_HEADERS Missing To: header -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature -0.2 AWL AWL: From: address is in the auto white-list X-Headers-End: 1Rb670-0001EB-LT Subject: Re: [Bitcoin-development] Fwd: [BIP 15] Aliases X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Dec 2011 07:52:19 -0000 2011/12/15, Jordan Mack : > I believe it is also worth mentioning the possible susceptibility of a > DOS attack on a publicly available alias system. Assuming that an alias > lookup triggers the creation of a new Bitcoin address, the private key > would need to be retained indefinitely. If gone unnoticed, this could > consume considerable resources over time. Unlike system logs and such, > this is not something that can be so easily pruned. You're right. Then servers should not use a different address with every lookup. Maybe don't change it more than once per min/hour/whatever, maybe wait to see a payment to that address to start giving another one...