Update keygen to use correct NSS slot on ChromeOS multiprofile.

chrome/browser/ui/crypto_module_delegate_nss.h

+// Copyright (c) 2013 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef CHROME_BROWSER_UI_CRYPTO_MODULE_DELEGATE_NSS_H_
+#define CHROME_BROWSER_UI_CRYPTO_MODULE_DELEGATE_NSS_H_
+
+#include <string>
+
+#include "chrome/browser/ui/crypto_module_password_dialog.h"
+
+namespace content {
+class ResourceContext;
+}
+
+namespace crypto {
+class NSSCryptoModuleDelegate;
+}
+
+namespace chrome {
+
+// Creates a NSSCryptoModuleDelegate.  The Initalize method must be called on
+// the IO thread, and |context| must still be valid at the time Initalize is
+// called.  The RequestPassword method must be called on a worker thread.
+crypto::NSSCryptoModuleDelegate* CreateNSSCryptoModuleDelegate(
+    content::ResourceContext* context,
+    CryptoModulePasswordReason reason,
+    const std::string& server);

[Ryan Sleevi, 2013/11/26 20:13:17]

naming nit: It's not clear to me what |server| is. Is it a host-port tuple? Just
a hostname? A URL?

hostname / host_and_port ?

design: It does feel weird that you're documenting how to use the
NSSCryptoModuleDelegate in this factory function, rather than as part of the
crypto::NSSCryptoModuleDelegate. That you're imposing additional threading
requirements on where methods can be called definitely seems to violate the is-a
inheritance principle.

[mattm, 2013/12/03 00:40:54]

It does seem to be a bit underspecified. Some places pass host:port, keygen is
just passing hostname. Would be good to standardize on something, but I don't
really have a feeling for what.

+
+}  // namespace chrome
+
+#endif  // CHROME_BROWSER_UI_CRYPTO_MODULE_DELEGATE_NSS_H_