Bug 787669 - print more informative message to qemu log when client provides wrong password
Summary: print more informative message to qemu log when client provides wrong password
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: spice-server
Version: 6.3
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: 6.3
Assignee: Uri Lublin
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-06 13:23 UTC by David Jaša
Modified: 2012-06-20 12:17 UTC (History)
5 users (show)

Fixed In Version: spice-server-0.10.1-4.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 12:17:03 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 RHBA-2012:0765 0 normal SHIPPED_LIVE spice-server bug fix and enhancement update 2012-06-19 19:30:21 UTC

Description David Jaša 2012-02-06 13:23:24 UTC 
Description of problem:
SSIA

Version-Release number of selected component (if applicable):
spice-server-0.10.1-1.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. run /usr/libexec/qemu-kvm -spice port=<port>,password=<password>
2. in different terminal, run spicec -h <host> -p <port> -w <password>
3.
  
Actual results:
qemu-kvm prints to the console:
reds_handle_read_link_done: Peer doesn't support AUTH selection

Expected results:
qemu-kvm prints something like this:
reds_handle_read_link_done: connection refused: wrong password by client <ip>

Additional info:
Comment 1 Christophe Fergeau 2012-03-02 16:02:28 UTC 
Patch for this sent upstream
Comment 6 David Jaša 2012-04-16 12:40:55 UTC 
spice-server-0.10.1-5.el6.x86_64 prints:

reds_handle_auth_mechanism: Auth method: 1
reds_handle_ticket: Invalid password

--> can be moved to VERIFIED
Comment 9 errata-xmlrpc 2012-06-20 12:17:03 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/RHBA-2012-0765.html
Note You need to log in before you can comment on or make changes to this bug.