BIND 10 #1148: Make XfrOut use global TSIG keyring

[BIND 10 Development]

#1148: Make XfrOut use global TSIG keyring
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  vorner                             |                Status:  new
                       Type:         |             Milestone:
  defect                             |  Sprint-20120515
                   Priority:  low    |            Resolution:
                  Component:         |             Sensitive:  0
  xfrout                             |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  4
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:11 jaspain]:
 > Referring to my message
 https://lists.isc.org/pipermail/bind10-users/2012-May/000322.html, there
 was clearly some confusion on my part, and I don't think this reflects
 either a failure to solve the problem addressed by this ticket or a new
 problem.

 [...]

 > It is the `config set Xfrout/tsig_key_ring` command that is causing the
 error I reported previously. Clearly that is because the
 `Xfrout/tsig_key_ring` no longer exists. The global keyring is being used
 instead. I can confirm that TSIG-secured communications are working
 normally on this server. That is what this ticket was supposed to
 accomplish, and I believe it has done so successfully. Sorry for my
 earlier misinterpretation of the issue. Jeff.

 Okay, thanks for the confirmation.

 I also checked the code and confirmed it indeed uses the global
 keyring.

 I'm now going to closing this ticket.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1148#comment:12>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development