... | @@ -36,7 +36,7 @@ Kea uses the DHCPv4 and DHCPv6 protocols, which assume the server will open priv |
... | @@ -36,7 +36,7 @@ Kea uses the DHCPv4 and DHCPv6 protocols, which assume the server will open priv |
|
|
|
|
|
Kea can optionally use an external MySQL, PostgreSQL or Cassandra database to store configuration, host reservations or leases. The use of databases is a popular feature, but it is optional. It's also possible to store this data in a flat file on disk.
|
|
Kea can optionally use an external MySQL, PostgreSQL or Cassandra database to store configuration, host reservations or leases. The use of databases is a popular feature, but it is optional. It's also possible to store this data in a flat file on disk.
|
|
|
|
|
|
When using a database, Kea will store and use credentials in the form of username, password, host, port and database name in order to authenticate with the database. **These are stored (how? in clear text in the config file? or where?)**
|
|
When using a database, Kea will store and use credentials in the form of username, password, host, port and database name in order to authenticate with the database. **These are stored (how? in clear text in the config file? or where?)** yes, clear text in the config file
|
|
|
|
|
|
Depending on the database configuration, it's also possible to check if the system user matches the database username. Consult MySQL or PostgreSQL manuals for details.
|
|
Depending on the database configuration, it's also possible to check if the system user matches the database username. Consult MySQL or PostgreSQL manuals for details.
|
|
|
|
|
... | | ... | |