Bug 498104 – GSSAPI/SASL security layer - no support for rekeying

Bug 498104 - GSSAPI/SASL security layer - no support for rekeying

Summary:	GSSAPI/SASL security layer - no support for rekeying

Status:	NEW

Aliases:	None

Product:	Red Hat Enterprise MRG
Classification:	Red Hat
Component:	qpid-cpp (Show other bugs)
Sub Component:
Version:	1.1.1
Hardware:	All Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	messaging-bugs
QA Contact:	MRG Quality Engineering
Docs Contact:

URL:
Whiteboard:
Keywords:	Improvement

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2009-04-28 16:58 EDT by Gordon Sim
Modified:	2013-02-24 16:59 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
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.)

Groups: None (edit)

Description Gordon Sim 2009-04-28 16:58:46 EDT

When the GSSAPI security context expires on a running connection (i.e. when
Kerberos ticket expires), communication to the broker on that connection becomes impossible.

To avoid this there would need to be a new sasl exchange introduced to renegotiate a new key before the old one expires. (This is an isue for the AMQP protocol in general).

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