Bug #15490
closed
Sanitize RFC 2136 Dynamic DNS update keys in ``status.php`` output
Added by Lev Prokofev 6 months ago.
Updated 10 days ago.
Plus Target Version:
24.11
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.
- 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
)
I can confirm this behavior on 24.03.
- Plus Target Version changed from 24.07 to 24.08
- Status changed from New to Feedback
- % Done changed from 0 to 100
- Plus Target Version changed from 24.08 to 24.11
- Status changed from Feedback to Resolved
Status output config.xml
has the key data redacted on current builds:
<keydata>xxxxx</keydata>
Also available in: Atom
PDF