Modified: trunk/LayoutTests/ChangeLog (280845 => 280846)
--- trunk/LayoutTests/ChangeLog 2021-08-10 16:35:00 UTC (rev 280845)
+++ trunk/LayoutTests/ChangeLog 2021-08-10 16:56:35 UTC (rev 280846)
@@ -1,3 +1,14 @@
+2021-08-10 Arcady Goldmints-Orlov <[email protected]>
+
+ [GLIB] Update crypto test baselines after r280790
+ https://bugs.webkit.org/show_bug.cgi?id=228957
+
+ Unreviewed test gardening.
+
+ * platform/glib/TestExpectations:
+ * platform/glib/crypto/subtle/aes-cbc-cfb-decrypt-malformed-parameters-expected.txt:
+ * platform/glib/crypto/subtle/aes-cbc-cfb-encrypt-malformed-parameters-expected.txt:
+
2021-08-10 Ayumi Kojima <[email protected]>
[ MacOS ] inspector/canvas/shaderProgram-add-remove-webgl2.html is flaky.
Modified: trunk/LayoutTests/platform/glib/TestExpectations (280845 => 280846)
--- trunk/LayoutTests/platform/glib/TestExpectations 2021-08-10 16:35:00 UTC (rev 280845)
+++ trunk/LayoutTests/platform/glib/TestExpectations 2021-08-10 16:56:35 UTC (rev 280846)
@@ -1193,6 +1193,9 @@
# TODO: This failure exists in the general TestExpectations, I got in a GTK run.
# I think marking the whole folder as 'Slow' makes the expected result for this test 'Pass'.
imported/w3c/web-platform-tests/WebCryptoAPI/generateKey/successes_RSA-OAEP.https.any.worker.html [ Failure Pass ]
+imported/w3c/web-platform-tests/WebCryptoAPI/encrypt_decrypt/aes_ctr.https.any.html [ DumpJSConsoleLogInStdErr ]
+imported/w3c/web-platform-tests/WebCryptoAPI/encrypt_decrypt/aes_cbc.https.any.html [ DumpJSConsoleLogInStdErr ]
+imported/w3c/web-platform-tests/WebCryptoAPI/wrapKey_unwrapKey/wrapKey_unwrapKey.https.any.html [ Failure Pass ]
webkit.org/b/186638 imported/w3c/web-platform-tests/xhr/send-timeout-events.htm [ Failure Pass ]
Modified: trunk/LayoutTests/platform/glib/crypto/subtle/aes-cbc-cfb-decrypt-malformed-parameters-expected.txt (280845 => 280846)
--- trunk/LayoutTests/platform/glib/crypto/subtle/aes-cbc-cfb-decrypt-malformed-parameters-expected.txt 2021-08-10 16:35:00 UTC (rev 280845)
+++ trunk/LayoutTests/platform/glib/crypto/subtle/aes-cbc-cfb-decrypt-malformed-parameters-expected.txt 2021-08-10 16:56:35 UTC (rev 280846)
@@ -1,3 +1,6 @@
+CONSOLE MESSAGE: AES-CBC and AES-CTR do not provide authentication by default, and implementing it manually can result in minor, but serious mistakes. We recommended using authenticated encryption like AES-GCM to protect against chosen-ciphertext attacks.
+CONSOLE MESSAGE: AES-CBC and AES-CTR do not provide authentication by default, and implementing it manually can result in minor, but serious mistakes. We recommended using authenticated encryption like AES-GCM to protect against chosen-ciphertext attacks.
+CONSOLE MESSAGE: AES-CBC and AES-CTR do not provide authentication by default, and implementing it manually can result in minor, but serious mistakes. We recommended using authenticated encryption like AES-GCM to protect against chosen-ciphertext attacks.
Test decrypting using AES-CBC/AES-CFB with malformed parameters
On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
Modified: trunk/LayoutTests/platform/glib/crypto/subtle/aes-cbc-cfb-encrypt-malformed-parameters-expected.txt (280845 => 280846)
--- trunk/LayoutTests/platform/glib/crypto/subtle/aes-cbc-cfb-encrypt-malformed-parameters-expected.txt 2021-08-10 16:35:00 UTC (rev 280845)
+++ trunk/LayoutTests/platform/glib/crypto/subtle/aes-cbc-cfb-encrypt-malformed-parameters-expected.txt 2021-08-10 16:56:35 UTC (rev 280846)
@@ -1,3 +1,15 @@
+CONSOLE MESSAGE: AES-CBC and AES-CTR do not provide authentication by default, and implementing it manually can result in minor, but serious mistakes. We recommended using authenticated encryption like AES-GCM to protect against chosen-ciphertext attacks.
+CONSOLE MESSAGE: AES-CBC and AES-CTR do not provide authentication by default, and implementing it manually can result in minor, but serious mistakes. We recommended using authenticated encryption like AES-GCM to protect against chosen-ciphertext attacks.
+CONSOLE MESSAGE: AES-CBC and AES-CTR do not provide authentication by default, and implementing it manually can result in minor, but serious mistakes. We recommended using authenticated encryption like AES-GCM to protect against chosen-ciphertext attacks.
+CONSOLE MESSAGE: AES-CBC and AES-CTR do not provide authentication by default, and implementing it manually can result in minor, but serious mistakes. We recommended using authenticated encryption like AES-GCM to protect against chosen-ciphertext attacks.
+CONSOLE MESSAGE: AES-CBC and AES-CTR do not provide authentication by default, and implementing it manually can result in minor, but serious mistakes. We recommended using authenticated encryption like AES-GCM to protect against chosen-ciphertext attacks.
+CONSOLE MESSAGE: AES-CBC and AES-CTR do not provide authentication by default, and implementing it manually can result in minor, but serious mistakes. We recommended using authenticated encryption like AES-GCM to protect against chosen-ciphertext attacks.
+CONSOLE MESSAGE: AES-CBC and AES-CTR do not provide authentication by default, and implementing it manually can result in minor, but serious mistakes. We recommended using authenticated encryption like AES-GCM to protect against chosen-ciphertext attacks.
+CONSOLE MESSAGE: AES-CBC and AES-CTR do not provide authentication by default, and implementing it manually can result in minor, but serious mistakes. We recommended using authenticated encryption like AES-GCM to protect against chosen-ciphertext attacks.
+CONSOLE MESSAGE: AES-CBC and AES-CTR do not provide authentication by default, and implementing it manually can result in minor, but serious mistakes. We recommended using authenticated encryption like AES-GCM to protect against chosen-ciphertext attacks.
+CONSOLE MESSAGE: AES-CBC and AES-CTR do not provide authentication by default, and implementing it manually can result in minor, but serious mistakes. We recommended using authenticated encryption like AES-GCM to protect against chosen-ciphertext attacks.
+CONSOLE MESSAGE: AES-CBC and AES-CTR do not provide authentication by default, and implementing it manually can result in minor, but serious mistakes. We recommended using authenticated encryption like AES-GCM to protect against chosen-ciphertext attacks.
+CONSOLE MESSAGE: AES-CBC and AES-CTR do not provide authentication by default, and implementing it manually can result in minor, but serious mistakes. We recommended using authenticated encryption like AES-GCM to protect against chosen-ciphertext attacks.
Test encrypting using AES-CBC/AES-CFB with malformed parameters
On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
