New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 633595 link

Starred by 5 users
Status: Untriaged
Owner: ----
Cc:
█ jayhlee@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature



Sign in to add a comment

FR: Remove obsolete hosts from crosh/network_diag --hosts command

Reported by yyefet@chromium.org, Aug 2 2016 
Version: all
OS: ChromeOS

Enterprise admins whitelist certain hosts in their proxy as per our published guidelines:
https://support.google.com/supportu/answer/2657319?hl=en

There has been an approved proposal to remove the following obsolete hosts from the list:

1) cros-omahaproxy.appspot.com
2) omahaproxy.appspot.com
3) dl-ssl.google.com
4) pack.google.com

This is an FR to remove the same hosts from crosh/network_diag --hosts command
Project Member

Comment 1 by bugdroid1@chromium.org, Sep 2 2016 

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

commit 697a1d8b9fdb1f05dc172d83a25587f2aaaf0228
Author: Yehuda Yefet <yyefet@chromium.org>
Date: Tue Aug 02 16:19:06 2016

crosh: remove obsolete hosts from crosh/network_diag --hosts

Remove obsolete hosts from crosh/network_diag --hosts cmd:
- cros-omahaproxy.appspot.com
- omahaproxy.appspot.com
- dl-ssl.googel.com
- pack.google.com

BUG=chromium:633595
TEST=ran network_diag --hosts in VM

Change-Id: Ifcf995d1650bba8635a0312e886da7c5f7517daf
Reviewed-on: https://chromium-review.googlesource.com/365191
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Yehuda Yefet <yyefet@google.com>
Reviewed-by: Yehuda Yefet <yyefet@google.com>
Reviewed-by: Alex Deymo <deymo@google.com>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/697a1d8b9fdb1f05dc172d83a25587f2aaaf0228/crosh/network_diag

Comment 2 by xiy...@chromium.org, Jul 27

Components: OS>Systems>Network

Comment 3 by jayhlee@google.com, Jul 27 

Is there some history on this change and adding an additional help article? We definitely need work to better doc hostname requirements and I appreciate effort but I'm not sure a 2nd article clarifies or further confuses the situation for our cusotmers.

Comment 4 by jayhlee@google.com, Jul 27

Cc: -royans@chromium.org jayhlee@chromium.org

Comment 5 by marcuskoehler@chromium.org, Jan 15

Labels: Enterprise-Triaged
►

Sign in to add a comment