Uploaded image for project: 'REEF (Retired)'
  1. REEF (Retired)
  2. REEF-465

Figure out how to produce safely signed NuGets

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 0.13
    • NuGet, REEF.NET
    • None

    Description

      We currently have the private / public key pair we use for our builds in the repository. This means that the signature on our NuGets and DLLs is not trustworthy. We should find a way to produce properly signed NuGets.

      Note: None of this affects the official source release, nor the signature on the Java Maven artifacts. Both are signed with GnuPG, using a key we keep private.

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. REEF-572 Release 0.13

          • Major - Major loss of function.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. REEF-457 Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. REEF-458 Remove key pair snk file from repository, regenerate the key and push public key

          • Major - Major loss of function.
          • Resolved
          relates to

          Bug - A problem which impairs or prevents the functions of the product. REEF-713 revert public key that should matche the keyfile.snk

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              markus.weimer Markus Weimer
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: