Skip to content

Commit 419567c

Browse files
committed
removed references to email contact in readme
1 parent 92b7725 commit 419567c

1 file changed

Lines changed: 3 additions & 6 deletions

File tree

README.md

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -44,11 +44,9 @@ pop open your browser's debugger to see the ajax requests that are going on. Ple
4444

4545
### Step 1: Account Info
4646

47-
First, the ACME protocol requires you register a public key and contact information
48-
so you can sign all the requests you make to the API. In this step, you need to
49-
put in an email and a public key. The javascript for this section then converts the
50-
public key to a JSON Web Key ([JWK](https://tools.ietf.org/html/rfc7517)). NOTE:
51-
currently only RSA 2048 and 4096 bit public keys are accepted by Let's Encrypt.
47+
First, the ACME protocol requires you register a public key so you can sign all the requests
48+
you make to the API. In this step, you need to put in a public key. The javascript for this
49+
section then converts the public key to a JSON Web Key ([JWK](https://tools.ietf.org/html/rfc7517)).
5250

5351
So if you paste it in this public key:
5452
```
@@ -98,7 +96,6 @@ you need to fulfill.
9896
Here's the list of requests that need to be made to the API:
9997

10098
* `/acme/new-acct` - Register the account public key and accept the terms (discarded if already registered)
101-
* `/acme/acct/...` - Update the account with your email address
10299
* `/acme/new-order` - Creates a new order for a certificate for your domains in your CSR
103100

104101
NOTE: Each request also requires an anti-replay nonce, so the javascript gets

0 commit comments

Comments
 (0)