You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2015/10/15 11:33:05 UTC

[jira] [Assigned] (IGNITE-1677) .Net: Sign assemblies and store SNK file in git

     [ https://issues.apache.org/jira/browse/IGNITE-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel  Tupitsyn reassigned IGNITE-1677:
---------------------------------------

    Assignee: Vladimir Ozerov  (was: Pavel  Tupitsyn)

> .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)