Bug 181869

Summary: Error given when duplicate non-updateable key (eg: keyring) added
Product: Red Hat Enterprise Linux 4 Reporter: David Howells <dhowells>
Component: kernelAssignee: David Howells <dhowells>
Status: CLOSED ERRATA QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHSA-2006-0575 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-08-10 22:20:23 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:
Bug Depends On:    
Bug Blocks: 181409    
Attachments:
Description Flags
Patch to replace duplicate non-updateable keys none

Description David Howells 2006-02-17 10:56:16 UTC 
Description of problem: 
 
Addition of duplicate non-updateable keys (such as keyrings) to a keyring 
should displace the old instance of the key but gives EEXIST instead. 
 
Version-Release number of selected component (if applicable): 
 
 
How reproducible: 
 
100% 
 
Steps to Reproduce: 
1. keyctl session - 
2. keyctl newring a @s 
3. keyctl newring a @s 
4. keyctl show 
   
Actual results: 
 
At step 3, the command gives a "File exists" error, and at step 4 you can see 
the keyring created at step 2 attached to the session keyring. 
 
Expected results: 
 
At step 3, the command should work, and should return a new key ID. At step 4 
you should see that the keyring created in step 3 is attached to the session 
keyring, and the keyring from step 2 is nowhere to be seen. 
 
 
Additional info:
Comment 1 David Howells 2006-02-17 10:56:16 UTC 
Created attachment 124805 [details]
Patch to replace duplicate non-updateable keys
Comment 6 Red Hat Bugzilla 2006-08-10 22:20:23 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2006-0575.html