Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare for 1.0 #66

Closed
1 of 9 tasks
bjrmatos opened this issue Aug 8, 2015 · 12 comments
Closed
1 of 9 tasks

Prepare for 1.0 #66

bjrmatos opened this issue Aug 8, 2015 · 12 comments
Milestone

Comments

@bjrmatos
Copy link
Contributor

bjrmatos commented Aug 8, 2015

The plan (discussed here):

  • [deprecate] sig.loadSignature (at least from the public API).
  • [new behaviour] checkSignature(String: xmlDocument, [String: externalSignatureXmlDocument]) will search and validate only the first signature found (a cool feature would be let the user to validate a specific signature, vía a XPath expression).
  • [new feature] checkAllSignatures(String: xmlDocument, [String: externalSignatureXmlDocument]) will validate all signatures found (by default it will search inside the document for all instances of and validate all instances accordingly. if externalSignatureXmlDocument is specified it will search inside the external document).
  • bring it back the condition: //*[local-name(.)='SignedInfo']/*[local-name(.)='Reference' and namespace-uri(.)='http://www.w3.org/2000/09/xmldsig#'] (removed here) to ensure a well formed xml document.. it will be ok since we have all the information that we need (namespaces) in the xml document node.
  • both checkSignature and checkAllSignatures must support the externalSignatureXmlDocument param for external signatures.
  • [refactor] adapt current tests
  • [fix/improve] travis build (seems like it is broken since some time ago)
  • [add] debug module for logging in development
  • [remove] hacky workaround in this commits if more information is not provided here

🎉 The user wont need to specify the signature manually, xml-crypto will do it and will support multiple signature validation. 🎉

@bjrmatos
Copy link
Contributor Author

bjrmatos commented Aug 8, 2015

i will post here if i find more improvements

@bjrmatos bjrmatos added this to the v1.0 milestone Aug 8, 2015
@bjrmatos
Copy link
Contributor Author

added a task to improve travis build

@bjrmatos
Copy link
Contributor Author

bjrmatos commented Sep 5, 2015

added a task to use debug module for logging useful information in development

@bjrmatos
Copy link
Contributor Author

bjrmatos commented Oct 4, 2015

fixed travis builds in fbb8dac

@fcorneli
Copy link
Contributor

Is it possible to tag each release properly?

@bjrmatos
Copy link
Contributor Author

@fcorneli sure! I will do it :)

@bjrmatos
Copy link
Contributor Author

@yaronn can you enable the Travis webhook again? would be great to have the results of travis builds in PRs again :)

@yaronn
Copy link
Contributor

yaronn commented Oct 15, 2015

where do I enable it? "build push" and "build pull requests" are already on
in the travis project. maybe its in the yml? or you can also create a
travis project with your name.

On Thu, Oct 15, 2015 at 7:33 AM, BJR Matos notifications@github.com wrote:

@yaronn https://github.com/yaronn can you enable the Travis webhook
again? would be great to have results of travis builds in PRs again :)


Reply to this email directly or view it on GitHub
#66 (comment).

I'm on Twitter (@YaronNaveh http://twitter.com/#!/YaronNaveh)

@bjrmatos
Copy link
Contributor Author

can you look at the repository settings and confirm that travis is there?

screenshot from another repository:

captura de pantalla 2015-10-17 a las 2 39 03 p m

@yaronn
Copy link
Contributor

yaronn commented Oct 22, 2015

yes, it's there exactly as in the picture.

On Sat, Oct 17, 2015 at 10:42 PM, BJR Matos notifications@github.com
wrote:

can you look at the repository settings and confirm that travis is there?

screenshot from another repository:

[image: captura de pantalla 2015-10-17 a las 2 39 03 p m]
https://cloud.githubusercontent.com/assets/4262050/10560862/2f506d8e-74dd-11e5-93d3-116b52ef9900.png


Reply to this email directly or view it on GitHub
#66 (comment).

I'm on Twitter (@YaronNaveh http://twitter.com/#!/YaronNaveh)

@bjrmatos
Copy link
Contributor Author

bjrmatos commented Feb 2, 2016

added a task to remove the code added here if more info is not provided.

@LoneRifle
Copy link
Collaborator

Closed as stale, we're now at versions beyond 1.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants