Comment #13 on issue 16360 by [email protected]: non-admin auto-update
http://code.google.com/p/chromium/issues/detail?id=16360
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=33241
------------------------------------------------------------------------
r33241 | [email protected] | 2009-11-28 14:05:11 -0800 (Sat, 28 Nov 2009) |
44 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/build/common.gypi?r1=33241&r2=33240
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/app/generated_resources.grd?r1=33241&r2=33240
D /trunk/src/chrome/app/keystone_glue.h
D /trunk/src/chrome/app/keystone_glue.mm
D /trunk/src/chrome/app/keystone_glue_unittest.mm
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/app/nibs/About.xib?r1=33241&r2=33240
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/app_controller_mac.mm?r1=33241&r2=33240
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/browser.cc?r1=33241&r2=33240
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/browser_init.cc?r1=33241&r2=33240
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/browser_main_mac.mm?r1=33241&r2=33240
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/about_window_controller.h?r1=33241&r2=33240
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/about_window_controller.mm?r1=33241&r2=33240
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/about_window_controller_unittest.mm?r1=33241&r2=33240
A
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/authorization_util.cc
A
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/authorization_util.h
A
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/keystone_glue.h
A
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/keystone_glue.mm
A
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/keystone_glue_unittest.mm
A
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/keystone_infobar.h
A
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/keystone_infobar.mm
A
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/keystone_promote_postflight.sh
A
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/keystone_promote_preflight.sh
A
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/cocoa/scoped_authorizationref.h
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/chrome.gyp?r1=33241&r2=33240
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/pref_names.cc?r1=33241&r2=33240
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/pref_names.h?r1=33241&r2=33240
In-application Keystone ticket promotion.
The concept of "ticket promotion" is added to the application when Keystone
is
in use. Ticket promotion is used to turn a user Keystone ticket, which
Chrome
normally establishes when it launches, into a system Keystone ticket, after
successful user authentication and authorization. Having a system Keystone
with a system ticket means that updates are applied with root privileges
instead of user privileges, essentially eliminating the possibility that a
user will fall off of the auto-update train because they can read and
execute
but not write the application.
Two principles of promotion apply:
- An application on a user ticket NEEDS promotion if it determines that it
doesn't have permission to write to itself. Being on a user ticket, an
update attempt would fail.
- An application on a user ticket WANTS promotion if it already NEEDS
promotion. Additionally, if it is installed in a system-wide location
such as /Applications, it will WANT promotion, even if it does not NEED
it.
If promotion is needed, an info bar will show up on launch requesting it.
This info bar works similarly to the default browser info bar: it has
a "don't
bother me again" button, it will only show up after the first launch, it
won't
disappear on navigation if the navigation happens very quickly, and it won't
show itself if another info bar is up. This means that if both the default
browser info bar and the promotion info bar have a shot at showing, only one
will win. In my experience, each wins about half of the time.
If promotion is needed, the update UI in the About window will be hidden.
Checking for updates and offering to apply them doesn't make much sense when
the update won't be able to install successfully. All of the auto-update
machinery is still working in the background, but the About window UI is
hidden.
If promotion is wanted, the About window will contain a new button allowing
the user to enter promotion. This gives access to the same promotion
routine
as the promotion info bar. It can be used even from an administrative
account
that is able to update the application without promotion. It's intended to
be
used by the system administrator of the family without requiring them to
switch to one of the kids' accounts.
BUG=16360
TEST=Exhaustively, please.
Review URL: http://codereview.chromium.org/437053
------------------------------------------------------------------------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
