1. 09 Nov, 2015 1 commit
  2. 21 Oct, 2015 2 commits
  3. 09 Oct, 2015 5 commits
  4. 03 Oct, 2015 1 commit
  5. 27 Sep, 2015 1 commit
  6. 25 Sep, 2015 2 commits
  7. 24 Sep, 2015 1 commit
  8. 09 Sep, 2015 1 commit
  9. 08 Sep, 2015 1 commit
  10. 07 Sep, 2015 1 commit
  11. 19 Aug, 2015 4 commits
  12. 18 Aug, 2015 3 commits
  13. 13 Aug, 2015 1 commit
  14. 10 Aug, 2015 1 commit
  15. 06 Aug, 2015 1 commit
  16. 05 Aug, 2015 2 commits
  17. 04 Aug, 2015 3 commits
    • Peter Loer's avatar
      Revising logic from PR #102 to just conditionally put the keyDescriptor in if... · cc652563
      Peter Loer authored
      Revising logic from PR #102 to just conditionally put the keyDescriptor in if needed, rather than deleting it if unneeded.
      cc652563
    • Peter Loer's avatar
      Merge pull request #102 from gnawhleinad/skip_null_keydescriptor · 19d2e49e
      Peter Loer authored
      skip KeyDescriptor if decryptionPvk is not provided
      19d2e49e
    • Ethan Mick's avatar
      Fixed an obscure bug in which certificates may not be found. · 24295ecf
      Ethan Mick authored
      Not sure if anyone else has run into this issue, but I did in a separate project.
      The issue is that when the signature node has been serialized to a String,
      it loses the context of where it is in the XML tree. When deserialized, it
      only knows about itself. Later in the code, in valdiateSignatureValue of xml-crypto,
      this is calleD:
      
      However, if the signature node has been serialized and deserialized, it
      incorrectly reports it only has 1 child (itself), as opposed to the correct number.
      This causes the certificate data to not be found, and the validation to fail.
      
      All tests still pass with this change. Update to xml-crypto required.
      24295ecf
  18. 31 Jul, 2015 1 commit
  19. 08 Jun, 2015 3 commits
  20. 26 May, 2015 2 commits
  21. 25 May, 2015 1 commit
  22. 24 May, 2015 1 commit
  23. 23 May, 2015 1 commit