Bug 1030043 - Ads and 3rd party tracking in TLS section of rsyslog documentation
Ads and 3rd party tracking in TLS section of rsyslog documentation
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rsyslog (Show other bugs)
Unspecified Unspecified
high Severity low
: rc
: ---
Assigned To: Tomas Heinrich
Hubert Kario
: Documentation, EasyFix
Depends On: 1030040 1030044
Blocks: 1030041
  Show dependency treegraph
Reported: 2013-11-13 14:19 EST by Filip Krska
Modified: 2014-08-07 13:41 EDT (History)
3 users (show)

See Also:
Fixed In Version: rsyslog-7.4.7-1.el7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1030040
Last Closed: 2014-08-07 13:41:57 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Filip Krska 2013-11-13 14:19:13 EST
+++ This bug was initially created as a clone of Bug #1030040 +++

Description of problem:

There are unsolicited ads loaded from 3rd party servers (implies unsolicited and unexpected tracking by the 3rd party, so privacy concerns may apply) via following markup:

<span style="float: left">
<script type="text/javascript"><!--
google_ad_client = "pub-3204610807458280";
/* rsyslog doc inline */
google_ad_slot = "5958614527";
google_ad_width = 125;
google_ad_height = 125;
<script type="text/javascript"

in following doc pages:


Version-Release number of selected component (if applicable):

All versions (RHEL 5,6,7, latest Fedora affected)

How reproducible:


Steps to Reproduce:
1. browse e.g. file:///usr/share/doc/rsyslog-5.8.10/rsyslog_secure_tls.html with web browser

Actual results:

Ads are loaded from http://pagead2.googlesyndication.com

Expected results:

No http request to 3rd party site is performed, no ads displayed when browsing local docs

Additional info:
Comment 6 Hubert Kario 2014-08-07 13:41:57 EDT
Issue fixed in currently released package versions.

Note You need to log in before you can comment on or make changes to this bug.