Bug 707873

Summary: corosync - Provide better checking of the message type
Product: Red Hat Enterprise Linux 6 Reporter: Jan Friesse <jfriesse>
Component: corosyncAssignee: Jan Friesse <jfriesse>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 6.1CC: cluster-maint, djansa, jkortus, sdake
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: corosync-1.4.0-1.el6 Doc Type: Bug Fix
Doc Text:
Cause A negative value for the message type (on systems where char is signed). his is highly probable if the cluster is, for example, misconfigured to have encryption enabled on some nodes but not others. Consequence Corosync crash Fix Strong check of message type Result Improper message is ignored.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 11:50:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Provide better checking of the message type none

Description Jan Friesse 2011-05-26 08:35:37 UTC 
Created attachment 501019 [details]
Provide better checking of the message type

Description of problem:

A negative value for the message type (on systems where char is signed)
would cause a crash. This is highly probable if the cluster is, for example,
misconfigured to have encryption enabled on some nodes but not others.


Expected results:
No crash
Comment 1 Jan Friesse 2011-05-26 08:36:09 UTC 
In GIT as 7e368581e9e152b5bfc43385645118f183df5d0a
Comment 9 Jan Friesse 2011-10-31 09:29:35 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause
A negative value for the message type (on systems where char is signed). his is highly probable if the cluster is, for example, misconfigured to have encryption enabled on some nodes but not others.

Consequence
Corosync crash

Fix
Strong check of message type

Result
Improper message is ignored.
Comment 10 errata-xmlrpc 2011-12-06 11:50:43 UTC 
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.

http://rhn.redhat.com/errata/RHBA-2011-1515.html