From 9bd35b68129ac676c4aaef58d398f0863cb477b7 Mon Sep 17 00:00:00 2001 From: Ben Cox Date: Tue, 28 Jun 2016 06:39:44 +0100 Subject: [PATCH] Replace LAN IP with loopback in gpg documentation (#40) --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index ad23e55..46ff558 100644 --- a/README.md +++ b/README.md @@ -87,12 +87,12 @@ The Releases file for a repository will not be signed until a signing key is giv signing you need to set the signing key (it cannot have a passphrase on it at this time): ``` -$ gpg --armor --export-secret-key | curl -XPUT --data-binary @- http://192.168.0.7:3000/dists/master/config/signingkey +$ gpg --armor --export-secret-key | curl -XPUT --data-binary @- http://localhost:3000/dists/master/config/signingkey ``` By default, changes fiels to be uploaded much be signed, to add keys to verify changes files against: ``` -$ gpg --armor --export--key | curl -XPOST --data-binary @- http://192.168.0.7:3000/dists/master/config/publickeys +$ gpg --armor --export--key | curl -XPOST --data-binary @- http://localhost:3000/dists/master/config/publickeys ``` Public Keys are managed via the API