Dismiss
InnovationQ/InnovationQ Plus content will be updated on Sunday, June 25, 10am ET, with new patent and non-patent literature collections. Click here to learn more.
Browse Prior Art Database

OpenPGP Message Format (RFC2440)

IP.com Disclosure Number: IPCOM000003018D
Original Publication Date: 1998-Nov-01
Included in the Prior Art Database: 2000-Sep-13

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Callas: AUTHOR [+4]

Abstract

This document is maintained in order to publish all necessary information needed to develop interoperable applications based on the OpenPGP format. It is not a step-by-step cookbook for writing an application. It describes only the format and methods needed to read, check, generate, and write conforming packets crossing any network. It does not deal with storage and implementation questions. It does,

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 2% of the total text.

Network Working Group J. Callas

Request for Comments: 2440 Network Associates

Category: Standards Track L. Donnerhacke

IN-Root-CA Individual Network e.V.

H. Finney

Network Associates

R. Thayer

EIS Corporation

November 1998

OpenPGP Message Format

Status of this Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1998). All Rights Reserved.

IESG Note

This document defines many tag values, yet it doesn't describe a

mechanism for adding new tags (for new features). Traditionally the

Internet Assigned Numbers Authority (IANA) handles the allocation of

new values for future expansion and RFCs usually define the procedure

to be used by the IANA. However, there are subtle (and not so

subtle) interactions that may occur in this protocol between new

features and existing features which result in a significant

reduction in over all security. Therefore, this document does not

define an extension procedure. Instead requests to define new tag

values (say for new encryption algorithms for example) should be

forwarded to the IESG Security Area Directors for consideration or

forwarding to the appropriate IETF Working Group for consideration.

Abstract

This document is maintained in order to publish all necessary

information needed to develop interoperable applications based on the

OpenPGP format. It is not a step-by-step cookbook for writing an

application. It describes only the format and methods needed to read,

check, generate, and write conforming packets crossing any network.

It does not deal with storage and implementation questions. It does,

however, discuss implementation issues necessary to avoid security

flaws.

Open-PGP software uses a combination of strong public-key and

symmetric cryptography to provide security services for electronic

communications and data storage. These services include

confidentiality, key management, authentication, and digital

signatures. This document specifies the message formats used in

OpenPGP.

Table of Contents

Status of this Memo 1

IESG Note 1

Abstract ...