Bug 1242007

Summary: Clock Applet (clock-applet) connecting to external IP on port 80
Product: Red Hat Enterprise Linux 6 Reporter: Ben <bduncan>
Component: gnome-appletsAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.6   
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-06 11:29:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ben 2015-07-10 15:33:51 UTC
Description of problem:

The clock-applet in gnome is connecting to an external IP (this is unwanted behavior). Per the following data:

[root@geo2 ~]# lsof -i :80
COMMAND    PID      USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
clock-app 4733 itsupport   22u  IPv4 1338949      0t0  TCP geo2.ncbp.org:43751->50.58.123.35:http (CLOSE_WAIT)

[root@geo2 ~]# ps -ef|grep -i 4733
501       4733     1  0 11:00 ?        00:00:00 /usr/libexec/clock-applet --oaf-activate-iid=OAFIID:GNOME_ClockApplet_Factory --oaf-ior-fd=34

[root@geo2 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.6 (Santiago)


[root@geo2 ~]# whois 50.58.123.35
[Querying whois.arin.net]
[Redirected to rwhois.twtelecom.net:4321]
[Querying rwhois.twtelecom.net]
[rwhois.twtelecom.net]
%rwhois V-1.5:003AB6:00 rwhois.twtelecom.net (rwhois_ngd v0.9.0 by James Sella)
network:Class-Name:network
network:ID:d5011896-dd7e-11e0-acb1-0015c5e40be3
network:Auth-Area:50.58.0.0/15
network:Network-Name:Akamai-Web-Caching-50-58-123-0
network:IP-Network:50.58.123.0/26
network:Organization;I:91fda446-2450-11dd-9334-0015c5e45005
network:Org-Name:Akamai Web Caching
network:Street-Address:hosts web caching on our network which our customers use
network:City:wdc
network:State:DC
network:Postal-Code:707260000
network:Country-Code:us
network:Phone:none
network:Admin-Contact;I:none
network:Tech-Contact;I:none
network:Abuse-Contact;I:abuse
network:Updated:20110912020903000



Component this file is in:
[root@geo2 ~]# yum whatprovides '*/usr/libexec/clock-applet'
Loaded plugins: product-id, refresh-packagekit, rhnplugin, security, subscription-manager
This system is receiving updates from RHN Classic or RHN Satellite.
rhel-x86_64-server-6/filelists                                                                                                                                            |  37 MB     00:13
rhn-tools-rhel-x86_64-server-6/filelists                                                                                                                                  | 112 kB     00:00
gnome-panel-2.30.2-14.el6.x86_64 : GNOME panel
Repo        : rhel-x86_64-server-6
Matched from:
Filename    : /usr/libexec/clock-applet

gnome-panel-2.30.2-15.el6.x86_64 : GNOME panel
Repo        : rhel-x86_64-server-6
Matched from:
Filename    : /usr/libexec/clock-applet

gnome-panel-2.30.2-5.el6.x86_64 : GNOME panel
Repo        : rhel-x86_64-server-6
Matched from:
Filename    : /usr/libexec/clock-applet

gnome-panel-2.30.2-15.el6.x86_64 : GNOME panel
Repo        : installed
Matched from:
Filename    : /usr/libexec/clock-applet




Version-Release number of selected component (if applicable):
RHEL 6.6
gnome-panel-2.30.2-15.el6.x86_64 : GNOME panel


How reproducible:
100%



1 - Log into the Gnome Desktop 
2 - Set Default TimeZone to:

USA - Boston/New_York

3 - The Clock-Applet will auto configure to pull data on this area and make connections ???

Actual results:
As above

Expected results:
Should NOT make connections to external IPs without permission

Additional info:

Comment 2 Jan Kurik 2017-12-06 11:29:08 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/