-
Notifications
You must be signed in to change notification settings - Fork 171
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
Comments
i will post here if i find more improvements |
added a task to improve travis build |
added a task to use debug module for logging useful information in development |
fixed travis builds in fbb8dac |
Is it possible to tag each release properly? |
@fcorneli sure! I will do it :) |
@yaronn can you enable the Travis webhook again? would be great to have the results of travis builds in PRs again :) |
where do I enable it? "build push" and "build pull requests" are already on On Thu, Oct 15, 2015 at 7:33 AM, BJR Matos notifications@github.com wrote:
I'm on Twitter (@YaronNaveh http://twitter.com/#!/YaronNaveh) |
yes, it's there exactly as in the picture. On Sat, Oct 17, 2015 at 10:42 PM, BJR Matos notifications@github.com
I'm on Twitter (@YaronNaveh http://twitter.com/#!/YaronNaveh) |
added a task to remove the code added here if more info is not provided. |
Closed as stale, we're now at versions beyond 1.0. |
The plan (discussed here):
sig.loadSignature
(at least from the public API).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).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).//*[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.🎉 The user wont need to specify the signature manually, xml-crypto will do it and will support multiple signature validation. 🎉
The text was updated successfully, but these errors were encountered: