[
https://issues.apache.org/jira/browse/WOOKIE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423150#comment-13423150
]
Paul Sharples commented on WOOKIE-139:
--------------------------------------
I think I got to the bottom of the problem by excluding xerces from the
ddlutils dependency in ivy.xml. I've done a few tests and everything seems to
be working okay, but we will have to keep an eye on it in case it now causes
other problems elsewhere in wookie. (we'll have to put it back as it was & try
something else if thats the case)
I've just committed the code to svn, with minor changes. Although its not
quite configured as a wookie subproject yet, I've laid it out as if it will be
in the future. (i.e. it could have its own ivy, build tasks etc so that we
could automate building an executable jar for example).
Please take a look at the source code and let me know if there are any
ommissions or errors. I've named it digsig-client - thinking that the dig-sig
server part will eventually live inside the root src folder, when done.
thanks!
> Implement the W3C XML Digital Signatures for Widgets specification in Wookie
> ----------------------------------------------------------------------------
>
> Key: WOOKIE-139
> URL: https://issues.apache.org/jira/browse/WOOKIE-139
> Project: Wookie
> Issue Type: New Feature
> Reporter: Scott Wilson
> Labels: gsoc2012, mentor
> Attachments: Signer_W3C_widget_digisg.patch,
> Wookie_Widget_Signer_Guide, logo.png
>
>
> W3C XML Digital Signatures for Widgets specifies how both authors and
> distributors of widgets can digitally sign a Widget package:
> The spec is here: http://dev.w3.org/2006/waf/widgets-digsig/
> This means that an organisation can choose to automatically install and
> update widgets that carry recognised signatures - for example from a
> reputable online widget store (distributor) or from an approved widget author
> rather than require admin intervention to approve them.
> For Wookie this means implementing the mechanism for locating and verifying
> W3C signature.xml files in Widgets, and providing signature management
> options.
> For example, we may want to have a configuration property set for requiring
> signatures be checked, and a file where trusted signatories are listed for
> checking against when a new widget is uploaded, or a new version is detected
> online using Widget Updates.
> We may also want to look at how Wookie can delegate upwards decisions based
> on signature verification, for example to let an Apache Rave admin choose to
> allow automatic publishing of signed widgets from trusted sources provided
> that Wookie has verified the signature and returned this information to Rave.
> This could be handled in the response to uploading a widget to Wookie using
> the REST API, e.g. adding <signature verified="true" type="author"/> to the
> metadata returned in the response body.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
