1. 16 May, 2014 1 commit
    • Thomas Markwalder's avatar
      [3432] Fixed d2::TSIGKeyInfo::remake to use correct dns::TSIGKey constructor · 5819b262
      Thomas Markwalder authored
      The dns::TSIGKey constructor that was being by d2:TSIGKeyINfo expects an
      ordinary string value for secret and then encodes it to base64. Since
      TSIGKeyInfo configuration value for secret is already expected to be base64
      encoded this was causing it to be encoded again resulting in verification
      errors when tested against Bind9.
      Changed TSIGKeyInfo::remake to use the appropriate TSIGKey constructor.
  2. 15 May, 2014 2 commits
  3. 14 May, 2014 2 commits
    • Thomas Markwalder's avatar
      [3432] TSIGKeyInfo now creates and owns a dns::TSIGKey · 3784b469
      Thomas Markwalder authored
      d2::TSIGKeyInfo now has an instance member for a dns::TSIGKey
      instance, which is created during the TSIGKeyInfo's construction.
    • Thomas Markwalder's avatar
      [3432] Added basic TSIG support to NameChangeTransaction · a00bfe54
      Thomas Markwalder authored
      Added TSIGKeyPtr instance member to NameChangeTransaction.
      Modified NameChangeTransaction::sendUpdate() to do a TSIG updates if its
      TSIGKeyPtr is not null.
      Extended FauxServer test class to support TSIG if given a key.
      Added round trip TSIG tests to NameChangeTransaction base class tests.
      This does not address how the transaction's key is determined. That
      requires changes to configuration classes in D2Config.
  4. 12 May, 2014 1 commit
    • Thomas Markwalder's avatar
      [3432] Added support for TSIG to D2UpdateMessage and DNSClient · dd0024cf
      Thomas Markwalder authored
      Change D2UpdateMessage to support TSIG signing and verification via its
      toWire and fromWire methods.  Both now accept a pointer to a TSIGContext,
      which they should use, if its not NULL.
      Implemented DNSCLient::doUpdate variant that accepts a TSIGKey. It will
      use the key to create a TSIGContext that will then be used to sign the
      outbound request and to verify the response in the operator() method.
      Added appropriate unit tests.
  5. 06 May, 2014 4 commits
  6. 29 Apr, 2014 2 commits
  7. 28 Apr, 2014 4 commits
  8. 25 Apr, 2014 6 commits
  9. 24 Apr, 2014 9 commits
  10. 23 Apr, 2014 5 commits
  11. 22 Apr, 2014 1 commit
  12. 21 Apr, 2014 2 commits
  13. 18 Apr, 2014 1 commit