From d34eab98d034598f2e9ed96c8e3aa992cb633bc8 Mon Sep 17 00:00:00 2001 From: Ingela Anderton Andin Date: Thu, 7 May 2015 13:29:16 +0200 Subject: public_key: Correct application names and typos --- lib/public_key/doc/src/introduction.xml | 10 +++++----- lib/public_key/doc/src/public_key.xml | 12 ++++++------ lib/public_key/doc/src/records.xml | 6 +++--- lib/public_key/doc/src/using_public_key.xml | 25 +++++++++++++------------ 4 files changed, 27 insertions(+), 26 deletions(-) (limited to 'lib/public_key') diff --git a/lib/public_key/doc/src/introduction.xml b/lib/public_key/doc/src/introduction.xml index 17f4e5155a..6542c8c509 100644 --- a/lib/public_key/doc/src/introduction.xml +++ b/lib/public_key/doc/src/introduction.xml @@ -5,7 +5,7 @@
2008 - 2013 + 2015 Ericsson AB, All Rights Reserved @@ -36,7 +36,7 @@
Purpose -

The public_key application deals with public-key related file +

The Public Key application deals with public-key related file formats, digital signatures, and X-509 certificates. It is a library application that provides encode/decode, sign/verify, encrypt/decrypt, and similar @@ -54,9 +54,9 @@

Performance Tips -

The public_key decode- and encode-functions try to use the NIFs - in the ASN.1 compilers runtime modules, if they can be found. - Thus, to have the ASN.1 application in the +

The Public Key decode- and encode-functions try to use the NIFs + in the ASN.1 compilers runtime modules, if they can be found. + Thus, to have the ASN1 application in the path of your system gives the best performance.

diff --git a/lib/public_key/doc/src/public_key.xml b/lib/public_key/doc/src/public_key.xml index 3d5c135075..8a81593341 100644 --- a/lib/public_key/doc/src/public_key.xml +++ b/lib/public_key/doc/src/public_key.xml @@ -43,9 +43,9 @@ public_key - public_key requires the crypto and ASN.1 applications, - the latter as OTP R16 (hopefully the runtime dependency on ASN.1 will - be removed again in the future). + Public Key requires the Crypto and ASN1 applications, + the latter as OTP R16 (hopefully the runtime dependency on ASN1 will + be removed again in the future). Supports RFC 5280 - Internet X.509 Public-Key Infrastructure Certificate and Certificate Revocation List @@ -268,7 +268,7 @@ Decodes a public-key ASN.1 DER encoded entity. Asn1Type = atom() - ASN.1 type present in the public_key applications + ASN.1 type present in the Public Key applications ASN.1 specifications. Der = der_encoded() @@ -282,7 +282,7 @@ Encodes a public-key entity with ASN.1 DER encoding. Asn1Type = atom() - ASN.1 type present in the public_key applications + ASN.1 type present in the Public Key applications ASN.1 specifications. Entity = term() Erlang representation of Asn1Type @@ -626,7 +626,7 @@ fun(OtpCert :: #'OTPCertificate'{},

The fun uses the information in the distribution point to access the latest possible version of the CRL. If this fun is not specified, - public_key uses the default implementation: + Public Key uses the default implementation:

fun(_DP, CRL) -> CRL end diff --git a/lib/public_key/doc/src/records.xml b/lib/public_key/doc/src/records.xml index ac1ecd176c..0090278da8 100644 --- a/lib/public_key/doc/src/records.xml +++ b/lib/public_key/doc/src/records.xml @@ -5,7 +5,7 @@
2008 - 2014 + 2015 Ericsson AB, All Rights Reserved @@ -50,7 +50,7 @@

Common non-standard Erlang data types used to describe the record fields in the - following sections and which are not defined in the public_key Reference Manual follows here:

@@ -772,7 +772,7 @@ are as follows:

Here:

crl_reason() - =

unspecifiedc>

+ =

unspecified

| keyCompromise

| cACompromise

| affiliationChanged

diff --git a/lib/public_key/doc/src/using_public_key.xml b/lib/public_key/doc/src/using_public_key.xml index 69b8c0dcb9..aaf802cd34 100644 --- a/lib/public_key/doc/src/using_public_key.xml +++ b/lib/public_key/doc/src/using_public_key.xml @@ -30,8 +30,8 @@

This section describes examples of how to use the - public_key API. Keys and certificates used in the following - sections are generated only for testing the public_key + Public Key API. Keys and certificates used in the following + sections are generated only for testing the Public Key application.

Some shell printouts in the following examples @@ -43,14 +43,15 @@

Public-key data (keys, certificates, and so on) can be stored in Privacy Enhanced Mail (PEM) format. The PEM files have the following structure:

- - <text> - -----BEGIN <SOMETHING>----- - <Attribute> : <Value> - <Base64 encoded DER data> - -----END <SOMETHING>----- - <text> - + + + <text> + -----BEGIN <SOMETHING>----- + <Attribute> : <Value> + <Base64 encoded DER data> + -----END <SOMETHING>----- + <text> +

A file can contain several BEGIN/END blocks. Text lines between blocks are ignored. Attributes, if present, are ignored except for Proc-Type and DEK-Info, which are used when DER @@ -59,7 +60,7 @@

DSA Private Key

A DSA private key can look as follows:

-

File handling is not done by the public_key application.

 +

File handling is not done by the Public Key application.

 1> {ok, PemBin} = file:read_file("dsa.pem"). {ok,<<"-----BEGIN DSA PRIVATE KEY-----\nMIIBuw"...>>} @@ -364,7 +365,7 @@ ok
RSA Public-Key Cryptography -

Suppose you have the followwing private key and a corresponding public key:

+

Suppose you have the following private key and a corresponding public key:

PrivateKey = #'RSAPrivateKey{}' and the plaintext Msg = binary() -- cgit v1.2.3