public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Sergio Lerner <sergiolerner@certimix.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Miners MiTM
Date: Sat, 09 Aug 2014 09:15:26 -0300	[thread overview]
Message-ID: <53E610DE.4070903@certimix.com> (raw)
In-Reply-To: <A5697066-6389-4F9A-99E6-B815ADB51006@heliacal.net>

Since the information exchanged between the pool and the miner is
public, all that's needed is a mutual private MAC key that authenticates
messages.
This requires a registration step, that can be done only once using a
simple web interface over https to the miner website.
But the miner website is not the miner server, so the worst DoS would be
preventing new miners to join the pool, which is not very often.
The MAC key can be provided directly by the miner. And the pool
associates the MAC key with a Bitcoin public address.
The overhead would be minimal.


-Sergio.




  reply	other threads:[~2014-08-09 12:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-07 23:02 [Bitcoin-development] Miners MiTM Pedro Worcel
2014-08-07 23:45 ` Luke Dashjr
2014-08-08  0:29   ` slush
2014-08-08  0:37     ` Christopher Franko
2014-08-08  1:07       ` Pedro Worcel
2014-08-08  2:22         ` slush
2014-08-08  1:01     ` Luke Dashjr
2014-08-08  9:53       ` Mike Hearn
2014-08-08 18:21         ` Jeff Garzik
2014-08-08 18:27           ` Luke Dashjr
2014-08-08 18:34           ` Laszlo Hanyecz
2014-08-09 12:15             ` Sergio Lerner [this message]
2014-08-08  3:18     ` Jeff Garzik
2014-08-08  9:42     ` Mike Hearn
2014-08-09 19:39       ` Troy Benjegerdes
2014-08-09 19:31   ` Troy Benjegerdes

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=53E610DE.4070903@certimix.com \
    --to=sergiolerner@certimix.com \
    --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