public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Wladimir <laanwj@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Anyone still using SOCKS4?
Date: Wed, 11 Jun 2014 17:39:51 +0200	[thread overview]
Message-ID: <CA+s+GJDSPS=zsM64wHaG1CucHVkO==L1QkHYiciUo9iJ-RADng@mail.gmail.com> (raw)

Hello all,

Is anyone using a SOCKS4-only proxy with Bitcoin Core? SOCKS5 was
introduced in 1996, so there is hardly an excuse to not support it.

If no one screams fire, we plan on removing support for it in the next
major release, for two reasons:

- It would remove some crufty, hardly tested code paths

- SOCKS5 offers better privacy as it allows DNS redirection

Wladimir



             reply	other threads:[~2014-06-11 15:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11 15:39 Wladimir [this message]
2014-07-04  7:15 ` [Bitcoin-development] Anyone still using SOCKS4? Wladimir
2014-07-04  7:28   ` Drak
2014-07-07  6:34   ` Odinn Cyberguerrilla
2014-07-07  6:47     ` Wladimir
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+GJDSPS=zsM64wHaG1CucHVkO==L1QkHYiciUo9iJ-RADng@mail.gmail.com' \
    --to=laanwj@gmail.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