BIND 10 #781: Define cryptographic API

[BIND 10 Development]

#781: Define cryptographic API
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jelte
  stephen                            |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20110503
  blocker                            |            Resolution:
                  Component:         |             Sensitive:  0
  Unclassified                       |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  6.0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 FYI (don't worry, this is not my usual one more additional comment:-)

 I've started making #812 reviewable, assuming the important part of this
 branch is now fixed.  My first step was to merge #781 and a new branch
 based on a recent master, and it required some straightforward but
 a non negligible amount of work due to the recent re-organization with
 the introduction of libutil.  So I first fixed the conflicts and made
 necessary fixups.  They are available in

 commit 00e36b253bd643b007f89a8ccb3addac1a723eba
 commit 65874313065ddb02756d5ef06c8802c7540c17c7

 You may be able to save your time when you merge the branch into
 master by simply merging these fixes, too.  (but you may find it
 rather simpler to do it yourself - they are basically boring, trivial
 fixes)

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