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.

Sign up for GitHub

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

Clarify target of securing DHCP API #2709

Closed
wants to merge 1 commit into from
Closed

Clarify target of securing DHCP API #2709

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions guides/common/modules/proc_securing-the-dhcp-api.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't true. It's the Smart Proxy process that communicates with the DHCP daemon. IMHO is SmartProxyServer the whole server.

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:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can also be done on your ProjectServer if you run DHCP there.

+
[options="nowrap", subs="+quotes,verbatim,attributes"]
----
Expand Down
Loading