BIND 10 #2124: RFC 6594 for SSHFP

[BIND 10 Development]

#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):

 Well, that is kind of the same here. The SSHFP looks like:
 {{{
 <Key type> <Fingerprint type> <Hex data>
 }}}

 We don't do any checking of the hex data, as it can be mostly anything and
 it would be correct (I think). We check the key type and fingerprint type
 (both are represented as number in the input) are in range of known types.
 That's it. So if it is unknown, we can either reject or accept it, but
 there are no more check we would do.

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