Robert McKay [ARCHIVE] / is on Nostr

⚠️ This account is not associated with a real person. It's an archival account for mailing list messages.
🗓️ Active from 2011-07-01 to 2015-03-27
💬 Posted a total of 16 messages
📚 Participated in the following categories: Bitcoin-development
🔇 Please do not DM this user as it's used for archive purposes only.

Last Notes

2023-06-07 15:24:31

- reply

📅 Original date posted:2014-07-28
📝 Original message:On Mon, 28 Jul 2014 07:28:15 -0400, Peter Todd wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> I've got a bitcoin-only exit running myself and right now there is
> absolutely no traffic leaving it. If the traffic coming from that
> node
> was legit I'd expect some to be exiting my node too.
>
> Multiple people have confirmed the node is connected to an abnormally
> large % of the Bitcoin network. Looks like a Sybil attack to me,
> trying to hide behind a Tor exit node for plausible deniability.
I don't think Sybil attack is the right term for this.. there is only
one IP address.. one "identity".
I'm not even sure that this behaviour can be considered abuse.. it's
pretty much following the rules and maybe even improving the transaction
and block propagation.
As far as monitoring transaction origins someone could do that using
lots of different IPs instead of just one (more like an actual Sybil
attack rather than this non-Sybil attack).. and noone would be making a
fuss (and imo, probably someone does do that too as it would be useful
to capture a larger number of inbound connections).
Rob

2023-06-07 15:22:00

- reply

📅 Original date posted:2014-05-30
📝 Original message:Hi Alex,
I think the problem is with my suggestion to use bind forwarding..
basically bind is stripping off the authorative answer bit in the
reply.. this causes the recursor to go into a loop chasing the authority
server which again returns a non-authoritve answer with itself as the
authority again. I'm not sure if this can be fixed without hacking the
bind src, so maybe it wasn't such a great suggestion in the first place.
Basically I think if bind was returning authorative answers it would
work, but I can't see any way to make that happen in the bind
configuration.
Rob
On Fri, 30 May 2014 14:19:05 +0100, Alex Kotenko wrote:
> Hi Peter
>
> Ive setup DNS seeds myself a week ago, at testnet-seed.alexykot.me
> [6]
> and bitcoin-seed.alexykot.me [7], but there is a problem with DNS
> settings that we with Andreas couldnt sort out quickly.
> The problem itself is that I can reach my nameserver and get dnsseed
> response if I query it directly with
> dig @node.alexykot.me [8] testnet-seed.alexykot.me [9]
>
> dig @node.alexykot.me [10] bitcoin-seed.alexykot.me [11]
>
> But when I try nslookup testnet-seed.alexykot.me [12] - it
> fails.
> I guess the problem is in my DNS settings but I cant figure out what
> is it.
>
> S o could you share
> how you configured DNS
> for your seed
> to help me debug
> mine
> ?
>
> Best regards,
>
> Alex Kotenko
>
> 2014-05-30 10:43 GMT+01:00 Peter Todd :
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> On 27 May 2014 02:19:39 GMT+03:00, Andreas Schildbach wrote:
>> >> Hey, really sorry I dont have the time to fix this issue, been
>> >> travelling for a few weeks for my consulting job. If you want to
>> >> step up and volunteer please feel free.
>> >
>> >Im already volunteering. At least I dont get paid for my efforts
>> in
>> >debugging the seed infrastructure.
>>
>> I meant running a seed yourself. Note that Ive only received funds
>> to cover expenses and a trivial amount on top to cover some time -
>> about one and a half hours at my usual rates.
>>
>> Gavin: Speaking of, given it looks like my work will be frequently
>> keeping me out of country and unable to provide any more than a
>> "best effort" attempt at running a seed, Id like to give back the
>> grant funds for doing so. Email me privately with an address to send
>> them too. I have no plans to take it down, however the expectations
>> users have for it arent something I can provide.
>>
>> >Can you verify if your copy of the seeder contains the commit
>> >8dcc006e6256cb746c2b025daf3df41baa26353e ?
>> >
>> >It fixed a bug that has exactly the symptoms we currently see.
>> >
>> >I wonder if the restart of your server actually changed/fixed
>> >anything. If you got a SERVFAIL this may be because you were
>> traveling
>> >through parts of the world that cant reach your server. Did you
>> >actually try at home, before the restart?
>>
>> I checked via the same proxy both times; I believe the endpoint is
>> located in Europe.
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: APG v1.1.1
>>
>> iQFQBAEBCAA6BQJTiFKwMxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8
>> cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhQFCB/4jypD+xzKVp6fqRUxu
>> v22Rc6PeCbeaPYKmdNu0LbY1G5spB8C8ooaZX6z0Ib/CYobzDPJ+rJNB+c1Fna4N
>> 1IdH7ZsrX0GFaEn7Grnp7D2rtOXGZV+1XGFAateIA/caQ9+rJfqkHLuvOI0Fh+Ua
>> /m857rxUNtA1kObLFS7gfhi2gwXGO6KQ3muS3462hXVVc9j7DhOWQQwJba5PL+Je
>> Eob4WtnF2gVFlCEWevxvflF7j4lW9I/S81yZQDnNW9ATF2mfZVqo26sB0yL6Tm4l
>> KgdKx7+w3khv6QfW9Ilx0Ov3Ml2ZMRhBimpbnENbW4jfklsuRQcM0yx6vXS/lIMz
>> LO5s
>> =Up3N
>> -----END PGP SIGNATURE-----
>>
>>
>
> ------------------------------------------------------------------------------
>> Time is money. Stop wasting it! Get your web API in 5 minutes.
>> www.restlet.com/download [2]
>> http://p.sf.net/sfu/restlet [3]
>>
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development at lists.sourceforge.net [4]
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>> [5]
>
>
>
> Links:
> ------
> [1] mailto:andreas at schildbach.de
> [2] http://www.restlet.com/download
> [3] http://p.sf.net/sfu/restlet
> [4] mailto:Bitcoin-development at lists.sourceforge.net
> [5] https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> [6] http://testnet-seed.alexykot.me
> [7] http://bitcoin-seed.alexykot.me
> [8] http://node.alexykot.me
> [9] http://testnet-seed.alexykot.me
> [10] http://alexykot.me
> [11] http://bitcoin-seed.alexykot.me
> [12] http://testnet-seed.alexykot.me
> [13] mailto:pete at petertodd.org

2023-06-07 15:21:27

- reply

📅 Original date posted:2014-05-19
📝 Original message:On Tue, 20 May 2014 01:44:29 +0100, Robert McKay wrote:
> On Mon, 19 May 2014 19:49:52 -0400, Jeff Garzik wrote:
>> On Mon, May 19, 2014 at 4:36 PM, Robert McKay <robert at mckay.com>
>> wrote:
>>> It should be possible to configure bind as a DNS forwarder.. this
>>> can
>>> be done in a zone context.. then you can forward the different
>>> zones
>>> to
>>> different dnsseed daemons running on different non-public IPs or
>>> two
>>> different ports on the same IP (or on one single non-public IP
>>> since
>>> there's really no reason to expose the dnsseed directly daemon at
>>> all).
>>
>> Quite the opposite. dnsseed data rotates through a lot of addresses
>> if available. Using the bind/zone-xfer system would result in fewer
>> total addresses going through to the clients, thanks to the addition
>> of caching levels that the bind/zone-xfer system brings.
>>
>> That said, if the choice is between no-service and bind, bind it is
>> ;p
>
> Setting it up as a zone forwarder causes each request to go through
> to
> the dnsseed backend for each request.
This stackoverflow describes a similar situation;
http://stackoverflow.com/questions/15338232/how-to-forward-a-subzone
you can additionally specify the port to forward too;
http://www.zytrax.com/books/dns/ch7/queries.html#forwarders
it should be possible to forward to different ports on 127.0.0.1 for
each dnsseed instance.
Rob

2023-06-07 15:21:26

- reply

📅 Original date posted:2014-05-19
📝 Original message:It should be possible to configure bind as a DNS forwarder.. this can
be done in a zone context.. then you can forward the different zones to
different dnsseed daemons running on different non-public IPs or two
different ports on the same IP (or on one single non-public IP since
there's really no reason to expose the dnsseed directly daemon at all).
Rob
On Mon, 19 May 2014 21:14:32 +0100, Alex Kotenko wrote:
> Hmm, Ive mostly setup whats promised, testing DNS seeds now. There is
> one problem I see that I cant really solve myself.
> This dnsseed daemon cannot serve more than one name at once, which
> means that I cannot serve testnet and mainnet seeds off one daemon
> instance which means I need to buy two IP addresses for it. Thats
> unfortunate as it needs much more spendings from me to operate,
> second
> IP address will cost nearly as much as the server itself.
>
> Can anybody help with this? I cannot into C++ to fix that myself.
>
>
> Best regards,
>
> Alex Kotenko
>
> 2014-05-17 13:39 GMT+01:00 Andreas Schildbach :
>
>> On 05/17/2014 02:02 PM, Alex Kotenko wrote:
>>
>> > So, my understanding is that atm we have no working DNS seeds at
>> the
>> > testnet3, right? There are two DNS seeds known, of which one is
>> > unreachable atm, and another one is giving just one IP address,
>> which is
>> > also a dead node.
>>
>> Yes, thats my understanding too.
>>
>> > If Ill start a DNS seed of my own and make sure it works well,
>> will
>> > this help?
>>
>> Yes, definately.
>>
>> > Ive found this DNS seeder daemon
>> > , and it seems to be exactly
>>
>>> what I need to run a DNS seeder myself.
>>
>> Afaik this is what most of the other seeds are using, yes.
>>
>> > So if my understanding is correct, Ill setup a DNS seeds for
>> mainnet
>> > and for testnet at bitcoin-seed.alexykot.me [2]
>> > and testnet-seed.alexykot.me [4]
>> > , and also a well connected nodes for
>>
>>> mainnet and testnet on the same server.
>> > Is this a good plan? Will this all help?
>>
>> Sound great! Let me know if youve got something to test.
>>
>>
>
> ------------------------------------------------------------------------------
>> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For
>> FREE
>> Instantly run your Selenium tests across 300+ browser/OS combos.
>> Get unparalleled scalability from the best Selenium testing
>> platform available
>> Simple to use. Nothing to install. Get started now for free."
>> http://p.sf.net/sfu/SauceLabs [6]
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development at lists.sourceforge.net [7]
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>> [8]
>
>
>
> Links:
> ------
> [1] https://github.com/sipa/bitcoin-seeder
> [2] http://bitcoin-seed.alexykot.me
> [3] http://bitcoin-seed.alexykot.me
> [4] http://testnet-seed.alexykot.me
> [5] http://testnet-seed.alexykot.me
> [6] http://p.sf.net/sfu/SauceLabs
> [7] mailto:Bitcoin-development at lists.sourceforge.net
> [8] https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> [9] mailto:andreas at schildbach.de

2023-06-07 15:21:26

- reply

📅 Original date posted:2014-05-19
📝 Original message:On Mon, 19 May 2014 19:49:52 -0400, Jeff Garzik wrote:
> On Mon, May 19, 2014 at 4:36 PM, Robert McKay <robert at mckay.com>
> wrote:
>> It should be possible to configure bind as a DNS forwarder.. this
>> can
>> be done in a zone context.. then you can forward the different zones
>> to
>> different dnsseed daemons running on different non-public IPs or two
>> different ports on the same IP (or on one single non-public IP since
>> there's really no reason to expose the dnsseed directly daemon at
>> all).
>
> Quite the opposite. dnsseed data rotates through a lot of addresses
> if available. Using the bind/zone-xfer system would result in fewer
> total addresses going through to the clients, thanks to the addition
> of caching levels that the bind/zone-xfer system brings.
>
> That said, if the choice is between no-service and bind, bind it is
> ;p
Setting it up as a zone forwarder causes each request to go through to
the dnsseed backend for each request.
Rob