From: Wladimir <laanwj@gmail•com>
To: Odinn Cyberguerrilla <odinn.cyberguerrilla@riseup•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Anyone still using SOCKS4?
Date: Mon, 7 Jul 2014 08:47:22 +0200 [thread overview]
Message-ID: <CA+s+GJDPnz-JYbhTZw2cLVb1QrerrHVim9GRBdgVPsOeTLFJ+Q@mail.gmail.com> (raw)
In-Reply-To: <4f55608991d5377117ecf1728cd8db0c.squirrel@fruiteater.riseup.net>
On Mon, Jul 7, 2014 at 8:34 AM, Odinn Cyberguerrilla
<odinn.cyberguerrilla@riseup•net> wrote:
> Wait, I thought SOCKS4 was supposed to help somehow in terms of prevention
> of leaking of information?
SOCKS4a (unlike SOCKS4) supports doing DNS lookups on the server, but
it is not supported by bitcoin core. So it is not part of this
discussion.
And SOCKS5 can do all of that just as well. But if you feel like
contributing SOCKS4a support that's fine with me.
Wladimir
next prev parent reply other threads:[~2014-07-07 6:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 15:39 Wladimir
2014-07-04 7:15 ` Wladimir
2014-07-04 7:28 ` Drak
2014-07-07 6:34 ` Odinn Cyberguerrilla
2014-07-07 6:47 ` Wladimir [this message]
2014-07-07 6:54 ` Odinn Cyberguerrilla
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=CA+s+GJDPnz-JYbhTZw2cLVb1QrerrHVim9GRBdgVPsOeTLFJ+Q@mail.gmail.com \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=odinn.cyberguerrilla@riseup$(echo .)net \
/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