[Mac] Add option to reauthenticate the OS user before revealing passwords.

chrome/browser/password_manager/password_manager_util.h

Index: chrome/browser/password_manager/password_manager_util.h
diff --git a/chrome/browser/password_manager/password_manager_util.h b/chrome/browser/password_manager/password_manager_util.h
new file mode 100644
index 0000000000000000000000000000000000000000..fe05a848389174d2e4517c0b29efad0a9648895b
--- /dev/null
+++ b/chrome/browser/password_manager/password_manager_util.h
@@ -0,0 +1,18 @@
+// 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_PASSWORD_MANAGER_PASSWORD_MANAGER_UTIL_H_
+#define CHROME_BROWSER_PASSWORD_MANAGER_PASSWORD_MANAGER_UTIL_H_
+
+namespace password_manager_util {
+
+// Attempts to (re-)authenticate the user of the OS account. Returns true if
+// the user was successfully authenticated, or if authentication was not
+// possible. On platforms where reauthentication is not possible or does not
+// make sense, the default implementation always returns true.
+bool AuthenticateUser();

[Nico, 2013/10/18 14:47:57]

As is, this api forces the implementation to run a nested message loop. Should
this get a "done" callback instead?

[Patrick Dubroy, 2013/10/18 15:24:01]

I think on most platforms it will simply call into a native API to show a modal
dialog, so this seems like the simplest approach for now. 

+
+}  // namespace password_manager_util
+
+#endif  // CHROME_BROWSER_PASSWORD_MANAGER_PASSWORD_MANAGER_UTIL_H_