From 7548839ba6a98319f13f5f8b5434c0a5a189f53a Mon Sep 17 00:00:00 2001 From: mayurbhandary Date: Fri, 1 Nov 2019 17:58:27 -0400 Subject: [PATCH 1/2] Domain Verification and IP addresses The verified domain name should not resolve to the ip address of the validator. --- .../configuration/run-rippled-as-a-validator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-validator.md b/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-validator.md index d57bf38afd..973683f19a 100644 --- a/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-validator.md +++ b/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-validator.md @@ -282,7 +282,7 @@ Creating this link establishes strong evidence that you own both the validator k To provide domain verification: -1. Choose a domain name you own that you want to be publicly associated with your validator. You must run a public-facing HTTPS server on port 443 of that domain and you must have access to the private key file associated with that server's TLS certificate. (Note: [TLS was formerly called SSL](https://en.wikipedia.org/wiki/Transport_Layer_Security).) +1. Choose a domain name you own that you want to be publicly associated with your validator. You must run a public-facing HTTPS server on port 443 of that domain and you must have access to the private key file associated with that server's TLS certificate. (Note: [TLS was formerly called SSL](https://en.wikipedia.org/wiki/Transport_Layer_Security)). As a precaution against DDoS attempts, your domain name should not resolve to the ip address of your validator. 2. Share your validator's public key with the public, especially other `rippled` operators. For example, you can share your validator's public key on your website, on social media, in the [XRPChat community forum](https://www.xrpchat.com/), or in a press release. From d008b529e8cfe1db520fb0fa8d4b4214333e3e02 Mon Sep 17 00:00:00 2001 From: Rome Reginelli Date: Fri, 1 Nov 2019 15:17:01 -0700 Subject: [PATCH 2/2] Nit: period goes with the sentence in parentheses --- .../configuration/run-rippled-as-a-validator.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-validator.md b/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-validator.md index 973683f19a..4456dddfc6 100644 --- a/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-validator.md +++ b/content/tutorials/manage-the-rippled-server/configuration/run-rippled-as-a-validator.md @@ -282,7 +282,7 @@ Creating this link establishes strong evidence that you own both the validator k To provide domain verification: -1. Choose a domain name you own that you want to be publicly associated with your validator. You must run a public-facing HTTPS server on port 443 of that domain and you must have access to the private key file associated with that server's TLS certificate. (Note: [TLS was formerly called SSL](https://en.wikipedia.org/wiki/Transport_Layer_Security)). As a precaution against DDoS attempts, your domain name should not resolve to the ip address of your validator. +1. Choose a domain name you own that you want to be publicly associated with your validator. You must run a public-facing HTTPS server on port 443 of that domain and you must have access to the private key file associated with that server's TLS certificate. (Note: [TLS was formerly called SSL](https://en.wikipedia.org/wiki/Transport_Layer_Security).) As a precaution against DDoS attempts, your domain name should not resolve to the ip address of your validator. 2. Share your validator's public key with the public, especially other `rippled` operators. For example, you can share your validator's public key on your website, on social media, in the [XRPChat community forum](https://www.xrpchat.com/), or in a press release.