Actions
Bug #15490
closed
Sanitize RFC 2136 Dynamic DNS update keys in ``status.php`` output
Start date:
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
24.11
Release Notes:
Default
Affected Version:
Affected Architecture:
Description
The keys inside the <dnsupdates> should be sanitized because restoring the client's config for test purposes can cause a lot of issues if the test system has internet access.
For example, after the DYDNS update the remote VPN clients will be not able to connect before the DNS receives a fresh update.
Updated by Jim Pingle 6 months ago
- Subject changed from rfc2136 keys are not sanitezed in Status output to Sanitize RFC 2136 Dynamic DNS update keys in ``status.php`` output
- Category changed from Logging to Diagnostics
- Assignee set to Jim Pingle
- Target version set to 2.8.0
- Plus Target Version set to 24.07
Specifically the tag is <keydata> that should be sanitized. (dnsupdates/dnsupdate/<idx>/keydata)
Updated by
Updated by Jim Pingle 6 months ago
- Plus Target Version changed from 24.07 to 24.08
Updated by Jim Pingle about 2 months ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 2d9db4c6bfe1e437eb8f074dae79817728533761.
Updated by Jim Pingle about 1 month ago
- Plus Target Version changed from 24.08 to 24.11
Updated by Jim Pingle 10 days ago
- Status changed from Feedback to Resolved
Status output config.xml has the key data redacted on current builds:
<keydata>xxxxx</keydata>
Actions