Pretty Good Privacy

Pretty Good PrivacyOriginal author(s)|

* Phil Zimmermann
* PGP Inc.
* Network Associates
* PGP Corp.[1]

|

Developer(s)| Broadcom Inc.
Initial release| 1991; 35 years ago (1991)
Stable release|

11.4.0 Maintenance Pack 2 / May 23, 2023; 2 years ago (2023-05-23)[2]

Written in| C
Operating system| macOS, Windows[3]
Standard(s)|

* OpenPGP: RFC 4880, 5581, 6637, 9580
* PGP/MIME: RFC 2015, 3156

Type| Encryption software
License| Commercial proprietary software

Pretty Good Privacy (PGP) is an encryption program that provides cryptographic privacy and authentication for data communication. PGP is used for signing, encrypting, and decrypting texts, e-mails, files, directories, and whole disk partitions and to increase the security of e-mail communications. Phil Zimmermann developed PGP in 1991.[4]

PGP and similar software follow the OpenPGP standard (RFC 4880), an open standard for encrypting and decrypting data. Modern versions of PGP are interoperable with GnuPG and other OpenPGP-compliant systems.[5]

The OpenPGP standard has received criticism for its long-lived keys and the difficulty in learning it,[6] as well as the Efail security vulnerability that previously arose when select e-mail programs used OpenPGP with S/MIME.[7][8] The new OpenPGP standard (RFC 9580) has also been criticised by the maintainer of GnuPG Werner Koch, who in response created his own specification LibrePGP.[9] This response was dividing, with some embracing his alternative specification,[10] and others considering it to be insecure.[11]

## Contents

* 1 Design
* 1.1 PGP fingerprint
* 1.2 Compatibility
* 1.3 Confidentiality
* 1.4 Digital signatures
* 1.5 Web of trust
* 1.6 Certificates
* 1.7 Security quality
* 2 History
* 2.1 Early history
* 2.2 Criminal investigation
* 2.3 PGP 3 and founding of PGP Inc.
* 2.4 Network Associates acquisition
* 2.5 Asset split
* 2.5.1 McAfee
* 2.5.2 PGP Corporation
* 2.5.2.1 Symantec
* 2.5.2.2 Broadcom
* 3 PGP Corporation encryption applications
* 4 OpenPGP
* 4.1 Implementations
* 5 Limitations
* 6 See also
* 7 References
* 8 Further reading
* 9 External links

## Design

How PGP encryption works visually

PGP encryption uses a serial combination of hashing, data compression, symmetric-key cryptography, and finally public-key cryptography; each step uses one of several supported algorithms. Each public key is bound to a username or an e-mail address. The first version of this system was generally known as a web of trust to contrast with the X.509 system, which uses a hierarchical approach based on certificate authority and which was added to PGP implementations later. Current versions of PGP encryption include options through an automated key management server.

### PGP fingerprint

A public key fingerprint is a shorter version of a public key. From a fingerprint, someone can validate the correct corresponding public key. A fingerprint such as C3A6 5E46 7B54 77DF 3C4C 9790 4D22 B3CA 5B32 FF66 can be printed on a business card.[12][13]

### Compatibility

As PGP evolves, versions that support newer features and algorithms can create encrypted messages that older PGP systems cannot decrypt, even with a valid private key. Therefore, it is essential that partners in PGP communication understand each other's capabilities or at least agree on PGP settings.[14]

### Confidentiality

PGP can be used to send messages confidentially.[15] For this, PGP uses a hybrid cryptosystem by combining symmetric-key encryption and public-key encryption. The message is encrypted using a symmetric encryption algorithm, which requires a symmetric key generated by the sender. The symmetric key is used only once and is also called a session key. The message and its session key are sent to the receiver. The session key must be sent to the receiver so they know how to decrypt the message, but to protect it during transmission it is encrypted with the receiver's public key. Only the private key belonging to the receiver can decrypt the session key, and use it to symmetrically decrypt the message.

### Digital signatures

PGP supports message authentication through digital signatures to verify whether a message was actually sent by the person or entity claimed to be the sender. The sender uses PGP to create a digital signature for the message with one of several supported public-key algorithms. To do so, PGP computes a hash, or digest, from the plaintext and then creates the digital signature from that hash using the sender's private key.

### Web of trust

Main article: Web of trust

Both when encrypting messages and when verifying signatures, it is critical that the public key used to send messages to someone or some entity actually does 'belong' to the intended recipient. Simply downloading a public key from somewhere is not a reliable assurance of that association; deliberate (or accidental) impersonation is possible. From its first version, PGP has always included provisions for distributing user's public keys in an 'identity certification', which is also constructed cryptographically so that any tampering (or accidental garble) is readily detectable. However, merely making a certificate that is impossible to modify without being detected is insufficient; this can prevent corruption only after the certificate has been created, not before. Users must also ensure by some means that the public key in a certificate actually does belong to the person or entity claiming it. A given public key (or more specifically, information binding a user name to a key) may be digitally signed by a third-party user to attest to the association between someone (actually a user name) and the key. There are several levels of confidence that can be included in such signatures. Although many programs read and write this information, few (if any) include this level of certification when calculating whether to trust a key.

The web of trust protocol was first described by Phil Zimmermann in 1992, in the manual for PGP version 2.0:

> As time goes on, you will accumulate keys from other people that you may want to designate as trusted introducers. Everyone else will each choose their own trusted introducers. And everyone will gradually accumulate and distribute with their key a collection of certifying signatures from other people, with the expectation that anyone receiving it will trust at least one or two of the signatures. This will cause the emergence of a decentralized fault-tolerant web of confidence for all public keys.

The web of trust mechanism has advantages over a centrally managed public key infrastructure scheme such as that used by S/MIME but has not been universally used. Users have to be willing to accept certificates and check their validity manually or have to simply accept them. No satisfactory solution has been found for the underlying problem.

### Certificates

Main article: Public key certificate

In the (more recent) OpenPGP specification, trust signatures can be used to support creation of certificate authorities. A trust signature indicates both that the key belongs to its claimed owner and that the owner of the key is trustworthy to sign other keys at one level below their own. A level 0 signature is comparable to a web of trust signature since only the validity of the key is certified. A level 1 signature is similar to the trust one has in a certificate authority because a key signed to level 1 is able to issue an unlimited number of level 0 signatures. A level 2 signature is highly analogous to the trust assumption users must rely on whenever they use the default certificate authority list (like those included in web browsers); it allows the owner of the key to make other keys certificate authorities.

PGP versions have always included a way to cancel ('revoke') public key certificates. A lost or compromised private key will require this if communication security is to be retained by that user. This is, more or less, equivalent to the certificate revocation lists of centralised PKI schemes. Recent PGP versions have also supported certificate expiration dates.

The problem of correctly identifying a public key as belonging to a particular user is not unique to PGP. All public key/private key cryptosystems have the same problem, even if in slightly different guises, and no fully satisfactory solution is known. PGP's original scheme at least leaves the decision as to whether or not to use its endorsement/vetting system to the user, while most other PKI schemes do not, requiring instead that every certificate attested to by a central certificate authority be accepted as correct.

### Security quality

To the best of publicly available information, there is no known method which will allow a person or group to break PGP encryption by cryptographic or computational means. Indeed, in 1995, cryptographer Bruce Schneier characterized an early version as being "the closest you're likely to get to military-grade encryption."[16] Early versions of PGP have been found to have theoretical vulnerabilities and so current versions are recommended.[17] In addition to protecting data in transit over a network, PGP encryption can also be used to protect data in long-term data storage such as disk files. These long-term storage options are also known as data at rest, i.e. data stored, not in transit.

The cryptographic security of PGP encryption depends on the assumption that the algorithms used are unbreakable by direct cryptanalysis with current equipment and techniques.

In the original version, the RSA algorithm was used to encrypt session keys. RSA's security depends upon the one-way function nature of mathematical integer factoring.[18] Similarly, the symmetric key algorithm used in PGP version 2 was IDEA, which might at some point in the future be found to have previously undetected cryptanalytic flaws. Specific instances of current PGP or IDEA insecurities (if they exist) are not publicly known. As current versions of PGP have added additional encryption algorithms, their cryptographic vulnerability varies with the algorithm used. However, none of the algorithms in current use are publicly known to have cryptanalytic weaknesses.

New versions of PGP are released periodically and vulnerabilities fixed by developers as they come to light. Any agency wanting to read PGP messages would probably use easier means than standard cryptanalysis, e.g. rubber-hose cryptanalysis or black-bag cryptanalysis (e.g. installing some form of trojan horse or keystroke logging software/hardware on the target computer to capture encrypted keyrings and their passwords). The FBI has already used this attack against PGP[19][20] in its investigations. However, any such vulnerabilities apply not just to PGP but to any conventional encryption software.

In 2003, an incident involving seized Psion PDAs belonging to members of the Red Brigade indicated that neither the Italian police nor the FBI were able to decrypt PGP-encrypted files stored on them.[21] A second incident in December 2006, (see In re Boucher), involving US customs agents who seized a laptop PC that allegedly contained child pornography, indicates that US government agencies find it "nearly impossible" to access PGP-encrypted files. Additionally, a magistrate judge ruling on the case in November 2007 has stated that forcing the suspect to reveal his PGP passphrase would violate his Fifth Amendment rights i.e. a suspect's constitutional right not to incriminate himself.[22][23] The Fifth Amendment issue was opened again as the government appealed the case, after which a federal district judge ordered the defendant to provide the key.[24]

Evidence suggests that as of 2007[update], British police investigators are unable to break PGP,[25] so instead have resorted to using RIPA legislation to demand the passwords/keys. In November 2009 a British citizen was convicted under RIPA legislation and jailed for nine months for refusing to provide police investigators with encryption keys to PGP-encrypted files.[26]

PGP as a cryptosystem has been criticized for complexity of the standard, implementation and very low usability of the user interface[27] including by recognized figures in cryptography research.[28][29] It uses an ineffective serialization format for storage of both keys and encrypted data, which resulted in signature-spamming attacks on public keys of prominent developers of GNU Privacy Guard. Backwards compatibility of the OpenPGP standard results in usage of relatively weak default choices of cryptographic primitives (CAST5 cipher, CFB mode, S2K password hashing).[30] The standard has been also criticized for leaking metadata, usage of long-term keys and lack of forward secrecy. Popular end-user implementations have suffered from various signature-striping, cipher downgrade and metadata leakage vulnerabilities which have been attributed to the complexity of the standard.[31]

## History

### Early history

Phil Zimmermann created the first version of PGP encryption in 1991. The name, "Pretty Good Privacy" was inspired by the name of a grocery store, "Ralph's Pretty Good Grocery", featured in radio host Garrison Keillor's fictional town, Lake Wobegon.[32] This first version included a symmetric-key algorithm that Zimmermann had designed himself, named BassOmatic after a Saturday Night Live sketch. Zimmermann had been a long-time anti-nuclear activist, and created PGP encryption so that similarly inclined people might securely use BBSs and securely store messages and files. No license fee was required for its non-commercial use, and the complete source code was included with all copies.

In a posting of June 5, 2001, entitled "PGP Marks 10th Anniversary",[33] Zimmermann describes the circumstances surrounding his release of PGP:

> It was on this day in 1991 that I sent the first release of PGP to a couple of my friends for uploading to the Internet. First, I sent it to Allan Hoeltje, who posted it to Peacenet, an ISP that specialized in grassroots political organizations, mainly in the peace movement. Peacenet was accessible to political activists all over the world. Then, I uploaded it to Kelly Goen, who proceeded to upload it to a Usenet newsgroup that specialized in distributing source code. At my request, he marked the Usenet posting as "US only". Kelly also uploaded it to many BBS systems around the country. I don't recall if the postings to the Internet began on June 5th or 6th.

> It may be surprising to some that back in 1991, I did not yet know enough about Usenet newsgroups to realize that a "US only" tag was merely an advisory tag that had little real effect on how Usenet propagated newsgroup postings. I thought it actually controlled how Usenet routed the posting. But back then, I had no clue how to post anything on a newsgroup, and didn't even have a clear idea what a newsgroup was.

PGP found its way onto the Internet and rapidly acquired a considerable following around the world. Users and supporters included dissidents in totalitarian countries (some affecting letters to Zimmermann have been published, some of which have been included in testimony before the US Congress), civil libertarians in other parts of the world (see Zimmermann's published testimony in various hearings), and the 'free communications' activists who called themselves cypherpunks (who provided both publicity and distribution); decades later, CryptoParty activists did much the same via Twitter.

### Criminal investigation

Shortly after its release, PGP encryption found its way outside the United States, and in February 1993 Zimmermann became the formal target of a criminal investigation by the US Government for "munitions export without a license". At the time, cryptosystems using keys larger than 40 bits were considered munitions within the definition of the US export regulations; PGP has never used keys smaller than 128 bits, so it qualified at that time. Penalties for violation, if found guilty, were substantial. After several years, the investigation of Zimmermann was closed without filing criminal charges against him or anyone else.

Zimmermann challenged these regulations in an imaginative way. In 1995, he published the entire source code of PGP in a hardback book,[34] via MIT Press, which was distributed and sold widely. Anybody wishing to build their own copy of PGP could cut off the covers, separate the pages, and scan them using an OCR program (or conceivably enter it as a type-in program if OCR software was not available), creating a set of source code text files. One could then build the application using the freely available GNU Compiler Collection. PGP would thus be available anywhere in the world. The claimed principle was simple: export of munitions—guns, bombs, planes, and software—was (and remains) restricted; but the export of books is protected by the First Amendment. The question was never tested in court with respect to PGP. In cases addressing other encryption software, however, two federal appeals courts have established the rule that cryptographic software source code is speech protected by the First Amendment (the Ninth Circuit Court of Appeals in the Bernstein case and the Sixth Circuit Court of Appeals in the Junger case).

US export regulations regarding cryptography remain in force, but were liberalized substantially throughout the late 1990s. Since 2000, compliance with the regulations is also much easier. PGP encryption no longer meets the definition of a non-exportable weapon, and can be exported internationally except to seven specific countries and a list of named groups and individuals[35] (with whom substantially all US trade is prohibited under various US export controls).

The criminal investigation was dropped in 1996.[36]

### PGP 3 and founding of PGP Inc.

During this turmoil, Zimmermann's team worked on a new version of PGP encryption called PGP 3. This new version was to have considerable security improvements, including a new certificate structure that fixed small security flaws in the PGP 2.x certificates as well as permitting a certificate to include separate keys for signing and encryption. Furthermore, the experience with patent and export problems led them to eschew patents entirely. PGP 3 introduced the use of the CAST-128 (a.k.a. CAST5) symmetric key algorithm, and the DSA and ElGamal asymmetric key algorithms, all of which were unencumbered by patents.

After the Federal criminal investigation ended in 1996, Zimmermann and his team started a company to produce new versions of PGP encryption. They merged with Viacrypt (to whom Zimmermann had sold commercial rights and who had licensed RSA directly from RSADSI), which then changed its name to PGP Incorporated. The newly combined Viacrypt/PGP team started work on new versions of PGP encryption based on the PGP 3 system. Unlike PGP 2, which was an exclusively command line program, PGP 3 was designed from the start as a software library allowing users to work from a command line or inside a GUI environment. The original agreement between Viacrypt and the Zimmermann team had been that Viacrypt would have even-numbered versions and Zimmermann odd-numbered versions. Viacrypt, thus, created a new version (based on PGP 2) that they called PGP 4. To remove confusion about how it could be that PGP 3 was the successor to PGP 4, PGP 3 was renamed and released as PGP 5 in May 1997.

### Network Associates acquisition

In December 1997, PGP Inc. was acquired by Network Associates, Inc. ("NAI"). Zimmermann and the PGP team became NAI employees. NAI was the first company to have a legal export strategy by publishing source code. Under NAI, the PGP team added disk encryption, desktop firewalls, intrusion detection, and IPsec VPNs to the PGP family. After the export regulation liberalizations of 2000 which no longer required publishing of source, NAI stopped releasing source code.[37]

### Asset split

In early 2001, Zimmermann left NAI. He served as Chief Cryptographer for Hush Communications, who provide an OpenPGP-based e-mail service, Hushmail. He has also worked with Veridis and other companies. In October 2001, NAI announced that its PGP assets were for sale and that it was suspending further development of PGP encryption. The only remaining asset kept was the PGP E-Business Server (the original PGP Commandline version). In February 2002, NAI canceled all support for PGP products, with the exception of the renamed commandline product.[38][39]

#### McAfee

NAI, now known as McAfee, continued to sell and support the commandline product under the name McAfee E-Business Server until 2013.[40] In 2010, Intel Corporation acquired McAfee. In 2013, the McAfee E-Business Server was transferred to Software Diversified Services (SDS), which now sells, supports, and develops it under the name SDS E-Business Server.[40][38]

For the enterprise, Townsend Security currently[when?] offers a commercial version of PGP for the IBM i and IBM z mainframe platforms. Townsend Security partnered with Network Associates in 2000 to create a compatible version of PGP for the IBM i platform. Townsend Security again ported PGP in 2008, this time to the IBM z mainframe. This version of PGP relies on a free z/OS encryption facility, which utilizes hardware acceleration. SDS also offers a commercial version of PGP (SDS E-Business Server) for the IBM z mainframe.

#### PGP Corporation

In August 2002, several ex-PGP team members formed a new company, PGP Corporation, and bought the PGP assets (except for the command line version) from NAI. The new company was funded by Rob Theis of Doll Capital Management (DCM) and Terry Garnett of Venrock Associates. PGP Corporation supported existing PGP users and honored NAI's support contracts. Zimmermann served as a special advisor and consultant to PGP Corporation while continuing to run his own consulting company. In 2003, PGP Corporation created a new server-based product called PGP Universal. In mid-2004, PGP Corporation shipped its own command line version called PGP Command Line, which integrated with the other PGP Encryption Platform applications. In 2005, PGP Corporation made its first acquisition: the German software company Glück & Kanja Technology AG,[41] which became PGP Deutschland AG.[42] In 2010, PGP Corporation acquired Hamburg-based certificate authority TC TrustCenter and its parent company, ChosenSecurity, to form its PGP TrustCenter[43] division.[44]

After the 2002 purchase of NAI's PGP assets, PGP Corporation offered worldwide PGP technical support from its offices in Draper, Utah; Offenbach, Germany; and Tokyo, Japan.

##### Symantec

On April 29, 2010, Symantec Corp. announced that it would acquire PGP Corporation for $300 million with the intent of integrating it into its Enterprise Security Group.[45] This acquisition was finalized and announced to the public on June 7, 2010. The source code of PGP Desktop 10 is available for peer review.[46]

In May 2018, a bug named EFAIL was discovered in certain implementations of PGP which from 2003 could reveal the plaintext contents of emails encrypted with it.[47][48] The chosen mitigation for this vulnerability in PGP Desktop is to mandate the use SEIP protected packets in the ciphertext, which can lead to old emails or other encrypted objects to be no longer decryptable after upgrading to the software version that has the mitigation.[49]

##### Broadcom

On August 9, 2019, Broadcom Inc. announced they would be acquiring the Enterprise Security software division of Symantec, which includes PGP Corporation.

## PGP Corporation encryption applications

This section describes commercial programs available from PGP Corporation. For information on other programs compatible with the OpenPGP specification, see External links below.

While originally used primarily for encrypting the contents of e-mail messages and attachments from a desktop client, PGP products have been diversified since 2002 into a set of encryption applications that can be managed by an optional central policy server. PGP encryption applications include e-mails and attachments, digital signatures, full disk encryption, file and folder security, protection for IM sessions, batch file transfer encryption, and protection for files and folders stored on network servers and, more recently, encrypted or signed HTTP request/responses by means of a client-side (Enigform) and a server-side (mod openpgp) module. There is also a WordPress plugin available, called wp-enigform-authentication, that takes advantage of the session management features of Enigform with mod_openpgp.

The PGP Desktop 9.x family includes PGP Desktop Email, PGP Whole Disk Encryption, and PGP NetShare. Additionally, a number of Desktop bundles are also available. Depending on the application, the products feature desktop e-mail, digital signatures, IM security, whole disk encryption, file, and folder security, encrypted self-extracting archives, and secure shredding of deleted files. Capabilities are licensed in different ways depending on the features required.

The PGP Universal Server 2.x management console handles centralized deployment, security policy, policy enforcement, key management, and reporting. It is used for automated e-mail encryption in the gateway and manages PGP Desktop 9.x clients. In addition to its local keyserver, PGP Universal Server works with the PGP public keyserver—called the PGP Global Directory—to find recipient keys. It has the capability of delivering e-mail securely when no recipient key is found via a secure HTTPS browser session.

With PGP Desktop 9.x managed by PGP Universal Server 2.x, first released in 2005, all PGP encryption applications are based on a new proxy-based architecture. These newer versions of PGP software eliminate the use of e-mail plug-ins and insulate the user from changes to other desktop applications. All desktop and server operations are now based on security policies and operate in an automated fashion. The PGP Universal server automates the creation, management, and expiration of keys, sharing these keys among all PGP encryption applications.

The Symantec PGP platform has now undergone a rename. PGP Desktop is now known as Symantec Encryption Desktop (SED), and the PGP Universal Server is now known as Symantec Encryption Management Server (SEMS). The current shipping versions are Symantec Encryption Desktop 10.3.0 (Windows and macOS platforms) and Symantec Encryption Server 3.3.2.

Also available are PGP Command-Line, which enables command line-based encryption and signing of information for storage, transfer, and backup, as well as the PGP Support Package for BlackBerry which enables RIM BlackBerry devices to enjoy sender-to-recipient messaging encryption.

New versions of PGP applications use both OpenPGP and the S/MIME, allowing communications with any user of a NIST specified standard.[50]

## OpenPGP

OpenPGP is on the Internet Standards Track and is under active development. Many e-mail clients provide OpenPGP-compliant email security as described in RFC 3156. The current specification is RFC 9580 (July 2024), the successor to RFC 4880. RFC 9580 specifies a suite of required algorithms consisting of X25519, Ed25519, SHA2-256 and AES-128. In addition to these algorithms, the standard recommends X448, Ed448, SHA2-384, SHA2-512 and AES-256. Beyond these, many other algorithms are supported.

* PGP
* RFC 1991 PGP Message Exchange Formats (obsolete)[51]
* OpenPGP
* RFC 2440 OpenPGP Message Format (obsolete)[51]
* RFC 4880 OpenPGP Message Format (obsolete)
* RFC 5581 The Camellia Cipher in OpenPGP (obsolete)
* RFC 6637 Elliptic Curve Cryptography (ECC) in OpenPGP (obsolete)
* RFC 9580 OpenPGP
* PGP/MIME
* RFC 2015 MIME Security with Pretty Good Privacy (PGP)
* RFC 3156 MIME Security with OpenPGP

OpenPGP's encryption can ensure the secure delivery of files and messages, as well as provide verification of who created or sent the message using a process called digital signing. The open source office suite LibreOffice implemented document signing with OpenPGP as of version 5.4.0 on Linux.[52] Using OpenPGP for communication requires participation by both the sender and recipient. OpenPGP can also be used to secure sensitive files when they are stored in vulnerable places like mobile devices or in the cloud.[53] In late 2023, a schism occurred in the OpenPGP world: IETF's OpenPGP working group decided to choose a "crypto-refresh" update strategy for the RFC 4880 specification, rather than a more gradual "4880bis" path preferred by Werner Koch, author of GnuPG. As a result, Koch took his draft, now abandoned by the workgroup, and forked it into a "LibrePGP" specification.[9]

### Implementations

The Free Software Foundation has developed its own OpenPGP-compliant software suite called GNU Privacy Guard, freely available together with all source code under the GNU General Public License and is maintained separately from several graphical user interfaces that interact with the GnuPG library for encryption, decryption, and signing functions (see KGPG, Seahorse, MacGPG).Template:Undue inline Several other vendors have also developed OpenPGP-compliant software.

The development of an open source OpenPGP-compliant library, OpenPGP.js, written in JavaScript and supported by the Horizon 2020 Framework Programme of the European Union,[54] has allowed web-based applications to use PGP encryption in the web browser.

PGP keys are supported in Mozilla Thunderbird (Built-in in version 78 onwards on PC,[55] and with the OpenKeychain app as of version 9 on Android[56]), GitHub,[57] and GitLab.[58]

## Limitations

With the advancement of cryptography, parts of PGP and OpenPGP have been criticized for being dated:

* The long length of PGP public keys, caused by the use of RSA and additional data other than the actual cryptographic key[59]
* Lack of forward secrecy[59]
* Use of outdated algorithms by default in several implementations[59]
* Difficulty for the users to comprehend and poor usability[29]
* Lack of ubiquity[29]

In October 2017, the ROCA vulnerability was announced, which affects RSA keys generated by buggy Infineon firmware used on Yubikey 4 tokens, often used with OpenPGP. Many published PGP keys were found to be susceptible.[60] Yubico offers free replacement of affected tokens.[61]

## See also

* Bernstein v. United States
* Electronic envelope
* Email encryption
* Email privacy
* GNU Privacy Guard
* Gpg4win
* Key server (cryptographic)
* PGP word list
* PGPDisk
* Pretty Easy privacy
* Privacy software
* Public-key cryptography
* S/MIME
* X.509
* ZRTP

## References

1. ↑ "Where to Get PGP". Phil Zimmermann & Associates LLC. 28 February 2006. https://philzimmermann.com/EN/findpgp/.
2. ↑ "Symantec Endpoint Encryption 11.4.0 Maintenance Pack 2 Release Notes". https://techdocs.broadcom.com/us/en/symantec-security-software/information-security/encryption/11-4-0/release-notes-main-page/see-11-4-0-maintenance-pack-2-release-notes.html.
3. ↑ "System requirements for Symantec Endpoint Encryption Client". https://techdocs.broadcom.com/us/en/symantec-security-software/information-security/encryption/11-4-0/sys-req-home-page/see-client-sys-req.html.
4. ↑ Zimmermann, Philip R. (1999). "Why I Wrote PGP". Phil Zimmermann & Associates LLC. https://www.philzimmermann.com/EN/essays/WhyIWrotePGP.html.
5. ↑ "Gnu Privacy Guard". GnuPG.org. https://www.gnupg.org/faq/gnupg-faq.html#compatible.
6. ↑ Latacora (2019-07-16). "The PGP Problem" (in en). https://www.latacora.com/blog/2019/07/16/the-pgp-problem.
7. ↑ "Efail: Breaking S/MIME and OpenPGP Email Encryption using Exfiltration Channels". https://www.usenix.org/system/files/conference/usenixsecurity18/sec18-poddebniak.pdf.
8. ↑ Yen, Andy (2018-05-15). "No, PGP is not broken, not even with the Efail vulnerabilities". https://proton.me/blog/pgp-vulnerability-efail.
9. ↑ 9.0 9.1 "A schism in the OpenPGP world [LWN.net"]. https://lwn.net/Articles/953797/.
10. ↑ Tse, Ronald; Olshevsky, Nickolay (2024-07-22). "RNP proudly supports LibrePGP". https://www.rnpgp.org/blog/2024-07-22-rnp-and-librepgp.
11. ↑ Gallagher, Andrew (2024-09-11). "A Summary of Known Security Issues in LibrePGP". https://blog.pgpkeys.eu/security-issues-librepgp-2024-08.html.
12. ↑ Furley, Paul M. "PGP public key example". There are shorter ways of referring to PGP keys. https://www.paulfurley.com/pgp-public-key-example/. "can print it on my business card instead of trying to print my whole public key"
13. ↑ Marcia Hofmann [@marciahofmann] (20 January 2015). "my new business card (with image)". https://twitter.com/marciahofmann/status/557692432494915584.
14. ↑ "PGP User's Guide, Volume II: Special Topics". https://web.pa.msu.edu/reference/pgpdoc2.html.
15. ↑ Atkins, D.; Stallings, W.; Zimmermann, P. (August 1996), PGP Message Exchange Formats, doi:10.17487/RFC1991, RFC 1991, https://tools.ietf.org/html/rfc1991
16. ↑ Schneier, Bruce (October 9, 1995). Applied Cryptography. New York: Wiley. p. 587. ISBN 0-471-11709-9.
17. ↑ Messmer, Ellen (August 28, 2000). "Security flaw found in Network Associates' PGP". Network World (Southbourough, Massachusetts: IDG) 17 (35): 81. https://books.google.com/books?id=JxkEAAAAMBAJ&pg=PA81. Retrieved May 2, 2017.
18. ↑ Nichols, Randall (1999). ICSA Guide to Cryptography. McGraw Hill. p. 267. ISBN 0-07-913759-8.
19. ↑ "United States v. Scarfo (Key-Logger Case)". Epic.org. https://www.epic.org/crypto/scarfo.html.
20. ↑ McCullagh, Declan (July 10, 2007). "Feds use keylogger to thwart PGP, Hushmail | Tech news blog – CNET News.com". News.com. https://www.cnet.com/news/feds-use-keylogger-to-thwart-pgp-hushmail/.
21. ↑ Grigg, Ian (2003). "PGP Encryption Proves Powerful". https://www.metzdowd.com/pipermail/cryptography/2003-May/004808.html.
22. ↑ McCullagh, Declan (December 14, 2007). "Judge: Man can't be forced to divulge encryption passphrase | The Iconoclast - politics, law, and technology - CNET News.com". News.com. https://www.news.com/8301-13578_3-9834495-38.html?tag=nefd.blgs.
23. ↑ McCullagh, Declan (January 18, 2008). "Feds appeal loss in PGP compelled-passphrase case | The Iconoclast - politics, law, and technology - CNET News.com". News.com. https://www.news.com/8301-13578_3-9854034-38.html.
24. ↑ McCullagh, Declan (February 26, 2009). "Judge orders defendant to decrypt PGP-protected laptop". CNET news. https://www.cnet.com/news/judge-orders-defendant-to-decrypt-pgp-protected-laptop/.
25. ↑ John Leyden (November 14, 2007). "Animal rights activist hit with RIPA key decrypt demand". The Register. https://www.theregister.co.uk/2007/11/14/ripa_encryption_key_notice.
26. ↑ Chris Williams (November 24, 2009). "UK jails schizophrenic for refusal to decrypt files". The Register: p. 2. https://www.theregister.co.uk/2009/11/24/ripa_jfl/page2.html.
27. ↑ Staff, Ars (2016-12-10). "Op-ed: I'm throwing in the towel on PGP, and I work in security" (in en-us). https://arstechnica.com/information-technology/2016/12/op-ed-im-giving-up-on-pgp/.
28. ↑ "What's the matter with PGP?" (in en). 2014-08-13. https://blog.cryptographyengineering.com/2014/08/13/whats-matter-with-pgp/.
29. ↑ 29.0 29.1 29.2 Marlinspike, Moxie (February 24, 2015). "GPG And Me". https://moxie.org/2015/02/24/gpg-and-me.html.
30. ↑ "Latacora - The PGP Problem". July 16, 2019. https://latacora.micro.blog/2019/07/16/the-pgp-problem.html.
31. ↑ "Efail: Breaking S/MIME and OpenPGP Email Encryption using Exfiltration Channels". https://www.usenix.org/system/files/conference/usenixsecurity18/sec18-poddebniak.pdf.
32. ↑ Holtsnider, Bill; Jaffe, Brian D. (2006). IT manager's handbook: getting your new job done (2nd ed.). Morgan Kaufmann. p. 373. ISBN 978-0-08-046574-6. https://books.google.com/books?id=OeQD_QPOYY4C&pg=PA373.
33. ↑ "PGP Marks 10th Anniversary". Phil Zimmermann. https://www.philzimmermann.com/EN/news/PGP_10thAnniversary.html.
34. ↑ Zimmermann, Philip (1995). PGP Source Code and Internals. MIT Press. ISBN 0-262-24039-4.
35. ↑ "Lists to Check". US Department of Commerce, Bureau of Industry and Security. https://www.bis.doc.gov/complianceandenforcement/liststocheck.htm.
36. ↑ Zimmermann, Phil. "Significant Moments in PGP's History: Zimmermann Case Dropped". https://philzimmermann.com/EN/news/PRZ_case_dropped.html. "The U.S. Attorney's Office for the Northern District of California has decided that your client, Philip Zimmermann, will not be prosecuted in connection with the posting to USENET in June 1991 of the encryption program Pretty Good Privacy. The investigation is closed." - page also contains NPR morning radio recording on this matter
37. ↑ "Important Information About PGP & Encryption". proliberty.com. https://www.proliberty.com/references/pgp/.
38. ↑ 38.0 38.1 "Long Live E-Business Server for Enterprise-Scale Encryption". 2013-08-11. https://www.sdsusa.com/newsdocs/130811.sds.ebs.pdf.
39. ↑ Conger, Kate (2017-04-03). "Intel Security is McAfee again" (in en-us). TechCrunch. https://techcrunch.com/2017/04/03/intel-security-is-mcafee-again.
40. ↑ 40.0 40.1 "McAfee partners with Software Diversified Services to deliver E-Business Server sales and support". 2014-01-17. https://kc.mcafee.com/corporate/index?page=content&id=KB79203.
41. ↑ "glueckkanja.com". glueckkanja.com. https://glueckkanja.com/.
42. ↑ "pgp.de". pgp.de. https://pgp.de/.
43. ↑ "pgptrustcenter.com". pgptrustcenter.com. January 26, 2010. https://www.pgptrustcenter.com.
44. ↑ "News Room – Symantec Corp". Pgp.com. https://www.pgp.com/insight/newsroom/press_releases/pgp_corporation_acquires_chosensecurity.html.
45. ↑ "Symantec buys encryption specialist PGP for $300M". Computerworld. April 29, 2010. https://www.computerworld.com/s/article/9176121/Symantec_buys_encryption_specialist_PGP_for_300M.
46. ↑ "Symantec PGP Desktop Peer Review Source Code". Symantec.com. September 23, 2012. https://www.symantec.com/connect/downloads/symantec-pgp-desktop-peer-review-source-code.
47. ↑ "Critical PGP and S/MIME bugs can reveal encrypted emails—uninstall now [Updated"]. May 14, 2018. https://arstechnica.com/information-technology/2018/05/critical-pgp-and-smime-bugs-can-reveal-encrypted-e-mails-uninstall-now/.
48. ↑ "EFAIL" (in en-US). https://efail.de/.
49. ↑ "Cannot decrypt PGP Zip files created with earlier releases of Encryption Desktop" (in en-US). https://knowledge.broadcom.com/external/article/173613/cannot-decrypt-pgp-zip-files-created-wit.html.
50. ↑ "Archived NIST Technical Series Publication". nist.gov. https://nvlpubs.nist.gov/nistpubs/specialpublications/nist.sp.800-177.pdf.
51. ↑ 51.0 51.1 David, Shaw; Lutz, Donnerhacke; Rodney, Thayer; Hal, Finney; Jon, Callas (2007) (in en). OpenPGP Message Format. doi:10.17487/RFC4880. https://tools.ietf.org/html/rfc4880. Retrieved April 19, 2018.
52. ↑ "OpenPGP signature support in LibreOffice". 28 July 2017. https://blog.thebehrens.net/2017/07/28/openpgp-signature-support-in-libreoffice/.
53. ↑ Geier, Eric (2014-08-22). "How to use OpenPGP to encrypt your email messages and files in the cloud". https://www.pcworld.com/article/2472771/how-to-use-openpgp-to-encrypt-your-email-messages-and-files-in-the-cloud.html.
54. ↑ OpenPGPjs-Team. "OpenPGPjs". https://openpgpjs.org/.
55. ↑ "Thunderbird 78 Has Finally Got Built-In Calendar And OpenPGP Support". LinuxReviews. 8 October 2020. https://linuxreviews.org/Thunderbird_78_Has_Finally_Got_Built-In_Calendar_And_OpenPGP_Support.
56. ↑ Jack Wallen (13 November 2024). "How to add PGP support on Android for added security and privacy". ZDNET. https://www.zdnet.com/article/how-to-add-pgp-support-on-android-for-added-security-and-privacy/.
57. ↑ "Using GPG keys on GitHub: Creating and updating expired keys". Inspirezone. 18 April 2021. https://inspirezone.tech/using-gpg-keys-on-github/.
58. ↑ Madison Moore (23 August 2025). "GitLab 9.5, Xcode 9, IEEE standard for quantum computing, and Chrome Enterprise — SD Times news digest: August 23, 2017". SD Times. https://sdtimes.com/automation/gitlab-xcode-chrome-enterprise-sdtimes-newsdigest/.
59. ↑ 59.0 59.1 59.2 Green, Matthew (August 13, 2014). "What's the matter with PGP?". A Few Thoughts on Cryptographic Engineering. https://blog.cryptographyengineering.com/2014/08/13/whats-matter-with-pgp/.
60. ↑ Nemec, Matus; Sys, Marek; Svenda, Petr; Klinec, Dusan; Matyas, Vashek (2017). "The Return of Coppersmith's Attack: Practical Factorization of Widely Used RSA Moduli". https://crocs.fi.muni.cz/_media/public/papers/nemec_roca_ccs17_preprint.pdf.
61. ↑ "Yubico Replacement Program". https://www.yubico.com/keycheck/verify_otp.

## Further reading

* Garfinkel, Simson (1995). PGP: Pretty Good Privacy. O'Reilly & Associates. ISBN 1-56592-098-8.
* Levy, Steven (January 8, 2001). Crypto: How the Code Rebels Beat the Government—Saving Privacy in the Digital Age. Penguin Books. ISBN 0140244328.
* Lucas, Michael W. (April 1, 2006). PGP & GPG Email for the Practical Paranoid. No Starch Press. ISBN 978-1-59327-071-1.
* Zimmermann, Phil (June 1991). "Why I Wrote PGP". https://www.philzimmermann.com/EN/essays/WhyIWrotePGP.html.

## External links

* OpenPGP::SDK
* MIT Public Key Directory for Registration and Search
* List of public keyservers
* IETF OpenPGP working group
* OpenPGP Alliance

* v
* t
* e

Cryptographic software

Email clients|

* Apple Mail
* Autocrypt
* Claws Mail
* Enigmail
* GPG (Gpg4win)
* Kontact
* Outlook
* p≡p
* PGP
* Sylpheed
* Thunderbird

Secure
communication|

| OTR|

* Adium
* BitlBee
* Centericq
* ChatSecure
* climm
* Jitsi
* Kopete
* MCabber
* Profanity

|

SSH|

* Dropbear
* lsh
* OpenSSH
* PuTTY
* SecureCRT
* WinSCP
* wolfSSH

TLS & SSL|

* Bouncy Castle
* BoringSSL
* Botan
* cryptlib
* GnuTLS
* JSSE
* LibreSSL
* MatrixSSL
* NSS
* OpenSSL
* mbed TLS
* RSA BSAFE
* SChannel
* SSLeay
* stunnel
* wolfSSL

VPN|

* Check Point VPN-1
* Hamachi
* Openswan
* OpenVPN
* SoftEther VPN
* strongSwan
* Tinc
* WireGuard

ZRTP|

* CSipSimple
* Jitsi
* Linphone
* Jami
* Zfone

P2P|

* Bitmessage
* RetroShare
* Tox

DRA|

* Matrix
* OMEMO
* Conversations
* Cryptocat
* ChatSecure
* Proteus
* Signal Protocol
* Google Allo
* Facebook Messenger
* Signal
* TextSecure
* WhatsApp

Disk encryption
(Comparison)|

* BestCrypt
* BitLocker
* CrossCrypt
* Cryptoloop
* DiskCryptor
* dm-crypt
* DriveSentry
* E4M
* eCryptfs
* FileVault
* FreeOTFE
* GBDE
* geli
* LUKS
* PGPDisk
* Private Disk
* Scramdisk
* Sentry 2020
* TrueCrypt
* History
* VeraCrypt

Anonymity|

* GNUnet
* I2P
* Java Anon Proxy
* Tor
* Vidalia
* RetroShare
* Ricochet
* Wickr

File systems (List)|

* EncFS
* EFS
* eCryptfs
* LUKS
* PEFS
* Rubberhose
* StegFS
* Tahoe-LAFS

Service providers|

* Freenet
* Tresorit
* Wuala

Educational|

* CrypTool

Related topics|

* Outline of cryptography
* Timeline of cryptography
* Hash functions
* Cryptographic hash function
* List of hash functions
* S/MIME

* Category
* Commons

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Pretty Good Privacy. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Software:Pretty_Good_Privacy&oldid=3966740"
*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template