🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/dehydrated-io/dehydrated/pull/75
**Author:** [@germeier](https://github.com/germeier)
**Created:** 1/8/2016
**Status:** ❌ Closed
**Base:** `master` ← **Head:** `master`
---
### 📝 Commits (1)
- [`b6611a7`](https://github.com/dehydrated-io/dehydrated/commit/b6611a7d05c0171db01a5dd904fb0da052d753b8) add support for dns-01 challenge
### 📊 Changes
**4 files changed** (+97 additions, -9 deletions)
<details>
<summary>View changed files</summary>
📝 `README.md` (+2 -0)
📝 `config.sh.example` (+3 -0)
➕ `hook-dns-01.sh.example` (+41 -0)
📝 `letsencrypt.sh` (+51 -9)
</details>
### 📄 Description
This adds support for the new dns-01 challenge!
ATTENTION: This challenge is currently only available in staging, see: https://community.letsencrypt.org/t/dns-challenge-is-in-staging/8322
I added a example script on how to deploy a DNS challenge using nsupdate. This should be easy to port to other APIs/services.
I am uncertain if "urlbase64" is the correct way in this case or if this should be a "base64 -w0".
See also: https://tools.ietf.org/html/draft-ietf-acme-acme-01#section-7.5
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
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.
📋 Pull Request Information
Original PR: https://github.com/dehydrated-io/dehydrated/pull/75
Author: @germeier
Created: 1/8/2016
Status: ❌ Closed
Base:
master← Head:master📝 Commits (1)
b6611a7add support for dns-01 challenge📊 Changes
4 files changed (+97 additions, -9 deletions)
View changed files
📝
README.md(+2 -0)📝
config.sh.example(+3 -0)➕
hook-dns-01.sh.example(+41 -0)📝
letsencrypt.sh(+51 -9)📄 Description
This adds support for the new dns-01 challenge!
ATTENTION: This challenge is currently only available in staging, see: https://community.letsencrypt.org/t/dns-challenge-is-in-staging/8322
I added a example script on how to deploy a DNS challenge using nsupdate. This should be easy to port to other APIs/services.
I am uncertain if "urlbase64" is the correct way in this case or if this should be a "base64 -w0".
See also: https://tools.ietf.org/html/draft-ietf-acme-acme-01#section-7.5
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.