node-opcua-crypto 4.9.4 → 4.10.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/LICENSE CHANGED
@@ -1,23 +1,23 @@
1
- The MIT License (MIT)
2
-
3
- Copyright (c) Etienne Rossignon 2015-2022
4
- Copyright (c) Sterfive.com 2022-2024
5
-
6
- Permission is hereby granted, free of charge, to any person obtaining a copy
7
- of this software and associated documentation files (the "Software"), to deal
8
- in the Software without restriction, including without limitation the rights
9
- to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
10
- copies of the Software, and to permit persons to whom the Software is
11
- furnished to do so, subject to the following conditions:
12
-
13
- The above copyright notice and this permission notice shall be included in all
14
- copies or substantial portions of the Software.
15
-
16
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
17
- IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
18
- FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
19
- AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
20
- LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
21
- OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
22
- SOFTWARE.
23
-
1
+ The MIT License (MIT)
2
+
3
+ Copyright (c) Etienne Rossignon 2015-2022
4
+ Copyright (c) Sterfive.com 2022-2024
5
+
6
+ Permission is hereby granted, free of charge, to any person obtaining a copy
7
+ of this software and associated documentation files (the "Software"), to deal
8
+ in the Software without restriction, including without limitation the rights
9
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
10
+ copies of the Software, and to permit persons to whom the Software is
11
+ furnished to do so, subject to the following conditions:
12
+
13
+ The above copyright notice and this permission notice shall be included in all
14
+ copies or substantial portions of the Software.
15
+
16
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
17
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
18
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
19
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
20
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
21
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
22
+ SOFTWARE.
23
+
package/README.md CHANGED
@@ -1,114 +1,114 @@
1
- # node-opcua-crypto
2
-
3
- NodeOPCUA Crypto is a powerful JavaScript module for handling security and cryptography for OPCUA. It's written in TypeScript and runs smoothly on Node.js and in the browser.
4
-
5
- [![NPM download](https://img.shields.io/npm/dm/node-opcua-crypto.svg)](https://www.npmtrends.com/node-opcua-crypto)
6
- [![NPM version](https://img.shields.io/npm/v/node-opcua-crypto)](https://www.npmjs.com/package/node-opcua-crypto?activeTab=versions)
7
- [![Build Status](https://github.com/node-opcua/node-opcua-crypto/actions/workflows/main.yml/badge.svg)](https://github.com/node-opcua/node-opcua-crypto/actions/workflows/main.yml)
8
- [![Code Climate](https://codeclimate.com/github/node-opcua/node-opcua-crypto/badges/gpa.svg)](https://codeclimate.com/github/node-opcua/node-opcua-crypto)
9
- [![Coverage Status](https://coveralls.io/repos/github/node-opcua/node-opcua-crypto/badge.svg?branch=master)](https://coveralls.io/github/node-opcua/node-opcua-crypto?branch=master)
10
- [![install size](https://packagephobia.com/badge?p=node-opcua-crypto)](https://packagephobia.com/result?p=node-opcua-crypto)
11
- [![FOSSA Status](https://app.fossa.com/api/projects/custom%2B20248%2Fgithub.com%2Fnode-opcua%2Fnode-opcua-crypto.svg?type=shield)](https://app.fossa.com/projects/custom%2B20248%2Fgithub.com%2Fnode-opcua%2Fnode-opcua-crypto?ref=badge_shield)
12
- <!-- [![Test Coverage](https://codeclimate.com/github/node-opcua/node-opcua-crypto/badges/coverage.svg)](https://codeclimate.com/github/node-opcua/node-opcua-crypto/coverage) -->
13
-
14
- ## Features
15
-
16
- * a comprehensive set of cryptographic functionalities.
17
- * supports both Node.js and browser environments.
18
- * compatible with TypeScript for robust, type-safe coding.
19
- * implements advanced security standards for OPCUA.
20
-
21
- ## Getting Started
22
-
23
- To use NodeOPCUA Crypto in your project, follow these steps:
24
-
25
- #### Installation
26
-
27
- ``` bash
28
- npm install nodeopcua-crypto
29
- ```
30
-
31
- ### Usage
32
-
33
- ``` bash
34
-
35
- import { generatePrivateKey, privateKeyToPEM, CertificatePurpose, createSelfSignedCertificate } from "./node-opcua-crypto.js";
36
-
37
- async function demonstratePrivateKeyAndSelfSignedCertificateCreation() {
38
-
39
- // create the Private Key
40
- const privateKey = await generatePrivateKey();
41
-
42
- // convert the private key to a PEM format
43
- const { privPem } = await privateKeyToPEM(privateKey);
44
-
45
- console.log(privPem);
46
-
47
- // create a self-sign certificate
48
- const { cert } = await createSelfSignedCertificate({
49
- privateKey,
50
- notAfter: new Date(2025, 1, 1),
51
- notBefore: new Date(2019, 1, 1),
52
- subject: "CN=Test",
53
- dns: ["DNS1", "DNS2"],
54
- ip: ["192.168.1.1"],
55
- applicationUri: "urn:HOSTNAME:ServerDescription",
56
- purpose: CertificatePurpose.ForApplication,
57
- });
58
- console.log(cert);
59
- }
60
- demonstratePrivateKeyAndSelfSignedCertificateCreation();
61
-
62
-
63
- ```
64
-
65
- Please refer to the examples directory for more specific use cases and comprehensive samples.
66
-
67
-
68
- ## Support
69
-
70
- For any inquiries or issues related to NodeOPCUA Crypto, you can contact us at contact@sterfive.com. Please note that priority support is available to NodeOPCUA Support Subscription members.
71
-
72
- ### Getting professional support
73
-
74
- NodeOPCUA PKI is developed and maintained by sterfive.com.
75
-
76
- To get professional support, consider subscribing to the node-opcua membership community:
77
-
78
- [![Professional Support](https://img.shields.io/static/v1?style=for-the-badge&label=Professional&message=Support&labelColor=blue&color=green&logo=data:image/svg%2bxml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB2ZXJzaW9uPSIxLjEiIGlkPSJMYXllcl8xIiB4PSIwcHgiIHk9IjBweCIgdmlld0JveD0iMCAwIDQ5MS41MiA0OTEuNTIiIHN0eWxlPSJlbmFibGUtYmFja2dyb3VuZDpuZXcgMCAwIDQ5MS41MiA0OTEuNTI7IiB4bWw6c3BhY2U9InByZXNlcnZlIj4NCjxnPg0KCTxnPg0KCQk8cGF0aCBkPSJNNDg3Ljk4OSwzODkuNzU1bC05My4xMDktOTIuOTc2Yy00LjgxMy00LjgwNi0xMi42NDItNC42NzQtMTcuMjczLDAuMzA3Yy03LjE0OCw3LjY4OS0xNC42NCwxNS41NTQtMjEuNzMsMjIuNjM0ICAgIGMtMC4yNzEsMC4yNy0wLjUwMSwwLjQ5My0wLjc2MywwLjc1NUw0NjcuMyw0MzIuNTA0YzguOTEtMTAuNjE0LDE2LjY1Ny0yMC40MSwyMS43My0yNi45NyAgICBDNDkyLjcyLDQwMC43NjIsNDkyLjI1NywzOTQuMDE5LDQ4Ny45ODksMzg5Ljc1NXoiLz4NCgk8L2c+DQo8L2c+DQo8Zz4NCgk8Zz4NCgkJPHBhdGggZD0iTTMzNC4zLDMzNy42NjFjLTM0LjMwNCwxMS4zNzktNzcuNTYsMC40MTMtMTE0LjU1NC0yOS41NDJjLTQ5LjAyMS0zOS42OTMtNzUuOTcyLTEwMi42NDItNjUuODM4LTE1MC41OTNMMzcuNjM0LDQxLjQxOCAgICBDMTcuNjUzLDU5LjQyNCwwLDc4LjU0NSwwLDkwYzAsMTQxLjc1MSwyNjAuMzQ0LDQxNS44OTYsNDAxLjUwMyw0MDAuOTMxYzExLjI5Ni0xLjE5OCwzMC4xNzYtMTguNjUxLDQ4LjA2Mi0zOC4xNjdMMzM0LjMsMzM3LjY2MSAgICB6Ii8+DQoJPC9nPg0KPC9nPg0KPGc+DQoJPGc+DQoJCTxwYXRoIGQ9Ik0xOTMuODU0LDk2LjA0MUwxMDEuMjEzLDMuNTNjLTQuMjI1LTQuMjItMTAuODgyLTQuNzI0LTE1LjY2NC0xLjE0NWMtNi42NTQsNC45ODMtMTYuNjQ4LDEyLjY1MS0yNy40NTMsMjEuNDk4ICAgIGwxMTEuOTQ1LDExMS43ODVjMC4wNjEtMC4wNiwwLjExMS0wLjExMywwLjE3Mi0wLjE3NGM3LjIzOC03LjIyOCwxNS4zNTUtMTQuODg1LDIzLjI5MS0yMi4xNjcgICAgQzE5OC41MzQsMTA4LjcxMywxOTguNjg0LDEwMC44NjMsMTkzLjg1NCw5Ni4wNDF6Ii8+DQoJPC9nPg0KPC9nPg0KPGc+DQo8L2c+DQo8Zz4NCjwvZz4NCjxnPg0KPC9nPg0KPGc+DQo8L2c+DQo8Zz4NCjwvZz4NCjxnPg0KPC9nPg0KPGc+DQo8L2c+DQo8Zz4NCjwvZz4NCjxnPg0KPC9nPg0KPGc+DQo8L2c+DQo8Zz4NCjwvZz4NCjxnPg0KPC9nPg0KPGc+DQo8L2c+DQo8Zz4NCjwvZz4NCjxnPg0KPC9nPg0KPC9zdmc+)](https://support.sterfive.com)
79
-
80
- or contact [sterfive](https://www.sterfive.com) for dedicated consulting and more advanced support.
81
-
82
- ## Contributing
83
-
84
- We appreciate contributions from the community. To contribute:
85
-
86
- * Fork the repository.
87
- * Create a new branch.
88
- * Commit your changes.
89
- * Submit a pull request.
90
- * Sign the CLA (Contributor Licence Agreement) form
91
-
92
- For more detailed instructions, refer to the CONTRIBUTING.md file.
93
-
94
- ## License
95
-
96
- NodeOPCUA Crypto is MIT licensed. See the LICENSE file for full license details.
97
-
98
- Copyright © 2023-2024 Sterfive.com.
99
-
100
- ## Disclaimer
101
-
102
- NodeOPCUA Crypto is provided as-is, and while we strive to ensure its quality and security, Sterfive.com cannot be held liable for any damage caused directly or indirectly by the usage of this module.
103
-
104
- Please report any issues or vulnerabilities you find via the issue tracker.
105
-
106
- Thank you for considering NodeOPCUA Crypto for your OPCUA cryptography needs. We look forward to seeing what you build with i
107
-
108
-
109
-
110
- ## Supporting the development effort - Sponsors & Backers
111
-
112
- If you like `node-opcua-pki` and if you are relying on it in one of your projects, please consider becoming a backer and [sponsoring us](https://github.com/sponsors/node-opcua), this will help us to maintain a high-quality stack and constant evolution of this module.
113
-
114
- If your company would like to participate and influence the development of future versions of `node-opcua` please contact [sterfive](mailto:contact@sterfive.com).
1
+ # node-opcua-crypto
2
+
3
+ NodeOPCUA Crypto is a powerful JavaScript module for handling security and cryptography for OPCUA. It's written in TypeScript and runs smoothly on Node.js and in the browser.
4
+
5
+ [![NPM download](https://img.shields.io/npm/dm/node-opcua-crypto.svg)](https://www.npmtrends.com/node-opcua-crypto)
6
+ [![NPM version](https://img.shields.io/npm/v/node-opcua-crypto)](https://www.npmjs.com/package/node-opcua-crypto?activeTab=versions)
7
+ [![Build Status](https://github.com/node-opcua/node-opcua-crypto/actions/workflows/main.yml/badge.svg)](https://github.com/node-opcua/node-opcua-crypto/actions/workflows/main.yml)
8
+ [![Code Climate](https://codeclimate.com/github/node-opcua/node-opcua-crypto/badges/gpa.svg)](https://codeclimate.com/github/node-opcua/node-opcua-crypto)
9
+ [![Coverage Status](https://coveralls.io/repos/github/node-opcua/node-opcua-crypto/badge.svg?branch=master)](https://coveralls.io/github/node-opcua/node-opcua-crypto?branch=master)
10
+ [![install size](https://packagephobia.com/badge?p=node-opcua-crypto)](https://packagephobia.com/result?p=node-opcua-crypto)
11
+ [![FOSSA Status](https://app.fossa.com/api/projects/custom%2B20248%2Fgithub.com%2Fnode-opcua%2Fnode-opcua-crypto.svg?type=shield)](https://app.fossa.com/projects/custom%2B20248%2Fgithub.com%2Fnode-opcua%2Fnode-opcua-crypto?ref=badge_shield)
12
+ <!-- [![Test Coverage](https://codeclimate.com/github/node-opcua/node-opcua-crypto/badges/coverage.svg)](https://codeclimate.com/github/node-opcua/node-opcua-crypto/coverage) -->
13
+
14
+ ## Features
15
+
16
+ * a comprehensive set of cryptographic functionalities.
17
+ * supports both Node.js and browser environments.
18
+ * compatible with TypeScript for robust, type-safe coding.
19
+ * implements advanced security standards for OPCUA.
20
+
21
+ ## Getting Started
22
+
23
+ To use NodeOPCUA Crypto in your project, follow these steps:
24
+
25
+ #### Installation
26
+
27
+ ``` bash
28
+ npm install nodeopcua-crypto
29
+ ```
30
+
31
+ ### Usage
32
+
33
+ ``` bash
34
+
35
+ import { generatePrivateKey, privateKeyToPEM, CertificatePurpose, createSelfSignedCertificate } from "./node-opcua-crypto.js";
36
+
37
+ async function demonstratePrivateKeyAndSelfSignedCertificateCreation() {
38
+
39
+ // create the Private Key
40
+ const privateKey = await generatePrivateKey();
41
+
42
+ // convert the private key to a PEM format
43
+ const { privPem } = await privateKeyToPEM(privateKey);
44
+
45
+ console.log(privPem);
46
+
47
+ // create a self-sign certificate
48
+ const { cert } = await createSelfSignedCertificate({
49
+ privateKey,
50
+ notAfter: new Date(2025, 1, 1),
51
+ notBefore: new Date(2019, 1, 1),
52
+ subject: "CN=Test",
53
+ dns: ["DNS1", "DNS2"],
54
+ ip: ["192.168.1.1"],
55
+ applicationUri: "urn:HOSTNAME:ServerDescription",
56
+ purpose: CertificatePurpose.ForApplication,
57
+ });
58
+ console.log(cert);
59
+ }
60
+ demonstratePrivateKeyAndSelfSignedCertificateCreation();
61
+
62
+
63
+ ```
64
+
65
+ Please refer to the examples directory for more specific use cases and comprehensive samples.
66
+
67
+
68
+ ## Support
69
+
70
+ For any inquiries or issues related to NodeOPCUA Crypto, you can contact us at contact@sterfive.com. Please note that priority support is available to NodeOPCUA Support Subscription members.
71
+
72
+ ### Getting professional support
73
+
74
+ NodeOPCUA PKI is developed and maintained by sterfive.com.
75
+
76
+ To get professional support, consider subscribing to the node-opcua membership community:
77
+
78
+ [![Professional Support](https://img.shields.io/static/v1?style=for-the-badge&label=Professional&message=Support&labelColor=blue&color=green&logo=data:image/svg%2bxml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHhtbG5zOnhsaW5rPSJodHRwOi8vd3d3LnczLm9yZy8xOTk5L3hsaW5rIiB2ZXJzaW9uPSIxLjEiIGlkPSJMYXllcl8xIiB4PSIwcHgiIHk9IjBweCIgdmlld0JveD0iMCAwIDQ5MS41MiA0OTEuNTIiIHN0eWxlPSJlbmFibGUtYmFja2dyb3VuZDpuZXcgMCAwIDQ5MS41MiA0OTEuNTI7IiB4bWw6c3BhY2U9InByZXNlcnZlIj4NCjxnPg0KCTxnPg0KCQk8cGF0aCBkPSJNNDg3Ljk4OSwzODkuNzU1bC05My4xMDktOTIuOTc2Yy00LjgxMy00LjgwNi0xMi42NDItNC42NzQtMTcuMjczLDAuMzA3Yy03LjE0OCw3LjY4OS0xNC42NCwxNS41NTQtMjEuNzMsMjIuNjM0ICAgIGMtMC4yNzEsMC4yNy0wLjUwMSwwLjQ5My0wLjc2MywwLjc1NUw0NjcuMyw0MzIuNTA0YzguOTEtMTAuNjE0LDE2LjY1Ny0yMC40MSwyMS43My0yNi45NyAgICBDNDkyLjcyLDQwMC43NjIsNDkyLjI1NywzOTQuMDE5LDQ4Ny45ODksMzg5Ljc1NXoiLz4NCgk8L2c+DQo8L2c+DQo8Zz4NCgk8Zz4NCgkJPHBhdGggZD0iTTMzNC4zLDMzNy42NjFjLTM0LjMwNCwxMS4zNzktNzcuNTYsMC40MTMtMTE0LjU1NC0yOS41NDJjLTQ5LjAyMS0zOS42OTMtNzUuOTcyLTEwMi42NDItNjUuODM4LTE1MC41OTNMMzcuNjM0LDQxLjQxOCAgICBDMTcuNjUzLDU5LjQyNCwwLDc4LjU0NSwwLDkwYzAsMTQxLjc1MSwyNjAuMzQ0LDQxNS44OTYsNDAxLjUwMyw0MDAuOTMxYzExLjI5Ni0xLjE5OCwzMC4xNzYtMTguNjUxLDQ4LjA2Mi0zOC4xNjdMMzM0LjMsMzM3LjY2MSAgICB6Ii8+DQoJPC9nPg0KPC9nPg0KPGc+DQoJPGc+DQoJCTxwYXRoIGQ9Ik0xOTMuODU0LDk2LjA0MUwxMDEuMjEzLDMuNTNjLTQuMjI1LTQuMjItMTAuODgyLTQuNzI0LTE1LjY2NC0xLjE0NWMtNi42NTQsNC45ODMtMTYuNjQ4LDEyLjY1MS0yNy40NTMsMjEuNDk4ICAgIGwxMTEuOTQ1LDExMS43ODVjMC4wNjEtMC4wNiwwLjExMS0wLjExMywwLjE3Mi0wLjE3NGM3LjIzOC03LjIyOCwxNS4zNTUtMTQuODg1LDIzLjI5MS0yMi4xNjcgICAgQzE5OC41MzQsMTA4LjcxMywxOTguNjg0LDEwMC44NjMsMTkzLjg1NCw5Ni4wNDF6Ii8+DQoJPC9nPg0KPC9nPg0KPGc+DQo8L2c+DQo8Zz4NCjwvZz4NCjxnPg0KPC9nPg0KPGc+DQo8L2c+DQo8Zz4NCjwvZz4NCjxnPg0KPC9nPg0KPGc+DQo8L2c+DQo8Zz4NCjwvZz4NCjxnPg0KPC9nPg0KPGc+DQo8L2c+DQo8Zz4NCjwvZz4NCjxnPg0KPC9nPg0KPGc+DQo8L2c+DQo8Zz4NCjwvZz4NCjxnPg0KPC9nPg0KPC9zdmc+)](https://support.sterfive.com)
79
+
80
+ or contact [sterfive](https://www.sterfive.com) for dedicated consulting and more advanced support.
81
+
82
+ ## Contributing
83
+
84
+ We appreciate contributions from the community. To contribute:
85
+
86
+ * Fork the repository.
87
+ * Create a new branch.
88
+ * Commit your changes.
89
+ * Submit a pull request.
90
+ * Sign the CLA (Contributor Licence Agreement) form
91
+
92
+ For more detailed instructions, refer to the CONTRIBUTING.md file.
93
+
94
+ ## License
95
+
96
+ NodeOPCUA Crypto is MIT licensed. See the LICENSE file for full license details.
97
+
98
+ Copyright © 2023-2024 Sterfive.com.
99
+
100
+ ## Disclaimer
101
+
102
+ NodeOPCUA Crypto is provided as-is, and while we strive to ensure its quality and security, Sterfive.com cannot be held liable for any damage caused directly or indirectly by the usage of this module.
103
+
104
+ Please report any issues or vulnerabilities you find via the issue tracker.
105
+
106
+ Thank you for considering NodeOPCUA Crypto for your OPCUA cryptography needs. We look forward to seeing what you build with i
107
+
108
+
109
+
110
+ ## Supporting the development effort - Sponsors & Backers
111
+
112
+ If you like `node-opcua-pki` and if you are relying on it in one of your projects, please consider becoming a backer and [sponsoring us](https://github.com/sponsors/node-opcua), this will help us to maintain a high-quality stack and constant evolution of this module.
113
+
114
+ If your company would like to participate and influence the development of future versions of `node-opcua` please contact [sterfive](mailto:contact@sterfive.com).
@@ -102,6 +102,7 @@ var oid_map = {
102
102
  "1.3.6.1.4.1.311.2.1.22": { d: "1.3.6.1.4.1.311.2.1.22", c: "SPC_COMMERCIAL_SP_KEY_PURPOSE_OBJID" },
103
103
  "1.3.6.1.4.1.311.10.3.1": { d: "1.3.6.1.4.1.311.10.3.1", c: "Signer of CTLs -- szOID_KP_CTL_USAGE_SIGNING" },
104
104
  "1.3.6.1.4.1.311.10.3.4": { d: "1.3.6.1.4.1.311.10.3.4", c: "szOID_EFS_RECOVERY (Encryption File System)" },
105
+ "1.3.6.1.4.1.311.20.2.3": { d: "1.3.6.1.4.1.311.20.2.3", c: "id-on-personalData" },
105
106
  "1.3.6.1.5.5.7.3.17": { d: "1.3.6.1.5.5.7.3.17", c: "Internet Key Exchange (IKE)" },
106
107
  "1.3.6.1.5.5.7.3.1": { d: "serverAuth", c: "PKIX key purpose" },
107
108
  "1.3.6.1.5.5.7.3.2": { d: "clientAuth", c: "PKIX key purpose" },
@@ -361,12 +362,15 @@ var TagType = /* @__PURE__ */ ((TagType3) => {
361
362
  TagType3[TagType3["BMPString"] = 30] = "BMPString";
362
363
  TagType3[TagType3["SEQUENCE"] = 48] = "SEQUENCE";
363
364
  TagType3[TagType3["SET"] = 49] = "SET";
364
- TagType3[TagType3["A3"] = 163] = "A3";
365
+ TagType3[TagType3["CONTEXT_SPECIFIC0"] = 160] = "CONTEXT_SPECIFIC0";
366
+ TagType3[TagType3["CONTEXT_SPECIFIC1"] = 161] = "CONTEXT_SPECIFIC1";
367
+ TagType3[TagType3["CONTEXT_SPECIFIC2"] = 162] = "CONTEXT_SPECIFIC2";
368
+ TagType3[TagType3["CONTEXT_SPECIFIC3"] = 163] = "CONTEXT_SPECIFIC3";
369
+ TagType3[TagType3["A4"] = 164] = "A4";
365
370
  return TagType3;
366
371
  })(TagType || {});
367
372
  function readTag(buf, pos) {
368
- assert(buf instanceof Buffer);
369
- assert(Number.isFinite(pos) && pos >= 0);
373
+ const start = pos;
370
374
  if (buf.length <= pos) {
371
375
  throw new Error("Invalid position : buf.length=" + buf.length + " pos =" + pos);
372
376
  }
@@ -382,7 +386,7 @@ function readTag(buf, pos) {
382
386
  pos += 1;
383
387
  }
384
388
  }
385
- return { tag, position: pos, length };
389
+ return { start, tag, position: pos, length };
386
390
  }
387
391
  function _readStruct(buf, blockInfo) {
388
392
  const length = blockInfo.length;
@@ -447,8 +451,8 @@ function _readIntegerAsByteString(buffer, block) {
447
451
  function _readListOfInteger(buffer) {
448
452
  const block = readTag(buffer, 0);
449
453
  const inner_blocks = _readStruct(buffer, block);
450
- return inner_blocks.map((bblock) => {
451
- return _readIntegerAsByteString(buffer, bblock);
454
+ return inner_blocks.map((innerBlock) => {
455
+ return _readIntegerAsByteString(buffer, innerBlock);
452
456
  });
453
457
  }
454
458
  function parseOID(buffer, start, end) {
@@ -914,7 +918,8 @@ function _readGeneralNames(buffer, block) {
914
918
  5: { name: "ediPartyName", type: "EDIPartyName" },
915
919
  6: { name: "uniformResourceIdentifier", type: "IA5String" },
916
920
  7: { name: "iPAddress", type: "OCTET_STRING" },
917
- 8: { name: "registeredID", type: "OBJECT_IDENTIFIER" }
921
+ 8: { name: "registeredID", type: "OBJECT_IDENTIFIER" },
922
+ 32: { name: "otherName", type: "AnotherName" }
918
923
  };
919
924
  const blocks = _readStruct(buffer, block);
920
925
  function _readFromType(buffer2, block2, type) {
@@ -931,10 +936,25 @@ function _readGeneralNames(buffer, block) {
931
936
  const t = block2.tag & 127;
932
937
  const type = _data[t];
933
938
  if (!type) {
934
- throw new Error(" INVALID TYPE => " + t + "0x" + t.toString(16));
939
+ console.log("_readGeneralNames: INVALID TYPE => " + t + " 0x" + t.toString(16));
940
+ continue;
941
+ }
942
+ if (t == 32) {
943
+ n[type.name] = n[type.name] || [];
944
+ const blocks2 = _readStruct(buffer, block2);
945
+ const name = _readObjectIdentifier(buffer, blocks2[0]).name;
946
+ const buf = _getBlock(buffer, blocks2[1]);
947
+ const b = readTag(buf, 0);
948
+ const nn = _readValue(buf, b);
949
+ const data = {
950
+ identifier: name,
951
+ value: nn
952
+ };
953
+ n[type.name].push(data.value);
954
+ } else {
955
+ n[type.name] = n[type.name] || [];
956
+ n[type.name].push(_readFromType(buffer, block2, type.type));
935
957
  }
936
- n[type.name] = n[type.name] || [];
937
- n[type.name].push(_readFromType(buffer, block2, type.type));
938
958
  }
939
959
  return n;
940
960
  }
@@ -6258,4 +6278,4 @@ asn1js/build/index.es.js:
6258
6278
  *
6259
6279
  *)
6260
6280
  */
6261
- //# sourceMappingURL=chunk-WLW5XUML.mjs.map
6281
+ //# sourceMappingURL=chunk-46EEAYVO.mjs.map