You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/10/15 11:22:05 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14958570#comment-14958570 ]
ASF GitHub Bot commented on IGNITE-1677:
----------------------------------------
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/159
IGNITE-1677 .Net: Sign assemblies and store SNK file in git
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-1677
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/159.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #159
----
commit 7fd76bb0f218540f6efcc2e06bf1c7edb911f49f
Author: ptupitsyn <pt...@gridgain.com>
Date: 2015-10-15T08:45:48Z
wip signing
commit 460cab2961169fe63c8e3404dfb524e4689079e7
Author: ptupitsyn <pt...@gridgain.com>
Date: 2015-10-15T08:48:36Z
wip signing
commit edfe3450a5a217c7a86d4a5444b407f1257dc544
Author: ptupitsyn <pt...@gridgain.com>
Date: 2015-10-15T09:15:00Z
wip
commit 87eb00b765a808b83dab424ba27eb6eebd19ed52
Author: ptupitsyn <pt...@gridgain.com>
Date: 2015-10-15T09:16:42Z
wip signing
----
> .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: Pavel Tupitsyn
> 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)