BIND 10 #2745: format of TSIG keys looks like a data format encoded inside a string

[BIND 10 Development]

#2745: format of TSIG keys looks like a data format encoded inside a string
-------------------------------------+-------------------------------------
            Reporter:  cas           |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  medium        |                    Milestone:  New
           Component:  Unclassified  |  Tasks
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  Core          |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by cas):

 Replying to [comment:1 vorner]:
 > Isn't this some format usually used when exchanging the keys with other
 software?

 not to my knowledge. BIND 9 "nsupdate" uses "[hmac:]keyname:secret]" when
 specifying a TSIG key on the commandline, but that is a workaround to
 prevent extra option switches for the three parts of a TSIG key, which is
 understandable for a commandline utility.

 BIND 10 has structured data types, they should be used instead of building
 yet another data structure inside a string that needs to be parsed with
 it's own (simple, but extra) parser.

-- 
Ticket URL: <https://bind10.isc.org/ticket/2745#comment:2>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development