Added authorized install with a script to do the copy.

chrome/installer/mac/app/AuthorizedInstall.m

Index: chrome/installer/mac/app/AuthorizedInstall.m
diff --git a/chrome/installer/mac/app/AuthorizedInstall.m b/chrome/installer/mac/app/AuthorizedInstall.m
new file mode 100644
index 0000000000000000000000000000000000000000..550f718daf308d51e9cb542aee9277b34703097f
--- /dev/null
+++ b/chrome/installer/mac/app/AuthorizedInstall.m
@@ -0,0 +1,85 @@
+// Copyright 2016 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.
+
+#import "AuthorizedInstall.h"
+
+@implementation AuthorizedInstall
+
+// Does the setup needed to authorize a tool to run as admin.
+- (BOOL)setUpAuthorization {
+  status_ = AuthorizationCreate(NULL, kAuthorizationEmptyEnvironment,
+                                kAuthorizationFlagDefaults, &authRef_);
+
+  AuthorizationItem items = {kAuthorizationRightExecute, 0, NULL, 0};
+  AuthorizationRights rights = {1, &items};
+  AuthorizationFlags flags =
+      kAuthorizationFlagDefaults | kAuthorizationFlagInteractionAllowed |
+      kAuthorizationFlagPreAuthorize | kAuthorizationFlagExtendRights;
+
+  status_ = AuthorizationCopyRights(authRef_, &rights, NULL, flags, NULL);
+  return (status_ == errAuthorizationSuccess);
+}
+
+// Starts up the proccess with privileged permissios.
+- (void)startAuthorizedTool:(const char*)toolPath
+              withArguments:(const char**)args {
+  if (status_ != errAuthorizationSuccess)
+    return;
+
+#pragma clang diagnostic push
+#pragma clang diagnostic ignored "-Wdeprecated-declarations"

[Anna Zeng, 2016/08/18 15:57:16]

Mark (mark@chromium.org): Have we tried NSAppleScript yet?
(https://developer.apple.com/library/mac/documentation/Cocoa/Reference/Foundat...)
Ivan did mention we've determined SMJobBless was not a viable alternative, but
is NSAppleScript possible?

+  status_ = AuthorizationExecuteWithPrivileges(
+      authRef_, toolPath, kAuthorizationFlagDefaults, (char* const*)args,
+      &communicationPipe_);
+#pragma clang diagnostic pop
+}
+
+// Finds the tool to be authorized, Finds the paths needed for the tool to do
+// its job, and starts the process.
+// TODO: Move attemptAuthorizedInstall body into Unpacker method which will

[Anna Zeng, 2016/08/18 15:57:16]

As discussed, we're actually going to have AuthorizedInstall take care of
putting Chrome into the Applications folder of choice.

[ivanhernandez, 2016/08/22 15:34:49]

Done.

+// provide alternative in the case where authorization failed.
+- (BOOL)authorizeInstallationTool {
+  NSString* toolPath =
+      [[NSBundle mainBundle] pathForResource:@"copy_to_disk" ofType:@"sh"];
+  NSFileManager* manager = [NSFileManager defaultManager];
+  if (![manager fileExistsAtPath:toolPath]) {
+    return false;
+  }
+
+  NSString* appBundleName = @"Google Chrome.app";
+
+  NSArray* applicationDirectories = NSSearchPathForDirectoriesInDomains(
+      NSApplicationDirectory, NSLocalDomainMask, YES);
+  NSString* applicationDirectory = applicationDirectories.firstObject;
+
+  // TODO: Change sourceAppBundlePath to the temporary folder that chrome will
+  // be downloaded and extracted to.
+  NSArray* downloadDirectories = NSSearchPathForDirectoriesInDomains(
+      NSDownloadsDirectory, NSUserDomainMask, YES);
+  NSString* sourceAppBundlePath = [NSString

[Anna Zeng, 2016/08/18 15:57:16]

We can make this a parameter.

[ivanhernandez, 2016/08/22 15:34:49]

We could but we would need to make some changes to unpacker first. The thing is
that this method runs at the very beginning of the program. The Unpacker creates
the temporary directory. Theres no way to know what that directory will be at
this point. We could just simply create the temporary directory at the beginning
and then pass it to both this and to the unpacker.

+      pathWithComponents:@[ downloadDirectories.firstObject, appBundleName ]];
+  NSString* destinationAppBundlePath =

[Anna Zeng, 2016/08/18 15:57:16]

If root, this can just be @"/Applications/Google Chrome.app". Is there any
particular reason this needs to be found programmatically, or cannot be
hardcoded in such a way?

If not root, we can use `[[NSFileManager defaultManager]
isWritableFileAtPath:@"/Applications/"]` to check if it's actually writeable
before feeding in the path. I think that logic definitely belongs in here.

[ivanhernandez, 2016/08/22 15:34:49]

I don't know actually. Its true the path will always be "/Applications/Google
Chrome.app" for root unless Apple decides to do some major OS redesign. But
seeing as thats highly unlikely I suppose either way would be okay. Maybe Elly
or Mark can weigh in on which choice is better.

+      [NSString pathWithComponents:@[ applicationDirectory, appBundleName ]];
+
+  const char* sourcePath = [sourceAppBundlePath UTF8String];
+  const char* destinationPath = [applicationDirectory UTF8String];
+  const char* fullDestinationPath = [destinationAppBundlePath UTF8String];
+  const char* args[] = {sourcePath, destinationPath, fullDestinationPath, NULL};
+
+  if ([self setUpAuthorization]) {
+    [self startAuthorizedTool:[toolPath UTF8String] withArguments:args];
+    AuthorizationFree(authRef_, kAuthorizationFlagDestroyRights);
+  }
+  return (status_ == errAuthorizationSuccess);
+}
+
+// Sends a message to the auhtorized tool's stdin.
+- (void)sendMessageToTool:(NSString*)message {
+  if (communicationPipe_ != NULL) {
+    const char* readyState = message.UTF8String;
+    write(fileno(communicationPipe_), readyState, sizeof(readyState));
+  }
+}
+
+@end