The watchtower-plugin was specifying a custom tor flag to signal whether Tor may be used by the client. This was due to cln-plugin (v0.1.1-) not allowing plugins to access the CoreLN configuration options and, therefore, our plugin was unable to fetch the proxy / always-use-proxy options.
This fetches the aforementioned options and revamps the logic to comply with the always-use-proxy requirements, that is, if the flag is set all communications must be performed using Tor. Also, it replaces some of the currently used Strings for more meaningful types to store network data (such as AddressType, NetAddress, or ProxyInfo).
This drops our custom watchtower-proxy config option
sr-gi
commented
1 year ago
Changes
The
watchtower-pluginwas specifying a custom tor flag to signal whether Tor may be used by the client. This was due tocln-plugin (v0.1.1-)not allowing plugins to access the CoreLN configuration options and, therefore, our plugin was unable to fetch theproxy/always-use-proxyoptions.This fetches the aforementioned options and revamps the logic to comply with the
always-use-proxyrequirements, that is, if the flag is set all communications must be performed using Tor. Also, it replaces some of the currently usedStrings for more meaningful types to store network data (such asAddressType,NetAddress, orProxyInfo).This drops our custom
watchtower-proxyconfig option