# Class KeyObject

Node.js uses a `KeyObject` class to represent a symmetric or asymmetric key, and each kind of key exposes different functions. The createSecretKey, createPublicKey and createPrivateKey methods are used to create `KeyObject`instances. `KeyObject` objects are not to be created directly using the `new`keyword.

Most applications should consider using the new `KeyObject` API instead of passing keys as strings or `Buffer`s due to improved security features.

`KeyObject` instances can be passed to other threads via `postMessage()`. The receiver obtains a cloned `KeyObject`, and the `KeyObject` does not need to be listed in the `transferList` argument.

#### Since

v11.6.0

- Defined in node_modules/@types/node/crypto.d.ts:572

#####
Index

### Properties

asymmetricKeyType?
asymmetricKeySize?
asymmetricKeyDetails?
symmetricKeySize?
type

### Methods

from
export
equals

##
Properties

### `Optional` asymmetricKeyType

asymmetricKeyType?: KeyType

For asymmetric keys, this property represents the type of the key. Supported key types are:

- `'rsa'` (OID 1.2.840.113549.1.1.1)
- `'rsa-pss'` (OID 1.2.840.113549.1.1.10)
- `'dsa'` (OID 1.2.840.10040.4.1)
- `'ec'` (OID 1.2.840.10045.2.1)
- `'x25519'` (OID 1.3.101.110)
- `'x448'` (OID 1.3.101.111)
- `'ed25519'` (OID 1.3.101.112)
- `'ed448'` (OID 1.3.101.113)
- `'dh'` (OID 1.2.840.113549.1.3.1)

This property is `undefined` for unrecognized `KeyObject` types and symmetric keys.

#### Since

v11.6.0

- Defined in node_modules/@types/node/crypto.d.ts:612

### `Optional` asymmetricKeySize

asymmetricKeySize?: number

For asymmetric keys, this property represents the size of the embedded key in bytes. This property is `undefined` for symmetric keys.

- Defined in node_modules/@types/node/crypto.d.ts:617

### `Optional` asymmetricKeyDetails

asymmetricKeyDetails?: AsymmetricKeyDetails

This property exists only on asymmetric keys. Depending on the type of the key, this object contains information about the key. None of the information obtained through this property can be used to uniquely identify a key or to compromise the security of the key.

For RSA-PSS keys, if the key material contains a `RSASSA-PSS-params` sequence, the `hashAlgorithm`, `mgf1HashAlgorithm`, and `saltLength` properties will be set.

Other key details might be exposed via this API using additional attributes.

#### Since

v15.7.0

- Defined in node_modules/@types/node/crypto.d.ts:631

### `Optional` symmetricKeySize

symmetricKeySize?: number

For secret keys, this property represents the size of the key in bytes. This property is `undefined` for asymmetric keys.

#### Since

v11.6.0

- Defined in node_modules/@types/node/crypto.d.ts:669

### type

type: KeyObjectType

Depending on the type of this `KeyObject`, this property is either`'secret'` for secret (symmetric) keys, `'public'` for public (asymmetric) keys or `'private'` for private (asymmetric) keys.

#### Since

v11.6.0

- Defined in node_modules/@types/node/crypto.d.ts:675

##
Methods

### `Static` from

- from(key): KeyObject

- Example: Converting a `CryptoKey` instance to a `KeyObject`:

      const { webcrypto, KeyObject } = await import('crypto');
      const { subtle } = webcrypto;

      const key = await subtle.generateKey({
        name: 'HMAC',
        hash: 'SHA-256',
        length: 256
      }, true, ['sign', 'verify']);

      const keyObject = KeyObject.from(key);
      console.log(keyObject.symmetricKeySize);
      // Prints: 32 (symmetric key size in bytes)

  #### Parameters

  - key: CryptoKey

  #### Returns KeyObject

  #### Since

  v15.0.0

  - Defined in node_modules/@types/node/crypto.d.ts:593

### export

- export(options): string | Buffer

- For symmetric keys, the following encoding options can be used:

  For public keys, the following encoding options can be used:

  For private keys, the following encoding options can be used:

  The result type depends on the selected encoding format, when PEM the result is a string, when DER it will be a buffer containing the data encoded as DER, when JWK it will be an object.

  When JWK encoding format was selected, all other encoding options are ignored.

  PKCS#1, SEC1, and PKCS#8 type keys can be encrypted by using a combination of the `cipher` and `format` options. The PKCS#8 `type` can be used with any`format` to encrypt any key algorithm (RSA, EC, or DH) by specifying a`cipher`. PKCS#1 and SEC1 can only be encrypted by specifying a `cipher`when the PEM `format` is used. For maximum compatibility, use PKCS#8 for encrypted private keys. Since PKCS#8 defines its own encryption mechanism, PEM-level encryption is not supported when encrypting a PKCS#8 key. See RFC 5208 for PKCS#8 encryption and RFC 1421 for PKCS#1 and SEC1 encryption.

  #### Parameters

  - options: KeyExportOptions<"pem">

  #### Returns string | Buffer

  #### Since

  v11.6.0

  - Defined in node_modules/@types/node/crypto.d.ts:655
- export(options?): Buffer

- #### Parameters

  - `Optional` options: KeyExportOptions<"der">

  #### Returns Buffer

  - Defined in node_modules/@types/node/crypto.d.ts:656
- export(options?): JsonWebKey

- #### Parameters

  - `Optional` options: JwkKeyExportOptions

  #### Returns JsonWebKey

  - Defined in node_modules/@types/node/crypto.d.ts:657

### equals

- equals(otherKeyObject): boolean

- Returns `true` or `false` depending on whether the keys have exactly the same type, value, and parameters. This method is not constant time.

  #### Parameters

  - otherKeyObject: KeyObject

  #### Returns boolean

  #### Since

  v16.15.0

  - Defined in node_modules/@types/node/crypto.d.ts:663