Skip to content

Should Strong-Name-Key (snk) files be included with open source?  #1

@vchendrix

Description

@vchendrix

Should Strong-Name-Key (snk) files be included with open source? What is their purpose in this project?

Here is a link n security issues with sharing *.pfx and *.snk files
https://stackoverflow.com/questions/10474852/any-security-issues-adding-a-strong-name-key-to-source-control-for-an-open-source

PFX might not make sense in open source.

  • Master/ACMAccess/ACMAccess.snk: data
  • Master/AspenSinterGUI/SinterConfigGUI.snk: data
  • Master/CSVConsoleSinter/CSVConsoleSinter.snk: data
  • Master/CSVConsoleSinter/CSVConsoleSinter_TemporaryKey.pfx: data
  • Master/CSVFileRW/CSVFileRW.snk: data
  • Master/ConsoleSinter/ConsoleSinter.snk: data
  • Master/ConsoleSinter/ConsoleSinter_TemporaryKey.pfx: data
  • Master/DataGrid2DLibrary/DataGrid2DLibrary.snk: data
  • Master/DefaultBuilder/DefaultBuilder.snk: data
  • Master/Sinter/Sinter.snk: data
  • Master/SinterRegressionTests/SinterRegressionTests.snk: data
  • Master/VariableTree/VariableTree.snk: data

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions