From 1c4202331b2fd0ffcd9bafa264bdd2c160a1fa37 Mon Sep 17 00:00:00 2001 From: Maximilian Kolb Date: Tue, 30 Jan 2024 09:29:11 +0100 Subject: [PATCH] Clarify target of securing DHCP API This procedure is only part of one assembly: "assembly_managing-dhcp-on-smart-proxies.adoc", which itself is only part of "doc-Installing_Proxy". --- guides/common/modules/proc_securing-the-dhcp-api.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/guides/common/modules/proc_securing-the-dhcp-api.adoc b/guides/common/modules/proc_securing-the-dhcp-api.adoc index bdf0a6a443f..6e3313189f6 100644 --- a/guides/common/modules/proc_securing-the-dhcp-api.adoc +++ b/guides/common/modules/proc_securing-the-dhcp-api.adoc @@ -1,12 +1,12 @@ [id="Securing_the_dhcpd_API_{context}"] = Securing the dhcpd API -{SmartProxy} interacts with DHCP daemon using the dhcpd API to manage DHCP. +{SmartProxyServer} interacts with DHCP daemon using the dhcpd API to manage DHCP. By default, the dhcpd API listens to any host without access control. You can add an `omapi_key` to provide basic security. .Procedure -. On your {SmartProxy}, install the required packages: +. On your {SmartProxyServer}, install the required packages: + [options="nowrap", subs="+quotes,verbatim,attributes"] ----