Bug 137612 - Kerberos 5 1.2 does not include support for the RC4 cipher.
Summary: Kerberos 5 1.2 does not include support for the RC4 cipher.
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: krb5 (Show other bugs)
(Show other bugs)
Version: 3.0
Hardware: All Linux
medium
high
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: 114938 122008
TreeView+ depends on / blocked
 
Reported: 2004-10-29 19:22 UTC by Nalin Dahyabhai
Modified: 2012-06-20 13:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 13:23:27 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Nalin Dahyabhai 2004-10-29 19:22:57 UTC 
Description of problem:
Kerberos 5 1.2 does not include support for the RC4 cipher.  This
triggers errors if a client attempts to exchange signed or encrypted
data with an application server using an RC4 session key.

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

How reproducible:
Always.

Additional info:
Proper RC4 support also requires support for the RC4 string-to-key
algorithm and GSSAPI message formats.
The type of the session key is selected by the KDC while responding to
a KRB_TGS_REQ request from the client, and is usually RC4 for services
running on Windows hosts.
Comment 2 Jiri Pallich 2012-06-20 13:23:27 UTC 
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.
Note You need to log in before you can comment on or make changes to this bug.