challenge tokens are created in wrong directory for freeBSD #182

New Issue

adam · 2025-12-29T00:26:44+01:00

adam commented

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

Originally created by @tekbasse on GitHub (Jan 5, 2017).

challenge tokens are created in WELLKNOWN dir instead of WELLKNOWN/.well-known/acme-challenge/

for bash under freeBSD 10.3 See #334

After commenting out line 545:
[[ "${CHALLENGETYPE}" = "http-01" ]] && rm -f "${WELLKNOWN}/${challenge_token}"

The files are found in WELLKNOWN dir.

Originally created by @tekbasse on GitHub (Jan 5, 2017). challenge tokens are created in WELLKNOWN dir instead of WELLKNOWN/.well-known/acme-challenge/ for bash under freeBSD 10.3 See #334 After commenting out line 545: ` [[ "${CHALLENGETYPE}" = "http-01" ]] && rm -f "${WELLKNOWN}/${challenge_token}"` The files are found in WELLKNOWN dir.

adam closed this issue

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

adam commented

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

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

This is not a bug, this is a feature: https://github.com/lukas2511/dehydrated/blob/master/docs/wellknown.md

@lukas2511 commented on GitHub (Jan 5, 2017): This is not a bug, this is a feature: https://github.com/lukas2511/dehydrated/blob/master/docs/wellknown.md

adam commented

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

@tekbasse commented on GitHub (Jan 5, 2017):

I call it a documentation bug. Poorly explained.

@tekbasse commented on GitHub (Jan 5, 2017): I call it a documentation bug. Poorly explained.

adam commented

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

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

In that document I state multiple times how files are stored, and there even is example configuration for probably every popular webserver, I'm really not sure what else I can do.

If you have a suggestion on how to make the documentation better feel free to send in a pull-request.

@lukas2511 commented on GitHub (Jan 5, 2017): In that document I state multiple times how files are stored, and there even is example configuration for probably every popular webserver, I'm really not sure what else I can do. If you have a suggestion on how to make the documentation better feel free to send in a pull-request.

adam commented

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

@tekbasse commented on GitHub (Jan 5, 2017):

Okay. Will do.

@tekbasse commented on GitHub (Jan 5, 2017): Okay. Will do.

adam commented

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

@tekbasse commented on GitHub (Jan 5, 2017):

The acme standard requires the file to be served from /.well-known/acme-challenge/

The path at which the resource is provisioned is comprised of the fixed prefix
".well-known/acme-challenge/", followed by the "token" value in the challenge.
The value of the resource MUST be the ASCII representation of the key
authorization.

.well-known/acme-challenge/evaGxfADs6pSRb2LAv9IZf17Dt3juxGJ-PCt92wr-oA

from: https://github.com/ietf-wg-acme/acme/blob/master/draft-ietf-acme-acme.md

So, WELLKNOWN needs to include this fixed value at the end.

The pull request will reflect this description.

cheers, Ben

@tekbasse commented on GitHub (Jan 5, 2017): The acme standard requires the file to be served from /.well-known/acme-challenge/ > The path at which the resource is provisioned is comprised of the fixed prefix ".well-known/acme-challenge/", followed by the "token" value in the challenge. The value of the resource MUST be the ASCII representation of the key authorization. `.well-known/acme-challenge/evaGxfADs6pSRb2LAv9IZf17Dt3juxGJ-PCt92wr-oA` from: [https://github.com/ietf-wg-acme/acme/blob/master/draft-ietf-acme-acme.md](url) So, WELLKNOWN needs to include this fixed value at the end. The pull request will reflect this description. cheers, Ben

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/dehydrated#182