Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#24 NMock Generates a new Strong Name for each Build

open
nmock2 (11)
5
2008-02-25
2008-02-06
Anonymous
No

The NAnt build script for NMock creates a new name each time NMock is compiled.

Common practice is to create one strong name key that is kept private by the developers and sign all official release with this key. Thus, if an unofficial release is made, it cannot be signed with the official NMock key.

The way you designed it, a new public key would appear for each release and users cannot validate whether their NMock binaries are from an official release short of checking the public key hash against the hashes of all releases ever made.

Discussion

  • Logged In: YES
    user_id=591527
    Originator: NO

    Could you give me more details on this, the way I have it designed there should only be one public key hash, for all the releases.

     
    • assigned_to: nobody --> aciddeath