I’d like to post a draft of the Let’s Encrypt Subscriber Agreement v1.1.1 here for community review before it gets schedule to take effect, ideally in late July 2016 (tentatively July 28). I’m doing this because we had previously posted a draft of v1.1 and then pulled it before it took effect becau…

Hi @josh , did you see the last message of Kathleen Wilson in https://bugzilla.mozilla.org/show_bug.cgi?id=1204656 ? More people commented in the discussion, so I think the discussion is not yet ready to be closed. The CA needs to drive the Q&A in the discussion to closure, by responding to the qu…

in paras 3.5, 3.6, 3.7, 3.8, 3.9 You warrant to ISRG and the public-at-large, and You agree, that You will ... In earlier paras it is " You warrant to ISRG and the public-at-large that" you have (in the past) and " You agree that" you will (in the future) ... which does make sense. However, in…

Thanks for the feedback. We’ve considered it and decided to move forward with v1.1.1 with no further changes. Both comments refer to potentially minor wording changes and we’d prefer to keep the current wording.

Will accounts who have accepted the existing TOS need to re-auth to this TOS… or will they automatically consent through continued use? I ask this because automated systems are involved.

@jvanasco : Existing accounts will automatically consent through continued use, so automated systems won’t have an interruption in service.

wonderful! it would be good to include whether or not that will happen on announcements like this.

Our automated system got bit by this today (it generates new keypairs frequently instead of reusing registrations long-term, which was the workaround we were suggested to use to avoid “bad replay nonce” errors). Is there some feed we should have been monitoring that would have told us ahead of time…

There was an e-mail sent on July 9th announcing the update: Let's Encrypt Subscriber, We're writing to let you know that we are updating the Let's Encrypt Subscriber Agreement, effective August 1, 2016. You can find the updated agreement (v1.1.1) as well as the current agreement (v1.0.1) in the…

@glasser @Majkl I’m sorry to hear that this caused you problems. The ACME protocol (as discussed in the thread @schoen linked to) provides enough information during the registration flow that you do not need to hardcode the ToS string. Compliant clients will not encounter outages from a ToS change i…

Let's Encrypt Subscriber Agreement v1.1.1

Issuance Policy

schoen August 2, 2016, 1:44am 11

There is some discussion of this question at How to get URL to subscriber agreement before registering (maybe that will be helpful to you).

Topic		Replies	Views
Email feedback: "Let’s Encrypt Subscriber Agreement Update" ISRG/Organizational	28	3051	August 7, 2022
More graceful handling of Subscriber Agreement changes Feature Requests	2	1626	January 8, 2018
Terms of service agreement Client dev	15	5335	December 2, 2015
Agreeing to subscriber agreement Issuance Tech	11	9186	December 27, 2016
Subsriber mailing list issues Site Feedback	4	2354	July 20, 2016

Let's Encrypt Subscriber Agreement v1.1.1

Related topics