nephele
/
haikuwebkit
1
0
Fork 0
Code Issues Releases Activity
haikuwebkit/LayoutTests/crypto/subtle/ecdh-import-pkcs8-key-p256-...

63 lines
4.1 KiB
HTML
Raw Permalink Normal View History

[WebCrypto] Add PKCS#8 import test that covers `parameters` and `publicKey` values in ECPrivateKey https://bugs.webkit.org/show_bug.cgi?id=174420 Reviewed by Darin Adler. Add test cases that cover testing of the optional ECParameters and publicKey bit string attributes in the ECPrivateKey ASN.1 structure that's embedded in the PKCS#8 PrivateKeyInfo ASN.1 structure. Per the spec, if the ECParameters attribute in the ECPrivateKey structure is present, the relevant curve object identifier should match the same curve identifier that's used in the ECParameters attribute of the AlgorithmIdentifier structure in PrivateKeyInfo. Both of these should of course match the curve that was specified for the import operation. For the publicKey bit string, the data contained there should be properly formatted for the specific curve, meaning it should be of proper curve-specific size and that it should use 0x04 as the leading byte, signalling an uncompressed EC point. On top of that the public key should have a valid value that positions it on the specified elliptic curve. These cases are covered for PKCS#8 key imports for P-256 and P-384 curves and for both ECDH and ECDSA algorithms in the newly-introduced tests. They are skipped on all platforms since no implementation in WebKit can pass them yet. * TestExpectations: * crypto/subtle/ecdh-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey-expected.txt: Added. * crypto/subtle/ecdh-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey.html: Added. * crypto/subtle/ecdh-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey-expected.txt: Added. * crypto/subtle/ecdh-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey.html: Added. * crypto/subtle/ecdsa-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey-expected.txt: Added. * crypto/subtle/ecdsa-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey.html: Added. * crypto/subtle/ecdsa-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey-expected.txt: Added. * crypto/subtle/ecdsa-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey.html: Added. Canonical link: https://commits.webkit.org/191815@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@220108 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2017-08-01 19:18:11 +00:00
<!DOCTYPE html>
<html>
<head>
<script src="../../resources/js-test.js"></script>
<script src="../resources/common.js"></script>
</head>
<body>
<p id="description"></p>
<div id="console"></div>
<script>
description("Test that importing P-256 EC keys for the ECDH algorithm through PKCS#8 fails in case of incorrect curve identifier or public key used in the ECPrivateKey structure");
jsTestIsAsync = true;
// Valid P-256 key that has matching named curve identifiers in ECParameters structures under
// both AlgorithmIdentifier parameters and under ECPrivateKey parameters in the PKCS#8 structure,
// as well as a valid public key under ECPrivateKey.
var pkcs8P256ValidKey = hexStringToUint8Array("308193020100301306072a8648ce3d020106082a8648ce3d0301070479307702010104203595fbf4dbf7ae788c5eae2f91c32a056dc2e8b37188edd50b2042bd767a97fba00a06082a8648ce3d030107a144034200040c6fc54db9cd81005b53fd7871b496712341531d1a2a0952b2f5ee192a560988563c3527d69bcf156c6eef098d3db3564ee77b6ecffb9f61486c8be7434fe4e2");
// Invalid P-256 key that has mismatched named curve identifiers in the mentioned ECParameters structures.
var pkcs8P256KeyMismatchedCurveIdentifiers = hexStringToUint8Array("308190020100301306072a8648ce3d020106082a8648ce3d0301070476307402010104203595fbf4dbf7ae788c5eae2f91c32a056dc2e8b37188edd50b2042bd767a97fba00706052b81040022a144034200040c6fc54db9cd81005b53fd7871b496712341531d1a2a0952b2f5ee192a560988563c3527d69bcf156c6eef098d3db3564ee77b6ecffb9f61486c8be7434fe4e2");
// Invalid P-256 key that has a public key of invalid length (its last byte is clipped).
var pkcs8P256KeyInvalidPublicKeyLength = hexStringToUint8Array("308186020100301306072a8648ce3d020106082a8648ce3d030107046c306a02010104203595fbf4dbf7ae788c5eae2f91c32a056dc2e8b37188edd50b2042bd767a97fba143034100040c6fc54db9cd81005b53fd7871b496712341531d1a2a0952b2f5ee192a560988563c3527d69bcf156c6eef098d3db3564ee77b6ecffb9f61486c8be7434fe4e2");
// Invalid P-256 key that has a public key of invalid EC point format (leading 0x05 byte instead of 0x04).
var pkcs8P256KeyInvalidPublicKeyECPointFormat= hexStringToUint8Array("308187020100301306072a8648ce3d020106082a8648ce3d030107046d306b02010104203595fbf4dbf7ae788c5eae2f91c32a056dc2e8b37188edd50b2042bd767a97fba144034200050c6fc54db9cd81005b53fd7871b496712341531d1a2a0952b2f5ee192a560988563c3527d69bcf156c6eef098d3db3564ee77b6ecffb9f61486c8be7434fe4e2");
// Invalid P-256 key that has a public key of invalid value (0xabad1dea).
var pkcs8P256KeyInvalidPublicKey = hexStringToUint8Array("308187020100301306072a8648ce3d020106082a8648ce3d030107046d306b02010104203595fbf4dbf7ae788c5eae2f91c32a056dc2e8b37188edd50b2042bd767a97fba14403420004000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000abad1dea");
function importKey(keyData)
{
return crypto.subtle.importKey("pkcs8", keyData, { name: "ECDH", namedCurve: "P-256" }, true, [ "deriveKey", "deriveBits" ]);
}
Promise.resolve().then(function(result) {
debug("ECDH: importing P-256 key that uses matching curve identifiers and valid public key in ECParameters structures in PKCS#8 ...");
return importKey(pkcs8P256ValidKey);
}).then(function(result) {
testPassed("Successfully imported a P-256 key.");
debug("ECDH: importing P-256 key whose curve identifiers in ECParameters structures in PKCS#8 don't match ...");
Use shouldRejectWithErrorName after r260579. The mentioned revision made shouldRejectWithErrorName (and shouldReject) actually omit the error name when it was not requested. So now to catch the desired error we must actually request it instead of just relying on the expectation file messages. Unreviewed test gardening. * crypto/subtle/ecdh-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey.html: * crypto/subtle/ecdh-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey.html: * crypto/subtle/ecdsa-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey.html: * crypto/subtle/ecdsa-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey.html: Canonical link: https://commits.webkit.org/223840@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@260618 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2020-04-24 04:46:07 +00:00
return shouldRejectWithErrorName('importKey(pkcs8P256KeyMismatchedCurveIdentifiers)', 'DataError');
[WebCrypto] Add PKCS#8 import test that covers `parameters` and `publicKey` values in ECPrivateKey https://bugs.webkit.org/show_bug.cgi?id=174420 Reviewed by Darin Adler. Add test cases that cover testing of the optional ECParameters and publicKey bit string attributes in the ECPrivateKey ASN.1 structure that's embedded in the PKCS#8 PrivateKeyInfo ASN.1 structure. Per the spec, if the ECParameters attribute in the ECPrivateKey structure is present, the relevant curve object identifier should match the same curve identifier that's used in the ECParameters attribute of the AlgorithmIdentifier structure in PrivateKeyInfo. Both of these should of course match the curve that was specified for the import operation. For the publicKey bit string, the data contained there should be properly formatted for the specific curve, meaning it should be of proper curve-specific size and that it should use 0x04 as the leading byte, signalling an uncompressed EC point. On top of that the public key should have a valid value that positions it on the specified elliptic curve. These cases are covered for PKCS#8 key imports for P-256 and P-384 curves and for both ECDH and ECDSA algorithms in the newly-introduced tests. They are skipped on all platforms since no implementation in WebKit can pass them yet. * TestExpectations: * crypto/subtle/ecdh-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey-expected.txt: Added. * crypto/subtle/ecdh-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey.html: Added. * crypto/subtle/ecdh-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey-expected.txt: Added. * crypto/subtle/ecdh-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey.html: Added. * crypto/subtle/ecdsa-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey-expected.txt: Added. * crypto/subtle/ecdsa-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey.html: Added. * crypto/subtle/ecdsa-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey-expected.txt: Added. * crypto/subtle/ecdsa-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey.html: Added. Canonical link: https://commits.webkit.org/191815@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@220108 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2017-08-01 19:18:11 +00:00
}).then(function(result) {
debug("ECDH: importing P-256 key that has a public key in PKCS#8 of invalid length ...");
Use shouldRejectWithErrorName after r260579. The mentioned revision made shouldRejectWithErrorName (and shouldReject) actually omit the error name when it was not requested. So now to catch the desired error we must actually request it instead of just relying on the expectation file messages. Unreviewed test gardening. * crypto/subtle/ecdh-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey.html: * crypto/subtle/ecdh-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey.html: * crypto/subtle/ecdsa-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey.html: * crypto/subtle/ecdsa-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey.html: Canonical link: https://commits.webkit.org/223840@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@260618 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2020-04-24 04:46:07 +00:00
return shouldRejectWithErrorName('importKey(pkcs8P256KeyInvalidPublicKeyLength)', 'DataError');
[WebCrypto] Add PKCS#8 import test that covers `parameters` and `publicKey` values in ECPrivateKey https://bugs.webkit.org/show_bug.cgi?id=174420 Reviewed by Darin Adler. Add test cases that cover testing of the optional ECParameters and publicKey bit string attributes in the ECPrivateKey ASN.1 structure that's embedded in the PKCS#8 PrivateKeyInfo ASN.1 structure. Per the spec, if the ECParameters attribute in the ECPrivateKey structure is present, the relevant curve object identifier should match the same curve identifier that's used in the ECParameters attribute of the AlgorithmIdentifier structure in PrivateKeyInfo. Both of these should of course match the curve that was specified for the import operation. For the publicKey bit string, the data contained there should be properly formatted for the specific curve, meaning it should be of proper curve-specific size and that it should use 0x04 as the leading byte, signalling an uncompressed EC point. On top of that the public key should have a valid value that positions it on the specified elliptic curve. These cases are covered for PKCS#8 key imports for P-256 and P-384 curves and for both ECDH and ECDSA algorithms in the newly-introduced tests. They are skipped on all platforms since no implementation in WebKit can pass them yet. * TestExpectations: * crypto/subtle/ecdh-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey-expected.txt: Added. * crypto/subtle/ecdh-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey.html: Added. * crypto/subtle/ecdh-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey-expected.txt: Added. * crypto/subtle/ecdh-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey.html: Added. * crypto/subtle/ecdsa-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey-expected.txt: Added. * crypto/subtle/ecdsa-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey.html: Added. * crypto/subtle/ecdsa-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey-expected.txt: Added. * crypto/subtle/ecdsa-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey.html: Added. Canonical link: https://commits.webkit.org/191815@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@220108 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2017-08-01 19:18:11 +00:00
}).then(function(result) {
debug("ECDH: importing P-256 key that has a public key in PKCS#8 of invalid EC point format ...");
Use shouldRejectWithErrorName after r260579. The mentioned revision made shouldRejectWithErrorName (and shouldReject) actually omit the error name when it was not requested. So now to catch the desired error we must actually request it instead of just relying on the expectation file messages. Unreviewed test gardening. * crypto/subtle/ecdh-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey.html: * crypto/subtle/ecdh-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey.html: * crypto/subtle/ecdsa-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey.html: * crypto/subtle/ecdsa-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey.html: Canonical link: https://commits.webkit.org/223840@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@260618 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2020-04-24 04:46:07 +00:00
return shouldRejectWithErrorName('importKey(pkcs8P256KeyInvalidPublicKeyECPointFormat)', 'DataError');
[WebCrypto] Add PKCS#8 import test that covers `parameters` and `publicKey` values in ECPrivateKey https://bugs.webkit.org/show_bug.cgi?id=174420 Reviewed by Darin Adler. Add test cases that cover testing of the optional ECParameters and publicKey bit string attributes in the ECPrivateKey ASN.1 structure that's embedded in the PKCS#8 PrivateKeyInfo ASN.1 structure. Per the spec, if the ECParameters attribute in the ECPrivateKey structure is present, the relevant curve object identifier should match the same curve identifier that's used in the ECParameters attribute of the AlgorithmIdentifier structure in PrivateKeyInfo. Both of these should of course match the curve that was specified for the import operation. For the publicKey bit string, the data contained there should be properly formatted for the specific curve, meaning it should be of proper curve-specific size and that it should use 0x04 as the leading byte, signalling an uncompressed EC point. On top of that the public key should have a valid value that positions it on the specified elliptic curve. These cases are covered for PKCS#8 key imports for P-256 and P-384 curves and for both ECDH and ECDSA algorithms in the newly-introduced tests. They are skipped on all platforms since no implementation in WebKit can pass them yet. * TestExpectations: * crypto/subtle/ecdh-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey-expected.txt: Added. * crypto/subtle/ecdh-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey.html: Added. * crypto/subtle/ecdh-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey-expected.txt: Added. * crypto/subtle/ecdh-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey.html: Added. * crypto/subtle/ecdsa-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey-expected.txt: Added. * crypto/subtle/ecdsa-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey.html: Added. * crypto/subtle/ecdsa-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey-expected.txt: Added. * crypto/subtle/ecdsa-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey.html: Added. Canonical link: https://commits.webkit.org/191815@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@220108 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2017-08-01 19:18:11 +00:00
}).then(function(result) {
debug("ECDH: importing P-256 key that has an invalid public key in PKCS#8 ...");
Use shouldRejectWithErrorName after r260579. The mentioned revision made shouldRejectWithErrorName (and shouldReject) actually omit the error name when it was not requested. So now to catch the desired error we must actually request it instead of just relying on the expectation file messages. Unreviewed test gardening. * crypto/subtle/ecdh-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey.html: * crypto/subtle/ecdh-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey.html: * crypto/subtle/ecdsa-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey.html: * crypto/subtle/ecdsa-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey.html: Canonical link: https://commits.webkit.org/223840@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@260618 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2020-04-24 04:46:07 +00:00
return shouldRejectWithErrorName('importKey(pkcs8P256KeyInvalidPublicKey)', 'DataError');
[WebCrypto] Add PKCS#8 import test that covers `parameters` and `publicKey` values in ECPrivateKey https://bugs.webkit.org/show_bug.cgi?id=174420 Reviewed by Darin Adler. Add test cases that cover testing of the optional ECParameters and publicKey bit string attributes in the ECPrivateKey ASN.1 structure that's embedded in the PKCS#8 PrivateKeyInfo ASN.1 structure. Per the spec, if the ECParameters attribute in the ECPrivateKey structure is present, the relevant curve object identifier should match the same curve identifier that's used in the ECParameters attribute of the AlgorithmIdentifier structure in PrivateKeyInfo. Both of these should of course match the curve that was specified for the import operation. For the publicKey bit string, the data contained there should be properly formatted for the specific curve, meaning it should be of proper curve-specific size and that it should use 0x04 as the leading byte, signalling an uncompressed EC point. On top of that the public key should have a valid value that positions it on the specified elliptic curve. These cases are covered for PKCS#8 key imports for P-256 and P-384 curves and for both ECDH and ECDSA algorithms in the newly-introduced tests. They are skipped on all platforms since no implementation in WebKit can pass them yet. * TestExpectations: * crypto/subtle/ecdh-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey-expected.txt: Added. * crypto/subtle/ecdh-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey.html: Added. * crypto/subtle/ecdh-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey-expected.txt: Added. * crypto/subtle/ecdh-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey.html: Added. * crypto/subtle/ecdsa-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey-expected.txt: Added. * crypto/subtle/ecdsa-import-pkcs8-key-p256-validate-ecprivatekey-parameters-publickey.html: Added. * crypto/subtle/ecdsa-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey-expected.txt: Added. * crypto/subtle/ecdsa-import-pkcs8-key-p384-validate-ecprivatekey-parameters-publickey.html: Added. Canonical link: https://commits.webkit.org/191815@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@220108 268f45cc-cd09-0410-ab3c-d52691b4dbfc
2017-08-01 19:18:11 +00:00
}).then(function(result) {
finishJSTest();
});;
</script>
</body>
</html>