Move client certificates retrieval logic out of the SSL sockets.

net/data/ssl/scripts/client_authentication/run-test-server.sh

Index: net/data/ssl/scripts/client_authentication/run-test-server.sh
diff --git a/net/data/ssl/scripts/client_authentication/run-test-server.sh b/net/data/ssl/scripts/client_authentication/run-test-server.sh
new file mode 100755
index 0000000000000000000000000000000000000000..adac3a5eba43849b66f1ae9fe66115c69697572b
--- /dev/null
+++ b/net/data/ssl/scripts/client_authentication/run-test-server.sh
@@ -0,0 +1,12 @@
+#!/bin/bash
+
+# Helper script for local manual testing. Runs an openssl test server at
+# localhost:4433. The server will be accessible for www connections and will
+# require a client certificate issued by Client Auth Test Root 1.
+openssl s_server \
+  -accept 4433 \
+  -cert out/root_1.pem \
+  -key out/root_1.key \
+  -www \
+  -Verify 5 \
+  -CAfile out/root_1.pem

[Ryan Sleevi, 2013/01/29 19:59:49]

For checking in, this should be a 'real' test using TestServer. Simply having
this script has no guarantees that it won't get broken in the future, so I'm not
sure it helps anyone.

[ppi, 2013/01/30 15:34:56]

This is just a tiny helper that I thought could be helpful to anyone willing to
manually test client authentication in Chrome (certainly such script would be
helpful to me if we had it before).

That being said, I agree that it is at least optional if not redundant - please
let me know if you would like it out of the patch set.