BIND 10 #2124: RFC 6594 for SSHFP

BIND 10 Development do-not-reply at isc.org
Mon Jul 16 10:34:07 UTC 2012


#2124: RFC 6594 for SSHFP
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  vorner                             |                Status:  new
                       Type:         |             Milestone:  Next-Sprint-
  defect                             |  Proposed
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:         |           Sub-Project:  DNS
  libdns++                           |  Estimated Difficulty:  0
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by vorner):

 What do you mean, by ignore? Reject, or accept?

 The (frustrating) problem I see is, because the code doesn't know the type
 exists, it rejects it. But if the check is just removed, everything works
 fine. I'm OK with allowing just the known ones, but once there's a new
 type, we'll need to extend the check again so the type accepts a valid key
 it is able to handle, just unwilling. I kind of don't see the advantage of
 having the check.

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


More information about the bind10-tickets mailing list