locked
Sealing a MP RRS feed

  • Question

  • After read online docs for Seal a MP I have some doubts:

    After create my KEY using sn.exe, can I use this same key to seal all my Unseald Management Packs?

    If I want to share my new Management Pack (in .MP format) with other companies, I need to send the KEY together the MP? or only the MP file?

    Wednesday, October 13, 2010 4:39 PM

Answers

  • >After create my KEY using sn.exe, can I use this same key to seal all my Unseald Management Packs?

    Yes, you can.

    >If I want to share my new Management Pack (in .MP format) with other companies, I need to send the KEY together the MP? or only the MP file?

    No, you do not need to share the key.


    http://OpsMgr.ru/
    • Proposed as answer by Nicholas Li Thursday, October 14, 2010 7:50 AM
    • Marked as answer by Nicholas Li Monday, October 18, 2010 2:53 AM
    Wednesday, October 13, 2010 4:44 PM
  • You're welcome.

    Personally I am do not see a difference to use sn.exe-key or CertSign... Customers will not 'check' it, like certificates(for example - web server certificate), this key will not 'completely hide' MP contents from end customers if they know how to export a sealed MP to XML...

    And yes, you can use the same key for all your custom MP.


    http://OpsMgr.ru/
    • Proposed as answer by Nicholas Li Thursday, October 14, 2010 7:50 AM
    • Marked as answer by Nicholas Li Monday, October 18, 2010 2:53 AM
    Thursday, October 14, 2010 4:11 AM
  • You could use the same key, forever and ever if you want.  In fact, you'll have to use the same key to support upgrade compatibility for your MP.  If you are selling your MP commercially, I think you would probably want to sign the MP as well, so customers know it's from a trusted souce.  Sealing a MP isn't necessarily intended to copyright the MP.  It's a mechanism used to control MP versioning.  If customer uses your MP and doesn't like all of it, nothing stops them from unsealing it, modifying it, and importing their version of your MP.  But they will be out of luck when you update the MP, because the key is necessary for upgrade compatibility.

    I'm not a licensing expert, so you'll probably want to talk to someone who is when you are ready to market your MP.


    HTH, Jonathan Almquist - MSFT
    • Proposed as answer by Nicholas Li Thursday, October 14, 2010 7:50 AM
    • Marked as answer by Nicholas Li Monday, October 18, 2010 2:53 AM
    Thursday, October 14, 2010 4:12 AM

All replies

  • >After create my KEY using sn.exe, can I use this same key to seal all my Unseald Management Packs?

    Yes, you can.

    >If I want to share my new Management Pack (in .MP format) with other companies, I need to send the KEY together the MP? or only the MP file?

    No, you do not need to share the key.


    http://OpsMgr.ru/
    • Proposed as answer by Nicholas Li Thursday, October 14, 2010 7:50 AM
    • Marked as answer by Nicholas Li Monday, October 18, 2010 2:53 AM
    Wednesday, October 13, 2010 4:44 PM
  • Thank You Alexey,

    So if I am a company, that develops Management Packs, I creat a simple key using SN.EXE, only one time, I will can use this same KEY forever to seal and sell my MPs? :)

    Use a key created by SN.EXE is a best practices for companies that want to sell MPs? Can I use a CertSign key to seal my MPs? Whats the difference to use SN.EXE Key or CertSign key for me as a company?

    Thank you so much,

    Wednesday, October 13, 2010 4:53 PM
  • You're welcome.

    Personally I am do not see a difference to use sn.exe-key or CertSign... Customers will not 'check' it, like certificates(for example - web server certificate), this key will not 'completely hide' MP contents from end customers if they know how to export a sealed MP to XML...

    And yes, you can use the same key for all your custom MP.


    http://OpsMgr.ru/
    • Proposed as answer by Nicholas Li Thursday, October 14, 2010 7:50 AM
    • Marked as answer by Nicholas Li Monday, October 18, 2010 2:53 AM
    Thursday, October 14, 2010 4:11 AM
  • You could use the same key, forever and ever if you want.  In fact, you'll have to use the same key to support upgrade compatibility for your MP.  If you are selling your MP commercially, I think you would probably want to sign the MP as well, so customers know it's from a trusted souce.  Sealing a MP isn't necessarily intended to copyright the MP.  It's a mechanism used to control MP versioning.  If customer uses your MP and doesn't like all of it, nothing stops them from unsealing it, modifying it, and importing their version of your MP.  But they will be out of luck when you update the MP, because the key is necessary for upgrade compatibility.

    I'm not a licensing expert, so you'll probably want to talk to someone who is when you are ready to market your MP.


    HTH, Jonathan Almquist - MSFT
    • Proposed as answer by Nicholas Li Thursday, October 14, 2010 7:50 AM
    • Marked as answer by Nicholas Li Monday, October 18, 2010 2:53 AM
    Thursday, October 14, 2010 4:12 AM