New issue
Advanced search Search tips

Issue 682637 link

Starred by 2 users
Status: Verified
Owner:
ljusten@chromium.org
Closed: Jan 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Chromad: Use "Chrome OS" policies on branded builds

Project Member Reported by tnagel@chromium.org, Jan 19 2017 
It seems that the parser is currently looking for "Chromium OS" registry keys.

Comment 1 by ljusten@chromium.org, Jan 19 2017

Status: Started (was: Assigned)
Project Member

Comment 2 by bugdroid1@chromium.org, Jan 20 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform2/+/e93d10da797b71c99742ae99a5841fd8984cef7e

commit e93d10da797b71c99742ae99a5841fd8984cef7e
Author: Lutz Justen <ljusten@chromium.org>
Date: Thu Jan 19 20:22:15 2017

authpolicy: Workaround for using Chromium OS registry keys in Chrome builds

Always use Chrome-branded registry keys for now until we find
a better solution.

BUG= chromium:682637 
TEST=Compiles

Change-Id: I847544ead9ae6ca78fc3f98dcd11a1bb227f1712
Reviewed-on: https://chromium-review.googlesource.com/430712
Commit-Ready: Lutz Justen <ljusten@chromium.org>
Tested-by: Lutz Justen <ljusten@chromium.org>
Reviewed-by: Zentaro Kavanagh <zentaro@google.com>

[modify] https://crrev.com/e93d10da797b71c99742ae99a5841fd8984cef7e/authpolicy/policy/policy_encoder_helper.cc

Comment 3 by tnagel@chromium.org, Jan 23 2017

Status: Fixed (was: Started)
This has been fixed in time for M-57.  Tracking the reverse problem in  issue 683920  (for M-58).

Comment 4 by kathrelk...@chromium.org, Jul 6 2017

Status: Verified (was: Fixed)
bulk Verify of older or not-user-facing Chromad bugs
►

Sign in to add a comment