-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Push remote LND static channel backups to GitHub via Tor #1089
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just a nit
c10f7de
to
c691e02
Compare
Ok so I tested it and my backup was pushed to my repo... however, how can I check that it indeed use Tor and not clearnet.. is there any way to check this? Also, how can I check again that the -global core.sshCommand command is enabled and set with the required value? |
You can try running
|
You have, |
Ah ok, good point! It looks a bit different from your output but looks ok I think..
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tACK
It's nice privacy improvement ❤️
What
Push LND local channel remote backups to GitHub via Tor, not clearnet.
Why
RaspiBolt configures LND to work as .onion service only by default. But without this change remote static channel pushes to github.com happen using clearnet. This way your real IP address ir revealed to github.com (Microsoft), together with your channel information.
How
Change git configuration for lnd user to use
torsocks ssh
instead ofssh
to connect to GitHub.Scope
Fixes #1065
Test & maintenance
Modify git config, do
touch /data/lnd/data/chain/bitcoin/mainnet/channel.backup
and check that new backup file is pushed to GitHub repository.