Skip to content

Conversation

@mikel-fernandez
Copy link

@mikel-fernandez mikel-fernandez commented Sep 27, 2017

Doc: https://www.haproxy.org/download/1.8/doc/proxy-protocol.txt

The proxy support not only enables miners behind a proxy-v1 to mine in the pool, it also enables the use of a local proxy; for example, to provide a TLS.

The TLS layer can be provided for example by hitch, by setting a local proxy:
$ hitch --daemon --backend=[127.0.0.1]:5555 --frontend=[*]:5566 pool.pem --write-proxy-v1

If the --write-proxy-v1 parameter is not used, the pool service will assume the miner is located in 127.0.0.1, which will break the ip-based ban system and will open the system to atacks.

If the --write-proxy-v1 parameter was used, the miner failed to connect to the pool because the pool was incapable of parsing the proxy header.

This commit enables the the pool to parse the proxy v1 header and thus to use hitch or a similar process to provide a TLS layer to the pool.

This code has been tested and is being used in https://www.moneropool.us

mikel-fernandez and others added 4 commits September 27, 2017 08:10
…n another currency (for instance, dollar).

To enable, set the cryptonatorEarnings in config.js as in the following example:

var cryptonatorWidget = ["XMR-BTC", "XMR-USD", "XMR-EUR"];
var cryptonatorEarnings = "XMR-USD" /* Must be included in the Widget */

If left unconfigured, the web interface does not show the conversion
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants