You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -103,270 +102,9 @@ ACME is the protocol used by Let's Encrypt to automate the issuance of HTTPS cer
103
102
-[Install root certificates](https://smallstep.com/docs/step-cli/reference/certificate/install/) on your machine and browsers, so your CA is trusted
104
103
-[Inspect](https://smallstep.com/docs/step-cli/reference/certificate/inspect/) and [lint](https://smallstep.com/docs/step-cli/reference/certificate/lint/) certificates
105
104
106
-
## Installation Guide
105
+
## Installation
107
106
108
-
These instructions will install an OS specific version of the `step-ca` binary on
109
-
your local machine.
110
-
111
-
Want to build from source? See [our contributor's guide](./docs/CONTRIBUTING.md)
112
-
113
-
### Mac OS
114
-
115
-
Install `step` and `step-ca` together, via [Homebrew](https://brew.sh/):
116
-
117
-
```
118
-
$ brew install step
119
-
```
120
-
121
-
### Linux
122
-
123
-
> **Note:** The [`step` CLI tool](https://github.com/smallstep/cli) is the easiest way to initialize, configure, and control `step-ca`. While `step` is not technically required to run `step-ca`, it is very much recommended.
Your PKI is ready to go. To generate certificates for individual services see 'step help ca'.</code></pre>
272
-
273
-
This command will:
274
-
275
-
- Generate [password protected](https://github.com/smallstep/certificates/blob/master/docs/GETTING_STARTED.md#passwords) private keys for your CA to sign certificates
276
-
- Generate a root and [intermediate signing certificate](https://security.stackexchange.com/questions/128779/why-is-it-more-secure-to-use-intermediate-ca-certificates) for your CA
277
-
- Create a JSON configuration file for `step-ca` (see [configuration docs](https://smallstep.com/docs/step-ca/configuration) for details)
278
-
279
-
You can find these artifacts in `$STEPPATH` (or `~/.step` by default).
280
-
281
-
#### 2. Start `step-ca`:
282
-
283
-
You'll be prompted for your password from the previous step, to decrypt the CA's private signing key:
Serial Number: 140439335711218707689123407681832384336 (0x69a7a1d7f6f22f68059d2d9088307750)
329
-
Signature Algorithm: ECDSA-SHA256
330
-
Issuer: CN=Example Inc. Intermediate CA
331
-
Validity
332
-
Not Before: Feb 18 21:32:35 2019 UTC
333
-
Not After : Feb 19 21:32:35 2019 UTC
334
-
Subject: CN=localhost
335
-
...
336
-
Certificate:
337
-
Data:
338
-
Version: 3 (0x2)
339
-
Serial Number: 207035091234452090159026162349261226844 (0x9bc18217bd560cf07db23178ed90835c)
340
-
Signature Algorithm: ECDSA-SHA256
341
-
Issuer: CN=Example Inc. Root CA
342
-
Validity
343
-
Not Before: Feb 18 21:27:21 2019 UTC
344
-
Not After : Feb 15 21:27:21 2029 UTC
345
-
Subject: CN=Example Inc. Intermediate CA
346
-
...</code></pre>
347
-
348
-
Note that `step` and `step-ca` handle details like [certificate bundling](https://smallstep.com/blog/everything-pki.html#intermediates-chains-and-bundling) for you.
349
-
350
-
#### 5. Run the simple server.
351
-
352
-
<pre><code><b>$ go run srv.go &</b></code></pre>
353
-
354
-
#### 6. Get the root certificate from the Step CA.
355
-
356
-
In a new Terminal window:
357
-
358
-
<pre><code><b>$ step ca root root.crt</b>
359
-
The root certificate has been saved in root.crt.</code></pre>
360
-
361
-
#### 7. Make an authenticated, encrypted curl request to your server using HTTP over TLS.
0 commit comments