Bug 816148 - GlusterFS should not abuse standard RPC-AUTH-flavour values
Summary: GlusterFS should not abuse standard RPC-AUTH-flavour values
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: protocol
Version: 3.3-beta
Hardware: Unspecified
OS: Unspecified
urgent
medium
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact: Anush Shetty
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2012-04-25 10:57 UTC by Niels de Vos
Modified: 2015-12-01 16:45 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:39:00 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Niels de Vos 2012-04-25 10:57:35 UTC 
Description of problem:
The GlusterFS 330 protocol uses value 6 as AUTH-flavor. This value is officially assigned to RPCSEC_GSS (RFC 5531, page 61).

This is a huge issue for any tools decoding the AUTH-flavor. When GlusterFS uses the AUTH-flavor 6, tools will try to decode this as RPCSEC_GSS. The decoded data will not make sense, but most importantly, any follow-up decoding will fail as a result.

Version-Release number of selected component (if applicable):
Gluster 3.3.x

How reproducible:
Any filesystem operations that require the RPC-AUTH-header.


Some background information was sent to the gluster-devel mailinglist earlier:
- http://lists.nongnu.org/archive/html/gluster-devel/2012-04/msg00118.html
Comment 1 Anand Avati 2012-05-03 21:10:36 UTC 
CHANGE: http://review.gluster.com/3230 (RPC: change the AUTH_GLUSTERFS_v2 value to private range) merged in master by Anand Avati (avati)
Comment 2 Anush Shetty 2012-05-30 14:09:47 UTC 
Verified with 3.3.0qa45
Note You need to log in before you can comment on or make changes to this bug.