Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

security/acme-client: Add support for Google Domains DNS API #3408

Closed
3 tasks
nmiller0113 opened this issue Apr 23, 2023 · 19 comments
Closed
3 tasks

security/acme-client: Add support for Google Domains DNS API #3408

nmiller0113 opened this issue Apr 23, 2023 · 19 comments
Assignees
Labels
feature Adding new functionality

Comments

@nmiller0113
Copy link

nmiller0113 commented Apr 23, 2023

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.
(e.g. I would like an input field in the /ui/firewall/alias which would add .... to ....)

Please add the exisiting deployment option from acme.sh that supports the Google Domains using their API
https://github.com/acmesh-official/acme.sh/wiki/dnsapi2#157-use-google-domains-dns-api

To Reproduce
Steps to reproduce the behavior:

Go to 'Challenge Types'
Click on 'add'
Scroll down to 'search Google Domains in the list of dns services'
See error ---> it is missing

@fraenki
Copy link
Member

fraenki commented Apr 24, 2023

Although the upstream PR acmesh-official/acme.sh#4542 was merged, there is no official release of acme.sh available that provides support for this new DNS API. We'll have to wait until a new release of acme.sh is available.

@fraenki fraenki added the feature Adding new functionality label Apr 24, 2023
@fraenki fraenki self-assigned this Apr 24, 2023
@nmiller0113
Copy link
Author

@fraenki, thanks for the quick reply. Am I mistaken in what I’m seeing here?

https://github.com/acmesh-official/acme.sh/tree/master/dnsapi

I see dns_googledomains.sh in there, so that’s why I was curious.

I actually read of someone using it in another forum first, so I thought I’d ask here as well since I use both. Here’s that link:

https://forum.proxmox.com/threads/please-add-support-for-google-domains-dns-api.124434/#post-551143

Thanks again!

@fraenki
Copy link
Member

fraenki commented Apr 25, 2023

I see dns_googledomains.sh in there, so that’s why I was curious.

It was merged to the code repository, yes. But there is no official release with support for Google Domains just yet. We only use official releases. Once there is a new release of acme.sh I will add support for Google Domains.

@nmiller0113
Copy link
Author

Ahhh, I see what you mean @fraenki! My apologies for the misunderstanding!

@fraenki fraenki changed the title security/acme client: Added support for Google Domains DNS API security/acme-client: Add support for Google Domains DNS API May 8, 2023
@nmiller0113
Copy link
Author

nmiller0113 commented Jun 14, 2023

Although the upstream PR acmesh-official/acme.sh#4542 was merged, there is no official release of acme.sh available that provides support for this new DNS API. We'll have to wait until a new release of acme.sh is available.

@fraenki I believe that the new official release contains the support. Thank you!

https://github.com/acmesh-official/acme.sh/releases/tag/3.0.6

https://github.com/acmesh-official/acme.sh/commits/3.0.6

@fichtner
Copy link
Member

Yep, required file was added... opnsense/ports@f5632185f54d3

@nmiller0113
Copy link
Author

Yep, required file was added... opnsense/ports@f5632185f54d3

Thanks for sharing this @fichtner. Forgive my ignorance on this, but do you know the next steps on where this has to go before it is released as an opnsense update?

@fichtner
Copy link
Member

While acme.sh itself will be 3.0.6 in 23.1.10 I’m unsure about the plugin state. If it’s not selectable now it still needs to be added to the plugin. I don’t see any pending changes in the development version, not sure about open PR here.

@nmiller0113
Copy link
Author

nmiller0113 commented Jun 14, 2023

While acme.sh itself will be 3.0.6 in 23.1.10 I’m unsure about the plugin state. If it’s not selectable now it still needs to be added to the plugin. I don’t see any pending changes in the development version, not sure about open PR here.

Thanks @fichtner. Perhaps @fraenki knows? I'm on 23.1.9 currently and do not see an option for 23.1.10. I'm assuming it's a development/beta version.

@fichtner
Copy link
Member

There is no beta/development code in our repository. Mentioned it before.

@nmiller0113
Copy link
Author

There is no beta/development code in our repository. Mentioned it before.

@fichtner, I was referring to updating my opnsense version to 23.1.10, not to the plugin beta/development. I did follow what you were mentioning. Thanks!

@fichtner
Copy link
Member

Let me clarify: unless something is actively added to the plugin for 23.1.10 you won't be able use the new dns_googledomains addition from acme.sh package itself.

@fichtner fichtner linked a pull request Jun 15, 2023 that will close this issue
@fichtner
Copy link
Member

It looks like #3429 might do the trick?

If you are on 23.1.9 with the acme.sh hotfix installed (check for version 3.0.6) you can try and test:

# opnsense-patch -c plugins e10a96037fa5

But there is a comment here that the PR is not complete: #3429 (comment)

Cheers,
Franco

@nmiller0113
Copy link
Author

Let me clarify: unless something is actively added to the plugin for 23.1.10 you won't be able use the new dns_googledomains addition from acme.sh package itself.

I understood @fichtner, thank you very much!

@nmiller0113
Copy link
Author

It looks like #3429 might do the trick?

If you are on 23.1.9 with the acme.sh hotfix installed (check for version 3.0.6) you can try and test:

# opnsense-patch -c plugins e10a96037fa5

But there is a comment here that the PR is not complete: #3429 (comment)

Cheers, Franco

@fichtner, is the opnsense-patch command you shared the way to install the hotfix mentioned? Sorry, have not done a hotfix in opnsense yet. Thanks again!

@fichtner
Copy link
Member

@nmiller0113 yep, opnsense-patch is a builtin. Run it from a root console on the OPNsense. It fetches the patch from GitHub and tries to install it so you don't have to :)

@fraenki
Copy link
Member

fraenki commented Jul 11, 2023

PR #3499 was merged, so this should be available in one of the next OPNsense releases.

@fraenki fraenki closed this as completed Jul 11, 2023
@nmiller0113
Copy link
Author

PR #3499 was merged, so this should be available in one of the next OPNsense releases.

Thank you @fraenki, I'm very much looking forward to the next OPNsense release!

@slackadelic
Copy link
Member

Well glad to see this being added. Hopefully a full patch will go out at some point before the next release so we can fully utilize this!

@opnsense opnsense locked as resolved and limited conversation to collaborators Jul 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature Adding new functionality
Development

Successfully merging a pull request may close this issue.

4 participants