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/
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?
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @leonklingele on GitHub (Jul 10, 2016).
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?
@germeier commented on GitHub (Jul 10, 2016):
https://community.letsencrypt.org/t/lets-encrypt-subscriber-agreement-v1-1-1/17409/7
@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.
@shoeper commented on GitHub (Jul 20, 2016):
https://community.letsencrypt.org/t/lets-encrypt-subscriber-agreement-v1-1-1/17409/7