diff options
| author | Ingela Anderton Andin <[email protected]> | 2016-02-29 15:35:26 +0100 |
|---|---|---|
| committer | Ingela Anderton Andin <[email protected]> | 2016-02-29 15:35:26 +0100 |
| commit | 291875a15a8097b61905b40a4d4385a6268db651 (patch) | |
| tree | cb6ebd9326b68b6b43ec338221ec7b4179bb8dbb /lib/gs/src/gstk_editor.erl | |
| parent | 6945d1266486d546aa1a591799591fa1e28e1b1d (diff) | |
| download | otp-291875a15a8097b61905b40a4d4385a6268db651.tar.gz otp-291875a15a8097b61905b40a4d4385a6268db651.tar.bz2 otp-291875a15a8097b61905b40a4d4385a6268db651.zip | |
public_key: An encapsulated PEM header shall be followed by a blank line
RFC 1421 Privacy Enhancement for Electronic Mail February 1993
Encapsulated Message
Pre-Encapsulation Boundary (Pre-EB)
-----BEGIN PRIVACY-ENHANCED MESSAGE-----
Encapsulated Header Portion
(Contains encryption control fields inserted in plaintext.
Examples include "DEK-Info:" and "Key-Info:".
Note that, although these control fields have line-oriented
representations similar to RFC 822 header fields, the set
of fields valid in this context is disjoint from those used
in RFC 822 processing.)
Blank Line
(Separates Encapsulated Header from subsequent
Encapsulated Text Portion)
Encapsulated Text Portion
(Contains message data encoded as specified in Section 4.3.)
Post-Encapsulation Boundary (Post-EB)
-----END PRIVACY-ENHANCED MESSAGE-----
Diffstat (limited to 'lib/gs/src/gstk_editor.erl')
0 files changed, 0 insertions, 0 deletions