Upload pk8 key files for ClientCertStoreChromeOS unittest.

This uploads key files before changing the unit test, as the Commit-Queue has problems with binary files.

Main CL will be committed afterwards: https://codereview.chromium.org/394013005/

BUG=210525, 329735, 315285
TBR=rsleevi@chromium.org

Review URL: https://codereview.chromium.org/399103002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283765 0039d316-1c4b-4281-b951-d872f2087c98

net/data/ssl/certificates/README

@@ -149,9 +149,11 @@ unit tests.
 
 - client_1.pem
 - client_1.key
+- client_1.pk8
 - client_1_ca.pem
 - client_2.pem
 - client_2.key
+- client_2.pk8
 - client_2_ca.pem
      This is a set of files used to unit test SSL client certificate
      authentication. These are generated by
@@ -162,6 +164,8 @@ unit tests.
        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_ca.pem.
+     - each .pk8 file contains the same key as the corresponding .key file
+       as PKCS#8 PrivateKeyInfo in DER encoding.
 
 - eku-test-root.pem
 - non-crit-codeSigning-chain.pem

net/data/ssl/scripts/generate-client-certificates.sh

@@ -113,6 +113,12 @@ do
     -key out/$id.key \
     -out out/$id.csr \
     -config client-certs.cnf
+  # Store the private key also in PKCS#8 format.
+  try openssl pkcs8 \
+    -topk8 -nocrypt \
+    -in out/$id.key \
+    -outform DER \
+    -out out/$id.pk8
 done
 
 echo B signs A
@@ -157,8 +163,10 @@ try openssl pkcs12 \
 echo Package the client certs for unit tests
 try cp out/A.pem ../certificates/client_1.pem
 try cp out/A.key ../certificates/client_1.key
+try cp out/A.pk8 ../certificates/client_1.pk8
 try cp out/B.pem ../certificates/client_1_ca.pem
 
 try cp out/D.pem ../certificates/client_2.pem
 try cp out/D.key ../certificates/client_2.key
+try cp out/D.pk8 ../certificates/client_2.pk8
 try cp out/E.pem ../certificates/client_2_ca.pem