public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Christopher Allen <ChristopherA@lifewithalacrity.com>
To: LORD HIS EXCELLENCY JAMES HRMH via bitcoin-dev
	<bitcoin-dev@lists.linuxfoundation.org>
Cc: Peter Denton <fontainedenton@googlemail.com>
Subject: Re: [bitcoin-dev] v3 onion services
Date: Sun, 17 Nov 2019 15:01:23 -0800	[thread overview]
Message-ID: <CACrqygB779UgCfr=BEUs_zsQeO=btdnEHbxaxEVwvqo9i3jBKw@mail.gmail.com> (raw)
In-Reply-To: <PS2P216MB01798627A61D2214FB3ED0D79D720@PS2P216MB0179.KORP216.PROD.OUTLOOK.COM>

[-- Attachment #1: Type: text/plain, Size: 696 bytes --]

Blockchain Commons is using v3 tor authentication for remote clients
controlling a full node created using our Bitcoin Standup project
(currently only macOS but more platforms coming):
https://github.com/BlockchainCommons/Bitcoin-Standup

Docs at:
https://github.com/BlockchainCommons/Bitcoin-Standup#tor-v3-authentication-using-standup-and-fullynoded


Video demonstrating securing remote connection of a full node to the iOS
wallet Fully Noded: https://youtu.be/pSm2VftTCBI

More details on v3 authentication at:
https://github.com/AnarchoTechNYC/meta/wiki/Connecting-to-an-authenticated-Onion-service#connecting-to-authenticated-version-3-onion-services

— Christopher Allen

[-- Attachment #2: Type: text/html, Size: 1309 bytes --]

  reply	other threads:[~2019-11-17 23:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-17  4:33 [bitcoin-dev] v3 onion services Mr. Lee Chiffre
2019-11-17 15:35 ` s7r
2019-11-17 20:04   ` LORD HIS EXCELLENCY JAMES HRMH
2019-11-17 23:01     ` Christopher Allen [this message]
2019-11-17 23:42 ` Matt Corallo
2019-11-18 11:59   ` Aymeric Vitte
2019-11-18 12:34     ` LORD HIS EXCELLENCY JAMES HRMH
     [not found] ` <46FCD14B-02CC-4986-9C60-D8EC547F33FA@carldong.me>
2019-11-18 16:44   ` Carl Dong
2019-11-18 22:19     ` Aymeric Vitte

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='CACrqygB779UgCfr=BEUs_zsQeO=btdnEHbxaxEVwvqo9i3jBKw@mail.gmail.com' \
    --to=christophera@lifewithalacrity.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=fontainedenton@googlemail.com \
    /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