Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1464275 - RHEL7 does not support X11 Security Extension, need to enable xcsecurity
RHEL7 does not support X11 Security Extension, need to enable xcsecurity
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: xorg-x11-server (Show other bugs)
7.3
Unspecified Unspecified
high Severity high
: rc
: ---
Assigned To: Adam Jackson
Desktop QE
:
Depends On:
Blocks: 1420851 1472339
  Show dependency treegraph
 
Reported: 2017-06-22 17:47 EDT by Coby Isley
Modified: 2018-04-10 07:51 EDT (History)
1 user (show)

See Also:
Fixed In Version: xorg-x11-server-1.19.3-12.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-10 07:50:39 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0736 None None None 2018-04-10 07:51 EDT

  None (edit)
Description Coby Isley 2017-06-22 17:47:44 EDT
Description of problem:

Clients querying the X11 server for the SECURITY extension are returned an error.

The X11 server should support the SECURITY extension until a viable alternative exists.

Under RHEL6.5+, customers use the X11 Security Extension to generate authentication tokens for remote clients (xauth generate).  It appears that this capability is no longer available under RHEL7, even though the version of Xorg-server is the same.  Clients that query the X server for the Security Extension are rewarded with an error (both local and remote clients).  It appears that the only available remote client authentication available is via "xhost", which is undesirable for some cuistomers.  

This capability was also left out of early RHEL6 releases, but reinstated as of 6.5 - https://rhn.redhat.com/errata/RHSA-2013-1620.html

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


How reproducible: Every time


Steps to Reproduce:
1. Run # xdpyinfo -display :0 | grep SECURITY
2. For X11 servers that support the SECURITY extension, you will see output for the match.  For RHEL7, there is no match.

Additional info:

bash-4.2$ xdpyinfo|more
name of display:    :0
version number:    11.0
vendor string:    The X.Org Foundation
vendor release number:    11702000
X.Org version: 1.17.2
maximum request size:  16777212 bytes
motion buffer size:  256
bitmap unit, bit order, padding:    32, LSBFirst, 32
image byte order:    LSBFirst
number of supported pixmap formats:    7
supported pixmap formats:
    depth 1, bits_per_pixel 1, scanline_pad 32
    depth 4, bits_per_pixel 8, scanline_pad 32
    depth 8, bits_per_pixel 8, scanline_pad 32
    depth 15, bits_per_pixel 16, scanline_pad 32
    depth 16, bits_per_pixel 16, scanline_pad 32
    depth 24, bits_per_pixel 32, scanline_pad 32
    depth 32, bits_per_pixel 32, scanline_pad 32
keycode range:    minimum 8, maximum 255
focus:  window 0x2600008, revert to Parent
number of extensions:    29
    BIG-REQUESTS
    Composite
    DAMAGE
    DOUBLE-BUFFER
    DPMS
    DRI2
    GLX
    Generic Event Extension
    MIT-SCREEN-SAVER
    MIT-SHM
    NV-CONTROL
    NV-GLX
    Present
    RANDR
    RECORD
    RENDER
    SHAPE
    SYNC
    X-Resource
    XC-MISC
    XFIXES
    XFree86-DGA
    XFree86-VidModeExtension
    XINERAMA
    XINERAMA
    XInputExtension
    XKEYBOARD
    XTEST
    XVideo

The change is in the .spec file

Need to add --enable-xcsecurity
Comment 8 errata-xmlrpc 2018-04-10 07:50:39 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0736

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