Excel-DNA / Excel-DNA/ExcelDna

Sign our NuGet packages before submitting to nuget.org

Open
#198 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
1.5k
Forks
292
Avg merge
20d 12h
Merged PRs (30d)
1

Description

Today, NuGet [introduced the concept of **signed package submissions**](https://blog.nuget.org/20180522/Introducing-signed-package-submissions.html), giving us the ability for package authors to sign packages.

Issue #197 is already a good step towards package authenticity, and the concept of signing packages goes even further.

Opening this issue to start the discussion, as **there might be costs involved in [obtaining a code signing certificate that is trusted by nuget.org](https://docs.microsoft.com/en-us/nuget/reference/signed-packages-reference#get-a-code-signing-certificate)**, which is one of the [requirements](https://docs.microsoft.com/en-us/nuget/reference/signed-packages-reference#signature-requirements-on-nugetorg).

>
> ### Benefits of signing packages
> As we described in our original blog post, we have two primary goals to accomplish:
>
> * **Package Integrity**: We want to ensure the package contents have not been modified from the time the package was authored to when a developer downloads it for use in their projects. We also recognize that users copy packages from NuGet.org to multiple locations (such as setting up mirrors or copying them locally) and we want to ensure that such packages have not been modified before consumption.
>
> * **Package Authenticity**: We’ve heard from the community that it is often difficult to determine the origin of a package. In a previous blog post, we proposed some resolutions to the problem such as the ability for users to reserve package ID prefixes on NuGet.org. As we called out in that blog post, the next logical step is to address package signing. This will strengthen our package identity solution to provide authenticity on packages across multiple feeds.
>

## Compatibility:
>
> A signed NuGet package is designed to be fully compatible with pre-existing NuGet servers and clients. Only newer versions of NuGet clients will take advantage of validating package signatures. We added this capability to Visual Studio 2017 15.6.
>

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.