From d19510d319f79dc5cdcb03c08fb481315611985d Mon Sep 17 00:00:00 2001 From: Matt Drollette Date: Mon, 15 Dec 2014 00:15:38 -0600 Subject: [PATCH] fix docs --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 31f29d0..f5535e7 100644 --- a/README.md +++ b/README.md @@ -14,15 +14,15 @@ $ i2p-tools -h ... ``` -Otherwise, a binary for your OS can be download from http://matt.i2p/ +Otherwise, a binary for your OS can be downloaded from http://matt.i2p/ ## Usage If this is your first time running a reseed server (ie. you don't have any existing keys). You can simply run the following command and follow the prompts to create the appropriate keys and certificates. ``` -$ i2p-tools --signer=youremail@mail.i2p --tlsHost=your-server-name.tld --netdb=/var/lib/i2p/i2p-config/netDb +$ i2p-tools reseed --signer=you@mail.i2p --tlsHost=your-domain.tld --netdb=/var/lib/i2p/i2p-config/netDb ... ``` -This will start an HTTPS reseed server on the default port and generate 4 files in your current directory (a TLS key and certificate, and a signing key and certificate). Both of the certificates (*.crt) will need to be sent to the I2P developers in order for your reseed server to be included in the standard I2P package. +This will start an HTTPS reseed server on the default port and generate 4 files in your current directory (a TLS key and certificate, and a signing key and certificate). Both of the certificates (*.crt) will need to be sent to the I2P developers in order for your reseed server to be included in the standard I2P package.