From 9953aa3fafcbf323d44da5fc44153698b3769ddf Mon Sep 17 00:00:00 2001 From: Chris Masone Date: Tue, 4 Oct 2011 14:25:10 -0700 Subject: [PATCH] [crosutils] Make auth-testing cert CN be *.google.com It seems that the intermittent failure we see on the login screen is due to a sort of mixed-content error, where there's a failure within the page to load some embedded resource due to a cert error. Make the SSL cert we inject work for any google.com server to work around this. BUG=chromium-os:20323 TEST=login_CryptohomeMounted 50x, suite_Smoke Change-Id: Ic8e5b9bec799cd19cccfeddd2990fe3a494d2184 Reviewed-on: http://gerrit.chromium.org/gerrit/8818 Reviewed-by: Chris Sosa Commit-Ready: Chris Masone Tested-by: Chris Masone --- mod_for_test_scripts/710enableAuthTesting | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mod_for_test_scripts/710enableAuthTesting b/mod_for_test_scripts/710enableAuthTesting index 690100730b..03d4cf84ca 100755 --- a/mod_for_test_scripts/710enableAuthTesting +++ b/mod_for_test_scripts/710enableAuthTesting @@ -35,7 +35,7 @@ sudo mount --bind /proc "${ROOT_FS_DIR}"/proc # Generate testing root cert on the fly. sudo chroot "${ROOT_FS_DIR}" ${QEMU} /usr/bin/openssl req -x509 -days 21 \ - -subj "/CN=www.google.com" \ + -subj "/CN=*.google.com" \ -newkey rsa:1024 -nodes -keyout "${TMP_KEY}" -out "${TMP_CERT}" mkdir -m 0755 -p "${ROOT_FS_DIR}/${FAKE_NSSDB}"