Fix client certificate authentication on Mac and Linux introduced in r178732

net/data/ssl/certificates/README

 This directory contains various certificates for use with SSL-related
 unit tests.
 
 - google.binary.p7b
 - google.chain.pem
 - google.pem_cert.p7b
 - google.pem_pkcs7.p7b
 - google.pkcs7.p7b
 - google.single.der
 - google.single.pem
@@ skipping 130 matching lines @@
 - android-test-key-dsa-public.pem
 - android-test-key-ecdsa.pem
 - android-test-key-ecdsa-public.pem
      This is a set of test RSA/DSA/ECDSA keys used by the Android-specific
      unit test in net/android/keystore_unittest.c. They are used to verify
      that the OpenSSL-specific wrapper for platform PrivateKey objects
      works properly. See the generate-android-test-keys.sh script.
 
 - client_1.pem
 - client_1.key
-- client_1_root.pem
+- client_1_ca.pem
 - client_2.pem
 - client_2.key
-- client_2_root.pem
-     This is a set of files used to unit test SSL client authentication.
-     Generated by net/data/ssl/scripts/generate-client-certificates.sh.
-     Unit test is in net/socket/ssl_client_socket_openssl_unittest.cc.
-     - client_1_root.pem and client_2_root.pem are the certificates of
+- client_2_ca.pem
+     This is a set of files used to unit test SSL client certificate
+     authentication. These are generated by
+     net/data/ssl/scripts/generate-client-certificates.sh
+     - client_1_ca.pem and client_2_ca.pem are the certificates of
        two distinct signing CAs.
      - client_1.pem and client_1.key correspond to the certificate and
-       private key for a first certificate signed by client_1_root.pem.
+       private key for a first certificate signed by client_1_ca.pem.
      - client_2.pem and client_2.key correspond to the certificate and
-       private key for a second certificate signed by client_2_root.pem.
+       private key for a second certificate signed by client_2_ca.pem.
 
 - eku-test-root.pem
 - non-crit-codeSigning-chain.pem
 - crit-codeSigning-chain.pem
      Two code-signing certificates (eKU: codeSigning; eKU: critical,
      codeSigning) which we use to test that clients are making sure that web
      server certs are checked for correct eKU fields (when an eKU field is
      present). Since codeSigning is not valid for web server auth, the checks
      should fail.