-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
server+tor: add support for Tor HASHEDPASSWORD authentication method #4048
server+tor: add support for Tor HASHEDPASSWORD authentication method #4048
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.
Only a single nit, other than that really looking forward to this one! 😁
a771ab9
to
9134e04
Compare
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.
Ran locally and works as expected, LGTM!
Would be cool to update docs/configuring_tor.md
to indicate that there's an option other than safecookie available. Should be as simple as noting the tor config change and tor.password
flag but not a blocker.
9134e04
to
ae0a51e
Compare
@carlaKC added! |
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.
added!
Nice, still LGTM 😄
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.
Tested and works as expected! Should mention how to get the HashedControlPassword
, other than that LGTM.
This provides users an alternative over the SAFECOOKIE authentication method, which may not be as useful if users are connecting to a remote Tor sevrer due to lnd not being able to retrieve the cookie file.
ae0a51e
to
018e8b5
Compare
Tested and confirmed locally that all three authentication methods (
SAFECOOKIE
,HASHEDPASSWORD
,NULL
) work as intended.SAFECOOKIE
remains as the default unless a control password is provided.Replaces #2548.