This software generates asymmetric encryption using private/public keys portable.licensing. The document states:

Store the private key securely and distribute the public key with your product.

Is there any harm in embedding the public key in the licence itself as an attribute so it's plainly visible to the licence holder?

I'm assuming that anyone who has a copy of the application can easily find any embedded public keys but just wanted to check if there were any drawbacks to making it plainly visible.


    <Attribute name="PublicKey">MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEkCipKSjvVZxSa6s1oLJn4A+TP8e9XL2PQmymJiBwR+yi02ZDvVO5YejnWNokyrzg06owL7ErfVh9p71EB8DEMw==</Attribute>
  <Expiration>Wed, 04 May 2016 23:59:59 GMT</Expiration>
    <Email>[email protected]</Email>
  • 2
    Shoulda called it the "public (yes, public) key" Apr 27, 2017 at 19:43
  • only if you want people to be able to send you secure messages.
    – dandavis
    Apr 27, 2017 at 20:49

1 Answer 1


Sure, public key is included quite frequently as a part of challenge (for example HDCP2). Also there can be a problem to trust of the public key, so it's usually signed with a trusted authority. As public key is used during of the beginning of authentication phase, symmetric keys are not ready at this point.

You must log in to answer this question.