Sketch of Tor Authenticator - Fixes #6 #8
Loading…
Reference in New Issue
No description provided.
Delete Branch "authenticator"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes #6
Drone Build Status: failure
https://build.openprivacy.ca/openprivacy/connectivity/13
Drone Build Status: success
https://build.openprivacy.ca/openprivacy/connectivity/16
Sketch of Tor Authenticatorto Sketch of Tor Authenticator - Fixes #6Is the goal to always use authentication? If so then we could still have a default authenticator and control port object.
I'd rather still see a simple point of entry for ACN use, so keep the
NewTorACN(appDirectory string, bundledTorPath string)
signature and add aNewTorACNWithAuth(appDirectory string, bundledTorPath string, controlPort int, authenticator Authenticator)
that the first can redirect to with defaults@ -0,0 +1,5 @@
SOCKSPort 9050
ControlPort 9051
HashedControlPassword 16:848CFDB693D95D6360DF71363AF1B90EDEB6BC5AA6A9A254E8E976CEBA
Add a comment with the password for anyone else writing tests to use?
Drone Build Status: success
https://build.openprivacy.ca/openprivacy/connectivity/18
Drone Build Status: success
https://build.openprivacy.ca/openprivacy/connectivity/20