Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace LAN IP with loopback in gpg documentation #40

Merged
merged 1 commit into from
Jun 28, 2016
Merged

Replace LAN IP with loopback in gpg documentation #40

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down