kxco-post-quantum 1.2.1 → 1.4.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/CHANGELOG.md +374 -256
- package/CONFORMANCE.md +180 -0
- package/LICENSE +202 -202
- package/MIGRATION.md +143 -0
- package/README.md +215 -140
- package/SECURITY.md +41 -28
- package/THREAT-MODEL.md +194 -0
- package/package.json +124 -107
- package/src/_context.js +69 -0
- package/src/derive.d.ts +20 -20
- package/src/derive.js +47 -47
- package/src/index.d.ts +13 -8
- package/src/index.js +24 -17
- package/src/kid.d.ts +21 -21
- package/src/kid.js +53 -53
- package/src/ml-dsa-87.d.ts +81 -0
- package/src/ml-dsa-87.js +127 -0
- package/src/ml-dsa.d.ts +78 -45
- package/src/ml-dsa.js +102 -78
- package/src/ml-kem-1024.d.ts +59 -0
- package/src/ml-kem-1024.js +90 -0
- package/src/ml-kem.d.ts +49 -49
- package/src/ml-kem.js +61 -61
- package/src/slh-dsa.d.ts +72 -46
- package/src/slh-dsa.js +106 -88
- package/src/webhook.d.ts +119 -119
- package/src/webhook.js +135 -135
package/CONFORMANCE.md
ADDED
|
@@ -0,0 +1,180 @@
|
|
|
1
|
+
# Conformance and interoperability evidence
|
|
2
|
+
|
|
3
|
+
Two claims, each with a harness in this repository that anyone can run:
|
|
4
|
+
|
|
5
|
+
1. **This package computes what FIPS 203, 204 and 205 say it should.** Evidenced
|
|
6
|
+
against NIST's own ACVP test vectors.
|
|
7
|
+
2. **Independent implementations can consume what it produces, and it can
|
|
8
|
+
consume theirs.** Evidenced against Bouncy Castle (Java) and
|
|
9
|
+
dilithium-py / kyber-py (Python), in both directions.
|
|
10
|
+
|
|
11
|
+
The second claim is the one that matters in deployment and the one that vector
|
|
12
|
+
files cannot make. Passing NIST's vectors proves agreement with NIST. It does
|
|
13
|
+
not prove that a counterparty running a different stack can verify your
|
|
14
|
+
signature.
|
|
15
|
+
|
|
16
|
+
Everything below is reproducible:
|
|
17
|
+
|
|
18
|
+
```
|
|
19
|
+
npm run conformance:fetch # pinned NIST vectors, digest-checked
|
|
20
|
+
npm run conformance:acvp # claim 1
|
|
21
|
+
npm run conformance:interop # claim 2
|
|
22
|
+
```
|
|
23
|
+
|
|
24
|
+
Both harnesses run in CI on every push and in full weekly. See
|
|
25
|
+
[.github/workflows/conformance.yml](.github/workflows/conformance.yml).
|
|
26
|
+
|
|
27
|
+
---
|
|
28
|
+
|
|
29
|
+
## 1. NIST ACVP vectors
|
|
30
|
+
|
|
31
|
+
Source: [`usnistgov/ACVP-Server`](https://github.com/usnistgov/ACVP-Server) at
|
|
32
|
+
commit `975de31eb83d87039ec88934fdc47d8c312b892d`, pinned with per-file SHA-256
|
|
33
|
+
digests in [conformance/acvp-lock.json](conformance/acvp-lock.json). A rewritten
|
|
34
|
+
upstream file fails the fetch rather than silently changing the result.
|
|
35
|
+
|
|
36
|
+
Every parameter set NIST publishes vectors for is exercised, not only the five
|
|
37
|
+
this package wraps in its own helpers.
|
|
38
|
+
|
|
39
|
+
| Vector set | Tests | Passed | Failed | Skipped |
|
|
40
|
+
|---|---:|---:|---:|---:|
|
|
41
|
+
| ML-KEM-keyGen (FIPS 203) | 75 | 75 | 0 | 0 |
|
|
42
|
+
| ML-KEM-encapDecap (FIPS 203) | 165 | 165 | 0 | 0 |
|
|
43
|
+
| ML-DSA-keyGen (FIPS 204) | 75 | 75 | 0 | 0 |
|
|
44
|
+
| ML-DSA-sigGen (FIPS 204) | 360 | 316 | 0 | 44 |
|
|
45
|
+
| ML-DSA-sigVer (FIPS 204) | 180 | 157 | 0 | 23 |
|
|
46
|
+
| SLH-DSA-keyGen (FIPS 205) | 120 | 120 | 0 | 0 |
|
|
47
|
+
| SLH-DSA-sigGen (FIPS 205) | 624 | 472 | 0 | 152 |
|
|
48
|
+
| SLH-DSA-sigVer (FIPS 205) | 504 | 413 | 0 | 91 |
|
|
49
|
+
| **Total** | **2103** | **1793** | **0** | **310** |
|
|
50
|
+
|
|
51
|
+
A full pass takes hours, almost all of it SLH-DSA signing with the slow
|
|
52
|
+
parameter sets. CI subsamples per push with `--max-per-group` and runs the full
|
|
53
|
+
suite weekly; the generated report records which of the two it was, so a
|
|
54
|
+
subsampled run is never mistaken for a full one. To reproduce one expensive set
|
|
55
|
+
on its own: `node conformance/run-acvp.mjs --set SLH-DSA-sigGen-FIPS205`. The
|
|
56
|
+
generated report for that full run is committed at
|
|
57
|
+
[conformance/results/acvp-slh-dsa-siggen.json](conformance/results/acvp-slh-dsa-siggen.json),
|
|
58
|
+
with each skip and its reason.
|
|
59
|
+
|
|
60
|
+
Parameter sets covered: ML-KEM-512/768/1024, ML-DSA-44/65/87, and all twelve
|
|
61
|
+
SLH-DSA sets (SHA2 and SHAKE, 128/192/256, f and s).
|
|
62
|
+
|
|
63
|
+
The signature sets cover every interface variant in NIST's vectors: the external
|
|
64
|
+
and internal interfaces, pure and pre-hashed (HashML-DSA / HashSLH-DSA),
|
|
65
|
+
external-mu, deterministic and randomized signing, empty and non-empty context
|
|
66
|
+
strings. Deterministic groups reproduce NIST's expected signature bytes exactly;
|
|
67
|
+
randomized groups reproduce them from the `rnd` / `additionalRandomness` value
|
|
68
|
+
the vector supplies.
|
|
69
|
+
|
|
70
|
+
**Zero failures. The skips are all one thing, and it is not a gap in coverage.**
|
|
71
|
+
|
|
72
|
+
Every skipped case is a pre-hash pairing the backend refuses because the hash's
|
|
73
|
+
collision strength falls below the parameter set's security category, for example
|
|
74
|
+
SHA2-256 with ML-DSA-87 (128 bits offered against 256 required), or SHAKE-128
|
|
75
|
+
with ML-DSA-65 (128 against 192). NIST's sample files pair every approved hash
|
|
76
|
+
with every parameter set, including those combinations. The backend rejects them
|
|
77
|
+
rather than signing.
|
|
78
|
+
|
|
79
|
+
This is the library being stricter than the vector file, and it is counted
|
|
80
|
+
separately rather than folded into a pass total, because a skip is not a pass.
|
|
81
|
+
Every skip is listed with its reason in the generated reports, which CI writes as
|
|
82
|
+
`conformance/results/acvp-fast.json` and
|
|
83
|
+
`conformance/results/acvp-slh-signatures.json`. The SLH-DSA signature sets run as
|
|
84
|
+
their own job because a full pass of them takes over an hour, so a single
|
|
85
|
+
combined job would time out.
|
|
86
|
+
|
|
87
|
+
---
|
|
88
|
+
|
|
89
|
+
## 2. Cross-implementation interoperability
|
|
90
|
+
|
|
91
|
+
Peers, both pinned in
|
|
92
|
+
[conformance/interop/peers-lock.json](conformance/interop/peers-lock.json):
|
|
93
|
+
|
|
94
|
+
| Peer | Implementation | Language | Covers |
|
|
95
|
+
|---|---|---|---|
|
|
96
|
+
| `bouncycastle` | `org.bouncycastle:bcprov-jdk18on:1.85.2`, SHA-256 pinned | Java | ML-DSA, ML-KEM, SLH-DSA |
|
|
97
|
+
| `python` | `dilithium-py==1.4.0`, `kyber-py==1.2.0` | Python | ML-DSA, ML-KEM |
|
|
98
|
+
|
|
99
|
+
SLH-DSA is covered by Bouncy Castle only, because no maintained pure-Python
|
|
100
|
+
implementation was available to pin. That is a narrower base than the other two
|
|
101
|
+
families and is stated rather than averaged away.
|
|
102
|
+
|
|
103
|
+
Neither shares code with this package's backend. Bouncy Castle is a widely
|
|
104
|
+
deployed independent implementation; the Python pair are independent
|
|
105
|
+
spec-derived implementations.
|
|
106
|
+
|
|
107
|
+
**Result: 156 checks passed, 0 failed, 10 not applicable, across 24 rows.**
|
|
108
|
+
|
|
109
|
+
Per row, in both directions:
|
|
110
|
+
|
|
111
|
+
| Check | What it establishes |
|
|
112
|
+
|---|---|
|
|
113
|
+
| `keys` | The same seed derives the same public key bytes in both stacks, independently |
|
|
114
|
+
| `ours>theirs` | We sign, the peer verifies |
|
|
115
|
+
| `theirs>ours` | The peer signs, we verify |
|
|
116
|
+
| `bytes` | Deterministic signing produces byte-identical output in both stacks |
|
|
117
|
+
| `tamper` | One flipped bit in our signature, and the peer rejects it |
|
|
118
|
+
| `reject` | A corrupted ML-KEM ciphertext yields an unrelated secret, not the real one |
|
|
119
|
+
|
|
120
|
+
The `tamper` and `reject` rows are negative controls and they are the reason to
|
|
121
|
+
trust the positive ones. Without them, a peer whose verify function returned
|
|
122
|
+
`true` unconditionally would pass every other check in the matrix.
|
|
123
|
+
|
|
124
|
+
Test material is derived from published labels rather than shipped as opaque
|
|
125
|
+
fixtures, so a third party can recompute the seeds and rerun the matrix without
|
|
126
|
+
trusting anything in this repository. See `fixtureSeed` in
|
|
127
|
+
[conformance/interop/run-interop.mjs](conformance/interop/run-interop.mjs).
|
|
128
|
+
|
|
129
|
+
Each parameter set this package publishes a helper for is run twice: once
|
|
130
|
+
through that helper (`wrapper`) and once through the primitive (`backend`), so
|
|
131
|
+
the evidence covers the published API and not only its dependency.
|
|
132
|
+
|
|
133
|
+
### The ten not-applicable checks
|
|
134
|
+
|
|
135
|
+
`bytes` on the five `wrapper` rows, in each of two context modes. This package's
|
|
136
|
+
`sign` is hedged: it draws fresh randomness per signature, which FIPS 204 permits
|
|
137
|
+
and recommends, so its output is deliberately not reproducible. Byte equality is
|
|
138
|
+
asserted on the `backend` rows for the same parameter sets, so determinism is
|
|
139
|
+
still evidenced everywhere it is meaningful. Reasoning is in
|
|
140
|
+
[THREAT-MODEL.md](THREAT-MODEL.md).
|
|
141
|
+
|
|
142
|
+
The five wrapper rows are the five parameter sets this package publishes helpers
|
|
143
|
+
for: ML-DSA-65, ML-DSA-87, ML-KEM-768, ML-KEM-1024 and SLH-DSA-SHA2-192s.
|
|
144
|
+
|
|
145
|
+
---
|
|
146
|
+
|
|
147
|
+
## What this evidence does not cover
|
|
148
|
+
|
|
149
|
+
Stated plainly, because a conformance report that only lists what passed is
|
|
150
|
+
marketing.
|
|
151
|
+
|
|
152
|
+
- **No side-channel claim.** Nothing here measures timing, cache or power
|
|
153
|
+
behaviour, and this package makes no constant-time claim. See
|
|
154
|
+
[THREAT-MODEL.md](THREAT-MODEL.md).
|
|
155
|
+
- **No FIPS 140-3 validation.** This is algorithm-level conformance against
|
|
156
|
+
NIST's vectors, run by us. It is not CAVP or CMVP validation, and it is not
|
|
157
|
+
equivalent to either. No certificate number is claimed because none exists.
|
|
158
|
+
- **No CNSA 2.0 assertion.** CNSA 2.0 names ML-KEM-1024 and ML-DSA-87. This
|
|
159
|
+
package supports both: they pass NIST's vectors above, they interoperate in
|
|
160
|
+
the matrix above, and `mlDsa87` and `mlKem1024` are published helpers. That is
|
|
161
|
+
a support claim, not a compliance claim, and the distinction is not
|
|
162
|
+
decorative. CNSA 2.0 compliance is a property of a deployment, not of an
|
|
163
|
+
available function. The KXCO estate signs at Category 3 with ML-DSA-65,
|
|
164
|
+
including Armature L1 from block 0 and every issued KXCO ID, none of which
|
|
165
|
+
these modules change. The accurate sentences are "NIST FIPS 203/204/205
|
|
166
|
+
conformant" and "supports ML-DSA-87 and ML-KEM-1024". Anything stronger,
|
|
167
|
+
including "CNSA 2.0 ready", would be an overclaim.
|
|
168
|
+
- **Protocol-level interop is not covered here.** Key and signature bytes
|
|
169
|
+
interoperate. Certificate and message encodings, X.509, CMS, COSE, JOSE and
|
|
170
|
+
TLS group negotiation are separate surfaces and no claim is made about them.
|
|
171
|
+
- **Self-administered.** Every number above was produced by harnesses in this
|
|
172
|
+
repository, run by us. That is why they are reproducible and why the pins,
|
|
173
|
+
digests and negative controls are there. It is not third-party attestation and
|
|
174
|
+
should not be read as any.
|
|
175
|
+
|
|
176
|
+
## Correcting this document
|
|
177
|
+
|
|
178
|
+
If any figure here does not reproduce on your machine, that is a defect worth
|
|
179
|
+
reporting through [SECURITY.md](SECURITY.md). Include the generated
|
|
180
|
+
`conformance/results/*.json` from your run.
|
package/LICENSE
CHANGED
|
@@ -1,202 +1,202 @@
|
|
|
1
|
-
|
|
2
|
-
Apache License
|
|
3
|
-
Version 2.0, January 2004
|
|
4
|
-
http://www.apache.org/licenses/
|
|
5
|
-
|
|
6
|
-
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
-
|
|
8
|
-
1. Definitions.
|
|
9
|
-
|
|
10
|
-
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
-
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
-
|
|
13
|
-
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
-
the copyright owner that is granting the License.
|
|
15
|
-
|
|
16
|
-
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
-
other entities that control, are controlled by, or are under common
|
|
18
|
-
control with that entity. For the purposes of this definition,
|
|
19
|
-
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
-
direction or management of such entity, whether by contract or
|
|
21
|
-
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
-
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
-
|
|
24
|
-
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
-
exercising permissions granted by this License.
|
|
26
|
-
|
|
27
|
-
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
-
including but not limited to software source code, documentation
|
|
29
|
-
source, and configuration files.
|
|
30
|
-
|
|
31
|
-
"Object" form shall mean any form resulting from mechanical
|
|
32
|
-
transformation or translation of a Source form, including but
|
|
33
|
-
not limited to compiled object code, generated documentation,
|
|
34
|
-
and conversions to other media types.
|
|
35
|
-
|
|
36
|
-
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
-
Object form, made available under the License, as indicated by a
|
|
38
|
-
copyright notice that is included in or attached to the work
|
|
39
|
-
(an example is provided in the Appendix below).
|
|
40
|
-
|
|
41
|
-
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
-
form, that is based on (or derived from) the Work and for which the
|
|
43
|
-
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
-
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
-
of this License, Derivative Works shall not include works that remain
|
|
46
|
-
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
-
the Work and Derivative Works thereof.
|
|
48
|
-
|
|
49
|
-
"Contribution" shall mean any work of authorship, including
|
|
50
|
-
the original version of the Work and any modifications or additions
|
|
51
|
-
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
-
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
-
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
-
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
-
means any form of electronic, verbal, or written communication sent
|
|
56
|
-
to the Licensor or its representatives, including but not limited to
|
|
57
|
-
communication on electronic mailing lists, source code control systems,
|
|
58
|
-
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
-
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
-
excluding communication that is conspicuously marked or otherwise
|
|
61
|
-
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
-
|
|
63
|
-
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
-
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
-
subsequently incorporated within the Work.
|
|
66
|
-
|
|
67
|
-
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
-
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
-
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
-
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
-
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
-
Work and such Derivative Works in Source or Object form.
|
|
73
|
-
|
|
74
|
-
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
-
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
-
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
-
(except as stated in this section) patent license to make, have made,
|
|
78
|
-
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
-
where such license applies only to those patent claims licensable
|
|
80
|
-
by such Contributor that are necessarily infringed by their
|
|
81
|
-
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
-
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
-
institute patent litigation against any entity (including a
|
|
84
|
-
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
-
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
-
or contributory patent infringement, then any patent licenses
|
|
87
|
-
granted to You under this License for that Work shall terminate
|
|
88
|
-
as of the date such litigation is filed.
|
|
89
|
-
|
|
90
|
-
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
-
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
-
modifications, and in Source or Object form, provided that You
|
|
93
|
-
meet the following conditions:
|
|
94
|
-
|
|
95
|
-
(a) You must give any other recipients of the Work or
|
|
96
|
-
Derivative Works a copy of this License; and
|
|
97
|
-
|
|
98
|
-
(b) You must cause any modified files to carry prominent notices
|
|
99
|
-
stating that You changed the files; and
|
|
100
|
-
|
|
101
|
-
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
-
that You distribute, all copyright, patent, trademark, and
|
|
103
|
-
attribution notices from the Source form of the Work,
|
|
104
|
-
excluding those notices that do not pertain to any part of
|
|
105
|
-
the Derivative Works; and
|
|
106
|
-
|
|
107
|
-
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
-
distribution, then any Derivative Works that You distribute must
|
|
109
|
-
include a readable copy of the attribution notices contained
|
|
110
|
-
within such NOTICE file, excluding those notices that do not
|
|
111
|
-
pertain to any part of the Derivative Works, in at least one
|
|
112
|
-
of the following places: within a NOTICE text file distributed
|
|
113
|
-
as part of the Derivative Works; within the Source form or
|
|
114
|
-
documentation, if provided along with the Derivative Works; or,
|
|
115
|
-
within a display generated by the Derivative Works, if and
|
|
116
|
-
wherever such third-party notices normally appear. The contents
|
|
117
|
-
of the NOTICE file are for informational purposes only and
|
|
118
|
-
do not modify the License. You may add Your own attribution
|
|
119
|
-
notices within Derivative Works that You distribute, alongside
|
|
120
|
-
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
-
that such additional attribution notices cannot be construed
|
|
122
|
-
as modifying the License.
|
|
123
|
-
|
|
124
|
-
You may add Your own copyright statement to Your modifications and
|
|
125
|
-
may provide additional or different license terms and conditions
|
|
126
|
-
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
-
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
-
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
-
the conditions stated in this License.
|
|
130
|
-
|
|
131
|
-
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
-
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
-
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
-
this License, without any additional terms or conditions.
|
|
135
|
-
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
-
the terms of any separate license agreement you may have executed
|
|
137
|
-
with Licensor regarding such Contributions.
|
|
138
|
-
|
|
139
|
-
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
-
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
-
except as required for reasonable and customary use in describing the
|
|
142
|
-
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
-
|
|
144
|
-
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
-
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
-
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
-
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
-
implied, including, without limitation, any warranties or conditions
|
|
149
|
-
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
-
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
-
appropriateness of using or redistributing the Work and assume any
|
|
152
|
-
risks associated with Your exercise of permissions under this License.
|
|
153
|
-
|
|
154
|
-
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
-
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
-
unless required by applicable law (such as deliberate and grossly
|
|
157
|
-
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
-
liable to You for damages, including any direct, indirect, special,
|
|
159
|
-
incidental, or consequential damages of any character arising as a
|
|
160
|
-
result of this License or out of the use or inability to use the
|
|
161
|
-
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
-
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
-
other commercial damages or losses), even if such Contributor
|
|
164
|
-
has been advised of the possibility of such damages.
|
|
165
|
-
|
|
166
|
-
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
-
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
-
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
-
or other liability obligations and/or rights consistent with this
|
|
170
|
-
License. However, in accepting such obligations, You may act only
|
|
171
|
-
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
-
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
-
defend, and hold each Contributor harmless for any liability
|
|
174
|
-
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
-
of your accepting any such warranty or additional liability.
|
|
176
|
-
|
|
177
|
-
END OF TERMS AND CONDITIONS
|
|
178
|
-
|
|
179
|
-
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
-
|
|
181
|
-
To apply the Apache License to your work, attach the following
|
|
182
|
-
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
-
replaced with your own identifying information. (Don't include
|
|
184
|
-
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
-
comment syntax for the file format. We also recommend that a
|
|
186
|
-
file or class name and description of purpose be included on the
|
|
187
|
-
same "printed page" as the copyright notice for easier
|
|
188
|
-
identification within third-party archives.
|
|
189
|
-
|
|
190
|
-
Copyright [yyyy] [name of copyright owner]
|
|
191
|
-
|
|
192
|
-
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
-
you may not use this file except in compliance with the License.
|
|
194
|
-
You may obtain a copy of the License at
|
|
195
|
-
|
|
196
|
-
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
-
|
|
198
|
-
Unless required by applicable law or agreed to in writing, software
|
|
199
|
-
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
-
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
-
See the License for the specific language governing permissions and
|
|
202
|
-
limitations under the License.
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|