Bug 798283 - Remove trust store file, when spice client quits
Summary: Remove trust store file, when spice client quits
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: spice-xpi
Version: 6.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Peter Hatina
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-28 14:26 UTC by Peter Hatina
Modified: 2016-06-01 01:31 UTC (History)
6 users (show)

Fixed In Version: spice-xpi-2.7-8.el6
Doc Type: Bug Fix
Doc Text:
No documentation needed.
Clone Of:
Environment:
Last Closed: 2012-06-20 14:48:29 UTC
Target Upstream Version:

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


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2012:0956 0 normal SHIPPED_LIVE spice-xpi enhancement update 2012-06-19 21:12:18 UTC

Description Peter Hatina 2012-02-28 14:26:13 UTC 
Description of problem:
Spice-xpi should remove trust store file, when spice client exits.

Version-Release number of selected component (if applicable):
spice-xpi-2.7-7.el6.x86_64.rpm

How reproducible:
Always

Steps to Reproduce:
1. connect to VM in userportal
2. close client
3. there is a file remaining in /tmp/truststore.pem-*
  
Actual results:
the trust store file exists

Expected results:
the trust store file should be removed

Additional info:
Comment 3 Peter Hatina 2012-02-28 15:03:07 UTC 
Fixed.
Comment 6 Bill Sanford 2012-03-13 14:23:10 UTC 
Tested with spice-xpi-2.7-14.el6.x86_64 and it works.
Comment 7 Christophe Fergeau 2012-05-02 08:23:03 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:
No documentation needed.
Comment 9 errata-xmlrpc 2012-06-20 14:48:29 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/RHEA-2012-0956.html
Note You need to log in before you can comment on or make changes to this bug.