Update license agreement (due at August 1st) #128

New Issue

adam · 2025-12-29T00:25:30+01:00

adam commented

2025-12-29 00:25:30 +01:00

Originally created by @leonklingele on GitHub (Jul 10, 2016).

Let's Encrypt Subscriber,
We're writing to let you know that we're 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 "Let's Encrypt Subscriber Agreement" section of the
following page: https://letsencrypt.org/repository/

Old: https://letsencrypt.org/documents/LE-SA-v1.0.1-July-27-2015.pdf
New: https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf

What happens if one does not update letsencrypt.sh to post the new LA? Does the signing process fail?

Originally created by @leonklingele on GitHub (Jul 10, 2016). ``` Let's Encrypt Subscriber, We're writing to let you know that we're 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 "Let's Encrypt Subscriber Agreement" section of the following page: https://letsencrypt.org/repository/ ``` Old: https://letsencrypt.org/documents/LE-SA-v1.0.1-July-27-2015.pdf New: https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf What happens if one does not update letsencrypt.sh to post the new LA? Does the signing process fail?

adam closed this issue

2025-12-29 00:25:30 +01:00

adam commented

2025-12-29 00:25:30 +01:00

@germeier commented on GitHub (Jul 10, 2016):

https://community.letsencrypt.org/t/lets-encrypt-subscriber-agreement-v1-1-1/17409/7

@germeier commented on GitHub (Jul 10, 2016): https://community.letsencrypt.org/t/lets-encrypt-subscriber-agreement-v1-1-1/17409/7

adam commented

2025-12-29 00:25:30 +01:00

@lukas2511 commented on GitHub (Jul 20, 2016):

Interesting thing is that I can't yet push an update with the new agreement as boulder doesn't accept a registration with that url... Also this will lead to another wave of stupid issues "letsencrypt.sh is not working" "did you try updating?" "oh now it works"... meh.

@lukas2511 commented on GitHub (Jul 20, 2016): Interesting thing is that I can't yet push an update with the new agreement as boulder doesn't accept a registration with that url... Also this will lead to another wave of stupid issues "letsencrypt.sh is not working" "did you try updating?" "oh now it works"... meh.

adam commented

2025-12-29 00:25:31 +01:00

@shoeper commented on GitHub (Jul 20, 2016):

https://community.letsencrypt.org/t/lets-encrypt-subscriber-agreement-v1-1-1/17409/7

@shoeper commented on GitHub (Jul 20, 2016): https://community.letsencrypt.org/t/lets-encrypt-subscriber-agreement-v1-1-1/17409/7

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/dehydrated#128