OpenStack Compute (Nova)

Client using sha1 won't be able to authenticate if sha256 is available to the server

Reported by Brendan Maguire on 2011-09-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Low
Brendan Maguire

Bug Description

If SHA256 is available on the server then it is automatically used when nova.auth.Signer generates the signature string. Specifying SHA1 does not return a SHA1 generated string.

Brendan Maguire (b-maguire) wrote :

Will commit fix when https://review.openstack.org/#change,682 is reviewed and merged to avoid conflicts

Changed in nova:
assignee: nobody → Brendan Maguire (b-maguire)
status: New → In Progress
Thierry Carrez (ttx) on 2011-10-21
Changed in nova:
importance: Undecided → Low

Reviewed: https://review.openstack.org/712
Committed: http://github.com/openstack/nova/commit/6183586fab71922675c573ddfd5854a7e1349c3f
Submitter: Jenkins
Branch: master

 status fixcommitted
 done

commit 6183586fab71922675c573ddfd5854a7e1349c3f
Author: Brendan Maguire <email address hidden>
Date: Wed Sep 28 13:10:41 2011 +0100

    Fixes Bug #861293
    nova.auth.signer.Signer now honors the SignatureMethod parameter for
    SHA1 when creating signatures

    Change-Id: I4050407d374d18427f9a955ea98242f7325a5d54

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2011-12-14
Changed in nova:
milestone: none → essex-2
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2012-04-05
Changed in nova:
milestone: essex-2 → 2012.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers