Better license handling #190

New Issue

2025-12-29T00:26:55+01:00

adam commented

2025-12-29 00:26:55 +01:00

Originally created by @lukas2511 on GitHub (Jan 29, 2017).

Originally assigned to: @lukas2511 on GitHub.

Currently users are basically accepting the Let's Encrypt terms of service the moment they run dehydrated for the first time, this is a bit ugly and since it's missing any hint on that it may not even be fully legal...

To make this better dehydrated should query boulder for the required license url and ask the user to set this URL in config on first use.
This way everything can still be fully automated by just adding the LICENSE variable to the configuration file, but for normal use it will make the user aware of the terms of service.

This ticket replaces #249 and #248.

Originally created by @lukas2511 on GitHub (Jan 29, 2017). Originally assigned to: @lukas2511 on GitHub. Currently users are basically accepting the Let's Encrypt terms of service the moment they run dehydrated for the first time, this is a bit ugly and since it's missing any hint on that it may not even be fully legal... To make this better dehydrated should query boulder for the required license url and ask the user to set this URL in config on first use. This way everything can still be fully automated by just adding the LICENSE variable to the configuration file, but for normal use it will make the user aware of the terms of service. This ticket replaces #249 and #248.

adam added the enhancement label 2025-12-29 00:26:55 +01:00

adam closed this issue

2025-12-29 00:26:55 +01:00

adam commented

2025-12-29 01:18:38 +01:00

@lukas2511 commented on GitHub (Jan 29, 2017):

Implemented in 6a32f20e00

@lukas2511 commented on GitHub (Jan 29, 2017): Implemented in 6a32f20e004b9d835cd02de9d78300be02784cf1

adam commented

2025-12-29 01:18:38 +01:00

@ezbik commented on GitHub (Jan 30, 2017):

So basically when they set new license URL in some monthes, what are steps to update automated setups? Manually update $LICENSE in config ? Or nothing is required?

@ezbik commented on GitHub (Jan 30, 2017): So basically when they set new license URL in some monthes, what are steps to update automated setups? Manually update `$LICENSE` in `config` ? Or nothing is required?

adam commented

2025-12-29 01:18:38 +01:00

@lukas2511 commented on GitHub (Jan 30, 2017):

Until now License only seems to be verified on registration, not entirely sure if there is some kind of account-update for future license changes, I'll have to look into that, but otherwise nothing is required to be changed.

@lukas2511 commented on GitHub (Jan 30, 2017): Until now License only seems to be verified on registration, not entirely sure if there is some kind of account-update for future license changes, I'll have to look into that, but otherwise nothing is required to be changed.

adam commented

2025-12-29 01:18:39 +01:00

@cpu commented on GitHub (Nov 15, 2017):

Until now License only seems to be verified on registration, not entirely sure if there is some kind of account-update for future license changes

The agreement URL is only enforced at the time of registration/account creation. The wording of the terms-of-service is such that existing accounts are automatically agreed to future updates without needing to do any kind of account update for the new ToS if it changes.

@cpu commented on GitHub (Nov 15, 2017): > Until now License only seems to be verified on registration, not entirely sure if there is some kind of account-update for future license changes The agreement URL is only enforced at the time of registration/account creation. The wording of the terms-of-service is such that existing accounts are automatically agreed to future updates without needing to do any kind of account update for the new ToS if it changes.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/dehydrated#190