Endpoint Encryption

 View Only
  • 1.  Default signing key

    Posted Mar 24, 2014 03:29 PM

    Hello,

    I need to make a key on a keyring a default signing key.

    I tried this solution from another thread:

    <key>CLdefaultKey</key>

    <string>0x060XXXXX</string>

    (in PGPPrefs.xml, and of course I've set some real keyID ;) )

    Still, when encrypting via PGP Desktop the key is not proposed as a signing. In fact, no key is proposed, i have to choose one from the list.

    Maybe I've set it up at the wrong place (at the end of the main dict section in file)?



  • 2.  RE: Default signing key

    Broadcom Employee
    Posted Mar 25, 2014 05:33 AM

    Hi rmikke,

    That seems to be a pref for PGP Command Line, not for PGP Desktop.
    According to the behavior I'm seeing the suggested key will be the one previously used. (If you right-click the file and select Symantec Encryption Desktop (PGP Desktop) > Sign as...)
    The only place I found where you can define the default key is PGP Messaging > Default Key.


    HTH,
    dcats



  • 3.  RE: Default signing key

    Posted Mar 25, 2014 02:28 PM

    It worked for me this way as well, until two things happened almost at once:

    1) I got new computer with Win7 instead of XP and installed PGP 10.2.1MP5 on it

    2) PGP got automagically upgraded to Symantec Encryption Desktop 10.3.2.

    I believe the last one changed the behavior, but I'm not 100% sure.

    When I right-click file and choose "Sijgn as" it works as you described (which is good as when I choose Sign as then most probably I need a signing key ;) ), but when I right-click a file and choose "Secure with key", still no signing key is selected and I have to select one manually.

    Seems I don't have PGP Messaging you write about or I can't find it, so haven't checked if setting this up would help....



  • 4.  RE: Default signing key

    Broadcom Employee
    Posted Mar 27, 2014 07:07 AM

    Hi rmikke,

    You will only see the PGP Messaging panel if you have the license for Messaging (email encryption), or have enabled the Messaging in the Consumer Policy (for managed clients).

    I've seen the exact same behavior as you describe in a fresh install of 10.3.2, even with PGP Messaging presenting a default key (which is defined for messaging).
    I'm not sure if such feature exists, but I will check if there is a way to define a "client default key".


    HTH,
    dcats