Endpoint Encryption

 View Only

  • 1.  Will the key of PGP command line sustain thru virtualisation?

    Posted Sep 11, 2012 10:32 AM

    Hi

     

    I have a windows 2003 server (Virtual Machine) installed with PGP command line tool and all the keys in position. I am going to duplicate the VM and use microsoft's sysprep to prepare a new server. I would like to know if all the keys store and work properly without any machine dependency in the clone machine? Where are those keys stored indeed?

     

    I am a newbie to the PGP command line tools. Please give me some advise or reference information.

     

    P.S. Of course, we will take care licenses issue.



  • 2.  RE: Will the key of PGP command line sustain thru virtualisation?
    Best Answer

    Posted Sep 11, 2012 11:32 AM

    It should work fine, provided you are using a recent version of PGP Command Line.  Older versions bind processor specific information into the license, which made it problematic to deploy in many virtual environments.

    Preference information is stored in the PGPprefs.xml file.  This file contains pointers to the files that contain your public and private key (these are your "keyring files").



  • 3.  RE: Will the key of PGP command line sustain thru virtualisation?

    Posted Sep 11, 2012 12:03 PM

    Thanks for your prompt response.

    For what version or before should I aware the license issue mentioned?



  • 4.  RE: Will the key of PGP command line sustain thru virtualisation?

    Posted Sep 11, 2012 01:24 PM

    This was addressed in PGP Command Line version 10.0.0.



  • 5.  RE: Will the key of PGP command line sustain thru virtualisation?

    Posted Sep 11, 2012 02:29 PM

    Mine is an older version.

    Besides upgrade to 10.0.0, is it possible to solve the mentioned problem? For example, simply apply a new license to the clone machine?



  • 6.  RE: Will the key of PGP command line sustain thru virtualisation?

    Posted Sep 11, 2012 04:18 PM

    Yes, though you may need to re-license each time the cloned machine is instatiated and you start to do commands.  If the VM ends up running on a different physical processor then the one on which it was licensed, it will think that the license is not valid.