[
https://issues.apache.org/jira/browse/IGNITE-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010604#comment-15010604
]
ASF GitHub Bot commented on IGNITE-1677:
----------------------------------------
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/159
> .Net: Sign assemblies and store SNK file in git
> -----------------------------------------------
>
> Key: IGNITE-1677
> URL: https://issues.apache.org/jira/browse/IGNITE-1677
> Project: Ignite
> Issue Type: Task
> Components: interop
> Affects Versions: ignite-1.4
> Reporter: Pavel Tupitsyn
> Assignee: Vladimir Ozerov
> Fix For: 1.5
>
>
> Currently there is no strong name signing, so anyone who wants to reference
> Ignite.NET in their signed assembly will have to modify our sources and build
> them.
> Providing snk file as part of the open source project is a standard practice
> (see log4net
> https://svn.apache.org/repos/asf/logging/log4net/trunk/log4net.snk.readme).
> Public strong name, of course, does not provide any means of authenticity
> checking, but makes development easier.
> Authenticity can be ensured by downloading Apache Ignite release from
> official download page and verifying check sums.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
