Licensing PGP Command Line
Article ID: 180234
Updated On:
Products
Issue/Introduction
PGP Command Line is an effective tool for securing data. It can encrypt and sign data, as well as decrypt and verify data. Whether you have one file or many, the speed of PGP Command Line increases with the number of CPUs your computer has.
The way PGP Command Line is licensed is unique due to its enhanced performance with more CPUs. This article explains the licensing method.
Resolution
Table of Contents
How licensing works
- Number of Cores/CPUs: The license you need depends on how many cores and CPUs your computer has.
- Single Core: For servers with a single core and 8 CPUs, you need an 8-CPU license.
- Dual Core: For servers with dual cores and 8 CPUs in each core, you need a 16-CPU license.
- PGP Command Line licenses allow for one Production and one Non-production per SKU purchased.
- A Production server is defined as a system that encrypts or decrypts production data for business operations.
- A Disaster Recovery system is considered a Production server as its purpose is to handle production data.
- A Non-Production server is defined as a server where you perform "testing", and will not handle production data in any scenario.
Using a license number
In order to license the PGP Command Line product, the following commands can be used for the various versions:
Scenario 1 : PGP Command Line 10.3.2 MP8 and later
pgp --license-authorize --license-number "Your license here"
If you are replacing an existing license you will need to add the following switch at the end of the command, which will replace the license number with the new one entered:--force
If you receive the following output, it occurs when PGP Command Line was already authorized.
pgp: license authorize (2706:PGP Command Line already has a license)
If you need to replace the license number, add the "--force" option to your command:
pgp --license-authorize --license-number "Your license here" --force
Scenario 2: PGP Command Line 10.3.0 to 10.3.2 MP7
pgp --license-authorize --license-name "Authorized User" --license-organization "Authorized Company" --license-number "Your license here" --license-email "Recovery Email here"
If you receive the following output, this occurs when PGP Command Line was already authorized:
pgp: license authorize (2706:PGP Command Line already has a license)
If you need to replace the license number, add the "--force" option to your command:
pgp --license-authorize --license-name "Authorized User" --license-organization "Authorized Company" --license-number "Your license here" --license-email "Recovery Email here" --force
(Legacy Versions) Using a manual license authorization file
If you have both a license number and a license authorization (a text file) from PGP Corporation instead of just a license number, you need to enter the name of the license authorization file in the command.
You may need a license authorization if you are having problems authorizing your license number or if the system hosting PGP Command Line is not connected to the Internet.
Use the following to license PGP Command Line.
--license-authorize
Scenario 3: PGP Command Line 9.5 to 10.1 (manual license file bolded)
You will need to first create a text file and copy/paste the contents into this file. Name the file "license-auth.txt":
-----BEGIN PGP LICENSE AUTHORIZATION-----
ADIAC5YAAKDskWq4rZS67+yoTc/iWaSyGIbDUgCgrX05EyNW4YUaVvPM4wf2kDSb+N0=
-----END PGP LICENSE AUTHORIZATION-----
Once this has been done, you will run the following command:
pgp --license-authorize --license-name "Authorized User" --license-organization "Authorized Company" --license-number "aaaaa-bbbbb-ccccc-ddddd-eeeee-fff" license-auth.txt --license-email "[email protected]"
Licensing PGP Command Line for Linux
If you are going to be issuing encryption/decryption commands with other profiles on a system, we recommend licensing the product as the "root" account. When this is done, all the profiles will receive the license status skipping the need to license on each individual profile.
For best operation, license as "root", otherwise, you will need to license each individual user profile separately.
Additional Information
Feedback
