PGP, Pretty Good Privacy, and the PGP logo are registered trademarks of PGP Corporation in the US and other countries. IDEA is a trademark of Ascom
Tech AG. Windows and ActiveX are registered trademarks of Microsoft Corporation. AOL is a registered trademark, and AOL Instant Messenger is a
trademark, of America Online, Inc. Red Hat and Red Hat Linux are trademarks or registered trademarks of Red Hat, Inc. Linux is a registered trademark
of Linus Torvalds. Solaris is a trademark or registered trademark of Sun Microsystems, Inc. AIX is a trademark or registered trademark of International
Business Machines Corporation. HP-UX is a trademark or registered trademark of Hewlett-Packard Company. SSH and Secure Shell are trademarks of
SSH Communications Security, Inc. Rendezvous and Mac OS X are trademarks or registered trademarks of Apple Computer, Inc. All other registered
and unregistered trademarks in this document are the sole property of their respective owners.
Licensing and Patent Information
The IDEA cryptographic cipher described in U.S. patent number 5,214,703 is licensed from Ascom Tech AG. The CAST-128 encryption algorithm,
implemented from RFC 2144, is available worldwide on a royalty-free basis for commercial and non-commercial uses. PGP Corporation has secured a
license to the patent rights contained in the patent application Serial Number 10/655,563 by The Regents of the University of California, entitled Block
Cipher Mode of Operation for Constructing a Wide-blocksize block Cipher from a Conventional Block Cipher. Some third-party software included in PGP
Universal Server is licensed under the GNU General Public License (GPL). PGP Universal Server as a whole is not licensed under the GPL. If you would
like a copy of the source code for the GPL software included in PGP Universal Server, contact PGP Support (https://support.pgp.com). PGP Corporation
may have patents and/or pending patent applications covering subject matter in this software or its documentation; the furnishing of this software or
documentation does not give you any license to these patents.
- JacORB, a Java object used to facilitate communication between processes written in Java and the data layer, is open source licensed under the GNU
Library General Public License (LGPL) available at http://www.jacorb.org/lgpl.html
open-source implementation of a CORBA Object Request Broker (ORB), and is used for communication between processes written in C/C++ and the
data layer. Copyright (c) 1993-2006 by Douglas C. Schmidt and his research group at Washington University, University of California, Irvine, and
Vanderbilt University. The open source software license is available at http://www.cs.wustl.edu/~schmidt/ACE-copying.html
downloading files via common network services, is open source software provided under a MIT/X derivate license available at
http://curl.haxx.se/docs/copyright.html
under a BSD-style license, available at http://thunk.org/hg/e2fsprogs/?file/fe55db3e508c/lib/uuid/COPYING
libpopt, a library that parses command line options, is released under the terms of the GNU Free Documentation License available at
http://directory.fsf.org/libs/COPYING.DOC
communicate with the Intel Corporation AMT chipset on a motherboard, is distributed under the gSOAP Public License version 1.3b, available at
), Jakarta Commons (http://jakarta.apache.org/commons/license.html) and log4j, a Java-based library used to parse HTML,
). -- Libxml2, the XML C parser and toolkit developed for the Gnome project and distributed and copyrighted under
http://www.cs.fsu.edu/~engelen/license.html. -- Windows Template Library (WTL) is used for developing user interface components and is distributed
under the Common Public License v1.0 found at http://opensource.org/licenses/cpl1.0.php
automate a variety of maintenance functions and is provided under the Perl Artistic License, found at
-- Java Radius Client, used to authenticate PGP Universal Web Messenger users via Radius, is distributed under the Lesser General Public License
(LGPL) found at http://www.gnu.org/licenses/lgpl.html
Copyright (c) 2009, Yahoo! Inc. All rights reserved. Released under a BSD-style license, available at http://developer.yahoo.com/yui/license.html. --
JSON-lib version 2.2.1, a Java library used to convert Java objects to JSON (JavaScript Object Notation) objects for AJAX. Distributed under the Apache
2.0 license, available at http://json-lib.sourceforge.net/license.html
at http://ezmorph.sourceforge.net/license.html
configuration file format used on Windows, on other platforms. Distributed under the MIT License found at http://www.opensource.org/licenses/mit-
license.html. Copyright 2006-2008, Brodie Thiesfield. -- uSTL provides a small fast implementation of common Standard Template Library functions and
data structures and is distributed under the MIT License found at http://www.opensource.org/licenses/mit-license.html
Mike Sharov <msharov@users.sourceforge.net
the PGP SDK. Distributed under the BSD license found at http://www.opensource.org/licenses/bsd-license.php. Copyright 2008
reserved.
Additional acknowledgements and legal notices are included as part of the PGP Universal Server.
. -- Apache Commons BeanUtils, used by JSON-lib, is distributed under the Apache 2.0 license, available at
. -- SimpleIni is an .ini format file parser and provides the ability to read and write .ini files, a common
. -- rEFIt - libeg, provides a graphical interface library for EFI, including image rendering, text
. -- Yahoo! User Interface (YUI) library version 2.5.2, a Web UI interface library for AJAX.
. -- EZMorph, used by JSON-lib, is distributed under the Apache 2.0 license, available
. -- Apache Commons Lang, used by JSON-lib, is distributed under the Apache 2.0 license, available at
>. -- Protocol Buffers (protobuf), Google's data interchange format, are used to serialize structure data in
. -- The Perl Kit provides several independent utilities used to
. Copyright (c) 2006 Christoph Pfisterer. All rights reserved.
. Copyright (c) 2005-2009 by
Google Inc. All rights
Export Information
Export of this software and documentation may be subject to compliance with the rules and regulations promulgated from time to time by the Bureau
of Export Administration, United States Department of Commerce, which restricts the export and re-export of certain products and technical data.
Limitations
The software provided with this documentation is licensed to you for your individual use under the terms of the End User License Agreement provided
with the software. The information in this document is subject to change without notice. PGP Corporation does not warrant that the information meets
your requirements or that the information is free of errors. The information may include technical inaccuracies or typographical errors. Changes may be
made to the information and incorporated in new editions of this document, if and when made available by PGP Corporation.
4
Contents
PGP Command Line Basics 1
Important Concepts 1
Getting Started 2
Installation 5
Overview 5
System Requirements 6
Windows 7 and Vista 6
Windows Server 2003 7
Windows XP 8
Windows 2000 9
IBM AIX 10
HP-UX 11i 10
Solaris 9 and 10 10
Red Hat Enterprise Linux and Fedora Core 10
Mac OS X 11
Installing on AIX 11
Installing on AIX 11
Changing the Home Directory on AIX 12
Uninstalling on AIX 13
Installing on HP-UX 13
Installing on HP-UX 13
Changing the Home Directory on HP-UX 14
Installing to a Non-Default Directory on HP-UX 14
Uninstalling on HP-UX 15
Installing on Mac OS X 15
Installing on Mac OS X 15
Changing the Home Directory on Mac OS X 16
Uninstalling on Mac OS X 16
Installing on Red Hat Enterprise Linux or Fedora Core 17
Installing on Red Hat Enterprise Linux or Fedora Core 17
Changing the Home Directory on Linux or Fedora Core 18
Uninstalling on Linux or Fedora Core 18
Installing on Solaris 19
Installing on Solaris 19
Changing the Home Directory on Solaris 20
Uninstalling on Solaris 20
Installing on Windows 21
PGP Command Line for Windows and PGP Desktop on the Same System 21
To Install on Windows 21
Changing the Home Directory on Windows 22
Uninstalling on Windows 23
i
PGP® Command Line 10.0 Contents
Licensing 25
Overview 25
License Recovery 26
Using a License Number 27
Using a License Authorization 28
Re-Licensing 29
Through a Proxy Server 30
The Command-Line Interface 33
Overview 33
Flags and Arguments 35
Flags 35
Arguments 36
Configuration File 38
Keyserver Configuration File Settings 42
Environment Variables 43
Standard Input, Output, and Error 44
Redirecting an Existing File 44
Entering Data 45
Specifying a Key 46
'Secure' Options 46
Passphrases 47
First Steps 49
Overview 49
Creating Your Keypair 50
Protecting Your Private Key 52
Distributing Your Public Key 52
Posting Your Public Key to a Keyserver 53
Exporting Your Public Key to a Text File 54
Getting the Public Keys of Others 54
Finding a Public Key on a Keyserver 54
Importing a Public Key from a Keyserver 55
Verifying Keys 56
Messages Without Codes 283
Messages With Codes 284
Parser 284
Keyrings 285
Wipe 286
Encrypt 287
Sign 287
Decrypt 287
Speed Test 288
Key edit 288
Keyserver 295
ix
PGP® Command Line 10.0 Contents
Key Reconstruction 296
Licensing 297
PGP Universal Server 298
General 298
Exit Codes 307
Frequently Asked Questions 309
Key Used for Encryption 309
"Invalid" Keys 310
Maximum File Size 311
Programming and Scripting Languages 312
File Redirection 312
Protecting Passphrases 312
Searching for Data on a PGP KMS 315
Overview 315
Keyword Listing 316
Example Searches 318
More About Types 319
Time Fields 319
Boolean Values 319
Open PGP Algorithms 319
Open PGP Key Usage Flags 320
Key Modes 320
Index 321
x
1
PGP Command Line Basics
This chapter describes some important PGP Command Line concepts and gives
you a high-level overview of the things you need to do to set up and use PGP
Command Line.
In This Chapter
Important Concepts................................................................................... 1
Getting Started .......................................................................................... 2
Important Concepts
The following concepts are important for you to understand:
PGP Command Line: A software product from PGP Corporation that
automates the processes of encrypting/signing, decrypting/verifying, and
file wiping; it provides a command-line interface to PGP technology.
command-line interface: An interface where you type commands at a
command prompt. PGP Command Line uses a command-line interface.
keyboard input: PGP Command Line was designed so that all relevant
information can be entered at the command line, thus requiring no further
input from the keyboard to implement the commands.
scripting: PGP Command Line commands can be easily inserted into
scripts to be used for automating tasks. For example, if your company
regularly copies a large database to an off-site backup and then stores it
there, PGP Command Line commands can be added to the script that does
this so that the database is encrypted before it is transmitted to the off-site
location and then decrypted when it arrives. PGP Command Line
commands are easily added to shell scripts or scripts written with scripting
languages (such as Perl or Python, for example).
environment variables: Environment variables control various aspects of
PGP Command Line behavior; for example, the location of the PGP
Command Line home directory. Environment variables are established on
the computer running PGP Command Line.
1
PGP® Command Line 10.0 PGP Command Line Basics
configuration file variables: When PGP Command Line starts, it reads the
configuration file, which includes special configuration variables and values
for each variable. These settings affect how PGP Command Line operates.
Configuration file variables can be changed permanently by editing the
configuration file or overridden on a temporary basis by specifying a value
for a configuration file variable on the command line.
Self-Decrypting Archives (SDAs): PGP Command Line lets you create
SDAs, compressed and conventionally encrypted archives that require a
passphrase to decrypt. SDAs contain an executable for the target platform,
which means the recipient of an SDA does not need to have any PGP
software installed to open the archive. You can thus securely transfer data
to recipients with no PGP software installed. You will have to communicate
the passphrase of the SDA to the recipient, however.
Additional Decryption Key (ADK): PGP Command Line supports the use
of an ADK, which is an additional key to which files or messages are
encrypted, thus allowing the keeper of the ADK to retrieve data or
messages as well as the intended recipient. Use of an ADK ensures that
your corporation has access to all its proprietary information even if
employee keys are lost or become unavailable.
PGP Zip archives: The PGP Zip feature lets you encrypt/sign groups of files
Getting Started
Now that you know a little bit about PGP Command Line, let’s go deeper into
what you need to do to get started using it:
1 Install PGP Command Line. Specific instructions for installing PGP
2 License the software. PGP Command Line functionality is extremely
3 Create your default key pair. Most PGP Command Line operations require
4 Protect your private key. Because your private key can decrypt your
or entire directories into a single compressed archive file. The archive
format is tar and the supported compression formats are Zip, BZip2, and
Zlib.
Command Line on the supported platforms are in Installation.
limited until you license the software. Refer to Licensing for more
information.
a key pair (a private key and a public key). Refer to Creating Your Keypair for
more information.
protected data, it is important that you protect it. Do not write down or tell
someone the passphrase. It is a good idea to keep your private key on a
machine that only you can access, and in a directory that is not accessible
from the network. Also, you should make a backup of the private key and
store it in a secure location. Refer to Protecting Your Private Key for more
information.
2
PGP® Command Line 10.0 PGP Command Line Basics
5 Exchange public keys with others. In order to encrypt data to someone
you need their public key; and they need yours to encrypt data to you. Refer
to Getting the Public Keys of Others for more information about how to
obtain public keys.
6Verify the public keys you get from the keyserver. Once you have a
copy of someone’s public key, you add it to your public keyring. When you
get someone’s public key, you should make sure that it has not been
tampered with and that it really belongs to the purported owner. You do
this by comparing the unique fingerprint on your copy of someone’s public
key to the fingerprint on that person’s original key. For more information
about validity and trust, refer to An Introduction to Cryptography (it was put
onto your computer during installation). For instructions how to verify
someone’s public key, see --fingerprint (page 80).
7Start securing your data. After you have generated your key pair and have
obtained public keys, you can begin encrypting, signing, decrypting, and
verifying your data.
3
2
Installation
This chapter lists the system requirements for, and tells you how to install PGP
Command Line onto, the six supported platforms: AIX, HP-UX, Mac OS X, Linux,
Solaris, and Windows. It also includes uninstall instructions.
System Requirements ............................................................................... 6
Installing on AIX ....................................................................................... 11
Installing on HP-UX .................................................................................. 13
Installing on Mac OS X.............................................................................15
Installing on Red Hat Enterprise Linux or Fedora Core............................17
Installing on Solaris .................................................................................. 19
Installing on Windows..............................................................................21
Overview
PGP Command Line can be installed on these platforms:
Windows 7 (32- and 64-bit), Windows Vista (32- and 64-bit), Windows
Server 2003 (SP 1), Windows XP (32- and 64-bit), Windows 2000 (SP 4)
HP-UX 11i and above (PA-RISC and Itanium)
IBM AIX 5.3 and 6.1
RedHat Enterprise Linux 3.0 and above (x86 only and x86_64)
Fedora Core 3 and above (x86_64 only)
Sun Solaris 9 (SPARC only) and Solaris 10 (SPARC, x86, and x86_64
Apple Mac OS X 10.5.x and 10.6.x (Intel-based systems only)
PGP Command Line uses a specific directory for the application data such as the
configuration file, and a specific directory (called the home directory) for the files
it creates, such as keyring files.
On any UNIX system, the application data and the home directory are identical
and they are configured through the $HOME environment variable. For more
information, refer to the installation instructions for the specific UNIX platform.
5
PGP® Command Line 10.0 Installation
On Windows, the application data directory is used to store data such as the
configuration file PGPprefs.xml. The home directory is called “My
Documents” and is used to store keys. These two directories can be named
differently, depending on the specific version on Windows. For more
information, see To Install on Windows (on page 21).
Note: You can also use the --home-dir option on the command line to
specify a different home directory. Using this option affects only the
command it is used in and does not change the PGP_HOME_DIR
environment variable.
Using --home-dir on the command line overrides the current setting of the
PGP_HOME_DIR environment variable.
System Requirements
In general, system requirements for PGP Command Line are the same as the
system requirements for the host operating system.
In addition to the hard drive space required by the base operating system, PGP
Command Line requires additional space for both the data on which
cryptographic operations (such as encryption, decryption, signing, and verifying)
will be applied and temporary files created in the process of performing those
operations.
For a given file being encrypted or decrypted, PGP Command Line can require
several times the size of the original file in free hard drive space (depending on
how much the file was compressed), enough to hold both the original file or files
and the final file resulting from the encryption or decryption operation.
In cases where PGP Zip functionality is used on a file, PGP Command Line may
also require several times the size of the original file or files in free hard drive
space, enough to hold the original file, a temporary file created when handling
the archive, and the final file resulting from the encryption or decryption
operation. Make sure you have adequate free hard drive space on your system
before using PGP Command Line.
Windows 7 and Vista
Component Requirement
Computer
and
processor
PC with 1 GHz 32-bit (x86) processor
Memory 1 gigabyte (GB) of RAM or higher recommended (64 MB
minimum supported; may limit performance and some
features)
6
PGP® Command Line 10.0 Installation
Hard disk 15 GB of available space
Drive DVD-ROM drive
Display Support for DirectX 9 graphics with WDDM driver, 128 MB of
graphics memory (minimum), Pixel Shader 2.0 in hardware, 32
bits per pixel
Windows Server 2003
PGP Command Line supports four editions of Windows Server 2003: Standard,
Datacenter, Enterprise, and Web.
Standard Edition
Component Requirement
Computer
and
processor
PC with a 133-MHz processor required; 550-MHz or faster
processor recommended (Windows Server 2003 Standard
Edition supports up to four processors on one server)
Memory 128 MB of RAM required; 256 MB or more recommended; 4
GB maximum
Hard disk 1.25 to 2 GB of available hard-disk space
Drive CD-ROM or DVD-ROM drive
Display VGA or hardware that supports console redirection required;
Super VGA supporting 800 x 600 or higher-resolution monitor
recommended
Pentium/Celeron family, AMD K6/Athlon/Duron family, or
compatible processor recommended
Memory 128 megabytes (MB) of RAM or higher recommended (64 MB
minimum supported; may limit performance and some
features)
Hard disk 1.5 gigabyte (GB) of available hard disk space
Drive CD-ROM or DVD-ROM drive
Display Super VGA (800 × 600) or higher resolution video adapter and
monitor supporting 800 x 600 or higher-resolution monitor
recommended
64-bit Windows XP
Component Requirement
Computer
and
processor
PC with AMD Athlon 64, AMD Opteron, Intel Xeon with Intel
EM64T support, Intel Pentium 4 with Intel EM64T support
Memory 256 megabytes (MB) of RAM or higher recommended
Hard disk 1.5 gigabyte (GB) of available hard disk space
Drive CD-ROM or DVD-ROM drive
Display Super VGA (800 × 600) or higher resolution video adapter and
monitor supporting 800 x 600 or higher-resolution monitor
recommended
Windows 2000
Component Requirement
Computer
and
processor
133 MHz or higher Pentium-compatible CPU
9
PGP® Command Line 10.0 Installation
Memory At least 64 megabytes (MB) of RAM; more memory generally
improves responsiveness
Hard disk 2 GB with 650 MB free space
Drive CD-ROM or DVD-ROM drive
Display VGA or higher resolution monitor
IBM AIX
PGP Command Line runs on the range of IBM eServer p5, IBM eServer pSeries,
IBM eServer i5 and IBM RS/6000, as supported by IBM AIX 5.3 and 6.1.
HP-UX 11i
PGP Command Line runs on the list of PA-RISC workstation and servers
supported by HP-UX 11i, as specified at http://docs.hp.com/
http://docs.hp.com/en/5187-2239/ch03s01.html.
Solaris 9 and 10
Component Requirement
Computer
SPARC (32- and 64-bit) platforms
and
processor
Memory 64 MB minimum (128 MB recommended)
Hard disk 600 MB for desktops; one GB for servers
Red Hat Enterprise Linux and Fedora Core
Component Requirement
Computer
and
processor
Memory 256 MB minimum
Hard disk 800 MB minimum
x86 for Red Hat Enterprise Linux, x86_64 for Fedora Core; see
Red Hat or Fedora websites for hardware compatibility.
10
PGP® Command Line 10.0 Installation
Mac OS X
Component Requirement
Computer
Macintosh computer, Intel-based system only
and
processor
Memory 128 MB of physical RAM
Installing on AIX
This section tells you how to install, change the home directory, and uninstall on
AIX.
Installing on AIX
You need to have root or administrator privileges on the machine on which you
are installing PGP Command Line.
To install PGP Command Line on an AIX system:
1 If you have an existing version of PGP Command Line installed on the
computer, uninstall it.
2Download the installer application called PGPCommandLine10IX.tar to a
known location on your system.
3Untar the package first. You will get the following file:
By default, the PGP Command Line application, pgp, is installed into the
directory /opt/pgp/bin. You need to add this directory to your PATH
environment variable in order for the application to be found.
For sh-based shells, use this syntax:
PATH=$PATH:/opt/pgp/bin
For csh-based shells, use this syntax:
set path = ($path /opt/pgp/bin)
Also, in order to access the PGP Command Line man page, you need to set the
MANPATH environment variable appropriately.
11
PGP® Command Line 10.0 Installation
For sh-based shells, use this syntax:
MANPATH=$MANPATH:/opt/pgp/man; export MANPATH
For csh-based shells, use this syntax:
setenv MANPATH "/opt/pgp/man"
By adding the option --prefix to the rpm command, you can install PGP
Command Line to a location other than the default.
Type rpm --prefix=/usr/pgp -ivh PGPCommandLine10AIX.rpm and
press Enter.
This command installs the application binary in the directory /usr/pgp/bin/pgp,
libraries in /usr/pgp/lib, and so on.
You will need to edit the environmental variable LIBPATH to include the new
library path (/usr/pgp/lib) so that PGP Command Line can function in a location
other than the default.
By adding the option --prefix to the rpm command, you can install PGP
Command Line in a location other than the default:
1If you have an existing version of PGP Command Line installed on the
computer, uninstall it.
2Download the installer application called PGPCommandLine10AIX.tar to
a known location on your system.
3Untar the package first. You will get the following file:
This command will install the application binary, pgp, in the directory
/usr/pgp/bin/pgp, libraries in /usr/pgp/lib, and so on.
You will need to edit the environment variable LIBPATH to include the new
library path (/usr/pgp/lib), so that PGP Command Line can function in any
location other than the default.
Changing the Home Directory on AIX
The home directory is where PGP Command Line stores the files that it creates
and uses; for example, keyring files.
By default, the PGP Command Line installer for AIX creates the PGP Command
Line home directory at $HOME/.pgp. If this directory does not exist, it will be
created. For example, if the value of $HOME for user "alice"is
/usr/home/alice, PGP Command Line will attempt to create
/usr/home/alice/.pgp.
The PGP Command Line installer will not try to create any other part of the
directory listed in the $HOME variable, only .pgp.
12
PGP® Command Line 10.0 Installation
If you want the home directory changed on a permanent basis, you will need to
create the $PGP_HOME_DIR environment variable and specify the path of the
desired home directory.
Uninstalling on AIX
Uninstalling PGP Command Line on AIX requires root privileges, either through
su or sudo.
To uninstall PGP Command Line on AIX
1 Type the following command and press Enter:
rpm -e pgpcmdln
2 PGP Command Line is uninstalled.
Installing on HP-UX
This section tells you how to install, change the home directory, and uninstall on
HP-UX.
Installing on HP-UX
You need to have root or administrator privileges on the machine on which you
are installing PGP Command Line.
To install PGP Command Line on an HP-UX system
1 If you have an existing version of PGP Command Line installed on the
computer, uninstall it.
2Download the installer file called PGPCommandLine10HPUX.tar to a
known location on your system.
3Untar the package first. You will get the following file:
PGPCommandLine10HPUX.depot
4Type: swinstall -s
/absolute/path/to/PGPCommandLine10HPUX.depot
5Press Enter.
By default, the PGP Command Line application, pgp, is installed into the
directory /opt/pgp/bin. You need to add this directory to your PATH
environment variable in order for the application to be found.
For sh-based shells, use this syntax:
13
PGP® Command Line 10.0 Installation
PATH=$PATH:/opt/pgp/bin
For csh-based shells, use this syntax:
set path = ($path /opt/pgp/bin)
Also, in order to access the PGP Command Line man page, you need to set the
MANPATH environment variable appropriately.
For sh-based shells, use this syntax:
MANPATH=$MANPATH:/opt/pgp/man; export MANPATH
For csh-based shells, use this syntax:
setenv MANPATH "/opt/pgp/man"
Note: You may encounter an issue generating 2048- or 4096-bit keys on HPUX systems running PGP Command Line if you have altered the maximum
number of shared memory segments that can be attached to one process, as
configured by the shmseg system parameter. if you encounter this issue,
reset the shmseg system parameter to its default value of 120. Consult your
HP-UX documentation for information about how to alter system parameters.
Changing the Home Directory on HP-UX
The home directory is where PGP Command Line stores the files that it creates
and uses; for example, keyring files.
By default, the PGP Command Line installer for HP-UX creates the PGP
Command Line home directory in $HOME/.pgp. If this directory does not exist,
it will be created. For example, if the value of $HOME for user "alice" is
/usr/home/alice, PGP Command Line will attempt to create
/usr/home/alice/.pgp.
The PGP Command Line installer will not try to create any other part of the
directory listed in the $HOME variable, only .pgp.
If you want the PGP Command Line home directory changed on a permanent
basis, you can define the $PGP_HOME_DIR environment variable and specify the
path of the desired home directory.
Installing to a Non-Default Directory on HP-UX
This procedure describes how to install PGP Command Line for HP-UX into a
non-default directory. The information provided is in addition to the information
provided in Installing on HP-UX.
Note: This procedure uses /opt/pgp_alt as the non-default directory. Be sure
to substitute the desired directory in place of /opt/pgp_alt.
14
PGP® Command Line 10.0 Installation
To install PGP Command Line for HP-UX to a non-default directory
1 Add the following extra argument to the swinstall command:
2 Set all libraries to respect the SHLIB_PATH environment variable:
chatr +s enable /opt/pgp_alt/lib/*
3Set the SHLIB_PATH environment variable to the new library directory
when starting PGP Command Line:
Uninstalling on HP-UX
export SHLIB_PATH=/opt/pgp_alt/lib
Uninstalling PGP Command Line on HP-UX requires root privileges, either su or
sudo.
To uninstall PGP Command Line on HP-UX:
1 Type the following command and press Enter:
swremove pgpcmdln
2 PGP Command Line is uninstalled.
Installing on Mac OS X
This section tells you how to install, change the home directory, and uninstall on
Mac OS X.
Installing on Mac OS X
To install PGP Command Line on a Mac OS X system:
1 Close all applications.
2 Download the installer application, PGPCommandLine10MacOSX.tgz, to
your desktop.
3 Double-click on the file PGPCommandLine10MacOSX.tgz.
4 If you have Stuffit Expander, it will automatically first uncompress this file
into PGPCommandLine10MacOSX.tar, and then untar it into
PGPCommandLine10MacOSX.pkg.
5 Double-click on the file PGPCommandLine10MacOSX.pkg.
15
PGP® Command Line 10.0 Installation
6 Follow the on-screen instructions.
The Mac OS X PGP Command Line application, pgp, is installed into
/usr/bin/.
After you run PGP Command Line for the first time, its home directory will be
created automatically in the directory $HOME/Documents/PGP. This directory
may already exist if PGP Desktop for Mac OS X is already installed on the
system.
Changing the Home Directory on Mac OS X
The home directory is where PGP Command Line stores the files that it creates
and uses; for example, keyring files.
By default, the PGP Command Line installer for Mac OS X creates the PGP
Command Line home directory at $HOME/Documents/PGP. If this directory
does not exist, it will be created.
The PGP Command Line installer will not try to create any other part of directory
listed in the $HOME variable, only .pgp.
If you want the home directory changed permanently, you need to create the
$PGP_HOME_DIR environment variable and specify the path of the desired
home directory.
Uninstalling on Mac OS X
Uninstalling PGP Command Line on Mac OS X requires administrative privileges.
Caution: If you have PGP Desktop for Mac OS X installed on the same
system with PGP Command Line, do not uninstall PGP Command Line unless
you also plan to uninstall PGP Desktop. Uninstalling PGP Command Line will
delete files that PGP Desktop requires to operate; you will have to reinstall
PGP Desktop to return to normal operation.
To uninstall PGP Command Line on Mac OS X:
1 Using the Terminal application, enter the following commands:
rm -rf /usr/bin/pgp
rm -rf /Library/Frameworks/PGP*
rm -rf /Library/Receipts/PGP*
2PGP Command Line is uninstalled.
Preferences and keyrings are not removed when PGP Command Line is
uninstalled.
16
Loading...
+ 309 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.