News for hackers. Stuff that matters.

A comment on Nginx Introduces Native Support for Acme Protocol. Parent comment

Re:Nginx Introduces Native Support for Acme Protocol by petee on Wednesday August 13, 2025 @04:22PM (#44893387)
dns-01 is just a challenge; which api or dns update system should nginx support then? Some API, AFXR, or UPDATE?

I think this is kinda the OPs point, nginx an http server, why should it be messing with dns? There are plenty of other acme clients to do this with ease

[ Parent | on HN ]
Re:Nginx Introduces Native Support for Acme Protocol by 0x457 on Thursday August 14, 2025 @01:05PM (#44902902)
I mean, you just repeated my explanation why supporting dns-01 in nginx isn't straightforward has http-01. I've explained why dns-01 challenge is still useful and might be required for some users.
[ Parent | on HN ]
Re:Nginx Introduces Native Support for Acme Protocol by petee on Thursday August 14, 2025 @01:33PM (#44903257)
I misread your first paragraph, and was more responding to the second that I took as supporting the adding the dns implementation in reply to the OP.

It may still be required by some users, but I don't think that it makes sense for nginx

[ Parent | on HN ]
Re:Nginx Introduces Native Support for Acme Protocol by 0x457 on Friday August 15, 2025 @11:57AM (#44913972)
> I took as supporting the adding the dns implementation

Well, I am supporting it, but I pointed why it's not as straightforward as supporting http-01.

> I don't think that it makes sense for nginx

It makes sense for nginx because ultimately I don't make certificates just for the fun of it, I do it to give it to some HTTP server. So it makes sense.

However, this isn't a future that will be not used by paid users, and F5 seems to be opposing making OSS version users lives better.

[ Parent | on HN ]