2023-02-14 11:38:45 -05:00
|
|
|
// Copyright 2018-2023 the Deno authors. All rights reserved. MIT license.
|
|
|
|
// Copyright Joyent, Inc. and Node.js contributors. All rights reserved. MIT license.
|
|
|
|
|
|
|
|
import {
|
|
|
|
validateFunction,
|
|
|
|
validateInteger,
|
|
|
|
validateString,
|
refactor(core): include_js_files! 'dir' option doesn't change specifiers (#18019)
This commit changes "include_js_files!" macro from "deno_core"
in a way that "dir" option doesn't cause specifiers to be rewritten
to include it.
Example:
```
include_js_files! {
dir "js",
"hello.js",
}
```
The above definition required embedders to use:
`import ... from "internal:<ext_name>/js/hello.js"`.
But with this change, the "js" directory in which the files are stored
is an implementation detail, which for embedders results in:
`import ... from "internal:<ext_name>/hello.js"`.
The directory the files are stored in, is an implementation detail and
in some cases might result in a significant size difference for the
snapshot. As an example, in "deno_node" extension, we store the
source code in "polyfills" directory; which resulted in each specifier
to look like "internal:deno_node/polyfills/<module_name>", but with
this change it's "internal:deno_node/<module_name>".
Given that "deno_node" has over 100 files, many of them having
several import specifiers to the same extension, this change removes
10 characters from each import specifier.
2023-03-04 21:31:38 -05:00
|
|
|
} from "internal:deno_node/internal/validators.mjs";
|
2023-02-14 11:38:45 -05:00
|
|
|
import {
|
|
|
|
ERR_INVALID_ARG_TYPE,
|
|
|
|
ERR_OUT_OF_RANGE,
|
|
|
|
hideStackFrames,
|
refactor(core): include_js_files! 'dir' option doesn't change specifiers (#18019)
This commit changes "include_js_files!" macro from "deno_core"
in a way that "dir" option doesn't cause specifiers to be rewritten
to include it.
Example:
```
include_js_files! {
dir "js",
"hello.js",
}
```
The above definition required embedders to use:
`import ... from "internal:<ext_name>/js/hello.js"`.
But with this change, the "js" directory in which the files are stored
is an implementation detail, which for embedders results in:
`import ... from "internal:<ext_name>/hello.js"`.
The directory the files are stored in, is an implementation detail and
in some cases might result in a significant size difference for the
snapshot. As an example, in "deno_node" extension, we store the
source code in "polyfills" directory; which resulted in each specifier
to look like "internal:deno_node/polyfills/<module_name>", but with
this change it's "internal:deno_node/<module_name>".
Given that "deno_node" has over 100 files, many of them having
several import specifiers to the same extension, this change removes
10 characters from each import specifier.
2023-03-04 21:31:38 -05:00
|
|
|
} from "internal:deno_node/internal/errors.ts";
|
2023-02-14 11:38:45 -05:00
|
|
|
import {
|
|
|
|
toBuf,
|
|
|
|
validateByteSource,
|
refactor(core): include_js_files! 'dir' option doesn't change specifiers (#18019)
This commit changes "include_js_files!" macro from "deno_core"
in a way that "dir" option doesn't cause specifiers to be rewritten
to include it.
Example:
```
include_js_files! {
dir "js",
"hello.js",
}
```
The above definition required embedders to use:
`import ... from "internal:<ext_name>/js/hello.js"`.
But with this change, the "js" directory in which the files are stored
is an implementation detail, which for embedders results in:
`import ... from "internal:<ext_name>/hello.js"`.
The directory the files are stored in, is an implementation detail and
in some cases might result in a significant size difference for the
snapshot. As an example, in "deno_node" extension, we store the
source code in "polyfills" directory; which resulted in each specifier
to look like "internal:deno_node/polyfills/<module_name>", but with
this change it's "internal:deno_node/<module_name>".
Given that "deno_node" has over 100 files, many of them having
several import specifiers to the same extension, this change removes
10 characters from each import specifier.
2023-03-04 21:31:38 -05:00
|
|
|
} from "internal:deno_node/internal/crypto/util.ts";
|
2023-02-14 11:38:45 -05:00
|
|
|
import {
|
|
|
|
createSecretKey,
|
|
|
|
isKeyObject,
|
|
|
|
KeyObject,
|
refactor(core): include_js_files! 'dir' option doesn't change specifiers (#18019)
This commit changes "include_js_files!" macro from "deno_core"
in a way that "dir" option doesn't cause specifiers to be rewritten
to include it.
Example:
```
include_js_files! {
dir "js",
"hello.js",
}
```
The above definition required embedders to use:
`import ... from "internal:<ext_name>/js/hello.js"`.
But with this change, the "js" directory in which the files are stored
is an implementation detail, which for embedders results in:
`import ... from "internal:<ext_name>/hello.js"`.
The directory the files are stored in, is an implementation detail and
in some cases might result in a significant size difference for the
snapshot. As an example, in "deno_node" extension, we store the
source code in "polyfills" directory; which resulted in each specifier
to look like "internal:deno_node/polyfills/<module_name>", but with
this change it's "internal:deno_node/<module_name>".
Given that "deno_node" has over 100 files, many of them having
several import specifiers to the same extension, this change removes
10 characters from each import specifier.
2023-03-04 21:31:38 -05:00
|
|
|
} from "internal:deno_node/internal/crypto/keys.ts";
|
|
|
|
import type { BinaryLike } from "internal:deno_node/internal/crypto/types.ts";
|
|
|
|
import { kMaxLength } from "internal:deno_node/internal/buffer.mjs";
|
2023-02-14 11:38:45 -05:00
|
|
|
import {
|
|
|
|
isAnyArrayBuffer,
|
|
|
|
isArrayBufferView,
|
refactor(core): include_js_files! 'dir' option doesn't change specifiers (#18019)
This commit changes "include_js_files!" macro from "deno_core"
in a way that "dir" option doesn't cause specifiers to be rewritten
to include it.
Example:
```
include_js_files! {
dir "js",
"hello.js",
}
```
The above definition required embedders to use:
`import ... from "internal:<ext_name>/js/hello.js"`.
But with this change, the "js" directory in which the files are stored
is an implementation detail, which for embedders results in:
`import ... from "internal:<ext_name>/hello.js"`.
The directory the files are stored in, is an implementation detail and
in some cases might result in a significant size difference for the
snapshot. As an example, in "deno_node" extension, we store the
source code in "polyfills" directory; which resulted in each specifier
to look like "internal:deno_node/polyfills/<module_name>", but with
this change it's "internal:deno_node/<module_name>".
Given that "deno_node" has over 100 files, many of them having
several import specifiers to the same extension, this change removes
10 characters from each import specifier.
2023-03-04 21:31:38 -05:00
|
|
|
} from "internal:deno_node/internal/util/types.ts";
|
|
|
|
import { notImplemented } from "internal:deno_node/_utils.ts";
|
2023-02-14 11:38:45 -05:00
|
|
|
|
|
|
|
const validateParameters = hideStackFrames((hash, key, salt, info, length) => {
|
|
|
|
key = prepareKey(key);
|
|
|
|
salt = toBuf(salt);
|
|
|
|
info = toBuf(info);
|
|
|
|
|
|
|
|
validateString(hash, "digest");
|
|
|
|
validateByteSource(salt, "salt");
|
|
|
|
validateByteSource(info, "info");
|
|
|
|
|
|
|
|
validateInteger(length, "length", 0, kMaxLength);
|
|
|
|
|
|
|
|
if (info.byteLength > 1024) {
|
|
|
|
throw new ERR_OUT_OF_RANGE(
|
|
|
|
"info",
|
|
|
|
"must not contain more than 1024 bytes",
|
|
|
|
info.byteLength,
|
|
|
|
);
|
|
|
|
}
|
|
|
|
|
|
|
|
return {
|
|
|
|
hash,
|
|
|
|
key,
|
|
|
|
salt,
|
|
|
|
info,
|
|
|
|
length,
|
|
|
|
};
|
|
|
|
});
|
|
|
|
|
|
|
|
function prepareKey(key: BinaryLike | KeyObject) {
|
|
|
|
if (isKeyObject(key)) {
|
|
|
|
return key;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (isAnyArrayBuffer(key)) {
|
|
|
|
return createSecretKey(new Uint8Array(key as unknown as ArrayBufferLike));
|
|
|
|
}
|
|
|
|
|
|
|
|
key = toBuf(key as string);
|
|
|
|
|
|
|
|
if (!isArrayBufferView(key)) {
|
|
|
|
throw new ERR_INVALID_ARG_TYPE(
|
|
|
|
"ikm",
|
|
|
|
[
|
|
|
|
"string",
|
|
|
|
"SecretKeyObject",
|
|
|
|
"ArrayBuffer",
|
|
|
|
"TypedArray",
|
|
|
|
"DataView",
|
|
|
|
"Buffer",
|
|
|
|
],
|
|
|
|
key,
|
|
|
|
);
|
|
|
|
}
|
|
|
|
|
|
|
|
return createSecretKey(key);
|
|
|
|
}
|
|
|
|
|
|
|
|
export function hkdf(
|
|
|
|
hash: string,
|
|
|
|
key: BinaryLike | KeyObject,
|
|
|
|
salt: BinaryLike,
|
|
|
|
info: BinaryLike,
|
|
|
|
length: number,
|
|
|
|
callback: (err: Error | null, derivedKey: ArrayBuffer) => void,
|
|
|
|
) {
|
|
|
|
({ hash, key, salt, info, length } = validateParameters(
|
|
|
|
hash,
|
|
|
|
key,
|
|
|
|
salt,
|
|
|
|
info,
|
|
|
|
length,
|
|
|
|
));
|
|
|
|
|
|
|
|
validateFunction(callback, "callback");
|
|
|
|
|
|
|
|
notImplemented("crypto.hkdf");
|
|
|
|
}
|
|
|
|
|
|
|
|
export function hkdfSync(
|
|
|
|
hash: string,
|
|
|
|
key: BinaryLike | KeyObject,
|
|
|
|
salt: BinaryLike,
|
|
|
|
info: BinaryLike,
|
|
|
|
length: number,
|
|
|
|
) {
|
|
|
|
({ hash, key, salt, info, length } = validateParameters(
|
|
|
|
hash,
|
|
|
|
key,
|
|
|
|
salt,
|
|
|
|
info,
|
|
|
|
length,
|
|
|
|
));
|
|
|
|
|
|
|
|
notImplemented("crypto.hkdfSync");
|
|
|
|
}
|
|
|
|
|
|
|
|
export default {
|
|
|
|
hkdf,
|
|
|
|
hkdfSync,
|
|
|
|
};
|