mirror of
https://github.com/buger/goreplay.git
synced 2024-04-21 12:32:02 +00:00
Updated Distributed configuration (markdown)
@@ -15,7 +15,13 @@ gor --input-raw :80 --split-output --output-tcp replay1.local:28020 --output-tcp
|
||||
|
||||
### Encryption
|
||||
|
||||
Traffic between `--input-tcp` and `--output-tcp` can be encrypted using TLS protocol. To make it work you need to generate SSL certificate, specify paths to it and key used for generating cert, and enable secure mode. Certificate and key should be PEM encoded. Example: `--input-tcp :28020 --input-tcp-secure --input-tcp-certificate ./cert.pem --input-certificate ./key.pem`. You can use the following command to generate self-signed certificate and key `openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 365 -subj "/CN=localhost"` (do not forget to replace localhost by your domain or IP).
|
||||
Traffic between `--input-tcp` and `--output-tcp` can be encrypted using TLS protocol. To make it work you need to generate SSL certificate, specify paths to it and key used for generating cert, and enable secure mode.
|
||||
|
||||
Certificate and key should be PEM encoded. Example: `--input-tcp :28020 --input-tcp-secure --input-tcp-certificate ./cert.pem --input-certificate ./key.pem`. You can use the following command to generate a self-signed certificate and key:
|
||||
```
|
||||
openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 365 -subj "/CN=localhost"`
|
||||
```
|
||||
Do not forget to replace "localhost" by your domain or IP.
|
||||
|
||||
When you configured secure input, enable `--output-tcp-secure` flag for the GoReplay clients, connecting to it.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user