On Thu, Jun 05, 2025 at 02:29:36PM -0600, Jeremy Rowley wrote: > Hi Amir - I'm one of the people who mentioned ACME on the call. I've been > doing a lot of ACME related setups lately. It works wonderfully for server > devices but non-servers (like firewalls) are a pain. They require my team > to write scripts into the API to get the system working correctly. I don't > think this is an IETF problem but a device manufacturer problem where we > need to encourage better ACME adoption for non-traditional servers.
Yeah, that's not an ACME problem, that's a market problem. Mentioning the protocol as being involved at all, when the problem is some proprietary device and its lack of feature development, is bordering on disingenuous -- although it does have a long and storied history in the "stymying progress" movement (just look at IPv6 and the "my routers don't support it!" dance). - Matt -- You received this message because you are subscribed to the Google Groups "dev-security-policy@mozilla.org" group. To unsubscribe from this group and stop receiving emails from it, send an email to dev-security-policy+unsubscr...@mozilla.org. To view this discussion visit https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/9e2aad8a-7659-4a05-a722-fd2ddf1cac44%40mtasv.net.
