BIND 10 #2745: format of TSIG keys looks like a data format encoded inside a string
BIND 10 Development
do-not-reply at isc.org
Thu Feb 14 22:05:09 UTC 2013
#2745: format of TSIG keys looks like a data format encoded inside a string
-------------------------------------+-------------------------------------
Reporter: cas | Type:
Status: new | defect
Milestone: New Tasks | Priority:
Keywords: | medium
Sensitive: 0 | Component:
Sub-Project: Core | Unclassified
Estimated Difficulty: 0 | CVSS Scoring:
Total Hours: 0 | Defect Severity: N/A
| Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
The TSIG string format "name:base64secret:algorithm" is a data-format
encoded inside a configuration string.
It would be more "clean" to have the fields mapped into a JSON map:
{{{
> config set tsig_keys/keys/example.com { "secret": "c2VjcmV0",
"algorithm": "hmac-md5" }
}}}
instead of
{{{
> config add tsig_keys/keys "example.com.:c2VjcmV0:hmac-md5"
}}}
--
Ticket URL: <http://bind10.isc.org/ticket/2745>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list