You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@taverna.apache.org by "Stian Soiland-Reyes (JIRA)" <ji...@apache.org> on 2018/01/12 18:34:00 UTC

[jira] [Commented] (TAVERNA-1031) README: Note Export restrictions for Taverna Server

    [ https://issues.apache.org/jira/browse/TAVERNA-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16324351#comment-16324351 ] 

Stian Soiland-Reyes commented on TAVERNA-1031:
----------------------------------------------

Now in https://github.com/apache/incubator-taverna-server/#export-restrictions - please review.

> README: Note Export restrictions for Taverna Server
> ---------------------------------------------------
>
>                 Key: TAVERNA-1031
>                 URL: https://issues.apache.org/jira/browse/TAVERNA-1031
>             Project: Apache Taverna
>          Issue Type: Task
>          Components: Taverna Server
>    Affects Versions: server 3.1.0
>            Reporter: Stian Soiland-Reyes
>            Assignee: Stian Soiland-Reyes
>
> as mentioned in TAVERNA-959 we need to do a crypto-review of our software - this includes Taverna Server, as it uses Taverna Command Line, as well as does a bit of BouncyCastle keystore manipulation to work with Taverna engine's credential manager.
> This was already covered by https://cwiki.apache.org/confluence/display/TAVERNADEV/Taverna+Cryptography+review and taverna-server was part of the formal registration, so this should not block the current 3.1.0 RC3 
> However for the future we should include a section in the README similar to https://github.com/apache/incubator-taverna-commandline/#export-restrictions



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)