The openssl package implements a modern
interface to libssl and libcrypto for R. It builds on the new
EVP api which was introduced in OpenSSL 1.0 and provides a
unified API to the various methods and formats. OpenSSL supports three
major public key crypto systems:
For each type there are several common formats for storing keys and certificates:
===The openssl package automatically detects the format when possible. However being able to recognize the various formats can be useful.
DER is the standard binary format using by protocols for storing and exchanging keys and certificates. It consists of a serialized ASN.1 structure which hold the key’s (very large) prime numbers.
[1] 30 59 30 13 06 07 2a 86 48 ce 3d 02 01 06 08 2a 86 48 ce 3d 03 01 07 03 42
[26] 00 04 31 fb 49 bf 84 1f 65 2f 9a d8 4b d5 fd 4a 65 5b b7 b5 f6 25 dc 6d 8c
[51] 52 8b 13 8e 69 92 3c a7 2a 87 db 98 af 33 39 95 b0 28 95 e0 43 b9 69 24 e9
[76] b0 2b a7 93 aa 29 65 b3 da 96 0c 63 ad 19 24 f5
To read a DER key use read_key or
read_pubkey with der = TRUE.
[256-bit ecdsa public key]
md5: 0fdd176f1dd0fd86209df1e82702908f
sha256: 1154310b8df673d15dacaa65b591e12c87c1cddc3210330febbfca457cc70b8b
Users typically don’t need to worry about the key’s underlying
primes, but have a look at key$data if you are curious.
In practice the user rarely encounters DER because it is mainly for internal use. When humans exchange keys and certificates they typically use the PEM format. PEM is simply base64 encoded DER data, plus a header. The header identifies the key (and possibly encryption) type.
-----BEGIN PUBLIC KEY-----
MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEMftJv4QfZS+a2EvV/UplW7e19iXc
bYxSixOOaZI8pyqH25ivMzmVsCiV4EO5aSTpsCunk6opZbPalgxjrRkk9Q==
-----END PUBLIC KEY-----
-----BEGIN PRIVATE KEY-----
MIGHAgEAMBMGByqGSM49AgEGCCqGSM49AwEHBG0wawIBAQQg7LLC3y2NcOAFpFm3
PI6PplmHVAB+nHKIyO5Q8jIkDwuhRANCAAQx+0m/hB9lL5rYS9X9SmVbt7X2Jdxt
jFKLE45pkjynKofbmK8zOZWwKJXgQ7lpJOmwK6eTqills9qWDGOtGST1
-----END PRIVATE KEY-----
The PEM format allows for protecting private keys with a password. R will prompt you for the password when reading such a protected key.
-----BEGIN ENCRYPTED PRIVATE KEY-----
MIHrMFYGCSqGSIb3DQEFDTBJMDEGCSqGSIb3DQEFDDAkBBBJbEDCRHhEBapn+132
NwyQAgIIADAMBggqhkiG9w0CCQUAMBQGCCqGSIb3DQMHBAiuwCgDiSvcqwSBkOTO
soQRL3MSVdsIWfg5x0DZl6qgx0R4Jh4E17fZzA0JupHWHdAYxciC42HnyIZrLMR5
FBfOxcZbl+yfjDhRL5BosYk3Er3stBhx0MKJuYa5QWYzlKCwEg7SCjQKdKHCYngK
1ZY60uF1lBgrHeFIeQd/r5oPevVuhQ0nuzgT6tD/OYmqCrWSjfo1m+QVALgCfA==
-----END ENCRYPTED PRIVATE KEY-----
For better or worse, OpenSSH uses a custom format for public
keys. The advantage of this format is that it fits on a single
line which is nice for e.g. your ~/.ssh/known_hosts file.
There is no special format for private keys, OpenSSH uses PEM as
well.
[1] "ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBDH7Sb+EH2UvmthL1f1KZVu3tfYl3G2MUosTjmmSPKcqh9uYrzM5lbAoleBDuWkk6bArp5OqKWWz2pYMY60ZJPU="
The read_pubkey function will automatically detect if a
file contains a PEM or SSH key.
[256-bit ecdsa public key]
md5: 0fdd176f1dd0fd86209df1e82702908f
sha256: 1154310b8df673d15dacaa65b591e12c87c1cddc3210330febbfca457cc70b8b
Yet another recent format to store RSA or EC keys are JSON Web Keys
(JWK). JWK is part of the Javascript Object Signing and
Encryption (JOSE) specification. The write_jwk and
read_jwk functions are implemented in a separate package
which uses the openssl package.
{
"kty": "EC",
"crv": "P-256",
"x": "MftJv4QfZS-a2EvV_UplW7e19iXcbYxSixOOaZI8pyo",
"y": "h9uYrzM5lbAoleBDuWkk6bArp5OqKWWz2pYMY60ZJPU"
}
Keys from jose and openssl are the
same.
[1] TRUE
[256-bit ecdsa public key]
md5: 0fdd176f1dd0fd86209df1e82702908f
sha256: 1154310b8df673d15dacaa65b591e12c87c1cddc3210330febbfca457cc70b8b